Hmm, that the acquisition would mean anything for node directly seems off. At least, the blog post seemed to indicate that this wasn't meant to be about IBM buying influence. I wasn't a customer and not particularly keen on the enterprise focus of strongloop but I thought you had a really good thing going with loopback. Not sure what to think of it now... I was in a startup that got acquired by a huge multinational and it was shocking how quickly we went from nimble to gridlock.
I wrote that. I didn't mean it literally. It’s a response to Bryan saying that failure to be sensitive to gender issues would be a firing offense at his company. We take it really seriously, and I’d like to point out that two of our senior leaders are women and we are proud to employ talented women engineers. If this remained an issue, I’d need to find a way to rectify it with Ben, and that could get as serious as firing. But he understands now. In the rest of my post I make the point that jumping to firing him publicly was not giving him a sufficient chance nor crediting him for his efforts elsewhere.
You didn't fire him publicly. You only belittled him in public.
> If Ben can’t learn, we’ll fire him. [Edit: See comment below. This is not meant literally.]
Your correction doesn't make the statement much better. This whole debate is about how words matter, and yet your words put him on notice in a public place. All of Ben's friends now know his employer will fire him if he "can't learn." Is he so stubbornly misogynistic that that should be in question?
You could have conveyed the same message by saying "he was following the commit rules, no offense intended, won't happen again" and left it at that.
Yeah, I'm sorry, but you guys have just proven everyone right in criticizing the node.js community as a bunch of arrogant, immature hotheads. What is it with this discussing of firing someone in public?
And please don't tell me you didn't mean it literally. If you're joking or bluffing about firing someone, it's going to make you look even worse.
Don't you remember how everyone viewed that AOL CEO who fired someone in public a few months back? Well, please understand that people view this public threatening of firing in exactly the same way.
For what it's worth, I completely agree with the pull request. But you all couldn't have possibly handled this any worse.
Then you shouldn't have wrote it because most people and every reporter are going to take it literally.
Since pronouns are an issue that you want the node.js community to be correct about, would words with significance in certain cultures also be high on your priority list?
Issac, I realize that you had the best intentions in this, I see that you were trying to put out stupid fires rather than start another one, and I appreciate your willingness to criticize the crass and inappropriate response from Joyent. All that said, and please take it as friendly criticism: your tone towards the developer came across as unnecessarily belittling, and the phrase about firing, even if not meant literally, crossed the line. Yet another post would probably just add fuel to the fire, but I would seriously consider a private face-to-face apology, if I were you. Thanks for listening.
That is good of you. No more questions. Generally I agree with your assessment, however when confronting systemic biases sometimes it's necessary to speak out publicly. However, that can be done outside the context of a particular person-to-person encounter.
It's true that we're intent on serving enterprise customers, but we realize that many developers working on enterprise apps start out with personal project or small department projects and want as much innovation as they can have as long as we can stand behind it. The issue with many platforms is that the vendor doesn't have the long-term ability to stand behind the APIs and offer support. That's important when you get sick of debugging your own platform and you want to debug your app instead.
Power is intended to be a hosted version of the Aeolus capability: configure, update and migrate VMs across different clouds on-prem and off-prem.
We do support Java EE, and we're the only ones to do so right now. Check out the new Java development model called CDI which is part of EE 6 and is a radical simplification for Java while still providing access to nice things like transactions.
Finally, yes you could stand up your own JBoss on EC2, but then you'd have to patch it, back it up, configure all the systems management and load balancing and networking and keep that all up to date, etc. The lovely thing about whichever PaaS you choose is that we do all of that for you.
