Works great, I like this approach much better than the variants that I've seen, this is exactly what I was hoping to see. It's simple, concise, imposes nothing on you, ships with good presets (from what I've seen so far), still extensible. Nice work!
Using Neutrino to jump-start modern JavaScript development
21–30 of 68 posts
Re: Using Neutrino to jump-start modern JavaScript development
#22I think this is a cool tool, but it's somewhere between funny and depressing that the article brags about how they were able to get a 'Hello, world!' program up in less than 5 minutes .
[deleted]
Re: Using Neutrino to jump-start modern JavaScript development
#23Maybe it's just me, but I didn't find it all that difficult to get started with webpack after a few tutorials and samples. This seems like it hides away something that people should probably understand, which isn't all that difficult to get started with. Also when you start combining different packages in webpack (or encounter an error (or want to make some decisions in the config script)), the standard copy/paste bo…
We all do basically the same thing in every app ever, it's the fragmentation that is such a huge pain with JavaScript. Most apps don't have to be unique snowflakes, we make them that way with hacky css-in-js and so on.
Webpack is great for what it is, but I strongly disagree that people should have to understand the config boilerplate aspect to get something functioning. All it does is prevent you from doing real work, not to mention if you're working on dozens of apps, this quickly becomes a hellish thing to deal with.
Re: Using Neutrino to jump-start modern JavaScript development
#24Does anybody just write plain JS ?
[deleted]
Re: Using Neutrino to jump-start modern JavaScript development
#25Javascript Boilerplate Fatigue
[deleted]
Re: Using Neutrino to jump-start modern JavaScript development
#26Does anybody just write plain JS ?
I did recently for a very simple Cordova app used by sales reps for marketing purposes. A framework or external libraries was overkill to the extreme, so by sticking with just vanilla I kept the app size to a minimum.
Re: Using Neutrino to jump-start modern JavaScript development
#27Why not just use Yeoman? Moz really like reinventing the wheel.
Yeoman is boilerplate, this is code which directly avoids boilerplate, since it's an abstraction instead. Yeoman IMO encourages the wrong things, most true boilerplate (files) can just be a sample repo that you clone.
Re: Using Neutrino to jump-start modern JavaScript development
#28Maybe it's just me, but I didn't find it all that difficult to get started with webpack after a few tutorials and samples. This seems like it hides away something that people should probably understand, which isn't all that difficult to get started with. Also when you start combining different packages in webpack (or encounter an error (or want to make some decisions in the config script)), the standard copy/paste bo…
We all do basically the same thing in every app ever, it's the fragmentation that is such a huge pain with JavaScript. Most apps don't have to be unique snowflakes, we make them that way with hacky css-in-js and so on. Webpack is great for what it is, but I strongly disagree that people should have to understand the config boilerplate aspect to get something functioning. All it does is prevent you from doing real wor…
I have great respect for you but this seems a bit mean spirited. Why shouldn't devs want to be as many things as possible?
Is css-in-js is more ridiculous than regular CSS? I've left regular CSS behind and gained a lot of sanity.
Re: Using Neutrino to jump-start modern JavaScript development
#29Is there a simple example of how to add something like react-router, redux and bootstrap as to presets to neutrino. My problem with CRA is that while very helpful(!) I am often faced with having to add those kinds of components.
Re: Using Neutrino to jump-start modern JavaScript development
#30Earlier quoted context omitted.
We all do basically the same thing in every app ever, it's the fragmentation that is such a huge pain with JavaScript. Most apps don't have to be unique snowflakes, we make them that way with hacky css-in-js and so on. Webpack is great for what it is, but I strongly disagree that people should have to understand the config boilerplate aspect to get something functioning. All it does is prevent you from doing real wor…
I have great respect for you but this seems a bit mean spirited. Why shouldn't devs want to be as many things as possible? Is css-in-js is more ridiculous than regular CSS? I've left regular CSS behind and gained a lot of sanity.
It's just my opinion of course :) but I think css-in-js is a step backwards in the majority of cases. I do like CSS modules in terms of scoping / modularity, but I don't want to replace CSS with (what I consider to be) really gross JS implementations.
I don't want to discourage people trying new things, but I also don't want people to waste thousands of collective hours dealing with crazy configuration.
I think toying around with those things are fun for people who get paid by startups etc, but for those of us who simply want to get things done, the ecosystem is not enjoyable.