81–90 of 134 posts
This is an attempted capture of a major open source community by commercial interests.
I thought this was interesting at first. An effort to push the JS environment towards standardization is a much needed initiative. Then I saw the "initial projects" list. "Appium, contributed by Sauce Labs, is an open source Node.js server..." "Interledger.js, contributed by Ripple, enables instant payments and micropayments in any currency..." "JerryScript, contributed by Samsung, is a lightweight, fully-featured Ja…
Though nice to see moment and webpack
I thought this was interesting at first. An effort to push the JS environment towards standardization is a much needed initiative. Then I saw the "initial projects" list. "Appium, contributed by Sauce Labs, is an open source Node.js server..." "Interledger.js, contributed by Ripple, enables instant payments and micropayments in any currency..." "JerryScript, contributed by Samsung, is a lightweight, fully-featured Ja…
I thought this was interesting at first. An effort to push the JS environment towards standardization is a much needed initiative. Then I saw the "initial projects" list. "Appium, contributed by Sauce Labs, is an open source Node.js server..." "Interledger.js, contributed by Ripple, enables instant payments and micropayments in any currency..." "JerryScript, contributed by Samsung, is a lightweight, fully-featured Ja…
Though nice to see moment and webpack
I thought this was interesting at first. An effort to push the JS environment towards standardization is a much needed initiative. Then I saw the "initial projects" list. "Appium, contributed by Sauce Labs, is an open source Node.js server..." "Interledger.js, contributed by Ripple, enables instant payments and micropayments in any currency..." "JerryScript, contributed by Samsung, is a lightweight, fully-featured Ja…
I see a lot of comments here interpreting this as a push towards standardizing certain tools, yet I don't see anything on the site that suggests that is their mission, nor do I see any way they could possibly effect that kind of change. There seems to be some kind of messaging problem in that we are reading totally different things into what this foundation is about. Can you share why you think this foundation is try…
Pure speculation, but maybe some people see it as a last ditch effort to keep projects like jQuery relevant. I've run across a lot of negative opinions about it. I've known developers who will laugh if they see it in an app. I've seen some interesting uses where people import only specific functionality out of jQuery they want, cutting it way down. https://goo.gl/kWeIJe But honestly I haven't needed it for awhile now.
I thought this was interesting at first. An effort to push the JS environment towards standardization is a much needed initiative. Then I saw the "initial projects" list. "Appium, contributed by Sauce Labs, is an open source Node.js server..." "Interledger.js, contributed by Ripple, enables instant payments and micropayments in any currency..." "JerryScript, contributed by Samsung, is a lightweight, fully-featured Ja…
Though nice to see moment and webpack
Earlier quoted context omitted.
Though nice to see moment and webpack
moment.js is a monolithic beast. I would love to see date-fns instead https://github.com/date-fns/date-fns
Earlier quoted context omitted.
Then a couple years later you've learned a lot of arcane details about something that has already fallen out of fashion. It's not the end of the world but it's not optimal.
Such is life in programming. But feel free to continue using jQuery if you feel all the new stuff isn't worthwhile. IMHO the sweet spot for picking up new JS tech is about a year or two after it first starts appearing on Hacker News.
Actually no, the technology churn is much higher in JavaScript-land than most anywhere else.
Earlier quoted context omitted.
How can you find the js fragmentation a feature and not a stinking pile of shit? Seriously.
What exactly do you mean by js fragmentation? If that, you have power to pick from hundreds of lib/fw and combine them together, then what you call fragmentation is actual real benefit for me. I like to make decisions myself, but if you like the others to take decisions for you, js is probably not for you. The very good example is redux. Redux was once simple state management lib. Take a look at it now https://github…
But yes, as I've said in some recent comments: Dan and Andrew found a sweet spot with Redux's design in terms of approach, concepts, and providing building blocks for others, and that's led to an explosion of useful stuff that people have built for their own use cases.
Earlier quoted context omitted.
Plain old HTML, CSS, and ES5 still work. You aren't forced to install Node and Gulp and any of those things. So I rather much thing the use of the word "impossible" is way out of line here.
They are the foundations, and I recommended them in this very thread. But that's not what most of us would call "modern JS development". The amount of extra stuff between the foundations and current "best practices" is exactly the problem.
Stuff like minification you probably want a pre-existing tool to do. It's stupidly simple and not that difficulty to integrate into any build process.
But stuff like transpiling is completely optional. ES5 is a really high level language. There isn't anything particularly "wrong" with it, not any more so than most any other language you'll end up using.