There are Gentoo distros that have binary packages, and Funtoo (a Gentoo-based distro that’s 64-bit only) even suggests using Flatpak for certain software that needs 32-bit resources like Steam. Hell, you can install Flatpak on Gentoo if you want. Gentoo also provided binary packages in the past but only for a few packages (mainly web browsers, but annoyingly not qtwebengine. maybe that’s changed here.)
Gentoo is more about having fine-grained control of your system than anything else nowadays. If that’s what you want, go ahead! For most people, Arch or even something with less control like Ubuntu or Fedora will suffice.
literally 2 days ago i tried installing gentoo in a vm but gave up because it would take too long to compile… and now this??? guess my timing was pretty bad
if i did use gentoo, i’d probably compile smaller programs from source and bigger things like kernel and web browser i would use as binaries.
Seems kinda pointless to compile most packages unless there are specific performance optimizations or non-default features that can be enabled. I think the way I would use this would be to do binary by default and build only on the occasional instance there is a tangible benefit.
Wayland has fixed so many head-scratching issues I would get running 6 monitors on 2 GPUs under X11. I’d often end up with missing monitors, placed in wrong spots that I’d have to rearrange every reboot until an update would come through that would fix it again for a few months, then all over again.
Since I moved to wayland, everything just works. When it doesn’t, it’s not a display server issue, it’s something physical. I just had a couple monitors fail to show up and thought “oh hell, it’s back to this, eh”. But I open the tower, seat the offending GPU better, and everything comes up like normal, and all the screens are in the right position, it just remembers.
Anyone that thinks X11 is still superior probably runs on a laptop with a single screen.
I mean I’m fully with you on the fact screen autodetect isn’t stellar on X but there’s no need to exaggerate with “2 or 3 scripts”. It’s one xrandr command.
Ive seen several devs do that, and also some of my gaming friends have 3 monitors.
I barely know anyone who only has a single display. Most people I know have one high refresh rate monitor, and one office monitor for discord and the likes.
I have 2 75hz and a 240hz. It’s been alright for me on kde and x11. Although, I do want to give this Wayland thing a shot after hearing it being brought up so many times
If you base your opinion of vim from memes you are missing out. Anyone who can’t take 10 minutes to type vimtutor in their terminal is not someone to base an opinion on. These memes come mostly from impatient people that can’t read the docs. It’s a fantastic text editor.
That being said, it’s not meant to be used for written words it’s meant to write code and config files. You want to look for a word processor.
Abiword, etherpad, focuswciter are probably the next 3 biggest on Linux behind libre and open office.
Personally I prefer markdown for most things these days but it’s not exactly meant for word processing either.
A software approach to a hardware problem is an exercise in futility.
Test your memory with Memtest86
Test your disks too. badblocks is a Linux utility. I like the Victoria and HDDScan Windows programs because they’re less pass/fail in their reporting - you can see that a disk is degraded even if all of the sectors technically respond.
Memory is fine. I ran a couple disk checks as well and it’s also fine. I was also using two SSDs during the process with no difference in the problems experiences.
Over on Nate's other blog entry he indicates this:
The fundamental X11 development model was to have a heavyweight window server–called Xorg–which would handle everything, and everyone would use it. Well, in theory there could be others, and at various points in time there were, but in practice writing a new one that isn’t a fork of an old one is nearly impossible
And I think this is something people tend to forget. X11 as a protocol is complex and writing an implementation of it is difficult to say the least. Because of this, we've all kind of relied on Xorg's implementation of it and things like KDE and GNOME piggyback on top of that. However, nothing (outside of the pure complexity) prevented KWin (just as an example) implementing it's own X server. KWin having it's own X server would give it specific things that would better handle the things KWin specifically needed.
Good parallel is how crazy insane the HTML5 spec has become and how now pretty much only Google can write a browser for that spec (with thankfully Firefox also keeping up) and everyone is just cloning that browser and putting their specific spin to it. But if a deep enough core change happens, that's likely to find its way into all of the spins. And that was some of the issue with X. Good example here, because of the specific way X works an "OK" button (as an example) is actually implemented by your toolkit as a child window. Menus those are windows too. In fact pretty much no toolkit uses primitives anymore. It's all windows with lots and lots of text attributes. And your toolkit Qt, Gtk, WINGs, EFL, etc handle all those attributes so that events like "clicking a mouse button" work like had you clicked a button and not a window that's drawn to look like a button.
That's all because these toolkits want to do things that X won't explicitly allow them to do. Now the various DEs can just write an X server that has their concept of what a button should do, how it should look, etc... And that would work except that, say you fire up GIMP that uses Gtk and Gtk has it's idea of how that widget should look and work and boom things break with the KDE X server. That's because of the way X11 is defined. There's this middle man that always sits there dictating how things work. Clients draw to you, not to the screen in X. And that's fundamentally how X and Wayland are different.
I think people think of Wayland in the same way of X11. That there's this Xorg that exists and we'll all be using it and configuring it. And that's not wholly true. In X we have the X server and in that department we had Xorg/XFree86 (and some other minor bit players). The analog for that in Wayland (roughly, because Wayland ≠ X) is the Compositor. Of which we have Mutter, Clayland, KWin, Weston, Enlightenment, and so on. Which that's more than just one that we're used to. That's because the Wayland protocol is simple enough for these multiple implementations.
The skinny is that a Compositor needs to at the very least provide these:
wl_display - This is the protocol itself.
wl_registry - A place to register objects that come into the compositor.
wl_surface - A place for things to draw.
wl_buffer - When those things draw there should be one of these for them to pack the data into.
wl_output - Where rubber hits the road pretty much, wl_surface should display wl_buffer onto this thing.
wl_keyboard/wl_touch/etc - The things that will interact with the other things.
wl_seat - The bringing together of the above into something a human being is interacting with.
And that's about it. The specifics of how to interface with hardware and what not is mostly left to the kernel. In fact, pretty much compositors are just doing everything in EGL, that is KWin's wl_buffer (just random example here) is a eglCreatePbufferSurface with other stuff specific to what KWin needs and that's it. I would assume Mutter is pretty much the same case here. This gets a ton of the formality stuff that X11 required out of the way and allows Compositors more direct access to the underlying hardware. Which was pretty much the case for all of the Window Managers since 2010ish. All of them basically Window Manage in OpenGL because OpenGL allowed them to skip a lot of X, but of course there is GLX (that one bit where X and OpenGL cross) but that's so much better than dealing with Xlib and everything it requires that would routinely require "creative" workarounds.
This is what's great about Wayland, it allows KWin to focus on what KWin needs, mutter to focus on what mutter needs, but provides enough generic interface that Qt applications will show up on mutter just fine. Wayland goes out of its way to get out of the way. BUT that means things we've enjoyed previously aren't there, like clipboards, screen recording, etc. Because X dictated those things and for Wayland, that's outside of scope.
That’s my problem with this. It tries to be a desktop display server protocol without unifying all desktop requirements. Sure, X11 is old and have unnecessary things that aren’t relevant anymore, however, as someone who builds their own DE, (e.g.: tiling window managers) I see it as the end of this masterrace. Unless everybody moves to wlroots. Flameshot, for example, is already dealing with this, having at least 5 implementations only for linux, and only wlroots and x11 are standards.
Also, imo, having windows in windows is useful when you want to use your favourite terminal in your favourite IDE. But as you said DEs can implement it simply. Let’s say wlroots will implement this but others can decide otherwise. And for those the app won’t run.
Another example, that affects my app personally, is the ability to query which monitor is the pointer at. Wayland doesn’t care having these so I doesn’t care supporting wayland. And I"m being sad about this because X is slowly fading away so new apps will not run on my desktop.
Moreover with X11 I could write my own hotkey daemon in my lanuage of choice, now I would have to fork the compositor.
Also, imo, having windows in windows is useful when you want to use your favourite terminal in your favourite IDE.
The wayland way to do that is to have the application be a compositor, they made sure that nesting introduces only minimal overhead. And that ties in with the base protocol being so simple: If you only need to deal with talking to the compositor you’re running on, and to the client that you want to embed, a wayland compositor is indeed very small and lean. Much of the codebase in the big compositors deals with kms, multiple monitor support, complex windowing logic that you don’t need, etc.
Oh and just for the record that doesn’t mean that you can’t undock the terminal: Just ask the compositor you’re running on for a second window and compose it there. You can in principle even reparent (client disconnecting from one compositor and connecting to the other) but I think that’s only standardised for the crash case there’s no standard protocol to ask a client to connect to another compositor. Just need to standardise the negotiation protocol, not the mechanism.
Can you check the battery voltage with a multimeter if you know how to use one? when disconnected at full charge, when connected, and when the strange flickering is happening?
There are battery voltage monitoring tools on Windows and Linux which could work but I’d trust multimeter numbers more. Check to see if it’s above by more than 15% rated voltage or below rated voltage by any amount at full charge. Check for any strangeness in the charge curve.
If you see any of those signs your battery is likely busted. Also if your battery looks inflated at all replace it immediately.
You can try the battery monitoring software then. It would likely be a struggle to try to view the status while the screen flickers but if you can get a log then you can review it when you re-enable the fix.
OK keep monitoring i guess, if its good for now, fingers crossed?
It could be an Amazon quality battery or a combination of many factors… the design voltage of your battery is on the low side which pushes a lot of current to your display and other components. If that display cable is worn or frayed it can have a chance of busting the screen, or in very rare cases spark/catch fire. Inspect it carefully.
naturally, it began again after waking from sleep. that’s why it’s so darn tiresome diagnosing it, you never know if the tweak you’ve made has any effect, sometimes it works for hours, sometimes it freaks out after seconds.
if the battery is the culprit, shouldn’t it stop being a problem when running the device on external power? it’s not like it’s constantly charging the battery and simultaneously draining it; at least, no laptop I know of does that. and if the display cable is faulty, then it should also have those flickers when running it without battery. that never happens.
What if the battery is doing something hinky enough to cause very minor interference and the internal cable is close enough to be affected by it? I'm not super familiar with the low level details of battery tech but I think it could theoretically be possible (though obviously would be stupid rare).
+1 for battery voltage, OP. You may have a faulty battery. If that is the case, how long have you owned the replacement? Is it within a window of returning it?
This might be funnier than all those Facebook accounts with warnings about “I do not authorize anyone to use my photos!”
Because they’re trying to copyright an internet comment that they posted on a service hosted by someone else, with a creative commons license attached. It’s like a step up in knowing how shit works, but still not knowing enough.
If you really want ownership over what you say… don’t post it on the fucking internet.
I mean, not really. You own the stuff you create regardless of who’s hosting it. Microsoft doesn’t own the copyright for the millions of projects hosted on GitHub either.
I mean, probably not. That’s such a short post, chances are courts wouldn’t find it copyrightable. And obviously attaching a license at the end of your comments is useless in practice, because no one on the internet actually properly engages with copyright law. Plus suing over copy-pasting someone’s social media post is dumb as hell and no one does that, tho I do think you could technically do it and win, because current copyright laws make zero sense if you actually stop and think about it for any amount of time.
My lawyers will argue that this willful infringement of my rights as the orignal author of the famous 1997 Internet comment "So true" means that you now owe me $4000000 in damages, but I'll settle for one bitcoin.
And yet Microsoft made Copilot, and there are currently lots of clueless programmers out there using it to inject code with god knows what licenses into their company’s software.
Which hasn’t been free of legal challenges. Current copyright law doesn’t account for machine learning, which is what allows them to do this. This could soon change.
You own the original, which you’ve written on your pc or phone. But the one that ends up on the website is a copy, on which you’ve granted the website owner a non-revokable license to do with as they please ie. a copy-right.
Not really. You’ve granted the owner some rights, such as the right to host your content and present it to any user on the platform, but they don’t own it. Twitter can’t start using any art hosted on their platform for their branding, because it’s no theirs.
They can if the license you granted them says they can. Read it. These platforms usually make you grant then extensive rights. Yes they don’t own the content but given such broad permissions it makes very little practical difference.
The Linux Experiment covered Asahi (I believe it was Debian) and he said he’ll review the Fedora’s version too. It was a month or two ago and there were some things still in the works. But as a Fedora user and it being Asahi’s flagship which has been fine tuned according to them, I’d bet Nick will post a video soon. If you’re an early adopter, I’d say give Fedora a go now, otherwise just wait for Nick to cover it in his usual detail on his channel. Nick’s the man and will cover it very well. This will probably be the best conformation unless an early adopteradopter or Dev can chime in here.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.