|
|
|
|
|
by TobyTheDog123
1235 days ago
|
|
I never said we didn't have to set up an environment, but that the environment is 1. Installing Flutter
2. flutter create
3. flutter run Instead of installing/configuring/setting-up npm, typescript, eslint + rules, react + rules + types, prettier, react-native-web + rules + types, a rendering framework + rules + types, webpack, jest, and whatever else. You do, basically, get it for free. |
|
Again, it's definitely not free (or "basically" free, either). Step 1 negates that statement. You have to set up a development environment. It takes some non-zero amount of effort.
In contrast, the browser is already there. It already runs JS. You don't have to do anything to make that happen[1]. And in saying it takes nothing, that's not merely "basically" nothing; it's literally nothing.
> Instead of installing/configuring/setting-up npm [and a bunch of other crap]
What if I told you that while you're free to opt for doing any/all of those things, none of it is actually necessary, let alone a good idea? (Or point out that TypeScript is not even JS, for that matter?) That you're totally allowed to ignore the GitHub busyworkers and write actual (i.e. straightforward, standards-compliant) JS—in contrast to much of what's available for NPM/NodeJS, where you are most often encouraged to write "JS" that's incompatible with what's in the standard (and what the browser makers actually implement)?
1. <https://www.colbyrussell.com/2019/03/06/how-to-displace-java...>