91–100 of 134 posts
Shocking how the javascript community has done just fine before this group of well funded enterprises organized and nominated itself as leader of that community. This is an attempted capture of a major open source community by commercial interests.
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.
But for significant pieces of work it is still a hurdle which you must cross. Unless you're writing vanilla ES5 without any dependencies, you have to consider package management, build tools, how to load your modules, before even getting onto transpilation, minification etc. I can see what's so great about the JS community, but the fixed cost to get to actual production-ready development is pretty high. And rolling y…
Earlier quoted context omitted.
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.
> Such is life in programming. Actually no, the technology churn is much higher in JavaScript-land than most anywhere else.
If we look at this announce:
* the jQuery foundation (jQuery + jQuery UI) becomes the JS foundation (jQuery + jQuery UI + IBM + Samsung + unknown companies)
* the list of founding members is awkward. IBM to unite the JavaScript community? IBM is the company who creates things like JSONx [1]. These founders have done nothing for the web, for JavaScript or for the open source community. Where are the main actors like Facebook, Google, Microsoft or Netflix?
This new partnership is an attempt to gain visibility by companies that are non-existent in the JavaScript community.
To be clear: the JS foundation will not make the JavaScript ecosystem finally less fragmented and more standardized (the common complaints on Hacker News).
[1] https://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com...
Earlier quoted context omitted.
That's because "modern javascript" is not there yet, it's still in an experimental phase, we need transpilers and other stuff to use features that are not in a finished state. It will get better with time.
So when is Javascript not going to be in an experimental phase? A couple of years ago it would have been 'when browsers support ES6'. Now it's 'when browsers support ES7'. Next year it's going to be 'when browsers support ES8'.
But, most of experimentation isn't around the core ECMA features. The experimentation is happening around the toolchain, the libraries, the frameworks, etc. which are separate from stuff like ES6.
Earlier quoted context omitted.
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.
> Such is life in programming. Actually no, the technology churn is much higher in JavaScript-land than most anywhere else.
Earlier quoted context omitted.
Exactly this. All of the upfront choices, will I make the right choice? I've been meaning to jump in and learn. After years of backend development (C#, Python, and some Go), I want to give JS a shot and at least experiment. It's a daunting process that I keep pushing back as there is no immediate need.
The best thing to remember is that if you're doing it for fun and learning, you don't need anything but a plain old HTML5 and a plain old script tag. Once you feel you need something more than that for a particular project (or for work) you'll be better able to evaluate what's out there. // get started!
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.
But for significant pieces of work it is still a hurdle which you must cross. Unless you're writing vanilla ES5 without any dependencies, you have to consider package management, build tools, how to load your modules, before even getting onto transpilation, minification etc. I can see what's so great about the JS community, but the fixed cost to get to actual production-ready development is pretty high. And rolling y…
Earlier quoted context omitted.
I think the problem is keeping up. It's simple if you can pay attention, but if you're still on angular 1.x because you have other things to worry about, the fragmentation and pace means you can get years behind if you're not careful. It's not like ruby has another package manager every 6 months. I agree the many implementations probably are a feature, not a bug, but still induce fatigue. It's too easy to get behind.
Maybe I'm missing something really fundamental, but why try to keep up with everything? It's a huge ecosystem and any given dev/team can only use a tiny bit of it. If a library does everything you need it to, does it matter if you're years behind on it? (modulo e.g. security fixes) I mean, certainly I agree that trying to keep current on everything would be a nightmare. But surely that's just the result of lots of pe…
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…
It's not just "their own tools"[0]. webpack moment jquery mocha lodash eslint grunt [0] - https://js.foundation/projects/
In the end, I just don't think it's a great list... webpack, moment, lodash, sure... but jQuery UI, really? I mean bootstrap is a bit long in the tooth today, but still very modern in terms of structure. lodash is setup in a way that you can pick only the parts you need/want... but a lot of these tools just aren't what you probably want to be using starting a project today.