Today we are looking at the game engine/framework combo WebGLStudio, an entirely browser based game engine with a complete visual editor.

Key features of WebGLStudio include:

• A full 3D graphics engine (LiteScene.js) that supports multiple lights, shadowmaps, realtime reflections, custom materials, postFX, skinning, animation, and much more.
• An easily extended, component-based system for controlling the rendering pipeline and interaction event hooks
• An easy to use, what you see is what you get (WYSIWYG) editor that provides a single interface for all coding, graph compositing and timeline features.
• A graph editor for controlling behaviours, shaders and post-processing effects, using LiteGraph.js.
• Supports the LiteFileSystem.js, a virtual file system that allows drag-and-drop storage of resources on the web, with configurable quotas, users and shared folders.
• Export and share your work by sending a single link.

The entire technology stack behind WebGLStudio is open source under the MIT license and available on GitHub.  You can learn more about WebGLStudio in the video below.

GameDev News Engine HTML5 JavaScript

A new video from popular YouTube channel “The Slow Mo Guys” gets up close with Apple Watch’s water lock feature, which plays a series of tones to expel liquid from the device chassis and away from its speaker.

In recent months, we’ve worked closely with political campaigns and parties who are protected by our AccountGuard threat notification service and conducted hundreds of security trainings ahead of the 2020 elections. We’ve heard one repeated request throughout these engagements: Those involved in the democratic process want more protection for what we call identity management, or the ability for their staff to securely log into their accounts and access their email and files while preventing unwanted intrusions. Greater security in this area would help prevent the “hack-and-leak” scenario where cybercriminals or foreign governments steal a campaign official’s emails and release them online.

Starting today, we’re bringing Microsoft’s enterprise-grade identity and access management protections to AccountGuard members in the U.S. at no cost to further help secure them ahead of the 2020 elections. We’re also announcing a new partnership with Yubico to provide phishing-resistant security keys to AccountGuard customers. For political campaigns and committees, these services will be offered through Defending Digital Campaigns, a non-profit and non-partisan organization that has been authorized by the Federal Elections Commission to provide campaigns with free or low-cost technology from a variety of companies. Our Defending Democracy Program will also work directly with democracy-focused non-profit organizations and think tanks enrolled in AccountGuard to help them use these protections.

There are a range of identity and access management protections we’ll offer as part of this, but five examples, which we believe are protections that benefit all campaigns, include:

Multi-factor authentication: While all Microsoft business and consumer email services support multi-factor authentication, what we’re announcing today contains extra protection against phishing for those using this important feature. Customers can now use the Authenticator app on their phones or hardware keys from Yubico as another factor for identity protection.

Single sign-on: This feature enables one set of credentials to be used securely across hundreds of cloud apps, making it easier for a staffer or campaign official to access the apps they need with a high level of security but also more quickly and easily.

Conditional access policies: This is the ability for a campaign to help ensure only the right people are logging into their network by setting conditions such as the behavior people can use to navigate to their accounts, where they are physically located, what kinds of devices they might be using and what applications they might be using.

Privileged identity management (PIM): This includes security features enabling campaigns to manage, control and monitor access to important resources in the organization. PIM will provide time-based and approval-based authorization to access certain resources and lessen the risk of excessive, unnecessary and misused access permissions to sensitive resources.

Access governance: Campaigns have vendors, staffers and volunteers who come and go, and this set of features helps automatically terminate access when they depart an organization or complete a project, shrinking the number of entry points for a hacker.

Our new partnership with Yubico, the recognized industry leader in physical security keys, will provide YubiKeys to AccountGuard customers for defense against phishing and other cyberattacks. Yubico will provide 10 YubiKey 5 Series security keys, to be used on compatible computers or phones, to any AccountGuard-covered organizations for free, for a limited time, plus up to an additional 40 keys at a 50% discount.

We know that many political campaigns do not have dedicated IT support staff, and today’s news comes with hands-on help for those that need it. Deployment assistance for the technologies in today’s news will be provided to AccountGuard customers as an included benefit through our FastTrack program or through our FastTrack-ready partners. A dedicated team of deployment engineers will be available to help provide remote assistance and guidance, and Microsoft partner Patriot Consulting Technology Group will offer additional onboarding support, integration and trainings.

Any AccountGuard-eligible customer can learn more about enrolling in AccountGuard or taking advantage of the tools announced today by contacting AccountGuard@microsoft.com. While we’re offering this to U.S.-based AccountGuard customers ahead of the 2020 U.S. election, we will explore offering it in other geographies in the future.

Tags: cyberattacks, cybersecurity, elections, Microsoft AccountGuard, multi-factor authentication, phishing, Privacy and Security

