Hopefully we see some of these projects picked up by others. In a weird way, sometimes these sorts of events end up being exactly what a project needs to get forked/transferred and have even more funding/resources thrown at it.

Ive only recently been utilizing mull, mulch, and hypatia, but they’ve been fantastic. All the best to the devs.

I run a fairly standard arch setup and have had very few issues with games. I’ve done a bit of tinkering with bottles, lutris, etc, but pretty much everything just works first time with steam.

I’ve only had to set a few launch flags, usually for a game to use directx instead of vulkan or vice-versa. Sometimes you can’t play a game on launch, but usually one of the first few patches will get things in working order. Steam deck popularity has done wonders for this aspect.

The most common issue I run into is a game update that will break or degrade the experience. But usually those get fixed fairly quickly in follow up patches. A lot of developers will skip testing in proton (mostly because itll “just work” these days) but i imagine theyll start doing so more often before pushing updates as steam decks and Linux become larger shares of players.

Maybe. But its a bit pointless if only a subset of the user base goes through the effort.

https://addons.thunderbird.net/en-US/thunderbird/addon/filelink-provider-for-send/ this add on can be pointed at any send instance, so long as the instance isn’t too diverged from the popular fork or Mozilla’s original project.

The Thunderbird team has talked in the past about bringing Mozilla Send back as more of a feature for Thunderbird files embedded in emails, hence some of the work that’s happening off and on by Mozilla themselves in the original project, some of which has been merged into the project this post is about.

I moved one of my computers to endeavor, but one is still on manjaro and the contrast is kinda hilarious. Manjaro machine always gets funky after updates, it struggles to deal with sleep and hibernation, and it feels slow even when its like 4x as powerful as my EndeavourOS machine.

Its been in testing for a bit. It got bumped from the last major desktop Thunderbird release and since Thunderbird releases used to be synced to firefox ESR releases its been a slow turnaround to get their schedule moving faster.

Its an f-droid metadata issue that the team is already aware of https://github.com/thunderbird/thunderbird-android/issues/8478

I mean, the issues were present and widely reported for several months before Intel even acknowledged the problems. And it wasn’t just media reporting this, it was also game server hosts who were seeing massive deployments failing at unprecedented rates. Even those customers, who get way better support than the average home user, were largely dismissed by intel for a long time. It then took several more months to ship a fix. The widespread nature of the issues points to a major failure on the companies part to properly QA and ensure their partners were given accurate guidance for motherboard specs. Even so, the patches only prevent further harm to the processor, it doesnt fix any damage that has already been incurred that could amount to years off of its lifespan. Sure they are doing an extended warranty, but thats still a band-aid.

I agree it doesnt mean one should completely dismiss the possibility of buying an Intel chip, but it certinally doesn’t inspire confidence.

Even if this was all an oversight or process failure, it still looks a lot like Intel as a whole deciding to ship chips that had a nice looking set of numbers despite those numbers being achieved through a degraded lifespan.

I’m in a swing state with an abortion measure on the ballot, and while all the polls claim it’s close, I’m not really sure they are properly accounting for the number of voters that have been activated by the possibility of enshrining pro-choice into the state constitution.

These polling strategies are complex and a lot of thought goes into them, but they rarely can account for uncommon circumstances that increase voter turnout in local or state elections and how that will effect the national election.

While this is entirely personal reexperience bias, I also wonder how effective these polls are at reaching a representative survey group. I know at least on my phone basically all survey calls and texts go to spam and I wonder if older, more conservative voters are getting overrepresented due to their likelihood of not having those kinds of spam filters in place.

Mull and Fennec are way more obvious android browsers to switch to if Firefox doesnt meet your privacy needs/concerns.

Been using deno 1.x for edge functions use cases at work and its been pretty solid. The standard library is excellent and it leans into web standards rather than node.js, while usually still supporting the node.js standard lib (I’m assuming through some polyfilling to the web standard but idk for sure)

It feels a lot more like working in python where you can probably get the job done with the standard library rather than needing to reach for packages for every task.

I’m looking forward to 2.x, it’ll feel a lot less like a WIP runtime.

