Young Coder

A big part of the problem, I think, is that tools that make it easy have been deemed uncool and as a result are half-heartedly supported by Microsoft, such as Visual Basic and MS-Access. Lack of vendor support has killed or hampered other easy-to-use development software that might otherwise find widespread use, including BASIC (classic and VBA; Microsoft, Apple), HyperCard (Apple), and AppInventor (Google). My two cents. :-) Microsoft Plots the End of Visual Basic https://www.thurrott.com/dev/232268/microsoft-plots-the-end-of-visual-… Microsoft Access: The Database Software That Won’t Die https://medium.com/young-coder/microsoft-access-the-zombie-database-so…

The amount of energy Microsoft is pouring into these front-end efforts is pretty incredible. A more recent development that has me very excited is Blazor Desktop: https://medium.com/young-coder/blazor-desktop-the-electron-for-net-ecd… > This leads to the second difference — in a Blazor Desktop app hosted in WebWindow, there’s no built-in web server. Instead, it’s pure .NET all the way down. And while we haven’t seen exactly how this will be implemented, it offers the chance to simplify the hosting model quite a bit. If everything comes together just right, it will be like using Electron without needing to learn Node. I honestly believe this model is going to revolutionize front-end development. The productivity uplift of not having to fuck around with JSON APIs alone is worth the price of admission. We already use Blazor (server-side) for several of our webapps. I have been able to implement things in 4 hours that would easily have taken 4 weeks if I had to argue with other developers about the shape of a JSON blob on the wire. Need a projection involving 3 collections to produce a table? No problem. It's literally 3-5 lines of LINQ in your razor file. With a "proper" JSON API, you would probably have to fetch 3 different resources to the client or develop a special unicorn method for each unique projection.

Coming from C and having used thread and being totally ignorant to javascript, this article really helped me grasp async in js by clearing away implicit misconceptions I held : https://medium.com/young-coder/5-misconceptions-about-asynchronous-cod… And also that talk on the event loop : https://www.youtube.com/watch?v=cCOL7MC4Pl0

Applications like you’re describing should consider less DOM and more Canvas API. The apps aren’t documents. They’re more like video games. DOM manipulation and rendering usually degrades performance more than the JavaScript. One essay on this topic… https://medium.com/young-coder/the-future-web-will-canvas-rendering-re…

There is also a blog called "Techless Teaching": https://medium.com/young-coder/techlessteaching/home

This article about how Microsoft Access won't die got me thinking about creating an open source alternative. I just retired and am looking for a project. I also have a history with msft that might be helpful. https://medium.com/young-coder/microsoft-access-the-zombie-database-so…

I'm not sure how well browsers on MacOS utilizes cores, or if there is an artificial restriction there. At the very least it will have a separate thread for each tab. Though, if I'm not mistaken, I do believe that Web Workers is supported on all major browsers, including Safari. This allows the main JS thread (the one per tab) to spin up additional separate threads for other workloads. This page seems to confirm this: https://caniuse.com/webworkers Here is an example to try out: https://codepen.io/prosetech/embed/qeqGQR? (source: [1]). When I tried it in chrome (default settings on linux) with a search range of 1 to 5,000,000, it took roughly 16 seconds and overall CPU usage was around 12%. Feel free to try it on an M1 (I'm genuinely curious, since comparable benchmarks are really hard to come by). This doesn't use the GPU at all, and is already CPU resource restricted, so I would expect it to fare well. I'm sure the browser will handle some scheduling to limit 100% usage regardless of what the OS allows it. So, it is I said before. That it seems a bit dishonest to exclusively focus on single core performance, as if that matters more than what the CPU can do when fully utilized. And, when fully utilized, the M1 is not remarkable in the slightest. It was a seriously misleading and dishonest marketing campaign. The only exception is, power consumption, which is pretty good. I find the idea of needing a lot of computing power, while also being limited by battery life, to be…