genthree

I believe Zuckerberg has a term for people who willingly break online anonymity because someone with a domain name and website asks them to.

Last I checked, every distro of note had its own patchset that included stuff outside the vanilla kernel tree. Did that change? I admit I haven't looked at any of that in... oh, 15 years or so.

> "Wow that company has so many employees and yet, in practice, does so little"

Some of it is real need for things like support, payments, and compliance in a bunch of languages and jurisdictions and across a bunch of platforms and combinations of platforms.

A lot of it's just that large businesses tend to be shockingly inefficient, often taking literally many hundreds of person-hours to do things that a small company or small team might do in low-tens. Coordination costs are high, processes are often really bad in ways that nobody who could fix them is empowered to, serious principal-agent problems are the norm rather than the exception, et c.

One of the weirdest things to me about the AI craze is that I don't see how it fixes organizational problems, and most big orgs are already burning more cash on waste due to those than they could possibly gain from fairly-optimistic LLM gains. Like, if they wanted to 5x development speed, they already can without a single LLM involved, by managing better. They could have done that ten years ago. All the more wild that they're flipping out over LLMs. You can't even come close to efficiently organizing the resources you already have...

Anyone on Bedrock Minecraft is probably there for the cross-platform multiplayer. The Java version doesn't substitute for that. (MS made Bedrock and Java incompatible so they can rent-seek on closed mod and server-hosting "marketplaces"; can't let people share things and have fun without paying a middleman after all, think of the wasted "productivity"!)

I value performance and stability highly, and Apple's productivity programs are so light I can leave them open in the background and forget they're running for months at a time even on fairly old, weak machines. And I'm not sure I've ever seen any of them crash (I can't say the same about, say, LibreOffice or pretty much any other Linux-associated productivity software). That they're a ton more polished and stable than things like Abiword or Gnumeric, and have most modern features I'd expect (even live collaborative editing) puts them solidly above those other light options.

I hate modern MSOffice's UI, plus it's full of slow, heavy webtech which deducts a lot of points from basically anything for me. Google's leaks memory (like most of their software... so do Gmail tabs) and is so slow that it introduces a ton of input latency, which drives me nuts, I hate to type in it, aside from my experience with most of its formatting and editing features being that they're very janky even by the standards of GUI word processors. Both are very heavy on resources, which means they have a huge hurdle to overcome on the feature side before I'd consider them anything but extremely-unpleasant.

Old (like... '00s) MSOffice is pretty good because it's not such a resource hog, and the UI used to be really good.

Apple's office suite is my favorite I've ever used, and it's not close.

After that, old copies of MSOffice.

Next-best would be a hodgepodge of the lighter options on Linux and such. Gnumeric, Abiword, that sort of thing. Not great, but at least they're light on resources and easy to use.

Distantly after that, LibreOffice.

Then, modern MSOffice in last place.

The only reason I'd count any of them as "worse" than modern MSOffice is that ~perfect office compatibility and a bulletproof excuse when things go wrong ("I'm also using MSOffice, don't know why your document isn't working") is non-negotiable in any business context.

[EDIT] Oh I forgot about Google. That's actually the true last-place. Modern MSOffice isn't worse than that. Christ the performance is awful.

Been auto-hiding the taskbar since Win 95, and feel the need for the feature all the more with the macOS dock. I doubt I’ve spent a collective hour without auto-hide on the dock in more than a decade of macOS :-)

Oh, I was there for a good deal of it. Win 3.1 was my first GUI OS. Remember wacky compositor add-ons to x-window to get the wobbly windows and the really good transparency that doesn’t wait for you to stop moving the window to update, on Linux.

All those moments will be lost in time, like tears in the rain.

I’m on macOS, it’s where I started working this way… uh… 12ish years ago.

Still using Spectacle for window management, despite its being long-discontinued. Still works, never a problem or glitch at all.

I sort of miss when my way of using GUI desktops involved the wallpaper sometimes being visible. These days It’s all quarter/half/full windows that rarely close, and certainly are never minimized.

The entire point of any such system is the latter thing anyway, regardless of how you go about it. I mean the higher-level point, like “why do we have any system at all?”

Yes, it’s different if you live in the actual country. “For most”

Carter: “This energy crisis shows us how vulnerable we are to foreign autocrats. We should work toward energy independence via renewable energy and waste reduction, to lead the world away from this risky and unsustainable fossil fuel market and secure ourselves a brighter future.”

America: throws a decades-long, ongoing tantrum

It’s fairly reductive… but still kinda true.

I once read a claim that once you remove the distance that exists between places because of cars (large set-backs, unusable "green space", wide freeways including the medians and buffer around them, giant parking lots, et c.) cars are only an improvement for most car owners for day to day travel before a city adjusts to widespread car ownership, and adds all that stuff. Add in the time you spend working just to pay for the car (depreciation, fuel, insurance) and it's not a great deal at all. After that, it's only consistently a benefit if you can afford a driver. For most, it's a wash with bicycling, if not worse (in the hypothetical world that hadn't bloated way apart to account for tons of cars) except now you also need to schedule separate time to work out to stay healthy.

