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.<p>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.<p>I worked on a project that was on an island, and while it was more efficient than normal IBM dev, it was still 10x slower and tons of red tape then what was required to make a competitive product (and stay competitive). IBM is big and ultimately has to protect themselves - IMO ultimately it gets in your way of making a good/competitive product.<p>I like what StrongLoop does for the node community, and I do indeed hope you are successful and nothing changes. But to be honest I am very skeptical.
As 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.<p>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).
> <i>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:<p>Linux
OpenStack
Cloud Foundry
Docker
plus many Apache projects like Spark, Cordova and Hadoop
and of course, Node</i><p>They are? (keyword => "leading")<p><a href="https://github.com/docker/docker/graphs/contributors" rel="nofollow">https://github.com/docker/docker/graphs/contributors</a><p><a href="https://github.com/apache/spark/graphs/contributors" rel="nofollow">https://github.com/apache/spark/graphs/contributors</a><p>I find this claim dubious. Maybe I'm not digging hard enough.
From the customer side - I dealt with Netezza and Softlayer before and after IBM acquisition. In both cases an almost palpable drain in support and intelligence. I hate to say it like that as i know that there are brilliant folks in IBM (Watson, etc)<p>Softlayer and Netezza in different ways were smart, nimble and fearless companies. You had real relationships with the engineers. I got to know Netezza folks in Massachusetts, Poland and Australia - some of the smartest folks I've met. They shared scripts and passionate expertise.<p>IBM took it over and the bureaucracy set in. The term "TAM" brings tears of rage to my eyes... Opening a support ticket is about as hard as applying for a mortgage online. And they want to have these endless conference calls with 7 or 8 folks from their side. And nothing gets done.<p>I am embarrassed about the way I have acted on these calls. I have called folks out and out liars. I have screamed at and bashed conference phones.<p>Maybe it would have been better if I hadn't known the Netezza folks - they were good.<p>And Softlayer...<p>I used to be able to call a guy down in texas and after a 20 minute phone call have a cluster of servers ordered. Once did a hadoop cluster this way. Go off and have lunch come back and the servers would we ready by the afternoon.<p>And now: 2 major outages in the past 2 months. No communication - in both cases entirely their fault. Power failure and network misconfig causing an arp storm. Ignored for hours while we submitted tickets and called support... Nightmare.<p>And an absurd situation where their security dept threatened us with taking an haproxy server offline due to a clean-mx false positive - even after the tireless guy running clean-mx emailed to that effect...<p>It became apparent in the discussions following this event that the TAM and sales support which has had our account for years, knew nothing about our business.<p>Just horrible bureacracy and bad service.<p>So I have had really negative experiences with 2 IBM acquired companies. Hopefully it will be better for StrongLoop.<p>For anyone affected - watch for the good folks shedding off.
I 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.
If you're trying to relieve fears, the first paragraph does not help.<p>"IBM has identified Node.js as an important part of the future of enterprise middleware and StrongLoop’s technology and expertise as pivotal to their strategy to help companies fully unlock the value of their existing IT investments and legacy data with APIs."
Recently I got heavily into node-red[0] after playing with a ti sensortag[1], and I'm really amazed at what it can do, and that it is open source and actively used by IBM in bluemix.<p>Now they acquired another heavy weight in the js world, I wonder what is their next step.<p>On a side note, to the audience: have you looked at node-red, what do you think of it?<p>[0]: <a href="http://nodered.org/" rel="nofollow">http://nodered.org/</a>
[1]: <a href="http://www.ti.com/sensortag" rel="nofollow">http://www.ti.com/sensortag</a><p>ps. if you run node-red locally note by default it is insecure, you need to setup the config. But really it is a must try!
Congrats , I know nothing about "modern" IBM but it seems like they are trying interesting things with Bluemix. Let's see what happens next.
This announcement fits along with Node.js 4.0's release containing a commitment to an 18-month roadmap in giving Node.js a greater maturity.<p>As much as I like to think I have chosen Node.js purely for its merits, having a wide community who adopts a platform brings a few perks:<p>- Hiring developers requires less of a gamble on their part. Elixir looks very promising and probably has a lot of advantages over Node.js thanks to it's Erlang foundation but it makes it harder to assemble a team—I hope this changes as I wish the Erlang/Elixir folks all the best.<p>- There is a great amount of wealth contained in the package repository NPM. Before Node.js, this was a great strength of Perl's CPAN (and TeX' CTAN before that).<p>- Having large organizations adopt a platform will eventually increase OSS contributions.<p>I could be mistaken but I don't see Node.js following the bureaucratic of Java's JSR if it continues to adopt a lean and mean approach akin to UNIX tools (do 1 thing well).
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).
If IBM screws ExpressJS up (wishfully not), Hapi[1] is a good alternative.<p><a href="https://github.com/hapijs/hapi" rel="nofollow">https://github.com/hapijs/hapi</a>
> <i>Making sure that Node.js is a first class citizen on Softlayer and BlueMix</i><p>BlueMix is a Cloud Foundry installation. Is there a separate BlueMix-specific thing that is distinct from the Node.js buildpack?[0]<p>[0] <a href="https://github.com/cloudfoundry/nodejs-buildpack" rel="nofollow">https://github.com/cloudfoundry/nodejs-buildpack</a>
It is hard to say what this means at this stage...<p>IBM develops products that it acquires based on where IBM needs the product to go. Sometimes that matches where the user community wants it to go, sometimes it does not. But they will put resources behind it, and it will change - we just need to give it time to see what direction that change takes things.
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.
What node.js needs is a better way to manage packages. Right now, upgrading can fail with no way to roll back. Also, reproducibility is missing. E.g, it is not easy to download sources, and deploy those exact same sources on different machines.
What's a good book to learn about the new stuff? Async et al..<p>I learnt Python from "Dive Into Python 3", but that hasn't been updated for few years now. Any similar book with recent updates?
I imagine it doesn't mean much beyond some more b2b uses of Node. Node has its own independent governance and nothing about this acquisition changes that.
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 expertise in software can only be a plus I think!