In the wake of Pokémon’s astonishing success in Japan in 1996, many other developers attempted to ape the formula with their own RPG-style adventures. One of the more memorable was Imagineer’s Medabot (or “Medarot” as it’s known in Japan) series, which spawned a manga and anime and was focused on the construction of fighting robots. With the exception of Medarot Perfect Edition on the Bandai WonderSwan, all games in the series have been exclusive to Nintendo consoles.

Imagineer has announced that it is bringing together eight classic Game Boy, Game Boy Color and Game Boy Advance titles from the series to the Nintendo Switch as part of the Medarot Classics Plus collection – and, just like the original game, this pack will be released in two flavours: Kabuto and Kuwagata.

The collection arrives on November 12th in Japan and will cost 4980 yen, plus tax. A special edition will also be available that includes both versions, memorial plates based on the box artwork and three soundtrack CDs. This version will cost 15180 yen.

While the series scored some minor success with western players back in the day, there’s currently no indication that Medarot Classics Plus will be launched outside of Japan, but if this changes will we let you know.

If you’re like me, you may have asked yourself the following question:

Why is it string.join(list) instead of list.join(string) in Python?

The join method works with any iterable, not just with lists. Therefore, you’d have to implement it in hundreds of classes instead of just one (in the string class). Additionally, join() works only on a string delimiter and with an iterable of strings. Thus, it’s specific to strings and shouldn’t be allowed to be applied on, say, a list of integers.

Let’s divide the world into REALITY and FANTASY.

REALITY: You probably know the string.join(list) method in Python to concatenate all strings in the list using string as a delimiter:

# REALITY:

lst = ['a', 'b', 'c']

print('-'.join(lst))

# a-b-c

FANTASY: Many coders find this confusing, wouldn’t it be more intuitive to use list.join(string) rather than string.join(list)?

# FANTASY WORLD:

lst = ['a', 'b', 'c']

print(lst.join('-'))

# a-b-c

This option of joining a list to a string would feel more object-oriented: you want to join the list and not the string, after all!

So, what are the thought processes behind Python’s creators? Why did they decide to create a join() method on the string rather than the list type?

In this article, I’ve compiled the pro and con arguments from various sources. You can find a detailed list of the sources below.

Argument 1: One Method to Join ‘Em All

You can join any iterable such as a list, tuple, dictionary, or set. But the delimiter must be a string. Thus, you have two options:

• Require that each iterable implements its own join method (such as __str__).
• Implement only one join method that works on each iterable.

The latter is far less work for the language creators, and less confusing for the programmer.

# FANTASY WORLD:

['a', 'b', 'c'].join('-')

('a', 'b', 'c').join('-')

{'a', 'b', 'c'}.join('-')

...

# a-b-c

In the fantasy world, you have many implementations of basically the same method.

# FANTASY WORLD:

['a', 'b', 'c'].join('-')

('a', 'b', 'c').join('-')

{'a', 'b', 'c'}.join('-')

...

# a-b-c

This would be confusing as every single iterable must implement the same method. Either there would be a lot of redundant code, or the method must be implemented on the iterable object which leads us to the next argument:

Argument 2: Explicit is Better Than Implicit

If you type into your Python shell the two words import this, it’ll print the “Zen of Python”:

The Zen of Python, by Tim Peters

Beautiful is better than ugly.

Explicit is better than implicit.

...

Go ahead and try it yourself, I’ll wait:

The join() method can only join iterables if they contain strings:

lst = [1, 'b', 'c']

print('-'.join(lst))

# TypeError: sequence item 0: expected str instance, int found

Python will throw a TypeError, if you try to join an iterable that contains at least one non-string element.

Say, we live in FANTASY WORLD and the iterable type implements a join method that’s valid (among others) for all container types such as lists. This would be the only alternative that makes sense and doesn’t add lots of redundant code to the Python library.

This would mean that all iterables containing arbitrary elements could be joined to a string! Even if the elements in the iterable are not of type string. Even if they are absurd data types you created just to confuse Python.

You may ask: so what? But the problem is that Python would have to use an implicit string conversion scheme in case the objects are not of type string. The default string representation is often unreadable or not suitable to appear in a concatenation. Surely, this would add lots and lots of confusion.

For example: what does it, semantically, mean to join a list of integers? Adding them? Concatenating the string representations? Averaging them? There’s no clear answer and any implicit choice would lead to confusion. Explicit is better than implicit!

Note: There’s another problem with implementing a join method on the iterable level! The iterable is not a type but an interface for any type that defines an __iter__ method. Thus, it comes back to requiring all iterables to implement their custom join which is complicated and messy.

Argument 3: Unexpected Dependency of Iterables From String and Unicode

