fernandofig

I don't actually care about the drama per se at this point either. I mentioned it because, along with the fact that:

• development is not very open (in that only that one guy commits and releases stuff)
• release cadence is very erratic and often lags behind upstream chromium, which is a direct consequence of the previous point
• you mentioned about the guys absence - the first time was some time ago and he was inpatient in the hospital for (IIRC) alcohol abuse, and this absence actually coincided with the drama over the furry and the other stuff, so it took awhile for it to be addressed, which only added more fuel to the fire. The second was just this last couple of months were he was house sitting for his parents (mentioned on the release notes I linked before)

All of this paints a bleak outlook for the long term health of this project, IMO. Which is too bad , because I still think it's one of the better forks of chromium.

Well, Thorium developer stated he intends to support Mv2 past the 2025 deadline. Whether he'll make it, we'll see. It's a one man show, there was some drama involving it in the past, and there's the question of what's the point in maintaining Mv2 extensions support if you won't be able to install them from the store after they're cut off?

Sorry to slightly derail the thread, but I'll probably be on the market for a vertical mouse soon as well, which one do you use / recommend? I've been using Logitech mice for decades now, so I've naturally looked into their options and I'm not quite convinced on the ergonomics of the ones I've seen.

I'm very torn on disco. Season 2 is probably the best (due in no small part that it sets up SNW), but the rest are a chore to watch. Most of them have some neat ideas, but they're badly executed more often than not. They also were too heavy handed with each season arcs serialization, most episodes don't stand on their own, and the writing and consistency is just bad. I just finished the final season, and I'm glad they're done with it so they can put more money on good Trek like SNW - hopefully they don't screw it up eventually.

Here. Tl;dr: He took it private for reasons, should bring it back in a "build it yourself" form later.

Not really new. It's basically LCD without backlight. So, higher resolution GBC / GBA alike screen.

France has a big, big problem with overemphasizing individual politicians over policies.

I think that's a "humans" problem, really, specially in the last few decades.

To the extent that a boss demanding sex in exchange for career advancement, I agree that makes them sex offenders. But those women still have a choice. They making the wrong choice doesn't mean they aren't the victim, but they still should be accountable for their choice.

Apparently it's not that the software is broken, it's that the software being installed breaks Windows Update. There are reports from people that uninstalling StartAllBack, updating the OS, then reinstalling it back (renaming the install executable first) works fine.

As much as being affected by this is frustrating to me (though this is all happening still on the dev channel, so for me it'll be a problem for the future), I understand Microsoft's rationale here. They can't be expected to support every third-party tool that can break the OS, and it's known that both ExplorerPatcher and StartAllBack relies on many hacks using undocumented APIs to work.

In the last few decades that I've been using Windows, I never felt compelled to use shell replacements or customizations - the default experience always worked fine for me with a few tweaks. So, if anything I'm more frustrated at Microsoft that I'm forced to use StartAllBack, because MS went and removed options from the shell that existed forever and always took for granted, and then some.

Not to take Reddit's / spez side, but to clarify, that's not actually what he got in cash - what he got in cash on 2023 was something around 600k.

Those 193mil was in stock. Which kind of explains his drive to monetize users and kick out third-party apps: that piece of paper is only worth that much as long as he can keep the stock value afloat.

Thank you for digging this out. Turns out it's even worse than what I gleaned from my surface-level take.

This sounds like dev sour grapes but what the company was asking them to do seems better from the customer pov and for cyber security I'm general.

As a developer myself (though not on the level of these guys): sorry, but just, no.

The key point is this:

[...] we did not issue CVEs for experimental features and instead would patch the relevant code and release it as part of a standard release.

Emphasis mine. In software, features marked as "experimental" usually are not meant to be used in a production environment, and if they are, it's in a "do it at your own risk" understanding. Software features in an experimental state are expected to be less tested and have bugs - it's essentially a "beta" feature. It has a security bug? Though - you weren't supposed to be using it in a security-sensitive environment in the first place, it sounds perfectly reasonable to me that it should be addressed in a normal release as opposed to an out-of-band one.

We can argue if forking the project is or isn't extreme, but the devs absolutely have good reason to be pissed. This is typical management making decisions without understanding technical nuances and - from what is being told by the devs - not talking it through before doing it.