This seemed implausible, so I ran the numbers for my situation at the time that involved car costs and a commute distance that were both below median for my city, plus well above-median household income.

Sure enough! It worked out just the way they claimed, if only barely. For the median worker in my city though, it was very true.

I find avoiding legible and most "graphic" clothing, period, works great.

Plus it usually looks better.

Not sure why you need any flag on you.

> There are of course exceptions like critical medical applications and rocket/missile guidance systems but as a general rule code quality is only a problem when it inevitably bites you much farther down the line, usually when customers start jumping ship when it's obvious you can't scale or reach uptime contact targets.

My experience is it hits both new-feature velocity and stability (or the balance between those two) really early, but lots of managers don't realize that this feature that's taking literal months could have been an afternoon with better choices earlier on (because they're not in a position to recognize those kinds of things). For that matter, a lot of (greener) developers probably don't recognize when the thing that's a whole-ass project for them could have been toggling a feature flag and setting a couple config entries in the correct daemon, with better architecture, because... they don't even know what sort of existing bulletproof daemon ought to be handling this thing that somehow, horrifically, ended up in their application layer.

So the blame never gets placed where it belongs, and the true cost of half-assed initial versions is never accounted for, nor is it generally appreciated just how soon the bill comes due (it's practically instantly, in many cases).

I don't see any reason to doubt that plausible-next-token-guessing could sometimes plausibly-next-guess a sequence that happens to decode to the answer to some question we'd not yet solved.

... it'd be even more likely if, as other have suggested in this thread, we actually had recorded the answer in writing but nobody had noticed it yet, say, but even without that I don't see why it couldn't happen.

That it tends to become a caste system with extra steps (which steps provide a defense of the system as “fair”) is one of the chief criticisms of meritocracy (and criticism of the idea is where we got the term itself)

Yeah, it’s great.

No choice.

> Can I ask which version of iOS was perfect in our mind?

6.

For little utility apps where you don’t care to deviate from UI default appearance and behavior (and, as a user, it’s much better if you don’t anyway, though it’s very trendy to make UX worse by customizing everything) iOS and Android both are dead simple, very easy to write and maintain a utility app for either of them.

An enormous amount of the cost of developing a lot of native apps is customizing the appearance and behavior, to match some slide deck mockup or to make it “on-brand” or whatever. It’s better for the user, and way cheaper, if you just… don’t do that. Hell a lot of common UI elements are easier in native than web if you just don’t try to customize them a ton (data-backed tables and list views and such are sooooo nice)

Functional websites would be wonderful.

Instead we get “webapps”.

I was under the impression that some of the anti-screen-tearing and other features in Wayland unavoidably set a higher (and, higher-enough to be noticeable in some contexts) floor on latency, though, because of how those features necessarily work. I don't mean drivers.

I think a lot of folks don't consider that each child comes with a high-enough-to-worry-about risk of negatively affecting the life of everyone in your family to a level on par with one of the adults in your family becoming permanently and severely disabled relatively early in life.

Yeah sure we also risk some micromorts and the life-altering-disability equivalent every time we drive a car or get a sunburn, all right.

It also used a large multiple more memory than Alsa + basically any existing plausible combo of mixer software on top of alsa. While doing nothing. For no clear reason. And chewed processor cycles, while doing nothing. Back when 50MB was a meaningful amount of memory, and most machines were still single-core.

It was plainly really poorly-architected, just looking at its resource use patterns made this obvious in a heartbeat.

I maintain Red Hat backed it as part of a play to make it harder to develop competing distros that aren’t basically identical to Red Hat’s product.

Their actions on systemd, Wayland, plus gnome and associated tech, sure look like classic “fire and motion”. Everyone else has to play catch-up, and they steer enough incompatible-with-alternatives default choices that it’s a ton of work and may involve serious compromises to resist just doing whatever they do.

The Steamdeck loads games into some kind of nested x11 renderer-in-a-window, I think. If for no other reason than to try to avoid Wayland’s extra input latency? Dunno. Maybe you lost some component it needs to work, if regular Steam also does that.

I played some Web version in the late '90s or very early '00s, which is my main experience with the game, and it had 'ludes.

Each one's a reverse-lottery-ticket, though. Get the wrong draw and it's not a gift. Can easily massively reduce the QOL for everyone around, including other siblings.

Mostly due to chronic illnesses, of either the physical or mental variety.