Using list.join() was actually proposed by Skip Montanaro, one of Python’s creators:

On Fri, 11 Jun 1999, Skip Montanaro wrote: It occurred to me just a few minutes after sending my previous message that

it might make sense to make string.join a method for lists and tuples.

They'd obviously have to make the same type checks that string.join does.

as in:

['spam!', 'eggs!'].join() 'spam! eggs!'

?

But David replied that he didn’t like the implications from the generalization of join(): the reduce() function:

I like the notion, but I think it would naturally migrate towards

genericity, at which point it might be called "reduce", so that: ['spam!', 'eggs!'].reduce() 'spam!eggs!' ['spam!', 'eggs!'].reduce(' ') 'spam! eggs!' [1,2,3].reduce()

6 # 1 + 2 + 3 [1,2,3].reduce(10)

26 # 1 + 10 + 2 + 10 + 3 note that string.join(foo) == foo.reduce(' ')

and string.join(foo, '') == foo.reduce()

--david

You can see that this leads to unclear semantics if you have a list of integers. Do we reduce a list of integers by summing them up or concatenating them? What if you pass the value 10 as a separator?

Guido, Python’s benevolent dictator for life, replied (highlights by me):

>>> On Fri, 11 Jun 1999, Skip Montanaro wrote:

>>> It occurred to me just a few minutes after sending my previous message that

>>> it might make sense to make string.join a method for lists and tuples.

>>> They'd obviously have to make the same type checks that string.join does.

>>> as in:

>>> ['spam!', 'eggs!'].join()

>>> 'spam! eggs!' Note that this is not as powerful as string.join(); the latter works

on any sequence, not just on lists and tuples. (Though that may not

be a big deal.) I also find it slightly objectionable that this is a general list

method but only works if the list contains only strings; Dave Ascher's

generalization to reduce() is cute but strikes me are more general

than useful, and the name will forever present a mystery to most

newcomers. Perhaps join() ought to be a built-in function?

