4 ms·
probably because there are so many js “frameworks” that they are running out names
by andarleen 6y ago
probably because there are so many js “frameworks” that they are running out names
- taywrobel 6y agoSort of makes me bummed out that the Dart project failed. If there was one time when we could have escaped the client side hell that is JavaScript it would have been then, when chrome had astonishing market share, and Dart could compile down to JS to ease the transition until native support became standardized. But nope, here we are with anotherone.js every week.
- swyx 6y agowhat makes you say it failed? Flutter is growing strong.
- nivethan 6y agoIs there a way around the nested mess in Flutter widgets? I took a stab at a small app but it was basically a new div hell. Besides that however, it was quite neat.
- swyx 6y agohaha idk im just going off of what others say, i dont use it myself
- iratewizard 6y agoIt's ambitions and potential versus its current adoption make it a relative flop. Plus, since it's made by Google it may randomly end up in the graveyard without warning.
- Tade0 6y agoDart wouldn't stop the relentless cycle of frameworks coming and going. Case in point: Angular has an alternative Dart implementation which is AFAIK used by Google internally, but it didn't take the web by storm and currently the TS flavour is by far the dominant one.
- hombre_fatal 6y agoI don't get it. Dart looks almost 1:1 exactly like Javascript. How would it have saved you from people building frameworks in it? I think we're very lucky that Chrome never decided to include that Dart VM. Typescript turned out to be much better than Dart.
- holtalanm 6y ago> Typescript turned out to be much better than Dart I think we can agree to disagree. I would much rather use Dart, imo.