3 ms·

We only run Linux and use Macs. So powershell isn't an option for us. The SDKs for various languages aren't terribly mature either. I don't think any of them ex

by mdeeks 11y ago

We only run Linux and use Macs. So powershell isn't an option for us. The SDKs for various languages aren't terribly mature either. I don't think any of them except the .NET one are 1.0 yet. Don't get me started on the Beta UI vs normal UI. Some things are only supported in one and not the other and vice versa. I'm constantly being flipped back and forth between the two. Also they are both really unpleasant to use. I get lost a lot.

deleted 11y ago
[deleted]
tracker1 11y ago
It's actually kind of sad that they had a strong initial push to support other languages and platforms, only to let those SDK/API clients wither on the vine so to speak... The github issues on their public repos seem to be mostly unmaintained (several a month or older without an MS representative). On the flip side, there were some issues with connecting to Azure via the node `mssql/tedious` module, which isn't from MS, and a few developers from MS Azure SQL teams stepped up to track down the issue. Learned a bit more about the TDS protocol than I really wanted to that month. It seems to me that MS Azure's development department should either implement a 20-40% time for developers to work on the public stuff and/or documentation as developers desire, or have cowboy teams that do. MS isn't likely to spur more open development efforts as most corporate based projects don't inspire much community involvement. That said, given the choice I might be more inclined to use Joyent, DigitalOcean or Linode for my own stuff... The choice wasn't mine at work, the existing solutions are mostly .Net (some Node) based and Azure was the most pragmatic choice of migration to a hosted solution when that was done almost two years ago. And running anything under Ubuntu VMs with docker on Azure is pretty trivial... Once the next generation infrastracture is in place (a couple months away), it will become easy enough to run anywhere.

by mdeeks 11y ago

deleted 11y ago

[deleted]

tracker1 11y ago

It's actually kind of sad that they had a strong initial push to support other languages and platforms, only to let those SDK/API clients wither on the vine so to speak... The github issues on their public repos seem to be mostly unmaintained (several a month or older without an MS representative). On the flip side, there were some issues with connecting to Azure via the node `mssql/tedious` module, which isn't from MS, and a few developers from MS Azure SQL teams stepped up to track down the issue. Learned a bit more about the TDS protocol than I really wanted to that month. It seems to me that MS Azure's development department should either implement a 20-40% time for developers to work on the public stuff and/or documentation as developers desire, or have cowboy teams that do. MS isn't likely to spur more open development efforts as most corporate based projects don't inspire much community involvement. That said, given the choice I might be more inclined to use Joyent, DigitalOcean or Linode for my own stuff... The choice wasn't mine at work, the existing solutions are mostly .Net (some Node) based and Azure was the most pragmatic choice of migration to a hosted solution when that was done almost two years ago. And running anything under Ubuntu VMs with docker on Azure is pretty trivial... Once the next generation infrastracture is in place (a couple months away), it will become easy enough to run anywhere.