Readit Newskernel's code is terrible mess by java/c# web app standards (dependency injection, interfaces, mockability, testability, etc)
Even C#'s compiler code written in C# is below architect's dream web app code base full of DDD, various patterns, CQRS, Event Sourcing yada yada
“All the best hackers, all the best phreakers in the world, we don’t know who they are because they never got arrested. And they never went to prison. This is why you don’t know who the best ones in the world are. This is the truth. Think about it.”
then probably yea, but when it comes to skills?
I'd say that they're not really that unknown - https://ctftime.org/
- Plugins for desktop/mobile apps, wasm provides a nicely sandboxed environment for them.
- Gaming, the combination of WASM and WebGPU will be the perfect platform for cross platform game development. I could see Steam, for example, creating their own runtime.
- Embedded electronics, simplifying the development and deployment of IoT devices.
When it comes to wasm on the server, it’s often talked about as targeting the “edge”. I believe this the next area of massive growth, however the part that I don’t think is fully solved yet is on the database side. If your server app is making multiple database calls from the edge to a central db there is a good chance that it will slower than a traditional (single location) deployment.
What’s needed is a edge first database, we need at least read replicas to be at the edge with your app. Fly.io have something like this with their Postgres’s product. The alternative is to use an eventually consistent db such as CouchBD, but that causes other problems. I’m interested to see if CloudFlare do anything in this area as it’s the part of their stack that’s missing.
Lua, JS and LLV IRM?
If former, what other ways you've adapted for essential stuff that need a smart device.
If later, do you ever plan on getting a smartphone again ?
but the only things that make me really, really strongly consider getting smartphone is some form of Maps - let it be Google or something
and ability to send&receive pictures (MMS suck)
It's definitely possible to live with dumb phone, but stuff like maps, sending pictures and maybe access to email are sometimes incredibly handy
I'd argue it's not cheaper overall, just for the company choosing to do the development.
What I mean is, the lost productivity of waiting around for slack to load a channel is essentially outsourcing this cost difference via poor performance.
What makes you think that Slack's loading times is due to Electron, not shitty backend?
This is genuine question
I feel like Microsoft's approach is to create a framework for everything and hope it sticks - though they appear to repeatedly fail. Nobody really used Xamarin. Nobody is using Blazor.
This very minimal documentation of Maui doesn't really scream confidence in their own product, either. I predict this one will die as well.
Hmm, I don't think this is true.
Also this is kind of different beast - WASM has some limitations that need to be overcome
I agree with you, but luckily, it's not inferior!
Google Maps performance seems to be way worse
I do wonder how's the WASM performance
as trying to write it yourself
and then reading about how other people do it e.g VS Code blog
https://code.visualstudio.com/blogs/2018/03/23/text-buffer-r...
That's fair, but just take a look at how complex latest biggest hacks are like
https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-i...