I once ran 3 electron apps at the same time which is basically the same thing
I once had three windows of VSCode open. And two of them were Typescript.
Seriously, though. Why the fuck is the ESLint extension so horrible? Slow, bloated, misses changes outside the current file, and needs gigabytes of memory.
Yes, we know it was called the The South American Blackout of 2019.
RIP this guys RAM
Woah don’t just point out he has RAM like that, don’t want anybody coming to take it
When he said that my first thought was “Are you sure you wanna talk about efficiency?”
My 1st thought was “Are you sure you wanna talk about the optimal resource allocation for society?”
Mine was more specific: “How many homes do you own and what percentage of the rooms are occupied right now?”
It’d be more efficient for his organs to be split up and distributed to those on waiting lists.
seriously. treating the rich like they’re still human in any way that matters has to end. they must be harvested. give something back to the world. something we won’t be coping with for centuries.
I’ve managed to convince investors that my brute force solution is worth trillions.
The story of LLMs summed up in one sentence.
Tbf opposite happened a couple of times too where I was like “if only a nuclear war sent our hardware 30 years back so people would appreciate this logic right here.”
I still like efficiency. you are not unappreciated. only by people who matter.
Imagine being roasted on every social platform.
[Nobody likes you.]
Even the cuckholders.
I’ve had a problem like that once, but then I realized it made way more sense to allocate a big swap file instead and map that to memory.
But what if you “needed” to access all of that memory every single time you produced an output character? And (only hypothetically of course) “all of that memory” was like dozens of gigs at a time.
Only truly visionary computer scientists could be capable of such genius.
monarchist mode of production is just this.
Node developers sheepishly look away
malloc(999999999999999999999999999999999)
malloc(18,446,744,073,709,551,615)
ULLONG_MAXfromlimits.h- so on a 64bit machinesize_t = unsigned long long = uint64How about the equivalent
malloc(-1)?Also, it’s cheap to allocate memory if you never write to it. You should follow it up with memset() if you really wanna max out your Resident Set Size 🐏
Just once but my parents grounded me and took away my gameboy
You think he wrote that code himself?
For your retooting pleasure: labyrinth.social/@nash/1175421…
RE: labyrinth.social/users/nash/st…
