jetin

Yeah I agree, with a single small screen, I only use yabai with the stack layout allowing to navigate vertically in a predictable way with ‘ctrl+up/down’ between windows inside a workspace. I think it works great with the horizontal navigation between workspaces with ‘ctrl+left/right’ native to macOS. I honestly don’t need anything else.

Hi! I must say I'm really interested in what you are building there and I'd love to be a part of it. I can't apply for now but, if that's okay, I'd like to connect with you on LinkedIn in order to keep an eye on your enterprise.

As for me, I have a strong background in front-end development, I've been designing and building user interfaces for almost 10 years now. I'm also a passionate fan of Tolkien's works, I read a lot and hope to maybe write someday (more than simple blog articles). You can have a look of what I've done on my website: https://www.jeantinland.com/.

Have a nice day! I hope to be able to work with you in the future!

That's nice! It feels polished and feature-full, but like others commented, I'm not seeing myself paying for this.

On my end, I managed to first develop an open-source alternative status bar based on Übersicht (https://github.com/Jean-Tinland/simple-bar) 6 years ago and then a standalone rewrite in Swift (https://github.com/Jean-Tinland/a-bar) if anyone is interested. Though both bars require yabai or AeroSpace to work.

I agree with your comment, it is often an overlooked topic. Inlining icons can be one answer but be aware of the growing size of your DOM. Depending on the complexity, number and repetition of the icons you are using, an approach including lazy loading can be better. Layout shift is first and foremost caused by an improper space reservation.

There is also a whole population category that isn’t capable of differentiating Windows from Linux. Just yesterday I was showing something on Zorin OS to my father and I had to explain to him that I was not using Windows 10 like he is at home. As long as the web browser is working and he can use his printer, a desktop is a desktop and icons are icons that can be clicked. Any other operation will be written on paper in a step by step well phrased manner. OS choice doesn’t matter for him, he will always struggle so making him switch to Linux won’t change a thing of his experience.

I also agree with you, I simply think the need for shadow root depends on the level of encapsulation you need.

Interesting article, I think some points are covered by this ESlint plugin [0] specifically created for web components.

[0] https://github.com/43081j/eslint-plugin-wc

Yeah, I also used the Shadow DOM a lot working on a CMS that edit the website content “in place”: CMS UI was safely scoped inside my web components thanks to their Shadow roots, I never had to worry about arbitrary styles from the websites the CMS was loaded in colliding with internal CSS.

Shadow DOM exists for some specific use cases but it shouldn’t systematically used when creating web components.