oh_boy

This isn't less accessible than a hamburger menu. Even the opposite might be the case as defacto most hamburger menus are implemented without proper focus handing or correct aria attributes for announcing open/closed states.

With the sausage menu, at least as screenreader user, you will have less issues as you can tab through a list of links immediately without the need to open a broken menu . Also scroll position is adjusted by the browser automatically to the element in focus, so it isn't even a problem for keyboard users with eyesight.

My job is to build frontends on top of various client management systems and figured out, that I get more maintainable code and am more productive using the templating of the CMS itself instead if decoupling the frontend from the CMS entirely.

So since two years, I use the Hotwired stack on top of PHP (and now with Vite as bundler) and that is so far the best solution I found. I can like use the CMS integrated solution for handling forms, as an example, but can plug in Hotwired Turbo and some Stimulus controllers when I want things to happen async on the client. I now have my own set of generic stimulus controllers I reuse in every project. But at the end of the day, those websites work without JavaScript.

Sure you can use vscodium with the official marketplace. I use that for over a year now without issues.

https://github.com/VSCodium/vscodium/blob/master/DOCS.md#how...

At least in the non-rails environment, Turbo and Stimulus are two separate libraries and have to be included individually.

I didn't try to convince anyone. I deleted it and people started to reach out on Signal, Telegram and Threema. A friend of mine did the same 4 years earlier and it worked out.

This probably doesn't just work for everyone, in every country. But look, people still use phones and these things actually have a phone feature. You might not be as cut off without Whatsapp as you think.

I only heard of Akira. Put I'm not sure it will hit production state at any point as it never reached its crowdfunding financing goals.

https://github.com/akiraux/Akira

The official numbers we get from the newspapers/state media point to 80% occupation.

https://icumonitoring.ch/

UI design I do with Figma on Linux since 2 years. For video editing I recommemd looking into DsVinci Resolve.

Isn't that what Deno solves in this specific area?

Would be good if the website would feature a description and screenshots when accessing it on mobile.

Serious question: is there any difference between the developer editions and the non-developer editions except for the preinstalled OS? I have a non-developer XPS 15 (version from 2017 or 2018) and run Linux on it. The Dell website lists the current generation XPS 15 with 32 GB RAM. I'm curious why you don't consider the ones available?

Playing video games with friends, online, after work. That worked pretty well for me for the last 3 months.

How does this compare to Sourcebit?

https://github.com/stackbithq/sourcebit

A whiteboard or a Everlast Rocket Book, erasable pen and OfficeLens app to digitalise it. Then I put it into Figma and can prototype with them and show it to my clients.

I'm too slow with any software solution as it allows for too many details.

Figma Scripter maybe.

https://www.figma.com/c/plugin/757836922707087381/Scripter

You can use the Figma Linux wrapper to solve that issue. I have thrown my MacBook in a corner since them. I'm fully designing and developing on Pop_OS since 3 months.

https://github.com/Figma-Linux/figma-linux

In case you missed: Pidgin has many plugins including for Whatsapp.

I used the following site lately to choose a phone. I found it much easier to understand than the device list of LineageOS.

https://piotr-yuxuan.github.io/choose-a-new-phone/

Still, individual research still required e.g. to find out that the fancy 48 MP camera mode is not supported in LineageOS.

The one your referencing is related or the same issue. The very first mention of the problem I found with my initial search probably a year ago was the following issue from 2016, which is the one I'm watching:

https://gitlab.com/gitlab-org/gitlab-runner/issues/1151

Not sure what exact experience you made with the GitLab support but I can tell you our experience is different. It took over two months to resolve a license request we made to their support (or sales team) with multiple pushes from our side, every week. There are bugs with the CI system like an issue with the cache retrieval when multiple jobs run in different pipelines parallel to each other, that is actually blocking us from using the cache to it's meant extend and that was issued in 2016. You will find a dozens of those tickets.

Just some examples. Wouldn't say GitLab is the heaven on earth GitHub isn't. It just has it's own, different issues.

Why not? You might not be able to automatically hook it in via their UI, but can't you just do everything with the CLI in the GitLab CI? I mean I don't see a reason why this wouldn't work.

IE is mostly used here because it works best with the screenreaders, not because it's preinstalled or other common reasons. When I test with IE, and then with Firefox, I notice subtle things with big impact working better in IE e.g. I found that screenreaders are particular better with multilingual content on IE. I can't recall the exact screenreader/browser combo, but on IE, I got proper support for different voices for different languages when an element other than the HTML element had a lang attribute.

You're right. Had it wrong in my head.

Use aXe for automated tests and test everything manually with JAWS + Firefox (most popular screen reader Desktop combination) and iOS VoiceOver (most troubling mobile issues in my experience).

If you can afford in your project, use a external service that tests with people with different disabilities.

Tell me, what's the difference of simply importing a JavaScript file with your service code compared to injecting the service with DI in Angular? At the end of the day, Vue is just a UI library. From here you can build your application architecture the way you like. So the difference to Angular is, that Angular is a complete framework which tells you how to define services the Angular way. In React and Vue, you just do that how you would do it in vanilla JavaScript.

Never ever had that issue with Protonmail so I'm very curious where this happened for you.

The IMAP bridge is very slow and I guess, if you are someone that needs to retrieve emails every minute, that can get annoying. Otherwise in my experience, the bridge worked without big issues, using Linux (Manjaro and Arch) and macOS.

That's what you get for privacy. Honestly, the bridge works so flawlessy on my Mac and Linux machines, I don't mind that it is there.

Totally agree on your statement. It's not possible to build modern solutions that are accessible without using some JavaScript. It's always a matter of where you want to go. And it's easy to spare e.g. modals. The question is just if you can solve user experience issues with just HTML and CSS for all use cases.

On the other side, there are more solutions built into HTML and CSS one thinks. In your particular example, you can use the HTML dialog element and get built in keyboard and focus management (still requires a polyfill for many browsers).