Earlier quoted context omitted.
I don't get it and await an explanation
This is starting to look like Reddit.
Nothing wrong with a little bit of humor, imo. It's not like a thread is full of puns.
What the IBM Acquisition of StrongLoop Means for the Node.js Community
51–60 of 136 posts
Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community
#52Just a question -might be dumb- is the merger of io.js and node.js which happened a couple of months ago related to this news in anyway? Anyways IMHO this good news and I hope it will make node.js much better, who knows maybe replace V8 with something even better.
I can't imagine it wouldn't be. This kind of decisions aren't made very quickly. I'm more curious if the IO team was aware of this...
Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community
#53> And it’s not just Node.js. Maybe you haven’t looked at what IBM is doing with open source lately. I was surprised when I dug in. For example, did you know they are leading contributors to: Linux OpenStack Cloud Foundry Docker plus many Apache projects like Spark, Cordova and Hadoop and of course, Node They are? (keyword => "leading") https://github.com/docker/docker/graphs/contributors https://github.com/apache/spa…
What is it about these posts that bring out the HN contingent who think themselves firebrand skeptics? This is basically a marketing piece, what good is fact-checking it
A little more honest marketing would do the world some good. I'm all for having someone check and call out bs where it is found.
Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community
#54> And it’s not just Node.js. Maybe you haven’t looked at what IBM is doing with open source lately. I was surprised when I dug in. For example, did you know they are leading contributors to: Linux OpenStack Cloud Foundry Docker plus many Apache projects like Spark, Cordova and Hadoop and of course, Node They are? (keyword => "leading") https://github.com/docker/docker/graphs/contributors https://github.com/apache/spa…
What is it about these posts that bring out the HN contingent who think themselves firebrand skeptics? This is basically a marketing piece, what good is fact-checking it
> This is basically a marketing piece, what good is fact-checking it
Not sure about the US laws, but here in Germany, all marketing claims must stay to the facts, or the company can be sued.
(Which is why most marketing speak uses fuzzy terms that sound nice but don't convey any information. But that's a general trend anyway.)
Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community
#55Earlier quoted context omitted.
Current IBM dev here (but only speaking anecdotally for myself and my project), can confirm that when we were acquired they let our product and policies remain and did not "blue wash" the project. I would assume the same will occur for StrongLoop and their software practices will probably continue mostly unfettered.
Curious - how long ago did they acquire you? Your software get rolled into an IBM product or is it self standing? They let you continue to use your productive tools (asana,github,slack etc)?
Current IBM Dev here. I know several IBM teams that use slack & github. There should be no problem with that.
Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community
#56Earlier quoted context omitted.
Current IBM dev here (but only speaking anecdotally for myself and my project), can confirm that when we were acquired they let our product and policies remain and did not "blue wash" the project. I would assume the same will occur for StrongLoop and their software practices will probably continue mostly unfettered.
Were you really left alone, though? As in, not even forced to use Lotus Notes? Because even that kind of small-bore enterprisation can destroy the culture of a small tech-focused company.
About your point about Lotus Notes: I interned at IBM 3 times, and was never forced to use Lotus Notes. No one whom I worked with at IBM used Lotus Notes either. We used either Open Office or MS Office.
The most popular IBM software we used was SameTime for instance messaging and it was actually not bad at all.
Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community
#57As much as I fear this will drag StrongLoop, I feel that this is an excellent fit. StrongLoop has been focused on building "Enterprise" tools and module around node, as well as working on whitelisting/reviewing various modules... This is a good fit for IBM and their clients who are inclined to also want to have "approved" or "certified" modules to be able to use separately from the rest of npm.
As much as I like the power/openness of npm, a lot of corporate environments move more slowly... modules need to be cleared by legal and usually limited to specific versions. Having more resources to do this is a good thing and can only help people who are working for financial institutions (as an example).
Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community
#58I used to work with an old IBMer who used to say "it's no accident that IBM nearly collapsed at the same time as the Soviet Union did". Lou Gerstner famously rescued IBM from oblivion by turning it into a consultancy led company, and moving the focus away from mainframes. This is just a case of IBM snaffling up the latest cool thing so they can sell consulting services.
> the Russian decision in the late sixties to develop as their next national computer series a bit-compatible copy of the IBM 360 —the greatest American victory in the cold war!—.
https://www.cs.utexas.edu/users/EWD/transcriptions/EWD05xx/E...
Your quip reminded me of the above quote from Dijkstra!
Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community
#59Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community
#60Earlier quoted context omitted.
What is it about these posts that bring out the HN contingent who think themselves firebrand skeptics? This is basically a marketing piece, what good is fact-checking it
> This is basically a marketing piece, what good is fact-checking it Not sure about the US laws, but here in Germany, all marketing claims must stay to the facts, or the company can be sued. (Which is why most marketing speak uses fuzzy terms that sound nice but don't convey any information. But that's a general trend anyway.)
Es musst die Wahrheit sein!!!