d0ntpan1c

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.

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.

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.

The appearance of similarities between Generative AI and the unconscious mind do not mean there is any actual equivilance to be had. We gotta stop using the same terminology to describe generative AI as we do humans because they are not the same thing in the slightest. This only leads to further unintentional bias, and an increased likelihood of seeing connections with the unconscious mind that don't actually exist.

What drives me crazy about its programming responses is how awful the html it suggests is. Vast majority of its answers are inaccessible. If anything, a LLM should be able to process and reconcile the correct choices for semantic html better than a human... but it doesnt because its not trained on WIA-ARIA... its trained on random reddit and stack overflow results and packages those up in nice sounding words. And its not entirely that the training data wants to be inaccessible... a lot of it is just example code wothout any intent to be accessible anyway. Which is the problem. LLM's dont know what the context is for something presented as a minimal example vs something presented as an ideal solution, at least, not without careful training. These generalized models dont spend a lot of time on the tuned training for a particular task because that would counteract the "generalized" capabilities.

Sure, its annoying if it doesnt give a fully formed solution of some python or js or whatever to perform a task. Sometimes it'll go way overboard (it loves to tell you to extend js object methods with slight tweaks, rather than use built in methods, for instance, which is a really bad practice but will get the job done)

We already have a massive issue with inaccessible web sites and this tech is just pushing a bunch of people who may already be unaware of accessible html best practices to write even more inaccessible html, confidently.

But hey, thats what capitalism is good for right? Making money on half-baked promises and screwing over the disabled. they arent profitable, anyway.