"The problem is that thousands of miles of guardrails installed alongside American highways were designed decades ago"
Ah, yes, that is the problem. Cars becoming heavier with little to no added value are not the problem, its the guardrails and not enough tax dollars being spent.
In certain states in the US they require a drug test to make sure you are infact taking the medication yourself. Its almost like a reverse drug test; you get in trouble if you're not taking drugs.
So I guess also don't forget and/or try to get off the medication otherwise you'll fail the drug test and also loose access.
Also don't forget your mandatory call to the doc each month for every refill
and don't forget to call a day early when it lands on a weekend
and don't forget to setup the mandatory appointment every 6 months
and don't forget to actually go to the appointment
and don't forget to schedule a drug test once every whatever-amount-of-time it is for your state
and don't forget to not eat or drink or take the medication the morning of the drug test
Cause if you forget just 1 of those they'll obviously have no choice but to deny you the medication you've been taking every day for 10 years. But you understand because punishing disabled people for mistakes/crimes of able-minded people (who don't find those things challeging), is clearly the only option they have.
Sure not a breakthrough, but they are "real" progress not fake progress (which is what I was responding to in your earlier comment)
Clock speed and other areas I'd agree have stagnated, but graphics cards, wireless communicaiton standards, cheap fast SSD's, and power efficient CPU's have massively impacted end-user performance in the last 10 years. RISC-V is also a major development that is just getting started.
I disagree slightly, but only with his level of cynicism. I agree, we see the "peak diskwasher" problem everywhere. And I agree with his conclusion. But I feel he glossed over that, well, people still need dishwashers. Growth might be impossible, but a steady and "boring" amount of profit should still be possible selling plain-ole-dishwashers. Yet ... for some reason, we don't see that.
Instead companies throw everything into growth and we get the retarded bluetooth enabled dishwasher problem everywhere, and I'd like to know more about why.
I still use Prezi, although I'd really like an open source alternaitve.
Mark Zuckerbergs dystopian animatronic metaverse ad: "You will be surplus to requirements, first fungible and ridiculous and then literally disposable." It was so bad, the video was privated https://www.theverge.com/2022/2/12/22930776/metas-quest-2-super-bowl-metaverse-ad-animatronic-dog-virtual-reality
One little asterisk
Could fix the problem I think
[Segmentation fault]
npm install
peer dependency not found
npm install
I think maybe this is just a communication issue and we actually agree on the details.
Wasi and emscriptem from the ABI link, AFAIK, are basically wrappers to impure tools; console log, file system access, sockets, etc. For my usecase, I dont want the serialized functions to have access to those interfaces.
That aside, lets say we serilized
(m: f32, x: f32, b:f32): f32 => m*x + b.
Yes, there will need to be some conversion layer, like converting python floats into wasm f32 floats and converting the f32 output back to python float. And stuff like javascript not having ints, could cause some weirdness. Maybe thats the ABI you're talking about. Since that conversion basically already exists for every language that supports wasm, I didnt really think of it as an ABI, but you might be right that techically it is an ABI.
I suppose a real ABI would be needed if the wasm function wanted to manipulate complex types like hashmaps or arrays.
The serialization format could just be the bytes of a wasm file stored inside of a yaml file in base64. I'm not sure if yaml or utf8 would be considered a ABI. But basically the bytes would be loaded as a wasm module, then the wasm function inside the module would become value for that yaml key. The wasm function would be auto-wrapped by the language's default inter-op layer for wasm functions.
IMO, you should be exempt. The vast majority of jobs don't require a truck, yet the F150 is the most-sold vehicle in the US. So you're in the minority.