Yes! That’s why the headline says “overdesigned”:)
It’s designed as a universal native app. So browser here really is just a platform for deployment.
The design is for a an application that is a single download and few megabytes in size that runs the same on desktops natively (after compilation) and in the browser. Rust ecosystem is getting _really_ nice for that.
So it’s Egui with WebGPU backend.
So if the requirement is ”an universal app” it’s nicer alternative than using Electron but Tauri might have been a more reasonable choice if I didn’t want to leave the door open more for more options on rendering backend on desktop.
Sort of same lineage in thinking as Flash, Java apps (circa 2000 :) ) etc. Or something like Ghostty.
The downside is that it does not use native GUI for much which means it’s closer to a game than ”professional” desktop app.
There's already an established market for folding phones, so it's likely to have a recurring niche. It's not like the Vision Pro that tries to create an XR-headset market by doing everything it can to not have the functionality that would make it competitive against pre-existing VR headsets.
I thought CAs automatically filtered out really low keys. There's a great Suckerpinch video (https://youtu.be/M1si1y5lvkk) about trying to purposely make the least secure HTTPS page possible, and Tom initially tried to choose a laughably-low number as the key, but the CA automatically rejected it.
The magnetron burns out from a high standing wave ratio, which is the ratio of how much energy bounces back into it, to how much its outputting. If you aren't heating anything up, the microwaves bounce back and cause damage.
If you have something in the oven that absorbs the microwaves and gets hot, then you're fine. Liquid water does this, including the water in your food, but ceramics do it too. That is why when you cook frozen foods on a ceramic plate, the plate can heat up faster than your food. Once the food defrosts, it'll have liquid water and begin cooking at full speed. Sometimes the food only defrosts from the plate heating up, so you end up with food cooking from the bottom up, instead of the top down.
There's enough ceramic to absorb enough microwaves. There's other reasons the heat could ruin the microwave, and plenty of reasons not to share food with a microwave that has vapors from melted colored glass. Considering how cheap they are second-hand, I wouldn't use a kitchen microwave for it, especially so if there's colorants in the glass.
I work on hardware development, that matches pretty well the time I can spend on high-creativity design tasks. I fill the rest of the time with tasks that could be outsourced, like assembling prototypes or laying out circuit boards, but I do myself because they are more like relaxing puzzles than demanding work.
When I have to work on single a software-only project, after about two weeks of sitting at a desk for eight hours a day, I absolutely have to do something else.
8 hours of highly concentrated work is a unbearable load to do continuously for days, you definitely need some "normal" task as well. I can't imagine anyone claiming to do "12 hour work days" to engage in anything thoughtful for more than 12 minutes.
There is nothing like the feeling of getting off the nitpicky design tasking to assemble some SMD components under a microscope first thing in the morning.
Especially if it's a known-working design assembling the second or third prototype. Feels like gardening.
If CSS is Turing complete, that means it has a virtual machine with parsing and so forth. That means that difference between it and JavaScript is just syntax. (Same for any Turing complete language)
Not just. There’s also the issue of complexity. And JS is considerably more complex. Just think of all the APIs that are immediately available at runtime in JS, for one. It takes up far more memory and CPU cycles to initialize, the language itself is much more complex…
I am not quite sure I understand what you are getting at. Surely, we don't have to go into why syntax is extremely significant for feasibility of implementing features. I mean, we don't code in assembly much these days, do we?
reply