d0ntpan1c

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.

The central point of that article is certinally valid. Something that was worked on for a while with broad congressional support and public support getting vetoed isnt ideal for a democratic process. No resolution on issues is not a good thing since another 3-6-12 months of no regulation for a theoretically netter bill to work through the system will allow for continued abuse by AI behemoths. Newsom is a corpo dem, so idk what people expected, anyway.

I don't buy into the AGI FUD. These are word calculators. But these tools are being hooked up to all sorts of things they shouldn't be hooked up to and the lack of broad privacy regulation in the US puts LLM usage that handles sensitive data and/or decisions firmly into dangerous territory. Business decisions made by irresponsible management with no regard for data privacy or human safety are already a massive problem that actively cause harm, and hooking current AI tools onto these processes only seems to make the problems worse, especially while AI usage is in this gray space where no one wants to take responsibility for the outcomes.

Y'all realize a random employee performing the add-on store review process isn't representing Mozilla's or the Firefox teams entire position yeah? This kind of stuff happens all the time with all stores that have review processes.

Firefox Addons store prob needs to improve its process, gorhill is justified in being mad, and I understand if he needs a punching bag between this and google, but, as someone who also develops extensions.... These things happen. It's just a part of building browser extensions.

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.

I'm sure some places use it to share info, but usually it basically becomes their entire software stack. Its like the salesforce of the health world. It does their billing, shift management, HR, CMS, everything.

Vscodium is your solution then

If the doctor uses mychart, thats where they store the internal data whether you have an account or not. Its their entire computer system most of the time.

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.

Honestly, I'm not mad if AI fully defeats captchas to the point they go away. They almost always fail to be usable via accessibility tools. These things might block some automated systems, but they also block people with disabilities.

Manifest v3 extensions work in Firefox, too. Its just the new thing. Its way easier to build cross-browser extensions with, too. V3 is actually a good thing overall, as its led to a lot of extensions being available for Firefox when the devs might have just targeted chrome. Way more feature parity between browsers with v3.

Chrome dropping support for v2 doesn't merit a response from Firefox because nothing changes for Firefox users and they're not going to drop support. Any one who actually cares (and they should) will move to Firefox on their own, so why waste advertising money on that? Eventually Firefox and any other browsers who want to allow stuff like ublock will probably have a way to do the same tasks in v3 (and the Firefox Dev team has said as much in blog posts for ages), then it'll just be a feature that doesn't work in chrome. V3 just simply doesn't have the API that ublock uses in v2.

There have been discussions for years in the w3c standards group about this whole shitshow and this is one the chrome team have basically refused to budge on despite all the other browser teams. Its honestlu a mirscle they delayed it as long as they have. This was originally supposed to happen at the start of 2023.

Chrome is kinda like a country with a overrule veto vote at the UN when it comes to w3c working groups since they can just do whatever they want anyway, and nothing will change until they no longer have that power. That said, browser feature parity is at an all time high recently and its because all the browser teams are working together better than ever. There are just these hard limits chrome chooses to stick to.