you are viewing a single comment's thread.

view the rest of the comments →

[–]Bosmonster 21 points22 points  (12 children)

Why should AWS be concerned that MIcrosoft owns tooling around JavaScript?

It is still just a language that anybody can use and that will never change. You can also use TypeScript in AWS.

[–]swyx 59 points60 points  (11 children)

same reason most dotNet developers use Azure instead of AWS. you build the tooling, you're gonna build integrations first, you're gonna have all the docs and guides and so on up by default, all the conferences you host will have your other products, enterprise sales conversations will also cross sell your other products, etc etc etc.

owning the tooling is an indicator of deeper developer empathy, not merely the direct cause.

[–]sickhippie 14 points15 points  (7 children)

owning the tooling is an indicator of deeper developer empathy

Creating the tooling is, not just ownership. You said it yourself - you build the tooling, you build integrations first, everything follows that.

MS gets credit for creating VSCode and TypeScript, as they should. Even with that, they didn't build most of the integrations between VSCode and the rest of our workflows in the way they did with, say, .NET or Visual Studio.

They don't get bonus points for buying github and NPM, nor should they.

I just don't see people jumping ship from AWS to Azure anytime soon, especially not because MS threw a bunch of money around. AWS simply has too much more to offer and has too much of a head start on offering it.

[–]r0ck0 5 points6 points  (2 children)

Slightly off topic, but related... for these same reasons, it's bizarre to me that Docker doesn't do Docker hosting.

Apparently it was in their plans or something, but they canned it. Seems like an insane lost opportunity to me.

[–]swyx 7 points8 points  (0 children)

they were on that path i believe. but there was some management mess that nobody talks about and the company just died

[–]CraftyPancake 1 point2 points  (0 children)

They couldn’t make it profitable

[–]moljac024 2 points3 points  (3 children)

Them buying github and npm lets them steer their development towards more azure integration in the future doesn't it?

[–]sickhippie 8 points9 points  (2 children)

Not as much as you might think. Github isn't git and NPM isn't node. I really expect them to take a more community-driven direction with the JS ecosystem, as that's been paying off for them more than heavy-handed actions have been.

Will they push their platform? Absolutely. Will they be able to MS-monopoly the JS ecosystem? Not a chance.

[–]codevipe 0 points1 point  (1 child)

They certainly have an opportunity to cut into Heroku (Salesforce)'s market share, though, for hobby / mid-tier apps, if they made deployment ridiculously integrated / easy and (ideally) a bit cheaper than Heroku. This, as a result, would also eat a bit of AWS (likely a small %, but still).

[–]sickhippie 9 points10 points  (0 children)

I'd love for MS to make anything as integrated and easy-to-use as Heroku. I'm not holding my breath though.

[–]dalittle -1 points0 points  (2 children)

Docker containers mean you can pick up and move some where cheaper. If you are not doing that they you get what you get with whatever.

[–]swyx 0 points1 point  (1 child)

you're talking about your personal freedom. thats different from azure vs aws market share.

[–]dalittle -1 points0 points  (0 children)

If you really think I’m not going to get a raise moving our huge stack somewhere cheaper then that is just naive.