Hacker News Reader

Comment by sz4kerto | Hacker News Reader

I find it horrifying that on a Haswell i7 a chat app or a text editor STUTTERS. It's really ridiculous and sad at the same time.

View on HN

For every clock your CPU gets, a developer will find a way to waste it.

Why is there so much interest in HTML + Javascript based normal applications? They are slow, the langauges are awful, but besides Qt they are the ultimate portability. So sacrifice all those hz gains and power efficiency to make the developer workload minimal.

I assume because developers approach it with a different mindset:

Theoretically all of this problems can and will be solved. The advantage would persist.

But agree. Reality looks often different

Besides Qt, JavaFX, wxWidgets, Xwt, even Gtk offer a better native experience than a browser widget.

Script kiddies are cheaper than C++ developers.

Hear, hear. http://handmadehero.org is almost therapy for me in that regard: Casey looks at assembly output from the compiler all the time.

Yeah, it's amazing. We've had decades of improvements in hardware performance, only to end up with software that's slower than anything that came before it. Yet apart from a small minority, nobody seems to bat an eye.

Oh, the people do care.

Even my mum complains every day about it. "Can’t be that a 4 year old smartphone can’t run a chat app like whatsapp fluently"

But she refuses to buy a new phone, because that would just fuel this even more.

Or rather, the new phone would burn jet fuel even more.. That's the main problem, we shouldn't be coding for saturation of resources. It's ridiculous how wasteful apps are these days.

Yes, that is the exact issue. Upgrading just costs money and does not really improve anything.

I see it myself, upgraded from Huawei Ideos X3 (2.3.7) to Motorola Moto G (5.0), and it’s just as slow as the old phone was. Despite being twice as expensive.

There's plenty of us (game developers) that do our best to push the hardware!

I'll always remember fondly coding in my 486 days with the Borland Turbo C++ IDE; we had no keystroke latency at all back then.

Reply on news.ycombinator.com