fernandofig

joined 1 year ago
[–] [email protected] 14 points 3 days ago (4 children)

Thing is, ME as an idea made sense. Win2K wasn't targeted to consumers, XP was in the pipeline for that, but they needed an interim version until it was ready. It looked like Win2K, but ostensibly compatible with the Win9x line. They just fucked up the execution on the internals, so it was terribly unstable.

Windows 8 had the opposite problem: it improved on Win7 internals, so it was solid, but had a terrible UI that no one asked for.

One could argue that the reason ME failed was very possibly because it was rushed. Win8, on the other hand, looks very much like designed by comitee with either very misguided designers or marketing people at the helm. Because of that, Win8 feels like a much worse failure to me.

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago)

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.

[–] [email protected] 10 points 1 week ago (2 children)

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?

[–] [email protected] 7 points 3 weeks ago (5 children)

Ok OP, I've been seeing your posts here and they almost always seem to have an anti-west take on things. I try to read news from both sides of the aisle and make my own conclusions, so I'm genuinely curious: why do you think Ukraine should roll over and hand over their lands to Russia, or alternately, why is Russia justified in this war (that apparently they did provoke)?

[–] [email protected] 1 points 3 weeks ago

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.

[–] [email protected] 6 points 3 weeks ago (1 children)

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

[–] [email protected] 7 points 1 month ago (2 children)

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.

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (1 children)

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.

[–] [email protected] 17 points 6 months ago* (last edited 6 months ago) (3 children)

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.

[–] [email protected] 4 points 6 months ago

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

[–] [email protected] 27 points 6 months ago

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.

[–] [email protected] 2 points 7 months ago

Good. We think alike 👍

7
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
 

Sorry to be that guy, but looks like the alternate UIs are offline again. And btw, on status.reddthat it says old.reddthat (which I use) has been offline over a month, which is not correct :-)

7
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

See title. I've checked the announcements community and here, but couldn't find anything mentioning this. I normally use old.reddthat, so I initially noticed the problem there, but then I looked into voyager.reddthat and alexandrite.reddthat and they're giving out cloudflare errors too. www.reddthat still correctly opens voyager though, so maybe it's just a DNS issue?

1
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

I'm not sure if that's only on Reddthat and 0.18 servers (I'll go check out my account on beehaw now), but I'm getting shown posts very near the top of the list from, like, 20-30 days ago, sometimes even going as far as a year or two ago. They haven't that many upvotes or comments either. Anyone seeing that?

view more: next ›