--Guido van Rossum (home page: http://www.python.org/~guido/)

To summarize this conversation, Guido had two counter arguments:

• The join() method works on all iterables and not only on lists and tuples.
• The method must be a general list method but works only if the list contains strings.

The final note is interesting though: join() could have been built-in function, too!

Where to Go From Here?

Enough theory, let’s get some practice!

To become successful in coding, you need to get out there and solve real problems for real people. That’s how you can become a six-figure earner easily. And that’s how you polish the skills you really need in practice. After all, what’s the use of learning theory that nobody ever needs?

Practice projects is how you sharpen your saw in coding!

Do you want to become a code master by focusing on practical code projects that actually earn you money and solve problems for people?

Then become a Python freelance developer! It’s the best way of approaching the task of improving your Python skills—even if you are a complete beginner.

Join my free webinar “How to Build Your High-Income Skill Python” and watch how I grew my coding business online and how you can, too—from the comfort of your own home.

Join the free webinar now!

Sources

I combined web resources, email communications, and my own thoughts to write this comprehensive guide. I’m confident that the tutorial covers the real sources—but we’ll never know for 100%, don’t we?

1. https://stackoverflow.com/questions/493819/why-is-it-string-joinlist-instead-of-list-joinstring
2. https://www.edureka.co/community/3899/python-join-why-is-string-join-list-instead-list-join-string
3. https://www.edureka.co/community/12487/python-join-why-is-string-join-list-instead-list-join-string
4. https://intellipaat.com/community/225/python-join-why-is-it-string-join-list-instead-of-list-join-string
5. https://www.wyzant.com/resources/answers/689501/python-join-why-is-it-string-join-list-instead-of-list-join-string
6. https://www.quora.com/Why-is-it-string-join-list-instead-of-list-join-string
7. https://mail.python.org/pipermail/python-dev/1999-June/095366.html

Today’s sunny morning in Seattle brightened even further with the good news from the United States Supreme Court that restores legal protection for nearly 700,000 Dreamers, including more than 60 Microsoft employees. It was on their behalf that, in 2017, Microsoft filed a lawsuit with Princeton University and a Princeton student, Maria Perales Sanchez, to object to the rescission of the Deferred Action for Childhood Arrivals program, or DACA. We acted quickly because we saw firsthand this issue’s importance to the nation’s talented Dreamers and DACA’s critical benefits for every part of the American economy.   

Little did we know in 2017 that this case would bring Microsoft to the steps of the Supreme Court for the fifth time in a little more than a decade. This has been a good week at the Supreme Court for the rights of people who live in the United States. As a company that has brought a wide range of important issues before the court, we constantly appreciate the hard work that takes place within its four walls. Today’s decision marks an important milestone, and we’re gratified that the court once again has provided a thoughtful and fair outcome to a complicated legal issue. 

We also appreciate that today’s decision, while critical, is but one more step in a long and winding road. The DACA debate will continue, and the big question now is what comes next. 

Our plea is for a national discussion that involves more light and less heat. A path that starts with a recognition of the Dreamers’ collective importance to our country. A conversation that brings people together in a bipartisan spirit in a creative search for common ground. A discussion that encourages the White House and Congress to work together. An approach that gives people the time and space to be thoughtful. A route that avoids precipitating another crisis in a year that has already had more than its share. 

Some may suggest that this path sounds more like a dream itself. But it’s what the nation and our economy need. 

Consider this: While Microsoft was the only company in the country to file a lawsuit to contest DACA’s rescission, when the case reached the Supreme Court, we were no longer alone. By last year, 145 businesses signed amicus briefs supporting DACA. And the business community was joined by an even broader group that included 210 educational institutions, 129 religious organizations and 109 municipalities. All of us stood together to underscore the Dreamers’ talent and importance to the economy and the country. 

And that was before anyone had heard of COVID-19. 

The past few months have provided even more dramatic evidence of the role that DACA registrants play in our country. More than 30,000 of them work in the healthcare space alone. They are nurses, lab technicians and respiratory therapists who serve Americans from all backgrounds as our country responds to a pandemic that is unique in our lifetimes. Another 200,000 Dreamers provide other essential services, working in pharmacies and grocery stores and delivering vital goods to our front doors. In the middle of a pandemic, any step that puts Dreamers at risk can put all of us at risk. 

We filed this lawsuit because we believed at Microsoft that it was important to stand up for our employees. To make clear that we had their backs. But along the way, we’ve come to appreciate even more clearly how important the Dreamers are for all of us.  

The summer of 2020 comes in a year of crisis, but it provides a potential inflection point for the nation’s future. As we’ve seen in recent weeks, it’s a time to reflect on and recommit ourselves to racial equity and justice, especially for the country’s African American and Black populations. It’s a time that calls for thoughtful action to protect the rights of people in a fair manner. It’s a discussion that needs to bring people together, while making room for the nation’s Dreamers. 

Tags: DACA, Dreamer, Immigration, SCOTUS

Quality is more important than quantity in most walks of life, but the sheer quantity of games available for Switch is still a source of wonder for veteran Nintendo fans who remember the slim libraries of consoles past. Back in the Wii days Nintendo Life committed to reviewing every WiiWare game released, but keeping up with every single Switch release was a task that quickly overwhelmed us, despite our best intentions.

It’s certainly a fantastic problem to have, although it inevitably means great games slip through the net, and Switch has a trove of hidden gems that–for once–actually warrant that label.

A little while ago we asked you to suggest some games that we’d missed, and as a result we took a look at Wandersong, Anodyne, Songbird Symphony and Never Stop Sneakin’. However, there are still plenty of games available on the Switch eShop that will likely remain hidden unless we stumble on them in an eShop sale – and those can be overwhelming in their own right!

With that in mind, we’re asking Nintendo Life readers to send us their thoughts on Switch games they’ve enjoyed which flew under the radar. We’ll read them all and choose our favourites for a feature (or perhaps a series of features, depending on your response) showcasing games that we haven’t been able to review, but that the Nintendo Life community feels warrant some love and attention.

There’s no prize for having your entry selected, beyond seeing your words highlighted in an article of Switch games, of course. Here are some submission instructions and guidelines if you’d like your recommendation to be considered:

Submission guidelines

• 100-word limit – Keep it brief! A history of the genre and deep-dive into every mechanic is unnecessary. Concentrate on what the game is about, what sets it apart from other games and why you enjoyed it.
• One entry per game – Feel free to send your thoughts on multiple games, but there’s no need to duplicate.
• Choose only games that we haven’t reviewed on the site – To check if a Nintendo Life review exists, simply type the name of the game into the search box at the very top of the page (look for the magnifying glass icon in the top left corner) and click on the game page that appears. If there’s no review, you’re good to go!

How to send a recommendation

• Head to Nintendo Life’s Contact page and select the subject “Switch eShop Hidden Gems” from the drop down menu (it’s already done for you in the link above). Type your name, email and beautifully-crafted message into the appropriate box, hit send and Bob’s your uncle!

Hopefully, with your help, we’ll be able to highlight some quality games on the Switch eShop that passed us by for whatever reason. If you’ve got any questions on the format, feel free to drop them in the comments section below. If you don’t feel comfortable writing a recommendation, why not nominate games you’d like to see highlighted below?

We look forward to seeing what games you recommend.