4 ms·

> use whatever [JS] framework you want I don't want to have an opinion about which JS framework I should use. I want to worry about the client's requirements

> use whatever [JS] framework you want I don't want to have an opinion about which JS framework I should use. I want to worry about the client's requirements and build the software. Having 20 frameworks to evaluate and choose between just means that the entire toolset is less well documented and less stable and no one framework has any weight behind it. And after working for years in JavaScript I just don't like it -- I hate the constant brain-breaking workarounds that other languages solve by just not having the problem in the first place. Javascript sucks.

OJFord 3y ago
I'm no JS fan but this argument doesn't make sense to me - just pick from the big ones at random then? Far more weight behind them than Flutter, and I don't know why they get the higher bar of being 'evaluated' between when Flutter doesn't because it's the only option and you're stuck with it. But anyway if you want to use Dart & Flutter fine just use it? My comment wasn't about why someone shouldn't, it's why I think people don't, i.e. why it doesn't have that much adoption.
afavour 3y ago
> I don't want to have an opinion about which JS framework I should use. I want to worry about the client's requirements and build the software. Taking client requirements and selecting appropriate software is part of the job. Choosing Dart for said project is just as much of a choice.
lolinder 3y ago
> Having 20 frameworks to evaluate and choose between just means that the entire toolset is less well documented and less stable and no one framework has any weight behind it. There are hundreds of human languages in the world, but English still manages to have far and away the most weight behind it. JavaScript frameworks are in a similar boat: all the tiny frameworks together make up a tiny fraction of the total usage. React is far and away the largest, followed by Angular and Vue in a distant second and third. Most of the new frameworks you see on HN are actually layered on top of React, which means they're contributing to its weight, not detracting from it. So, if you want to make a decision based solely on weight, straight React is a no-brainer. If other factors matter more, then you've got other choices with different trade-offs.

OJFord 3y ago

I'm no JS fan but this argument doesn't make sense to me - just pick from the big ones at random then? Far more weight behind them than Flutter, and I don't know why they get the higher bar of being 'evaluated' between when Flutter doesn't because it's the only option and you're stuck with it. But anyway if you want to use Dart & Flutter fine just use it? My comment wasn't about why someone shouldn't, it's why I think people don't, i.e. why it doesn't have that much adoption.

afavour 3y ago

> I don't want to have an opinion about which JS framework I should use. I want to worry about the client's requirements and build the software. Taking client requirements and selecting appropriate software is part of the job. Choosing Dart for said project is just as much of a choice.

lolinder 3y ago

> Having 20 frameworks to evaluate and choose between just means that the entire toolset is less well documented and less stable and no one framework has any weight behind it. There are hundreds of human languages in the world, but English still manages to have far and away the most weight behind it. JavaScript frameworks are in a similar boat: all the tiny frameworks together make up a tiny fraction of the total usage. React is far and away the largest, followed by Angular and Vue in a distant second and third. Most of the new frameworks you see on HN are actually layered on top of React, which means they're contributing to its weight, not detracting from it. So, if you want to make a decision based solely on weight, straight React is a no-brainer. If other factors matter more, then you've got other choices with different trade-offs.