71–80 of 134 posts
"founding members include Bocoup, IBM, Ripple, Samsung, Sauce Labs, Sense Tecnic Systems, SitePen, StackPath, University of Westminster and WebsiteSetup." There's a name missing there I would have expected to see. Starts with M. Mo... mo ... something.
Earlier quoted context omitted.
How can you find the js fragmentation a feature and not a stinking pile of shit? Seriously.
I've never understood this complaint. JS is used everywhere from browsers to servers to native apps to IoT. Does there really need to be One True Framework/Linter/Build tool/etc?Is it really that big a problem that people have made a lot of different tools and libraries because they're solving a lot of different problems?
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.
Earlier quoted context omitted.
The fact that people can contribute is great, the fact that it is impossible to get started in modern JS development without making dozens of seemingly inscrutable choices is not.
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.
Earlier quoted context omitted.
I've never understood this complaint. JS is used everywhere from browsers to servers to native apps to IoT. Does there really need to be One True Framework/Linter/Build tool/etc?Is it really that big a problem that people have made a lot of different tools and libraries because they're solving a lot of different problems?
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.
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 people sharing lots of libraries, right? If other languages don't have the same problem, isn't that just because people aren't sharing as much code?
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/
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…
This gave me the impression that they were focusing on standardizing tools (the "drive broad adoption" part especially).
As for "pushing brands on developers", well... You can't standardize and encourage broad adoption of a technology if you cultivate and support multiple technologies. Maybe two or three, but there is a need to champion a particular technology as the tool developers should adopt. And the JS Foundation seems to be specifically promoting tools of its members where it can.
Of course, if the interpretation that their goal is to encourage standardization is incorrect, then the point is moot.
"founding members include Bocoup, IBM, Ripple, Samsung, Sauce Labs, Sense Tecnic Systems, SitePen, StackPath, University of Westminster and WebsiteSetup." There's a name missing there I would have expected to see. Starts with M. Mo... mo ... something.
And yeah, managing to do this without having ONE of:
* Mozilla * Google * Microsoft * Apple * Adobe * Facebook * eBay
Is just... weird. But they have IBM and Samsung.
A few years ago, some high profile organizations (W3C, Adobe, Facebook, Google, Hp, Intel, Microsoft, Mozilla, Nokia, Opera) came together to try to help standardize the web platform [1](Javascript, CSS, HTML). That was a HUGE failure - because it was driven by business rather than developers. How will the "Javascript foundation" do better? [1] http://webplatform.com
Earlier quoted context omitted.
But that can (and is) solved by either just "picking one of the big ones" and moving on, or by using even more tools layered on top to abstract away a lot of those choices (don't know anything about how to start with react? Just use react-create-app and go from there).
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.
IMHO the sweet spot for picking up new JS tech is about a year or two after it first starts appearing on Hacker News.
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!