d0ntpan1c

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.

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.

While I found ubuntu's business practices (all the upsells, mostly) the most grating, really the thing that pushed me off of Ubuntu was packages being behind inexplicably and all the forking/modifying they did to gnome and just always being like 1-2 major versions behind, especially since gnomes been shipping tons of features the last few years and Ubuntu wouldn't get them for ages.

Outside of the snaps that Ubuntu seems to force you back into if you purposely try to turn it off, its not the worst to avoid otherwise. Or just deal with for a few apps.

If they want the ubuntu stack of tooling, suggest debian. If they feel intimidated by Debian, Ubuntu is fine. Debian is really solid out of the box for a primary devices nowadays. no need to wait for Ubuntu to bless packages since the Debian ppa's are usually much faster to update. But as long as they aren't doing really weird stuff, they can always move off of Ubuntu to Debian or any other debian descendant easily if they want a smooth transition since its the same package manager.

As long as the immutable distro paradigm isnt a turn off for them, Vanilla OS is also really neat, including cross-package manager installs. V1 is Ubuntu based, v2 will be Debian based (if it isnt already GA'd... I know thats soonish)

I've mostly switched to using Debian for dev containers and servers, and 99% of the time any ubuntu-specific guides are still perfectlh helpful. I moved to Arch for main devices.

(Side note: I abandoned manjaro for similar reasons as I abandoned Ubuntu: too much customization forced upon me, manjaro's package repo was always behind or even had some broken packages vs the arch repos, and some odd decisions by the maintainers about all sorts of things. EndeavourOS has been just way better as someone who likes to have a less-dictated setup that is closer to the distro base and faster to get package updates)

Edit: I guess my tl:dr is... If one thinks "Ubuntu", first ask "why not debian?", and then proceed to Ubuntu if there are some solid reasons to do so for the situation.