4 ms·
Your last sentence is needlessly condescending :/
by aroman 8y ago
Your last sentence is needlessly condescending :/
- deleted 8y ago[deleted]
- dekhn 8y agoNo, it's not. It's an accurate assessment of the current state of the web world: web frameworks that last a year before they get abandoned by their creators. jwz wrote a nice blog post about it: https://www.jwz.org/doc/cadt.html https://www.jwz.org/doc/cadt.html
- hood_syntax 8y agoWhy do people link this dude here when you get redirected to that picture every time...
- shawnz 8y agoYes, how ironic to criticize childlike developers and then defer to jwz
- dekhn 8y agoA guy who has maintained a secure screensaver for 20+ years. Who aptly describes how fucked up our system is. Who built the technology your browser apps are based on.
- iiiggglll 8y agoNot that he's wrong about open-source abandonware, but that's rather an overstatement. No significant amount of his code remains in any modern browser, and when the engine that eventually became WebKit and later Blink (and which now powers the majority of end-user web client browsing today) was first announced as based off KHTML and not Mozilla tech, he wrote a self-congratulatory blog post[0] that started off with "Summary: I was right", even though it had nothing to do with him or his work. Not to mention KHTML was done using C++, something he was always against (no mention of "I was right" on that part, I see). He's done some good work here and there but he really gets carried away with his blowhard opinionating at times, and I think people should turn a more critical eye towards that sort of thing. [0] https://www.jwz.org/blog/2003/01/more-khtml/ https://www.jwz.org/blog/2003/01/more-khtml/
- Mononokay 8y agoThe link works for me.
- dekhn 8y agoYou're probably using an ad blocker
- icebraining 8y agoAre they being abandoned by their creators, or just superseded in popularity by others?
- pknopf 8y agoBoth are equally as bad.
- shawnz 8y agoIt's OK, the parent will be paying the price when they're still writing native x86 code in 20 years time.
- pjc50 8y agoshrug Nothing wrong with native code, and sometimes nothing else will get the job done. Besides, my retirement plan is to be the dinosaur brought out to fix all those 32-bit-time bugs in 2038.
- dekhn 8y agomost of my code is in Python (there are Qt bindings). That said, I'm interested in webassembly, and can also write javascript. I just don't think that browsers or javascript-based apps present a preferred alternative to native apps developed by teams who consider long-term API stability and getting the right regulatory boxes checked.
- ahartmetz 8y agoThe free performance lunch from ever faster hardware is over and that is saving native code for applications. The few percent hardware improvement each year is easily eaten by growing requirements.
- pkaye 8y agoLow level knowledge is useful at times. I rewrote a small amount of code on a project at work using SIMD instruction to reduce execution time by 60%. This is on something executes in tens of minutes so the time savings are quite noticeable.