2 ms·
It's a big project; they had senior developers with experience in building browsers, who realised that this would all of that plus the rest. They also knew that
by Cthulhu_ 3y ago
It's a big project; they had senior developers with experience in building browsers, who realised that this would all of that plus the rest. They also knew that the 1.0 release would only be the beginning of the project, so the setup needed to be good, and the development practices needed to be sustainable.
This differentiates senior developers from the rest I think. Mind you, I can also understand why a lot of people - myself included - think "what's the point", given how (in my own experience), a lot of software - mainly front-end - is replaced every 5 years, and major architecture overhauls every 10.
My current employers is currently replacing their SAP-to-API middleware with some commercial point-and-click software to, drumroll please, AWS lambda functions written in Typescript. It's an improvement, because there's more transparency and performance measurement instead of things hidden behind a GUI, but it's also a risk because it's set up by consultants who will eventually move on to somewhere else.
Already there was suddenly a presentation that came across as Authoritative about how they have Chosen to use Kotlin. I don't know for sure if that was to replace typescript but... it really doesn't matter to me tbh.