@@Tech-NO-CityBrodie's content is quite far down in the Linux iceberg. The other content drives far more hype than this, especially for those who don't understand that distribution doesn't really matter.
Yeah, as far as this channel goes if you're subbed it's most likely you're very familiar with Linux. And yeah, that slashes the discoverablity compered to channels that talk about entry lvl stuff that get traffic from outside the Linux userbase.
Hello Brodie, I'm the developer of Louvre. Thank you very much for sharing the project. I've been a fan of your channel for a long time, especially your videos on Wayland, so this really made my day. It also helps to get more people interested in contributing to its development. I wanted to mention that I agree with your comments on the benchmark. I'll try to add the hardware/drivers used in the tests soon. I just wanted to clarify a detail that seems to have been misunderstood. The charts regarding CPU and GPU usage on both the left and right sides use the same collected data (they are not two separate benchmarks). The difference is that on the left side, the data is displayed as is, while on the right side, the values are normalized (divided) by the FPS to obtain a value indicating how much CPU or GPU usage there is per rendered frame. That's it, and regarding the protocols, I'll gradually add more. First, I have to finish implementing the basics hahaha cheers!
I really like the tutorial of Louvre, it’s the most clear, thorough tutorial on how to write a X11 WM / Wayland compositor I ever seen. I have very little knowledge on Wayland, but it’s look very promising. So I will try to follow it and see if I could come up with something interesting. Really appreciate that.
Awante Hopper. Me pone contento que CuarzOS siga creciendo, aún recuerdo ver los primeros pasos en el 10k, cuando no andaba en el depa xD Les deseo lo mejor.
Your wayland news videos are my main way of keeping up with it right now. Thwnks to you i actuallt swirched to hyprland and it is sooo much better than when i tried it mere months ago.
Didn't notice the pointer constraint protocol, which is also very important for gaming, especially if you have a second monitor. And also, I don't beleave that "the date, when wayland will be the only option available" will happen soon, if ever. X11 still has it's usecases, which wayland is way far to cover (Like, for example, using a gui application via docker). Don't get me wrong, I'm using a selfmade wayland compositor (spent whole nigth to update it on wlroots 17, because of surprise update on arch) and I'm not an X11 prophet.
Looks like a good start. I've mentioned that i don't see the point in desktops working from scratch, but that doesn't mean development of alternative compositors are bad, if anything we need more so that there are a variety of implementations to encourage refinement.
SSDs ought to be part of the core protocols in the first place. It's completely absurd that there is a *core* protocol which allows windows to tell the compositor "hey, I'm being dragged" for CSDs to work, but not a protocol which simply tells the compositor "I ain't moving unless you make me" for SSDs to work.
For me, the answer is "I'll chase X11 as far as I have to until David Edmundson's work on restarting and crash recovery is sufficiently complete and widely merged". nVidia support shouldn't be as big a deal though, since, having been bitten by the Stable Diffusion bug, I just jumped on a Cyber Monday deal for an RTX 3060 to replace my GTX750 from 2014 (i.e. something likely to fall out of support before nVidia gets Wayland sorted) and, in 2024, I may upgrade from my 2011 Athlon to something with two x16 slots where I could slot in a low-end AMD card for display output if need be.
@@BrodieRobertson yea it's basically a work of concept. I tried to do it but it's way above my pay grade. Maybe I'm just stupid. The 3ds has Linux but it's basically a proof of concept. It does run Weston though.
Did not know that Gnome bans screen tearing. May explain why I got very little tearing after disabling vsync in a game I was testing. Lately the crashes are blamed on gnome-shell in kern.log. I wonder if double vsync was causing some kind of race condition.
to be fair, i think its genuinely a good idea for 99% of the usecases to ban screen tearing. however, some gamers may not like it. the latency difference is relatively minimal compared to other vsync methods, for example directly in games, so thats fine by me personally.
I like how you've gotten so up front on calling out Gnome's bullshit. Also hope the project does well. I don't want *too* many more options as I am one of the guys who thinks fragmentation in linux is a serious problem. But competition is good up to a point.
While I agree with most of the things you say, I would say it's better to take your time and do something correctly than to rush it and do something wrong. That's not always possible, but I feel like the Gnome developers always prioritize better over quicker.
You could, but (in my experience) gamescope doesn't respect the user configurations from the master compositor. Also it'll lock your mouse cursor inside the gamescope window.
[12:35] Even though Wayland is the future and Xorg is absolutely dying, we need to stop scaring people by saying that Xorg is just going to disappear one day. Because it is not. Stop it. Just like how you can still install GTK2 apps or install ancient software, you will still be able to install Xorg with no issues.
I'm convinced Wayland was a practical joke by the xorg devs. They were sitting around complaining about how everyone dogs on xorg and someone said "you know what? F them. If they think they can do it better, let's make them." And thus just an incomplete protocol was born and sold as the next great thing.
"when you're writing an X window manager, you're writing a window manager. With Wayland, you're also writing a display server, a compositor, etc..." This neatly sums up pretty much all my problems with wayland. From my uneducated perspective, this seems like an obvious blunder from the Wayland team, it seems like it would do little more than severely fracture the ecosystem and make it harder to write a compositor. Why is it that way? Is there any benefit to having the compositor do all those things instead of having them be separate? Going by the unix philosophy it seems pretty obvious that they should be separate programs, why would wayland be designed this way?
More's the merrier in the Wayland space. I don't think it matters what anyone else does, Gnome is gonna be Gnome, and I think my opinions on that are pretty well known in your comments section.
I do not understand. How can gnome hold back wayland? Aren't they different projects? Or did you mean to say those gnome devs are core maintainers of wayland project too, and can therefore, by definition, enforce their vision on it?
There should be a base compositor with all the protocols. If a child does not want a protocol it can just remove it from its fork and allow everyone else to just use the protocol. On Wayland it is objectively better with more protocols. There really are not any reason not to use them all. Why intentionally restrict users from features?
@@keit99 Is this critical of me or the Gnome guys? I'm bad at telling this lol. But personally I dont think it is user entitlement for people to just want Gnome to either work with the community that all want a feature or at the very least not hole back the rest of Wayland with stupid vetoes to actually needed improvements.
@@FBI_Master IMO, they should warn GNOME developers that if they keep this holding back the desktop for petty arguments up, they could (and should) be kicked out of planning and/or their veto power is gone.
Benchmarks don't usually reflect the performance in reality. This benchmark is just of moving transparent rectangles and is unlikely to be representative of the actual experience using the compositor.
@@kreuner11 Accurately profiling a large and complex piece of software such as a compositor is incredibly difficult. A microbenchmark like this does not show how performance for presenting videos or rendering real time graphics on a specific GPU. It is likely that other compositors have the edge for at least some of these activities.
I disagree about wayland being harder to implement for. In X11 you have 40 years of legacy code and basically 0 documentation. Yes, you have other wms to draw upon, but still, writing for X11 is not easy, far from it.
I convinced the dude making this to adopt a more permissive license. Currently, it's gpl licensed, and he wants to go with MIT, but the freeimage library is gpl or something and doesn't permit that. UPDATE: He's gonna switch over to libpng and libjpeg over freeimage.
8:20 Thats why i hate gnome they are like windows but in linux world. They do not take in consideration what users actually want, they completely ignore that
No, they do care what most users like, and refuses to just add "features" like a small group like and "need" in the configuration. Most things can be done from command line to change the configuration.
Was a big fan of Gnome 2 but man, Gnome 3 and their developers suck. You never hear anything good or inovations comming from them. Allways just things like "Gnome Devs dont want to implement this.." and "Gnome Devs dont want to implement that ... " or "Gnome Devs removed Feature xyz". I dont like wayland much either, but i would be happy if wayland just implements things and breaks gnome 3 cause gnome is hindering inovation in linux desktop
I just got update on Manjaro unstable that broke multimonitor support on Wayland. Had to roll back my backup. Being closer to default Wayland, seeing such serious regression is disheartening. Wayland is not ready, because it is not feature full and not stable enough. Of course, this may be a fault of Nvidia driver update, but somehow Wayland Plasma session was affected, while, X11 was fine.
@@qwesx Yet another linux user commenter being an elitist toxic to another linux user on the internet without resons. Sad. Users shouldn't have to know about the backend, it should just work. (plasma wayland user)
Modern C++ is great, it just gets a bad rep from terrible uni lectures, lots of legacy code, and C developers contributing C code to C++ projects. If guidelines and best practices are enforced, memory safety issues are a thing of the past.
@@happygofishing You rarely need template metaprogramming to be effective. Simple constrained function templates and auto params should cover most cases, and those are fairly easy to write with a little experience.
Nice job mentioning that gnome folks don’t want to support something every posible moment. You did a video on your another channel about peoples harassing gnome devs remember?
@@excidium666 there is a difference between "reporting on the current status of wayland protocols" and plugging btw's on how gnome is bad whenever possible further catalyzing hatred towards devs. this video is about louvre and not gnome after all. why should it be mentioned there?
@@thock_enjoyer good point but i imagine that when criticizing someone your are providing an arguments why the other side is wrong. not facepalming on video and saying "btw gnome doesn't support this protocol". if you think that everyone is a sane person and noone will go harassing peoples and spamming in gitlab issues after watching this video, read comments to this and previous video about emulator disabling wayland support: peoples saying how they hate gnome and it should die.
You know, after diving into the toxic community of Hyprland, my outlook on the C++ community took a nosedive. It's like the language somehow attracted the not-so-great side of the internet, filled with teenage-brained homophobes. Without some big corporate umbrella, I'm skeptical these projects won't end up in a mess of controversies or be all that friendly to newbies. Give me the quirks of wlroots any day; I'd rather tackle those complications than deal with a hostile environment.
"The toxic community of Hyprland"? my man, you just are interacting with elitist linux users, i see those all the time in any other place as well, what's so Hyperland/C++ specific?
this community, that community...free yourself from that mindset of internet cliques. People use sepples for objective reasons e.g linking directly C libraries like wlroots while having access to fancypants modern language features.
The C++ community is not toxic IMO, but the popularity seems to be decreasing again. The linux user community is very toxic, both in absolute terms and in comparison. Not sure what community you perceived as the C++ community, hopefully it's not 4Chan /g, because that's the 4Chan community, not the C++ one. The C++ community is kind-of a closed one, as it has little interaction with other language communities, compared to the web development community for example, and some of the most senior folks refuse to acknowledge and give credit to Rust as a new strong competitor language, but aside from that, everyone is respectful and welcoming. I suggest watching CppCon talks to get familiar with the community while also learning.
You don't have to like GNOME or agree with GNOME but GNOME is the de facto default desktop environment in Linux. There is no reason from application developer point of view to depend of features (like Wayland protocols) which are not available in default DE of Ubuntu (the de facto default Linux distribution), RHEL or SLES. If GNOME does not want to implement some API, the API does not matter for real-world software.
You don't have to like NVIDIA or agree with NVIDIA but NVIDIA is the de facto default graphics chip vendor for PCs. There is no reason from developer point of view to depend of features (like Operating systems) which are not available in default graphics chip vendor of PC (the de facto default home computer). If NVIDIA does not want to support some operating system, the operating system does not matter for real-world software.
If everyone stopped caring what GNOME thought, GNOME would be forced to capitulate or leave its users with a broken user experience. Sure, for now they are the default environment, but that situation could change very quickly between Valve's contributions to KDE and System76's Cosmic if the user experience just continues to become worse as a result of their decisions.
When GNOME doesn't care about their stuff working on other DEs then I'd rather those apps drop GNOME entirely. Some GNOME devs are too arrogant to be trusted to lead the world of FOSS. Therefore GNOME should not be default.
Get ready to sign in to your Microsoft account, watch ads in your OS, and to use Edge and Onedrive whether you like it or not. Or spend hours getting rid of the pooware after each installation and major update.
@@szaszm_ Normal people don't really care. If it works, who cares if the OS is idling at 3 GB on 16 GB of ram. Who cares if the OS is constantly sending data. Who cares that a normal Windows 11 install is around 20-30 GB with no user programs installed? Your point only works with people who.. probably aren't even thinking about going back to Windows anyways..
Sorry, what's this? Windows working out of the box? That's _never_ been something I've experienced. I won't say I've never had any linux related issues, but boy are they less frequent and actually _fixable_; neither of which was true of the constant issues I had on Windows.
Whatever makes a smoother and painless experience for compositing and window managing, session management and all the rest of it I'm fine with this really. IF there's a easy entry point to using and building on Wayland they should at least share and work on it together to make it better to work with with tools that fast tracks that process, while also being able to supply a backward compatible X11 applications if needed by simply checking what backend is being used currently. I want to see better GPU experience and configuration on Linux, NVIDIA's efforts with their settings panel feels like a very dated cousin who hasn't seen a computer in decades, or knows what kind of operating system its running on. It specifically expects the default file `xorg.conf` from `/etc/X11/xorg.d` or whatever, but on other OOB distros might have their own configuration file to use instead of the default location for your `xorg.conf` like for example with Manjaro having a `/etc/X11/`mhwd.d` directory and then labelling things with `nvidia.conf` or `amd.conf` and the Nvidia Settings Panel is incapable of loading any other directory than the default, which means it needs a SymLinked `xorg.conf` file, but even then when need to change something, it'll complain it can't read the file, and trying to save it wont even edits if you needed to make a manual edit.
Wow just noticed his sub count is so low for the amount of good quality content he pushes out.
I dont get it every linux youtube channel besides this guy just shows linux installs, themes and icon sets.
@@Tech-NO-CityBrodie's content is quite far down in the Linux iceberg. The other content drives far more hype than this, especially for those who don't understand that distribution doesn't really matter.
Yeah, as far as this channel goes if you're subbed it's most likely you're very familiar with Linux. And yeah, that slashes the discoverablity compered to channels that talk about entry lvl stuff that get traffic from outside the Linux userbase.
Linux extremists only here
Brodie's content is far more technical in reach than other channels, so his audience is a niched. But it's very good, he is one smart fella.
Hello Brodie, I'm the developer of Louvre. Thank you very much for sharing the project. I've been a fan of your channel for a long time, especially your videos on Wayland, so this really made my day. It also helps to get more people interested in contributing to its development.
I wanted to mention that I agree with your comments on the benchmark. I'll try to add the hardware/drivers used in the tests soon. I just wanted to clarify a detail that seems to have been misunderstood. The charts regarding CPU and GPU usage on both the left and right sides use the same collected data (they are not two separate benchmarks). The difference is that on the left side, the data is displayed as is, while on the right side, the values are normalized (divided) by the FPS to obtain a value indicating how much CPU or GPU usage there is per rendered frame.
That's it, and regarding the protocols, I'll gradually add more. First, I have to finish implementing the basics hahaha cheers!
I'm sure you're surprised by the sudden attention the project got considering how early on it still is but I do wish you the best of luck with it.
@@BrodieRobertson In fact I am hahaha thank you! ❤
I really like the tutorial of Louvre, it’s the most clear, thorough tutorial on how to write a X11 WM / Wayland compositor I ever seen.
I have very little knowledge on Wayland, but it’s look very promising. So I will try to follow it and see if I could come up with something interesting.
Really appreciate that.
Awante Hopper.
Me pone contento que CuarzOS siga creciendo, aún recuerdo ver los primeros pasos en el 10k, cuando no andaba en el depa xD
Les deseo lo mejor.
@@YeaSeb. jajajaja bueena, acabo de ver el comentario, pero quién eres? Supongo que algún Seba, quizás Musul?
Your wayland news videos are my main way of keeping up with it right now. Thwnks to you i actuallt swirched to hyprland and it is sooo much better than when i tried it mere months ago.
Yeah, it moves at a crazy pace. I fear the day vaxry graduates and gets a job
Why would you fear me getting a job? :)
@@vaxryy As a hyprland user I am entitled to your undivided attention
I have mad respect for everyone writing Wayland compositor. Even with the libraries it's absurdly complex and complicated.
Didn't notice the pointer constraint protocol, which is also very important for gaming, especially if you have a second monitor. And also, I don't beleave that "the date, when wayland will be the only option available" will happen soon, if ever. X11 still has it's usecases, which wayland is way far to cover (Like, for example, using a gui application via docker). Don't get me wrong, I'm using a selfmade wayland compositor (spent whole nigth to update it on wlroots 17, because of surprise update on arch) and I'm not an X11 prophet.
That's also an important one, I forgot about that
Looks like a good start. I've mentioned that i don't see the point in desktops working from scratch, but that doesn't mean development of alternative compositors are bad, if anything we need more so that there are a variety of implementations to encourage refinement.
Hey, look. Even a project without XWayland support has protocol for server-side decoration.
At least this one plans to support server side decorations
SSDs ought to be part of the core protocols in the first place. It's completely absurd that there is a *core* protocol which allows windows to tell the compositor "hey, I'm being dragged" for CSDs to work, but not a protocol which simply tells the compositor "I ain't moving unless you make me" for SSDs to work.
@@mckendrick7672 like MS Windows window handling. If the client locks, then Wayland locks on that window, and it can't be moved. Like it can i X11.
For me, the answer is "I'll chase X11 as far as I have to until David Edmundson's work on restarting and crash recovery is sufficiently complete and widely merged". nVidia support shouldn't be as big a deal though, since, having been bitten by the Stable Diffusion bug, I just jumped on a Cyber Monday deal for an RTX 3060 to replace my GTX750 from 2014 (i.e. something likely to fall out of support before nVidia gets Wayland sorted) and, in 2024, I may upgrade from my 2011 Athlon to something with two x16 slots where I could slot in a low-end AMD card for display output if need be.
let's not forget that linux and wayland runs on the 3ds
hm..
How functional is that, I can't imagine there's much performance to work with
@@BrodieRobertson yea it's basically a work of concept.
I tried to do it but it's way above my pay grade. Maybe I'm just stupid.
The 3ds has Linux but it's basically a proof of concept. It does run Weston though.
Hi Brodie, could you cover the Niri wayland compositor? seems really interesting
Did not know that Gnome bans screen tearing. May explain why I got very little tearing after disabling vsync in a game I was testing.
Lately the crashes are blamed on gnome-shell in kern.log. I wonder if double vsync was causing some kind of race condition.
Gnome refuses to cooperate with most wayland protocols. You're better off testing in KDE
imo gnome is a more enjoyable desktop but its philosophy and direction make it unusable for me, oh well
to be fair, i think its genuinely a good idea for 99% of the usecases to ban screen tearing. however, some gamers may not like it.
the latency difference is relatively minimal compared to other vsync methods, for example directly in games, so thats fine by me personally.
@@TVPInterpolation for most gamers even but it makes the gaming experience for those who prefer it straight up unusable
@@Gskvj Only using Gnome because it is the Ubuntu default. Sure miss focus follows cursor.
another robertson classic
I like how you've gotten so up front on calling out Gnome's bullshit.
Also hope the project does well. I don't want *too* many more options as I am one of the guys who thinks fragmentation in linux is a serious problem. But competition is good up to a point.
While I agree with most of the things you say, I would say it's better to take your time and do something correctly than to rush it and do something wrong. That's not always possible, but I feel like the Gnome developers always prioritize better over quicker.
Could one use gamescope as xwayland and then not worry about adding xwayland support?
That would be kind of a horrible hack, specially for non-game stuff
You could, but (in my experience) gamescope doesn't respect the user configurations from the master compositor. Also it'll lock your mouse cursor inside the gamescope window.
For some reason I think Brodie doesnt like gnome very much
Anybody reporting on wayland protocol blockers is gonna give that impression
I have a lot of respect for GNOME's UI development team. However there are a lot of issues on the Wayland protocol side that I can't ignore
[12:35] Even though Wayland is the future and Xorg is absolutely dying, we need to stop scaring people by saying that Xorg is just going to disappear one day. Because it is not. Stop it.
Just like how you can still install GTK2 apps or install ancient software, you will still be able to install Xorg with no issues.
I'm convinced Wayland was a practical joke by the xorg devs. They were sitting around complaining about how everyone dogs on xorg and someone said "you know what? F them. If they think they can do it better, let's make them." And thus just an incomplete protocol was born and sold as the next great thing.
Ya gotta cover **miriway** brodie, it is 800 LOC wayland compositor
"when you're writing an X window manager, you're writing a window manager. With Wayland, you're also writing a display server, a compositor, etc..." This neatly sums up pretty much all my problems with wayland. From my uneducated perspective, this seems like an obvious blunder from the Wayland team, it seems like it would do little more than severely fracture the ecosystem and make it harder to write a compositor. Why is it that way? Is there any benefit to having the compositor do all those things instead of having them be separate? Going by the unix philosophy it seems pretty obvious that they should be separate programs, why would wayland be designed this way?
Can you talk about Arcan/Durden too?
More's the merrier in the Wayland space. I don't think it matters what anyone else does, Gnome is gonna be Gnome, and I think my opinions on that are pretty well known in your comments section.
Excellent video 👍 Thank you 💜
I do not understand. How can gnome hold back wayland? Aren't they different projects? Or did you mean to say those gnome devs are core maintainers of wayland project too, and can therefore, by definition, enforce their vision on it?
There should be a base compositor with all the protocols. If a child does not want a protocol it can just remove it from its fork and allow everyone else to just use the protocol. On Wayland it is objectively better with more protocols. There really are not any reason not to use them all. Why intentionally restrict users from features?
Entitlement: 'I know what my users want and if they want something I don't want/need they don't ' (which seems to be the GnomeWayland dev sentiment'
@@keit99 Is this critical of me or the Gnome guys? I'm bad at telling this lol. But personally I dont think it is user entitlement for people to just want Gnome to either work with the community that all want a feature or at the very least not hole back the rest of Wayland with stupid vetoes to actually needed improvements.
@@FBI_Master the Gnome and wayland devs.
@@FBI_Master IMO, they should warn GNOME developers that if they keep this holding back the desktop for petty arguments up, they could (and should) be kicked out of planning and/or their veto power is gone.
@@keit99 Cool. Sorry spectrum+text makes that shit hard lol.
7:31 - 8:14 speaks from my heart. Why are Gnome devs like this?
Cool but why is it written in sepples?
@@notuxnobuxenjoy your symbol mangling you savage.
@@happygofishingsymbol mangling exists in everything that isnt C yk
Benchmarks don't usually reflect the performance in reality. This benchmark is just of moving transparent rectangles and is unlikely to be representative of the actual experience using the compositor.
Yeah but like it should work fine
@@kreuner11 Accurately profiling a large and complex piece of software such as a compositor is incredibly difficult. A microbenchmark like this does not show how performance for presenting videos or rendering real time graphics on a specific GPU. It is likely that other compositors have the edge for at least some of these activities.
Let me use my screensavers, please!
We need sex jokes back on the whiteboard
I disagree about wayland being harder to implement for. In X11 you have 40 years of legacy code and basically 0 documentation. Yes, you have other wms to draw upon, but still, writing for X11 is not easy, far from it.
Gnome devs are becoming the major proponents of Windows.
I convinced the dude making this to adopt a more permissive license. Currently, it's gpl licensed, and he wants to go with MIT, but the freeimage library is gpl or something and doesn't permit that.
UPDATE: He's gonna switch over to libpng and libjpeg over freeimage.
Why not go with the Mozilla Public License?
@jamesgarrard8301 why?
@@gljames24Because the initials are MPL which is way too close to MLP.
If I were the dev I wouldn't. I'm not letting companies steal my work lol
@iver5457 Why? It's not theft if the license permits that.
Something in wayland always striked me wrong, showing their true colors praising the fr*nch
8:20
Thats why i hate gnome they are like windows but in linux world. They do not take in consideration what users actually want, they completely ignore that
No, they do care what most users like, and refuses to just add "features" like a small group like and "need" in the configuration. Most things can be done from command line to change the configuration.
Was a big fan of Gnome 2 but man, Gnome 3 and their developers suck. You never hear anything good or inovations comming from them. Allways just things like "Gnome Devs dont want to implement this.." and "Gnome Devs dont want to implement that ... " or "Gnome Devs removed Feature xyz". I dont like wayland much either, but i would be happy if wayland just implements things and breaks gnome 3 cause gnome is hindering inovation in linux desktop
Maybe those "selfish gnome users" know the truth... that X11 is the best.
I just got update on Manjaro unstable that broke multimonitor support on Wayland. Had to roll back my backup. Being closer to default Wayland, seeing such serious regression is disheartening. Wayland is not ready, because it is not feature full and not stable enough. Of course, this may be a fault of Nvidia driver update, but somehow Wayland Plasma session was affected, while, X11 was fine.
>using Manjaro.
There is your problem mate
Yet another commentator who doesn't understand the difference between a compositor and a protocol. Sad.
@@qwesx Yet another linux user commenter being an elitist toxic to another linux user on the internet without resons. Sad.
Users shouldn't have to know about the backend, it should just work. (plasma wayland user)
@@richoumiaouyeah keep blaming it on wayland instead of the implementations.
@@n.m4497 Also nvidia on plasma wayland
I just stole a dead project and modified it to use tmux as the window manager.
C++ 😢
Modern C++ is great, it just gets a bad rep from terrible uni lectures, lots of legacy code, and C developers contributing C code to C++ projects. If guidelines and best practices are enforced, memory safety issues are a thing of the past.
@@szaszm_ templates scare me
@@happygofishing You rarely need template metaprogramming to be effective. Simple constrained function templates and auto params should cover most cases, and those are fairly easy to write with a little experience.
@@szaszm_ I know it's not a good habit, but whenever I write C++ I basically end up just writing C but with classes and stdstring.
Ill probably end up learning rust one day, just because the library management is so effortless.
Cargo is by far the best feature.
@@giusdbg
Just ban gnome devs already
Nice job mentioning that gnome folks don’t want to support something every posible moment. You did a video on your another channel about peoples harassing gnome devs remember?
Brodie stop reporting on the current status of wayland protocols or you will have blood on your hands
harassing the devs is awful but they are allowed to be criticized for holding back wayland
@@excidium666 there is a difference between "reporting on the current status of wayland protocols" and plugging btw's on how gnome is bad whenever possible further catalyzing hatred towards devs. this video is about louvre and not gnome after all. why should it be mentioned there?
@@thock_enjoyer good point but i imagine that when criticizing someone your are providing an arguments why the other side is wrong. not facepalming on video and saying "btw gnome doesn't support this protocol". if you think that everyone is a sane person and noone will go harassing peoples and spamming in gitlab issues after watching this video, read comments to this and previous video about emulator disabling wayland support: peoples saying how they hate gnome and it should die.
Im gonna break into your house and open all of your funko pops so that the value goes down.
Why would anyone buy a funko pop
so then... what... is the point of keeping the funko pops in boxes?...@@BrodieRobertson
Also you pronounced library wrong
Bro still has the same pepsi can from yesterday's video sitting on his desk 💀💀💀💀
Bro doesn't know what batch recording is
Wait so you're telling me you spend hours on end flailing your arms and talking about linux to a webcam?@@BrodieRobertson
With the speed that you kept replying to comments last night I have some doubts.@@BrodieRobertson
I can't believe what I have heard. "selfish Gnome developers". Open source and free sw made by selfish people. Interesting to hear...
You know, after diving into the toxic community of Hyprland, my outlook on the C++ community took a nosedive. It's like the language somehow attracted the not-so-great side of the internet, filled with teenage-brained homophobes. Without some big corporate umbrella, I'm skeptical these projects won't end up in a mess of controversies or be all that friendly to newbies.
Give me the quirks of wlroots any day; I'd rather tackle those complications than deal with a hostile environment.
"The toxic community of Hyprland"? my man, you just are interacting with elitist linux users, i see those all the time in any other place as well, what's so Hyperland/C++ specific?
Let me guess you believe in "Code of conducts" and other such things.
"Hostile" = not GitHub/discord monoculture
this community, that community...free yourself from that mindset of internet cliques. People use sepples for objective reasons e.g linking directly C libraries like wlroots while having access to fancypants modern language features.
"the C++ community" lmao you need to touch grass
The C++ community is not toxic IMO, but the popularity seems to be decreasing again. The linux user community is very toxic, both in absolute terms and in comparison. Not sure what community you perceived as the C++ community, hopefully it's not 4Chan /g, because that's the 4Chan community, not the C++ one. The C++ community is kind-of a closed one, as it has little interaction with other language communities, compared to the web development community for example, and some of the most senior folks refuse to acknowledge and give credit to Rust as a new strong competitor language, but aside from that, everyone is respectful and welcoming. I suggest watching CppCon talks to get familiar with the community while also learning.
You don't have to like GNOME or agree with GNOME but GNOME is the de facto default desktop environment in Linux. There is no reason from application developer point of view to depend of features (like Wayland protocols) which are not available in default DE of Ubuntu (the de facto default Linux distribution), RHEL or SLES. If GNOME does not want to implement some API, the API does not matter for real-world software.
I guess that’s what valve is trying to change by using KDE
I just wish they would cooperate with the rest of the Linux community more. Even as a GNOME user their behaviour is sometimes quite frustrating.
You don't have to like NVIDIA or agree with NVIDIA but NVIDIA is the de facto default graphics chip vendor for PCs. There is no reason from developer point of view to depend of features (like Operating systems) which are not available in default graphics chip vendor of PC (the de facto default home computer). If NVIDIA does not want to support some operating system, the operating system does not matter for real-world software.
If everyone stopped caring what GNOME thought, GNOME would be forced to capitulate or leave its users with a broken user experience. Sure, for now they are the default environment, but that situation could change very quickly between Valve's contributions to KDE and System76's Cosmic if the user experience just continues to become worse as a result of their decisions.
When GNOME doesn't care about their stuff working on other DEs then I'd rather those apps drop GNOME entirely. Some GNOME devs are too arrogant to be trusted to lead the world of FOSS. Therefore GNOME should not be default.
maybe just move to windows it just works ha L on Linux W for Windows
Get ready to sign in to your Microsoft account, watch ads in your OS, and to use Edge and Onedrive whether you like it or not. Or spend hours getting rid of the pooware after each installation and major update.
@@szaszm_ sorry cant hear you over things just working
@@szaszm_ ruclips.net/video/xVWeRnStdSA/видео.htmlsi=6FEz3aRs1zoHndAb
@@szaszm_ Normal people don't really care. If it works, who cares if the OS is idling at 3 GB on 16 GB of ram. Who cares if the OS is constantly sending data. Who cares that a normal Windows 11 install is around 20-30 GB with no user programs installed?
Your point only works with people who.. probably aren't even thinking about going back to Windows anyways..
Sorry, what's this? Windows working out of the box? That's _never_ been something I've experienced. I won't say I've never had any linux related issues, but boy are they less frequent and actually _fixable_; neither of which was true of the constant issues I had on Windows.
Lol i'll stick to X11, Wayland is trash.
Bro stop ranting about Wayland goddamn. We all know it has issues so just stick to x11 for a few more years and quit crying about it.
This is a new take, most of the time people call him a Wayland shill
I'm confusing, I sometimes hate Wayland, I sometimes love it, it's almost like there is nuance in my position
One thing isn't confusing, you sure do like dressing up as a maid and collecting nude anime figures
@@dehydratedwater3830 is that supposed to be an insult, you've described reality
@@dehydratedwater3830 nahhhh hes just confused about what he is
Whatever makes a smoother and painless experience for compositing and window managing, session management and all the rest of it I'm fine with this really. IF there's a easy entry point to using and building on Wayland they should at least share and work on it together to make it better to work with with tools that fast tracks that process, while also being able to supply a backward compatible X11 applications if needed by simply checking what backend is being used currently.
I want to see better GPU experience and configuration on Linux, NVIDIA's efforts with their settings panel feels like a very dated cousin who hasn't seen a computer in decades, or knows what kind of operating system its running on. It specifically expects the default file `xorg.conf` from `/etc/X11/xorg.d` or whatever, but on other OOB distros might have their own configuration file to use instead of the default location for your `xorg.conf` like for example with Manjaro having a `/etc/X11/`mhwd.d` directory and then labelling things with `nvidia.conf` or `amd.conf` and the Nvidia Settings Panel is incapable of loading any other directory than the default, which means it needs a SymLinked `xorg.conf` file, but even then when need to change something, it'll complain it can't read the file, and trying to save it wont even edits if you needed to make a manual edit.
KDE should move to wlroots already, hopefully after Plasma 6. Too many ressources wasted on KWin.
Wouldn't rewriting the entire compositor be a waste of resources
Im sure it would cut into your anime loli time.@@BrodieRobertson
I'm sorry that your life sucks so much
@@dehydratedwater3830 perhaps you should find time to get a life.