gasping

7 ms·

31.
by gasping 12y ago
Unfortunately reality just doesn't work that way. Projects are completed. Developers move on. New developers eventually are employed to make upgrades only to find the entire toolchain was built by some guy in a coffee shop 15 years ago
32.
by gasping 12y ago
And what's the deal with giving these projects meaningless names? Gulp and browserify mean nothing to me, whereas gcc and make are basically self-documenting. Can we please stop giving these projects trendy names and instead name them
33.
by gasping 12y ago
* https://github.com/gulpjs/gulp/blob/master/docs/recipes/brow...
34.
Ask HN: Do you think the JavaScript toolchain explosion is out of control?
12 points by gasping 12y ago|14 comments
35.
by gasping 12y ago
> If you have callback hell, it is an expression of muddled thought. No. It's an indication that you're using a FOTM runtime environment. There's a reason why no production-ready runtime uses continous passing / callb
36.
by gasping 12y ago
It's ReactJS. See my previous comments and surrounding comments for some discourse.
37.
by gasping 12y ago
No, just please no. Any moderately competent programmer can be productive in either Java or Javascript (+ Node.js). Javascript may help incompetent programmers feel productive because Javascript has fewer compile-time constraints but in the
38.
by gasping 12y ago
This is laughably stupid. I stopped reading when they substituted a relational database for MongoDB. Nevermind that they both solve completely different problems. This post must have been written by an incompetent business analyst who feels
39.
by gasping 12y ago
> powerful, elegant, and future-proof ReactJS. It's totally unlike Angular and Ember in a good way. You will not regret it.
40.
by gasping 12y ago
> you'll never go back to anything else. React completely changed the way I thought about rich clients. It took me a little longer than 2 days, I went into React with an absolute hatred of anything Javascript and came out 2 weeks la
41.
by gasping 12y ago
Angular 1 developers should see this as an opportunity to abandon Angular and move on to React. React is by far and away the best the market has to offer right now. From my perspective client-side applications are a solved problem thanks to
42.
by gasping 12y ago
I had to laugh at the revenue estimates based on the peak of a brief social media buzz. Most of that traffic will disappear over the next few days.
43.
by gasping 12y ago
What did you do when the infatuation with Angular wore off? Did you see the project through to production release? Was your employer satisfied with the outcome?
44.
by gasping 12y ago
Thanks for those resources, I will keep an eye on them. The new kid on the block is famo.us! Have a look! That's sort of my problem with these frameworks. A neverending explosion of new frameworks that haven't been thoroughly fi
45.
On the horrific state of JavaScript frameworks
21 points by gasping 12y ago|16 comments