ErikCorry
8k RAM, 64k ROM, compressed RISC-V insn set.
Edit: Apparently it's a QingKe RISC-V with about 130 Coremark.
Absolutely no way any OS or browser manufacturer forgives them and let's their certs validate anything in the future.
I don't know whether the log of the size of the table needed has a linear relationship to log(n) in this case.
Put another way, you need the gas turbines for the two week dunkelflaute (winter doldrums). Given that you have the turbines already, when are batteries cheaper than running the turbines for a few hours every evening?
A more interesting question than the cheapest 4 hour solution. I think that answer might also be batteries soon.
This also relates to my most controversial opinion: The caps lock key is good, actually.
If be curious if these are the sorts of optimizations I would find useful to the point where I would be happy to pay the price of this annoying new behaviour.
Or are they just the sorts of optimizations that a compiler writer finds useful who is engaged in a multi year career-defining pissing contest with a competing team?
Don't get me wrong, I have myself engaged in a multi year career-defining pissing contest with a competing team. It's fun. But let's not kid ourselves that it's for the users' sake.
The only things that can easily go wrong now are:
The compiler turns out to be evil and introduces an “optimization” that I don’t anticipate
The V8 developers turn out to be evil and modify how this logic works and break my assumptions in a future release
Wasm doesn't promise it either but there's a much better chance you get what you want there.
I haven't found a way to win today with 9 steps.
https://gist.github.com/erikcorry/b21723a0ba49c044b03a6030dc...
Edit: Using some of your words you can get to 9 steps (10 including the word you have to avoid): https://gist.github.com/erikcorry/d55d263b129eb7a56c8c212296...
When I see the "$1 introductory offer" I just think they are trying to trick me.
Poor performance of the single implementation.
A single implementation.
Leaky ref counted GC, but 'luckily' the syntax for references is so clunky that nobody does anything complicated enough that it really matters.
Bolted on object oriented features that never got the love they needed at a time when oo languages were sweeping the world.
Most of the wizards decamping to a new language (Perl6) that was 'developed' for years without an actual implementation to keep them grounded.
Why malloc? Surely this is an on-heap object, not malloc allocated?
V8 has its first module in Rust and I'm sure more are coming, but it's not necessarily an easy integration.
JS is a GCed language. Are there good examples of Rust interacting well with a GCed language runtime where it is able to free unreachable cross domain pointer cycles? Like a JS object that has a reference to a Rust object, which itself has a reference to a JS object. Add more steps and hopefully you can see that collecting such cycles is a hard problem. This is the problem the C++ GC solves.
By the way you can't always break cycles with weak pointers. The browser standards have semantics you have to adhere to.
To help prevent vitamin D toxicity, don't take more than 4,000 international units (IU) a day of vitamin D unless your healthcare professional tells you to. Most adults need only 600 IU of vitamin D a day https://www.mayoclinic.org/healthy-lifestyle/nutrition-and-h...
1 https://www.mdpi.com/2072-6643/17/17/2744#:~:text=highest%20...
2 https://www.abs.gov.au/articles/vitamin-d#edit-group-image--...
Unless you are an insect, most pesticides are harmless for you. And for those that are not, nobody has proved a connection to allergies.