Add a random string (like "AnyBrowser/1.2.3") to your user agent string, and get warnings about unsupported browsers, reduced functionality, and Google drive completely refusing to start at all.

It's the very same browser, just another user agent string. Ever heard of feature detection? Ever heard of usability, accessibility, progressive enhancement? How can developers be so lost in 2022?

I just tried to reproduce the reason why Vivaldi stopped adding their brand to user agent strings but sails under false flag pretending to be Google chrome. So it doesn't show up in browser statistics either and Google people can keep thinking everyone is using their shitware.

Even with something as simple as pagination, it's possible to create a complete accessibility abomination. Dear designer, you've perfected your flat design style.

Fuck you! I'm not coding this.

It's a website about selling solar panels, underfloor heating etc... Not a single piece of design reminds it.

Got this design for a button.
Now I'm writing an essay in the ticket about how this is problematic for localization and accessibility.

This website has no option to add alt text to uploaded images.

Atlassian needs improvement!
Screenshot from the Jira "Accessibility" settings page where I hoped to find a dark mode switch.

When I wanted to send them feedback about the settings page, the feedback form failed, cluttering vintage style error messages with poor UX writing all over the page.

> Help us improve!
>
> We’d love to hear more about your experience with the new accessibility settings in Jira. Any thoughts on what you liked and where we could improve are more than welcome.
> Oops! Something went wrong...
>
> There was a problem submitting your feedback, likely due to the configuration of this form. You might want to contact the site owner to let them know about this issue.

P.S. Thinking of accessibility: there is not way to enter an ALT text to image uploads on devrant? seriously?

Scaling support for large displays sucks! I have poor vision and rely on using a large display with low resolution + 300% scaling. So many programs fail to scale properly. I get that a 55-inch display at low resolution isn’t a common configuration but it is an accessibility issue and just ugh.

Since my XPS battery is dying I'm flirting with an idea of a new laptop. Requirements:
- 13" display
- 4k display (I'm so used to high-res that x1080 looks like accessibility mode)
- 16 (worst case), 32 (OK), 64 (possible?) GB RAM
- long battery life
- i7 or Ryzen equivalent (I need lots of ram, lots of computing power)
- plays nice with Linux
- GPU preferably integrated (don't need a separate GPU)
- ultrabook (small, compact, light) (I don't like to exercise while carrying it. God forbid I'd grow a muscle... )
- purrrrtty :)

So far the best candidate I've found is... XPS13 again :D The setup I'm after costs ~1.6k€ which is not that bad, really.

Is there anything else in the market that'd meet the criteria? Anything worth looking into? Better deals?

Dev goals for 2022? Best and worst DX in the past?

Wish to prioritize customers with useful business goals who are open to sustainable web dev, usability and accessibility.
Want to use even more CSS and find a way to use new features like parent selectors without sacrificing compatibility.

Continue learning and using Symfony, but also continue with my full-stack side project using JS or even better TypeScript for the backend also for the backend.

Best developer experience: getting new customers for my own business after leaving a company last winter.

Worst developer experiences:

Corporate customers with large budgets and design agencies seem to fancy all the antipatterns I thought bad and obsolete, like carousel content, animations everywhere, and autoplay videos on the home page. Poorly written, poorly thought, and sometimes contradictory, requirements. Customers and agencies changing their mind halfway through a project.

"Agile" daily meetings, not giving devops necessary repository permissions, and making Webpack mandatory for no real reason.

The worst part about being an accessibility expert in these times is getting a redundant flood of a11y stuff on developer knowledge email subscriptions.