And OP talks about Alchemy, which commonly uses the energy that different materials have inherently to create magical artifacts.
It’s literally using what God already created.
And OP talks about Alchemy, which commonly uses the energy that different materials have inherently to create magical artifacts.
It’s literally using what God already created.
If it involves pointers, not unlikely.
Honestly, given the context of a browser, Javascript’s “Everything is better than crashing” philosophy does not seem too out-of-place. Yes, the website might break, but at least it would be theoretically usable still.
Yes, a statically typed language would help, but I’d rather not have one that is “these two types are slightly different, fuck you, have a segfault”, but rather one that is slightly more flexible.
With C, you need to carefully craft your own gun with just iron ingots and a hammer. You will shoot yourself in the foot, but at least you’ll have the knowledge that it was your craftsmanship that led to it.
With C++, there are already prebuilt guns and tons of modifications that you can combine at will. If you shove it in the right way, you can make a flintlock shoot a 50 cal, but don’t complain when your whole leg gets obliterated.
And yet somehow it evolved to become something that will last to the heat death of the universe.
I’ve grown used to it with time, though. Once you know it’s “quirks”, it’s not so bad.
Yet not many people can brag about breaking half of the internet in one swift blow.
It’s way worse on C and it’s family. I still have nightmares with undocumented embedded dependencies that are so intertwined with the codebase that make JS look like a godsend.