Like a decade ago I got into a huge fight with a Staff Eng at our company over Dart. I had just been put in charge of the company's architecture and one of the first things I did was migrate everything to TypeScript (which was relatively new at the time). He was so angry I didn't pick Dart. Good choice by me in retrospect (though picking Angular 2 over React not so much).

▲

phatskat 5 hours ago | parent | next [-]

I don't know enough about Angular 2 to know exactly how much of a bad choice that was, but my experience in React has always been "they should have used something else". I vaguely recall our lead backend being unhappy with his decision to do the original admin panel in Angular, but I chalked that up to him not being a frontender.

For context: I begrudgingly adopted Vue a while ago after finding React to be too unwieldy, and part of that opinion is definitely related to a poorly written Redux implementation.

▲

rezonant an hour ago | parent | prev | next [-]

> though picking Angular 2 over React not so much

It sounds like you're coming at this from a perspective of popularity and thus access to engineering candidates with expertise in it which is fair, but speaking as someone who also went with Angular 2 over React during those times, I'm still using Angular and I'm very happy with it from a technical perspective. Yes, it does mean there are less options for hiring, but it has been a positive experience for my team and for me in my own projects to stick with it.

▲

darepublic an hour ago | parent | prev | next [-]

My dart story. While in college for computer programming our professor telling us if we wanted to get ahead of the curve start learning dart. It was the future

▲

ZeroCool2u 5 hours ago | parent | prev | next [-]

It's really a bummer that Dart gets a bad rap, because of its early versions. The recent versions of Dart are a lovely language to work with. Pub is the only package manager I've used that approaches Cargo in quality.

▲

p-e-w 5 hours ago | parent [-]

All TypeScript competitors got out-engineered by Microsoft. It’s a triumph of experience over new ideas.

How well designed the initial versions of TypeScript were can be seen by how smoothly later versions were able to build on them, and even after so many major improvements the language has barely a wart (enums probably being the only one).

	▲	WorldMaker 5 hours ago \| parent [-]
		namespaces are the other one, and that's a fun legacy because Typescript had to implement a half dozen module systems in the early days: no modules (jQuery-era globalThis pollution), AMD, UMD, CommonJS, SystemJS, Typescript's own which was proto-ESM inspired but not ESM, then Typescript's realignment with ESM. Something of its own sign of Microsoft out-engineering some of the hiccups of the ecosystem as a whole. (I started using Typescript < 1 simply because it was the safest and easiest way to write AMD modules also with an eye to UMD or SystemJS output with just a compiler flag change if you needed to ship something compatible outside the house.)

▲

lenkite 3 hours ago | parent | prev [-]

> He was so angry I didn't pick Dart. Good choice by me in retrospect (though picking Angular 2 over React not so much).

1/3rd of apps on the iOS and Android app store use flutter and that percentage is growing over time. Whereas people are moving away from JS/TS frameworks like React Native.

	▲	galaxyLogic 2 hours ago \| parent \| next [-]
		I wonder if TS could evolve into a compiler whose output would use either Deno, Bun or Node? When the exe is compiled it no longer matters what libraries it uses underneath?
	▲	michaelsalim an hour ago \| parent \| prev [-]
		Where is that stat from?