> Comparing today's internet to the 90s is hardly fair. It has become extremely predatory...
I think you're missing the point they're trying to make. It's not that the problem isn't real, it's that the solution won't work. Kids will find a way around. They have a lot more free time than us.
Physical is different from digital. Sure, today many kids don't know or care about VMs, but they certainly will know and care tomorrow when this regulation hits. And that info will spread like wildfire all over social and blog posts.
About a week after the policy goes live it won't just be the geeks that know, it'll be everyone in the 4th grade.
Modern languages come with lots of interesting features like better dev ex, null safety, etc.
Js is a fine language, but there are other languages that bring unique advantages, the web shouldn't block developers from using better tools.
The web is best off when developers have freedom.
Basically, it's sugar for `package` and `world` in the case where you aren't actually defining a world for others to use, and just for your own use. In such a case, the package and world names are irrelevant anyway.
Mostly because I want insight and control at a lower level, which breaks down into two different use-cases:
1. Debugging. The nature of bugs in this space is a lot more of "it doesn't look right on the screen" as opposed to "it breaks compilation", so I want to easily do things like peek into my buffers, use native js logging, etc. It's just a lot easier for me to reason about when I have more manual control.
2. Leaky abstractions. wgpu is a pretty low-level but it can't avoid the pain that comes with different backends, async where it should it shouldn't be, features that aren't available everywhere, etc.
That said, it would probably be pretty straightforward to convert the renderer into wgpu, most of the data structures and concepts should map cleanly
Yeah, I split the crates so `renderer-core` deals with the web-sys part, `renderer` is pretty much plain Rust (and wgsl with Askama templates)
I prefer this for 100% browser-only, but that's a niche. I do think wgpu makes more sense when you like the WebGPU headspace but want to target other backends (native, mobile, VR, etc.)
The quality of games on Google Play is much worse than what is available on Steam and the variety of titles are much greater on Valve's platform too, with far less in the way of microtransactions and other exploitative behaviours (though Steam isn't free of this) and a back catalogue stretching as far back to the mid 2000s.
Both Microsoft and Sony AAA titles, most third parties publish there and most indie games release there first. Steam's library is unparalleled in the industry, the only thing it's truly missing is Nintendo's games.
Ok, but the market is absolutely flooded with exploitative stuff, laden with micro transactions and a trickle of miniscule rewards, in attempt to addict the user, rather than genuinely provide enjoyment.
How do you even discover the good games that are worth being played on Android?
I think you're missing the point they're trying to make. It's not that the problem isn't real, it's that the solution won't work. Kids will find a way around. They have a lot more free time than us.
reply