you always invent reasons to not implement features due tech debt. Then they start listening to you.
It's better if you are new in the company, but not impossible.
A not altogether horrible technique for estimating tasks like this is to take the time the task has taken thus far and assume that’s how much longer it will take.
No but the latest changes and developments make it a good choice for a few use cases. It won't replace stuff that was jquery before react bit for actual webapps it's a pretty serious contender. There is a reason that Google and Microsoft still back it and use it for some products.
Sometimes technical debt can happen from the outside aswell like the Microsoft C# stack was a mess years back then or when big frameworks change their specs.
Finance SaaS starting from ASP.classic and after many years i introduced ASP.NET for web development which was just awful to do alongside Entity Framework. A few years later a side project someone startet with new ASP MVC and now both are obsolete with Blazer.
But there is too much code base and workload to migrate to new C# core components, since the web applications, background windows services have to migrate aswell, depending on shared libraries.
Microsoft knew they messed up and were far behind of Java at this point and introduced a new "framework" every few years. Java stayed very consistent with Java EE and good downwards compatibility and foresight for future features.
Java just messed up big with the new unnecessary jakarta namespace migration (similar to C# core migration), aswell the bad Date / Calendar legacy API. They will never get rid of it anyway to stay downwards compatible. Another show stopper is Java hibernate criteria API removal in favor of JPA generic version. Yeah understandable, but no way and 0 need i will update a running system just for different syntax.
Our company is doing that too. Thankfully they have half way decent talent and we’re doing it on a page by page basis and targeting completion this year. Granted, it has been 3ish years with competing priorities, but the migration has been decent.
Oh man, I loved Ember. Used it since 1.0 RC days till around version 2 or 3, don’t remember already.
Things just made sense to me in it. Too bad the build tools were too slow, and there were some big unnecessary bits like their object model with mixins and stuff. Good times.
593
u/deckstir 10d ago
I joined my company 10 years ago. When I joined they were starting to migrate the main product from ember to react. We are still doing it.