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.

Right, and then not watch YouTube or Netflix or anything on my… TV… Good plan!

Roku was such an easy recommendation for a long time… Non-complex UI, long support for updates, not owned by google or amazon… Far cheaper than LG and Samsung… (Not that Samsung’s UI is anywhere near as easy as roku)

But now I guess thats done. Unless an alternate firmware exists or this doesn’t hit older TVs I guess I’ll be looking for a new TV… Which is a shame because my current 4 year old roku TV is more than capable.

I picked up one of the ARZOPA ones and they are fine. Not the best looking, but good enough for a second monitor on the go. I used to take my ipad 9.7" with me places for this purpose and even though the image isnt as good, its way less effort to carry around.

I wouldnt use it as a single monitor regularly, nor for gaming.

I had to keep using the usb-c cable that came with it. Not sure if its a specific protocol that my thunderbolt 4 cables dont support or not. Minor inconvenience i havent looked into further.

Don’t feed the troll.

Especially not one that uses mental illness as an insult.

Power users love to bash accessibility features like this. Its a classic case of “I don’t need a wheelchair ramp so i dont know why the library added one!”

Accessibility is way more than screen readers. It’s more than specific disability-minded modes. The web needs to be friendly to everyone, including people who may not know they could benefit from accessibility features. Everyone benefits from this type of work.

There are definitely some legit feature concerns and priorities being called out here. Mozilla has left a lot to be desired of late on that front. But a power user is more than capable of jumping into settings or about:config to turn things like this off, or finding an extension to get by for now.

Also the firefox dev team isn’t tiny. This isn’t blocking other work or anything in a substantial way, it’s a fairly isolated piece of UI, and there’s no guarantee that skipping this would change the timeline on anything else.

The page title isn’t necessarily visible on the web page that sets the title.

Clicking is not always a simple task.

I shouldn’t have to leave my current page just to figure out what another tab is.

Again, just because you feel something is useless or easily avoided doesn’t mean that all internet users feel the same.

Tooltips are a standard accessibility feature. Just because you may not find them helpful doesn’t mean others do not benefit. The delay is to ensure they don’t get in the way unintentionally (but still allow usage) for those who do not need the accessibility benefit at all times.

+1

the UI could be improved (I always end up hovering for tooltips on controls) but it works really well.

I also like that tabs will stay in the stash by default on close, so its great for opening a bunch of reference sites really quickly without worrying about losing them

Closest thing to the old firefox experiment from a few years back.