A Look into CBL-Mariner, Microsoft’s Internal Linux Distribution

Post by ubermonkey » Mon, Jul 12, 2021, 5:11 PM UTC

beebmam wrote: post #46

azinman2 wrote: post #43

Earlier quoted context omitted.

Meanwhile no one at Apple is using windows unless they have to for very specific software.

That's unfortunately their loss in my opinion. Windows has a pretty awesome development story, far better than Apple's authoritarian hold on what software can be run and distributed for that platform. Moreover, gaming is great on Windows, and always has been, and WSL2 is extremely slick.

Post by ubermonkey » Mon, Jul 12, 2021, 5:13 PM UTC

jorvi wrote: post #98

jorvi wrote: post #65

Earlier quoted context omitted.

You can literally just right click and press 'open'. Might not be obvious to the layman, but you don't need to do a whole code signing bypass song and dance.

I can't edit my comment so I'll just put this here: what is up with HN heavily downvoting factual, useful information? It seems something from the past 1-1.5y or so and it infuriates me to no end.

Post by mdaniel » Mon, Jul 12, 2021, 5:49 PM UTC

josephg wrote: post #10

l0b0 wrote: post #4

It seems almost inevitable that Windows will eventually become a Linux distro. Microsoft could replace incredibly resilient cruft like NTFS with EXT4 or ZFS and the registry with human readable configuration files. On the other hand, they could replace Bash with PowerShell and hopefully pressure various orgs to adopt some sensible subset of configuration formats.

I understand a lot of the benefits of ZFS and Powershell. But whats wrong with NTFS? Can you talk a little about the relative strengths of NTFS vs EXT4?

Post by 908B64B197 » Mon, Jul 12, 2021, 7:21 PM UTC

discordance wrote: post #42

vermilingua wrote: post #35

A MS dev writing a blog on building MS’ own distro of Linux on his _Macbook_ must have Ballmer sweating bullets.

Many people at Microsoft use Macs. It’s not a big deal.

Post by nyanpasu64 » Mon, Jul 12, 2021, 9:19 PM UTC

VortexDream wrote: post #86

nyanpasu64 wrote: post #47

Earlier quoted context omitted.

Editing the registry never results in corrupt unreadable intermediate states, unlike writing to config files. A workaround is "atomic save" (where one app writes to a different filename and renames it over the original). This ensures you'll never get torn reads (I think the Windows registry doesn't support transactional/atomic updates of multiple values at once), but you lose permissions and symlinks or something lik…

Have you never experienced an unbootable system because of a corrupted registry? It's unfixable. And I'm not saying it happens when manually editing the registry. It might happen when Windows crashes at the wrong time and the system is in the middle of modifying it. It's quite failure-prone and I'm surprised it hasn't been improved much over the past decades.