6 ms·
You're right, you shouldn't let that overshadow the Chrome team's commitment to open source. You should maybe let the fact that Chrome is closed source overshad
by mort96 8y ago
You're right, you shouldn't let that overshadow the Chrome team's commitment to open source. You should maybe let the fact that Chrome is closed source overshadow the Chrome team's commitment to open source.
- skybrian 8y agoYes, it's true that Chrome has closed-source components. Meanwhile, Chromium is still available. Node and Electron wouldn't exist without having Google's work to start off with, as a base for the work of many others. (Though of course Google was building on the early work at Netscape, and some features of web standards were invented at Microsoft, despite IE not being open source at all). This way of building on the work of other people (hopefully giving due credit) is how open source is supposed to work. It doesn't mean Google can or should do everything for the community; if we don't like the direction Google is going we need to do some of the work ourselves.
- pjmlp 8y agoI actually given that I have to deal with apps that should have been web based, but are not, 'cause dev convenience. And having to untangle npm based builds to what used to be a simple set of scripts and HTML includes, because many JavaScript libraries assume a node based deployment and nothing else. With those outcomes I do not consider it a good result.