alt Hacker NewsSure, you can do that for your hobby projects. But "at work" you generally have these decisions made for you. And these decisions have changed over time for the wrong reasons.
As an aside: if we say k8s, we should also say j8t.
Replies
Otek • today at 12:58 PM
> And these decisions have changed over time for the wrong reasons.
Have you ever considered that you don’t understand why those decisions were made and that’s why you think they were made for the wrong reasons?
➕ show 2 replies
marcosdumay • today at 3:46 PM
> j8t
Javascript?
That would solve the trademark problem...
jagged-chisel • today at 1:08 PM
> if we say k8s, we should also say j8t
It’s that one extra spoken syllable that pushes it into k8s I guess. ¯\_(ツ)_/¯
➕ show 1 reply
> But "at work" you generally have these decisions made for you.
The idea that most employers make terrible decisions now, and amazing decisions back in the day, is plainly false. The author vividly recollects working at a decent Java shop. Even there I strongly doubt everything was amazing as they describe, but it sounds decent indeed. But plenty businesses at the time used C++, for no good reason other than inertia, usually in Windows-only Visual C++ 6-specific dialects. Their "build server" ran overnight, you'd check in your code in the late afternoon and get your compile errors back in the morning. The "source control" worked with company-wide file locks, and you'd get phoned your ass back to the office if you forgot to check in a file before leaving. Meanwhile, half the web was written in epic spaghetti plates of Perl. PHP was a joy to deploy, as it is now, but it was also a pain to debug.
If you care deeply about this stuff, find an employer who cares too. They existed back then and they exist now.