The space example is extremely apt. Its possible we could have had tons of space stations, a moon colony, maybe even some other stuff going on around the solar system, asteroid mining, etc. But thay would have at least required the space race to continue longer and for spending to grow to create a big enoigh industry to ensure thay outcome, assuming no capacity or time issue. Alas, we took another path.

Something that seems important to us might not matter in even 10 years, or at least, not have a monetary and/or societal incentive to keep advancing.

So the site should just… Not work in firefox then?

A lot of the sites in the about:compat block or don’t work in Firefox because the sites don’t follow web standards

All web browsers have semi hidden pages like this for all sorts of purposes. Its not really intended to be secret, its just not stuff worth even adding to a file menu. Some of the about: pages in firefox are in some submenus, some on settings, but def not all. Tho you’ll fimd them mentioned and linked in support guides.

If anything, the ability to access these is better than them being blocked…

I’ve also had struggles with arch with printing, more so than debian-based distros. EndeavourOS is where i did the most troubleshooting, but its also a problem on my manjaro install (whicj ill move to endeavour… Someday) But learning how to use cups directly was worth it.

Currently, printing via GUI is like 5ppm and very low dpi so… Not great. But at least I can print for the casual use cases out of the box and could work out a terminal solution if I needed to in the meantime.

I don’t print much so haven’t put time into getting things working better for bigger jobs, but printing is definitely going to be a more hit/miss experience with arch. Its looking like better GUI experience for my specific model will require a driver from the AUR or scripting the Debian install from brothers drivers site. But my model is apparently not as widely used and just hasn’t gotten as much community support I guess

Brother, in particular, has always been fairly well supported via Linux fortunately. Especially great since their laser printers have been the best cost/value for home use for a long time.

Best be careful when changing sheets anyway. It’d be a shame if your mattress wasn’t properly killed before being shipped from Sqornshellous Zeta and it went on a flollop rampage after being exposed to too much sunlight.

Personal experience bias in mind: I feel like owners and managers are less interested in resolving tech debt now vs even 5 years ago… Business owners want to grow sales and customer base, they don’t want to hear about how the bad decisions made 3 years ago are making us slow, or how the short-term solution we compromised on last month means we can’t just magically scale the product tomorrow. They also don’t want to give us time to resolve those problems in order to move fast. It becomes a double-edged sword, and they try to use the “oh well when we hit this milestone we can hire more people to solve the tech debt”… But it doesn’t really work that way.

Its also possible I’m more sensitive to the problem now that I’m in them lead/principal roles rather than senior roles. I put my foot down on tech debt a lot, but sometimes I can’t. Its a vicious cycle and it’ll only get worse the longer the tech sector is stuck in this investor-fueled forever-growth mindset.

Too much “move fast and break things” from non-technical people, not enough “let’s build a solid foundation now to reap rewards later”. Its a prioritization of short term profits. And that means we, the engineers, often get stuck holding the bag of problems to solve. And if you care about your work, it becomes a point of frustration even if you try to view the job as just a job.

Lots of mythology is compiled from many incomplete sources, and not all common accepted stories will completely mesh up with others. It’s also not uncommon for the myth of one village to be completely different from another regarding a particular entity, even if the towns are within a hour walk. What we have now is often just what survived.

Until recently, Wayland development was rather slow, especially in the areas where more specialized software run into issues that force them to stick with X11. Since Wayland does a lot less than X11 and is more componetized across multiple libraries designed to be swappable, some of these areas simply do not have solutions. Yet.

And, as always with FOSS, funding is a big part of the problem. The recent funding boosts the GNOME foundation received have also led to some increased funding for work on Wayland and friends. In particular, accessibility has been almost nonexistent on Wayland, so that also means that if an app wants to ensure certain levels of accessibility, they can’t switch to Wayland. GNOME’s Newton effort is still very alpha, but promising.

While big apps like blender and krita get good funding, they can’t necessarily solve the problem themselves by throwing money at it, either. But the more funding Wayland gets to fill in the feature-gaps and ease adoption, the sooner we’ll be able to move away from xwayland as a fallback.

Wayland and its whole implementation process certinally aren’t without fault. There’s a lot of really justified anger and frustration all around. Even so, staying on X11 isnt a solution.