| General > General Technical Chat |
| Hell freezes over... |
| << < (14/15) > >> |
| Karel:
A look into CBL-Mariner, Microsoft’s internal Linux distribution Yes, you read the title right. Hell is freezing because at Microsoft we have our own Linux distribution called Mariner or more exactly CBL-Mariner where CBL stands for Common Base Linux. https://blog.jreypo.io/2021/07/09/a-look-into-cbl-mariner-microsoft-internal-linux-distribution/ |
| duckduck:
--- Quote from: bd139 on July 25, 2018, 08:54:56 pm ---What’s worse is that if you compare it to Linux for example is the documentation stops immediately beneath the powershell and it becomes MSFT internal magic then. Linux it’s manpages all the way down. For ref, we use ISE as the shell. Comes with windows :) --- End quote --- This. Good documentation at Microsoft is getting to be pretty scarce in the past decade. There are tons of "Here's how to get started" and "Follow these steps" and it is very difficult to find information on how things work in order to troubleshoot when things don't go all unicorns and rainbows. One ends up creating many experiments to try to figure out how things work. For Microsoft's SaaS offerings things get even worse. It seems that MS have made the strategic decision to offer no documentation whatsoever that covers how things work. I suspect that this has to do with the fact that MS would love to have you talk to a salesperson about their professional services, or sign up for a Premier Support contract. With the Linux ecosystem, it can tend to be a little bit the opposite, but at least the information tends to be there. Additionally, there are many helpful greybeards, and you can always look at the source code if you care that much. Development is done in public, so the chances of talking to someone that can answer a hard question are much better. EDIT: Microsoft have had their own flavor of debian for years that they run on the SDN switches in their datacenters. |
| bd139:
Indeed. We had some trouble last week because we're trying to auto-deprovision users from Azure AD and it turns out that the native API and GraphQL ones aren't logically consistent :palm: At the same time, let's tar and feather Amazon too. Their documentation is far worse and some of their stuff is completely broken. I was on a presentation the other day with some very senior AWS folk and managed to break their demonstration pretty badly. The key metric for software is how the vendor reacts. Amazon had it fixed double-quick, within 48 hours. I've had to keep support cases open for nearly a decade with Microsoft who failed to issue anything past a registry hack. With Linux it's much much much worse. It can be a complete minefield. If you look at the sheer amount of quality control work that goes into a Debian release you'll understand this. A lot of the upstream vendors are unresponsive or plain asshats. On top of that any problems that span an interface boundary between two applications (DBus is a good one) turns into a shit slinging match. I used to contribute patches to things but gave up around the time github started gaining in popularity as the public record for patch acceptance is pretty poor. Maybe a 25% hit rate on getting a merge. 75% of patches fall on silence, rejection or politics and I quite frankly don't give a shit about any of that these days. |
| Mr. Scram:
--- Quote from: bd139 on July 13, 2021, 04:24:19 pm ---Indeed. We had some trouble last week because we're trying to auto-deprovision users from Azure AD and it turns out that the native API and GraphQL ones aren't logically consistent :palm: At the same time, let's tar and feather Amazon too. Their documentation is far worse and some of their stuff is completely broken. I was on a presentation the other day with some very senior AWS folk and managed to break their demonstration pretty badly. The key metric for software is how the vendor reacts. Amazon had it fixed double-quick, within 48 hours. I've had to keep support cases open for nearly a decade with Microsoft who failed to issue anything past a registry hack. With Linux it's much much much worse. It can be a complete minefield. If you look at the sheer amount of quality control work that goes into a Debian release you'll understand this. A lot of the upstream vendors are unresponsive or plain asshats. On top of that any problems that span an interface boundary between two applications (DBus is a good one) turns into a shit slinging match. I used to contribute patches to things but gave up around the time github started gaining in popularity as the public record for patch acceptance is pretty poor. Maybe a 25% hit rate on getting a merge. 75% of patches fall on silence, rejection or politics and I quite frankly don't give a shit about any of that these days. --- End quote --- Asshats, egos and politics in the Linux sphere? I'm shocked. |
| Karel:
Facebook, Google, Isovalent, Microsoft and Netflix Launch eBPF Foundation as Part of the Linux Foundation https://www.linuxfoundation.org/press-release/facebook-google-isovalent-microsoft-and-netflix-launch-ebpf-foundation-as-part-of-the-linux-foundation/ |
| Navigation |
| Message Index |
| Next page |
| Previous page |