@cmuratori The thing is, Casey, nobody could've spoken any better than you did.
Your word choice, pacing, sincerity, and composure give a whole different weight to what you're saying.
You're an incredible communicator.
@RichardN7@rfleury 100%.
In high level dynamic language there is some kind of branching on a variable type, that decides what the operator should do (or if that operation makes any sense for that type).
in assembly there is no such thing. it is "treat this memory as *this* and do that with it".
@chribjel That's because non primitive types are passed to functions by copying their reference, so they both point to the same memory location.
console.log is keeping a reference to that object to let you expand it and look at the prototype.
Solution: JSON.stringify!
@BarbascuraX Adoro il fatto che i 3 illustri professori, insieme ad altri 1497, fanno esattamente 1500 persone.
Vedi che a volte l'universo preferisce i numeri tondi.
@markdalgleish Anyways, the more i use Browser (and in general JS engines) APIs, the more i realize they're made for real low level interactions.
For example the IndexedDB API, that's hideous to work with directly, so you pretty much need to create (or find) a usable wrapper around it.
@markdalgleish I guess it's the other way around.
Browser APIs should have a promisified version, but this comes with a whole lot of issues, like the fact that Timeouts are in the macrotask queue, and promises are in the microtask one.
JS has pretty much nothing to do with it.