News for hackers. Stuff that matters.
Re:I fucking hate Jira by cogman10 on Monday June 20, 2022 @05:52PM (#31816558)
> How about when every single company rewrote their frontend stack in React

God I wish that were the case. My company is still rocking Angular unfortunately :(

> Or when everyone moved to k8s within 2 years around 2017-2019

That did not happen. k8s got a good share of the market, but it's far from "everyone moved".

> What I am trying to show by these examples is that things can move fast, very fast, and that in our industry there are no such thing as well-entrenched tools.

The tools you are listing are all dev tools picked, used, and curated by development. Jira isn't a dev tool, it's a product management tool. There's a major difference between tools that devs can pick and choose and tools that an organization gets to pick and choose.

Even with your "yarn" example, while it took over it didn't replace "npmjs" as the centralized repository server. Just like gradle still gets it's artifacts primarily from maven central.

I'll go back to something I said elsewhere. If it's so easy to move and change why is C++ still being written? Why does it remain one of the most popular programming languages even though most people are VERY quick to point out it's major flaws. Even though other better alternatives exist (Rust, Nim, D, etc).

> losing issue history is far less damaging than it was losing "commit" history when everyone was moving to git back in the days.

Assuming you like everyone else went from svn->git I don't see how you'd have lost commit history. I personally converted a BUNCH of repos to git and didn't see any cases of lost history.

Re:I fucking hate Jira by toshaga on Wednesday June 22, 2022 @04:47PM (#31841673)
> I'll go back to something I said elsewhere. If it's so easy to move and change why is C++ still being written?

Because C++ is very very much a living and, most importantly, evolving language. It gives modern conveniences, while benefiting from existing user base and maturity. Alternatives may be better for specific emerging use cases but can’t just yet challenge the incumbent for the reasons above. One day C++ may have to yield, but at the moment it’s been actively renewed and the effort to migrate codebases to a new standard is smaller than porting onto entirely new language.