Based on how much imported libraries are relied upon, it makes sense to treat everything as untrusted. Unless you write every line yourself/in-house, code should be considered untrusted.
I would be curious which attack vectors change or become safe after compiling though.
The point of the js engine sandbox is to protect the user in the browser - it's completely redundant on the server. Supply chain attacks are real, but only Deno has tried to fix that through permissions/rules.
I don't think anything changes with compile to native on the server.
Totally disagree. A spec-compliant JS engine has to support the features that allow vulnerabilities like prototype pollution, which can be exploited through user input alone.
I generally agree, but the company likely doesn't have those funds. Considering the largest player (Apple) stands to make way more from it than you and just works around your patent.
Not arguing Apple shouldn't poach, just that your suggestion doesn't work.
This feels like a bug that he snuck through early or during a temporary window, before Google started defaulting to . as an ignored alias. Maybe not ¯\_(ツ)_/¯
I had pretty much the exact same experience with Game Maker too. In retrospect, feels like a very powerful pedagogical tool. Even when I wasn't really trying to "learn coding" but rather I just wanted to make some games, I ended up learning to code
The fact that _most_ things could be done with drag-and-drop, but for some features you had to drop down to scripting, served as a really nice and gentle stepping stone to writing code.
I did the same gradual move, and I can remember being excited to get home from school because I might have solved some problem by letting it tick over in my head.
But I do remember thinking GML was amazing (it was fugly, kid), and struggling with C, because the language was so different. (These days, leap to love2D and Lua instead).
Just the idea of multiple languages was so foreign and impossible to me. Writing a raycaster in GML was possible, writing an event loop in C was insane... And these days picking up a language tutorial for something new is a hobby.
It is likely that new models had higher costs, including maintainers becoming familiar. Long-term, electric is unquestionably cheaper to fuel and maintain, assuming they are built to the same standards and scale as outgoing diesel models
We are already on the path to have the grid converted to majority green energy over the next decade. Solar is by far the largest of New deployments and growing annually.
Grid batteries are just starting to scale up.
These are cheaper than any other option by far, with the shortest payback period.
If you are traveling and need to deal with something that happens at home, too bad. There are plenty of timezones that make it quite difficult to manage, especially if they have phone wait times that exceed 30min.
I would be curious which attack vectors change or become safe after compiling though.