Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What the IBM Acquisition of StrongLoop Means for the Node.js Community

strongloop.com

Post reply on HN
Print view View original

41–50 of 136 posts

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#41

Post by granos »

kodablah wrote: post #32
rynop wrote: post #29

former IBM dev here (6 years in different areas). I hope they let you work on an island and don't force you to use their tooling/approve listed of open source software. IBM has long embraced the OSS community (I loved LTC), but the process to release/use anything OSS was not good (to put it nicely) and was one of the many reasons I left. I worked on a project that was on an island, and while it was more efficient tha…

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.

I hope it works out for StrongLoop. When a company I worked for was purchased by IBM, about 3/4 of the engineering staff left once we heard about "Work Life Integration (tm)". It's really hard to work inside Big Blue when you are used to the freedom provided by a small company.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#42

Post by ramigb »

Just 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.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#43

Post by mkozlows »

kodablah wrote: post #32
rynop wrote: post #29

former IBM dev here (6 years in different areas). I hope they let you work on an island and don't force you to use their tooling/approve listed of open source software. IBM has long embraced the OSS community (I loved LTC), but the process to release/use anything OSS was not good (to put it nicely) and was one of the many reasons I left. I worked on a project that was on an island, and while it was more efficient tha…

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.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#44

Post by rynop »

kodablah wrote: post #32
rynop wrote: post #29

former IBM dev here (6 years in different areas). I hope they let you work on an island and don't force you to use their tooling/approve listed of open source software. IBM has long embraced the OSS community (I loved LTC), but the process to release/use anything OSS was not good (to put it nicely) and was one of the many reasons I left. I worked on a project that was on an island, and while it was more efficient tha…

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)?

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#45

Post by nickpsecurity »

OldSchoolJohnny wrote: post #27

IBM recently bought out Softlayer hosting and support went from great to glacially slow and all but uncaring in about 28 seconds.

Damnit! That's one of the companies I found searching for a physical version of cloud hosting. Looked promising. Now they're IBM. (sighs) Going to have to delete them from my bookmarks...

Sucks that IBM has this effect. If they didn't, esp if had opposite effect, they could be the biggest and most awesome tech company in existence.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#46

Post by murukesh_s »

vidarh wrote: post #31
BowBun wrote: post #8

This has some awesome implications for open source. If a huge company like IBM openly supports and dedicates resources to FOSS, I think we can expect these products to get way more attention and receive the full treatment of corporate testing and development which would really offset the ephemeral nature of projects like Node. Not saying the current foundation guys aren't doing a great job already, but IBM's expertis…

IBM has been an open source supporter for a long time. Their first Linux kernel contributions came no later than '99 (when they started upstreaming changes to support Linux on their mainframes, available since 2000). You can see some details about their open source contributions here: http://www-03.ibm.com/linux/ossstds/oss/ossindex.html

And Eclipse.. When it was open sourced, it was one of the largest project to be open sourced.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#48

Post by NDizzle »

rogerthis wrote: post #6

Once I worked in a project which IBM was also involved. And everything in IBM related to that project was slow, very slow.

Yep. Same here. IBM contract in one of our huge data centers. (This was for a large accounting firm.)

The process to get a new blade installed in one of our chassis took 6 months.

Re: What the IBM Acquisition of StrongLoop Means for the Node.js Community

#50

Post by cdnsteve »

If anything this is a strong validation of Node.js in the enterprise space. This is actually good news for anyone working within the enterprise trying to use a different technology set. It makes selling Node to a CTO a bit easier (even if you choose not to use StrongLoop).
Post reply on HN