ozymandias117 @ ozymandias117 @lemmy.world Posts 3Comments 472Joined 2 yr. ago
Yeah, their branding makes it harder to recover.
I don't know how they'll change their versioning in the future, so I just went with that.
If they don't make an obvious split to when the extension system is stable, they may never get that new beloved version like KDE managed
If you just mean recently, one of the YouTubers with the most subscribers recently released a video about why he switched to Linux, and in it, he says he uses hyprland
May be affecting its popularity
GNOME 2 was different and easy to customize
GNOME is still in their KDE 4.x days where it needs time to mature.
KDE 3 was loved, KDE 4 made a ton of breaking changes, and was reviled. KDE 5/6 are now butter smooth and fixed all the issues from the 3 -> 4 transition
GNOME 4/5 will probably come back into the loved category if they start stabilizing the extension system some more
Oh, damn. He's going against Trump's statements here, so Trump is certainly asking someone to google how he can fire the VP.
Could lead for some funny interactions soon
So, would your suspicion be that it's causing them more failed boards in production?
I guess if it's reducing returns, that might be something they're accepting as a tradeoff?
I think you agreed with me?
I said the people who say Linux is so hard are the people that have learned so much about Windows that it's ingrained in them. So when they try to switch, they get frustrated that it isn't exactly the same
The vocal people saying it's harder have a lot of experience with Windows, and know how to work around all of its deficiencies after being a power user dealing with it for 15+ years
With that mindset and not wanting to start over, Windows is easier
For casual users or someone who's willing to learn, Linux is easier
They already have one: https://en.m.wikipedia.org/wiki/Budapest_Memorandum
Offering another empty promise is unlikely to cause them to make concessions again
Fixed, thanks
Their statement is that Alpine is designed such that it is friendlier to corporations who want to lock down their devices and prevent you from modifying them.
You cannot use coreutils and have a DRM locked down device.
You can use Alpine w/ musl + busybox and make a DRM locked down device
Alpine's licensing favors large corporation's rights in preventing the user from modifying their device
Operating systems using coreutils favor the end user's rights
If they can take my unlocked device by force, they can probably also break my fingers to coerce me to unlock it See also: https://xkcd.com/538/
Randall is right in pointing out you need to consider your attack vectors, but this doesn't mean you shouldn't take reasonable precautions
Most people are more likely to run into the type of attack OP references than someone who can break LUKS encryption stealing their device
My naive reading is the difference here is HP slapped a discount sticker on it without changing the price.
Where Kohls, et. al. set the price extremely high and then always have it "on sale."
Now, how companies get away with doing the same thing for Black Friday, no idea
I wasn't confident which requirement you were missing, but I love that error
The default in systemd, unless your distribution has modified it either globally, or for a specific service, is 90 seconds
Wasn't France the one that started switching to Matrix and funded a bunch of improvements?
It's great that Germany is doing the same, I just remember Matrix talking about money from France and helping the French government deploy Matrix for government use back in the day. A lot of the E2E encryption improvements were attributed to their collaboration with France at the time
That one's especially egregious because the Direct Rendering Manager handles displaying things to the screen, where you might have Digital Rights Management involvement in the form of HDCP support, etc.
Permanently Deleted
That's already how it functionally worked for each major release
Here's their previous strategy: https://web.archive.org/web/20220917195332/source.android.com/docs/setup/about/codelines
Google works internally on the next version of the Android platform and framework according to the product's needs and goals
When the n+1th version is ready, it's published to the public source tree
The source management strategy above includes a codeline that Google keeps private to focus attention on the current public version of Android.
We recognize that many contributors disagree with this approach and we respect their points of view. However, this is the approach we feel is best and the one we've chosen to implement for Android.
As far as I can tell, this would really only affect QPRs, since the public experimental branches that get made after they throw the next release over the wall is going away
Permanently Deleted
There's no chance in hell Vance knows what that phrase means
