Too late.

The article needs a lot more explaining what it is about. Took too long to read to understand that it’s something about containers but understood nothing about what/why this matters.

Some good classic default theme.

I know some of these words!

My default is too use fish shell in all my machines. Never worried again about losing history.

Yes.

Me using jvm based software for work and it barely being enough…

Gotta type first. Everyone knows thats the bottleneck for productivity.

Some random one that appeared out of nowhere for mac only, seems the be from some company and because of that people are hyping the shit out of it.

Many places that never mentioned the other more known and editors like helix now suddenly are mentioning this one. It smells as a huge ad/marketing campaign. Not sure what the plans are for monetisation and the business plan.

Maybe it works better than flatpak? It’s basically the same thing. But I’m not gonna install snap just to try it.

Thanks for the suggestion though.

I have it all installed. Discord native, discord flatkpak, vesktop. With vesktop you loose microphone sound auto detection and krysp. But yeah, sharing video works there also on the browser like firefox, but it’s a tradeoff of the rest.

Discord is still broken even with that bridge. But that’s the only I found not working so far.

Just glad that the comments not loading is now fixed.

And there’s also doas which is a nice substitute.

Yeah, it’s a new way that programs use to draw their stuff on the screens.

In the middle usually are other stuff that abstract away that part from normal application development, so in general, most applications don’t need to care with the low level thing that is being used to draw their stuff, but there is always somethings that some apps will do to bypass or expect to work in a certain way, so sometimes changes and time are need to adjust those applications to play well with the new way of drawing.

The core idea of why Wayland matters is that it is designed to take advantage of the hardware features and how hardware is designed in this century. On xorg, since it was designed around the architecture and expectations of what people thought things should work in the 70s, it was becoming really hard to add features related to how newer hardware worked. Things like multiple gpus, prime architectures, multiple surfaces/screens with multiple aspect ratios and dpis, varying refresh rates, taking advantage of hardware acceleration for graphics drawing, etc, were all really hard things to do because the code had multiple concepts not applicable to the modern age. So, essentially developers were already bypassing 99% of the internals of xorg architecture and hacking things in a very hard way. They basically decided/experimented with stripping apart all the things they didn’t need and didn’t matter and reduced it to the most basic and core thing that mattered: “how to push these pixels to that surface”.

It ended up being a successful experiment, in that it showed it was possible to do.

Now, in the current world, there are solutions that need to be implemented to bring some features up to speed since the wayland thing is so core and barebones. And this is a good thing. It allows developers and applications to think really hard about what they need to do and how they should do and how things should work across all toolkits and desktop environments. Obviously this takes time to make decisions and ensure everyone is onboard, experiment and reiterate on it until good solutions are found.

This last point is what makes end users frustrated when trying wayland because some things are lacking or not ready yet. For the general use, users without really specific needs, they can already use wayland now, but for others they can’t because of their particular needs or specific hardware situation.

If xorg is working for you, then there’s no need to worry. If it’s invisible to you then most likely you shouldn’t care, because the desktop environments are changing their sessions to use wayland by default and most users will not perceive any difference. If users see problems and then notice that it’s related to using wayland they can choose explicitly to use the xorg version since it will still work for a while.

Hope I didn’t make it too complicated now.

So you wanna go from home to school. The whole distance/trip can be done on a bus or your moms car. That’s a means of transportation. But, now people are creating a train and soon you will have another means of transportation that you can go to school with, by train.

That’s it, Wayland is another means of transportation (newer) than the older means of transportation that existed for a long time, x11 or xorg.

The route is how can applications show stuff on a screen, what transport should they use.

So this is why alias in fish are literally functions…

It enters a loop in discord and doesn’t work. There was a bug recently I was reading about it. Makes you go insane. All the other alternatives basically make you lose the krysp and auto microphone sound detection.

I used to mess with my windows Millenium so much and deleting random files and changing regex and understanding how things worked that tech support guy was almost every 2 weeks there reinstalling the system for me. And that was how they started to give me copies of the cds to install myself so I wouldn’t bother them so much.

For those that like firefox drawing its titlebar instead of using the system one (I can those psychopaths) it’s literally a right click on some part of the ui, customize and at bottom there’s an option about which titlebar to use.