Until you get some Windows apologist who points out that their proprietary touchscreen that has multiple layers of DRM doesn't have Linux drivers and therefore Linux doesn't have good hardware support.
You have to be careful in the same way that you can't expect to wipe an M series Mac and stick Windows on it.
Apple devices have multiple layers of touchscreen DRM, but most other devices are just lacking drivers, because there are far too many devices for five unpaid interns to write drivers for all of them.
I mean, a jelly is just broadly any thickened sweet goop (doesn't even have to be fruit, and is often allowed to have some savoury/umami, e.g. mint jelly or red pepper jelly). Usually a jelly also is relatively clear and translucent, as it is made with puree / concentrate strained to remove large fibers, but this isn't really a strict requirement, and the amount of straining / translucency is generally just a matter of degree. There are opaque jellies out there, and jellies with bits and pieces.
Ketchup has essentially all the key defining features of a jelly, technically, just is more fibrous / opaque and savoury than most typical jellies.
But, of course, calling a ketchup "jelly", due to such technical arguments, is exactly as dumb as saying "ayktually, tomato is a fruit": both are utterly clueless to how these words are actually used in culinary contexts.
> Inventive ideas like Pokemon may not exist if people could just reuse other people's IP to make a buck.
Ironic.
Pokémon drew inspiration from a number of areas including Ultraseven, which had the concept of the main character having number of capsules containing miniaturized monsters, which come out and return to their original sizes when the capsule is thrown into mid-air.
> and end up in some Github Issue where Systemd Project heavyweights go "Wow. Yeah, that looks bad. Maybe we should document it. Or fix it? IDK." and they'd do neither.
Do you have a reference? Not that I don't believe you, but I hated this behaviour from Poettering (although he seemed to more often blame the user) and we should totally raise up issue like this. It's a mature product that shouldn't have sharp edges any more.
I'm afraid I don't have a reference. The combination of the facts that the bugs are always damn obscure, there are so many Github Issues filed against systemd/systemd, $DAYJOB keeps me so busy with a huge variety of tasks, and the inappropriate lack of giveashit demonstrated by the project maintainers made me so angry means that the details just get blown out of my head.
> ...we should totally raise up issue like this. It's a mature product that shouldn't have sharp edges any more.
To whom would these issues be raised to? Based on my personal and professional experience, the SystemD maintainers (and -for those who are paid to work on the project- those who manage them) seem to disagree that "eliminating sharp edges" is a big priority!
The difference is that the people who designed X11 were honest in their intentions. The authors of systemd, wayland, etc are not. I'll just leave it at that.
(I recommend staying far away from "X11libre" also, for the same reason, with no further comment.)
Monolithic stuff is OK too, where it makes sense. The kernel is monolithic. ZFS is monolithic.
(Yes, this system has ZFS support. The module is built in to the kernel. In time it will support booting from ZFS also, when I finish the initrd code.)
There is a clear, solid reason for everything this system is or does. I'm not a contrarian or a purist, just someone with opinions gained from long experience who is not happy with the direction mainstream Linux is headed. My system is a zen garden of bliss compared to buggy garbage like Ubuntu.
Really, it's like someone added a turbo button. Ubuntu and friends are so bloated, laggy, and slow. I regularly use this system on 15-20+ year old hardware. The default window manager is Enlightenment e16. It's snappy and responsive everywhere.
KDE, Xfce, etc are supported also and are noticeably peppier than on mainstream distros, just due to the lack of bloat, gazillions of daemons running in the background, etc. Out of the box, nothing runs by default. You enable only what you want.
Another inviolable principle is that no application is allowed to originate or receive network traffic unless the user specifically requests it. There is ZERO network activity going on in the background. None of this steady stream of who knows what contacting who knows where that goes on with other systems. No auto update etc. No internet required or used during the system build. Python module installs do not consult the central repository or download anything. Meson or cmake does not download anything. Etc. All that's patched out and disabled.
It's a distro that is meant to be forked. It's very easily done. It's a blank slate, a vanilla Linux system with subtle and tasteful improvements that is the ideal starting point to customize to your exact specifications. If you want to add in systemd and wayland, fine, I don't care, it's your system and you can build it according to your desires. People can use this platform to build their own custom OS and save themselves a ton of work vs. starting completely from scratch.
It's a system that can be audited. Everything is built with shell scripts, starting with source archives and patches that are applied during the build process. It's all inspectable and the process can be understood step by step.
It's a way to hit the ground running with a full featured, working system, while learning in the process. This distro will teach you what LFS would teach you, but with less of a "sheer cliff face" learning curve, letting you focus more on higher aspects of building the system while still learning the low level details in time.
The build is actually overall simpler than LFS despite being way more featured, with things like Ada support. (Yes, it has GNAT.) I just found a way to do it better, and kept iterating countless times to simplify and improve to the max.
Existing systems did not satisfy my requirements or standards of quality, so I just had to create a new one.
> The difference is that the people who designed X11 were honest in their intentions. The authors of systemd, wayland, etc are not. I'll just leave it at that.
Leave it at what? How is Wayland not honest about it's intentions? It is completely transparent about the motivation behind the project. Whether you agree with the motivations is different, and thats fine to disagree with a project.
However there hasn't been a scenario where Wayland haven't been honest.
Yes, I am ignoring your side comments about systemd because I was asking about Wayland, and mixing the two together implies that you are just complaining about the new, rather than technical/architectural reasons.
(Plus I have to ask as "killthe.net" doesn't come up with anything)
Send me an email and I'll be happy to explain further, to whoever asks. I don't want to clutter up this thread with a bunch of arguing that will surely result, as the focus here is just on "going our separate ways" rather than throwing barbs at anyone, or causing more hard feelings.
People who like software that I don't personally like may continue to use it of course, with this system also even, it's just that it won't be in the official repository is all. But as the whole thing is designed and encouraged to be forked, that shouldn't be too much of a burden if someone likes other aspects of the system and wants to maintain their own 'systemd/wayland' version.
A person can get mistakenly (or not) flagged for special screening and get it over and over again - it happened to me many years ago.
I fixed it by filling out a form requesting a review, after which I received a “redress number” which could be entered into my booking information. It reliably stopped after that.
Not defending the practice but the Mohammed thing has a possible origin that isn't directly racist. The common names among Muslims and their propensity to appear on various watch lists lead to a lot of false alarms on those with those names.
It may be a racist result but there is a pretty reasonable and understandable reason it happens, ignoring the legality and morality of that kind of tracking as well.
I've been using Firefox on android for over a decade, including for YouTube, and maybe once a year I encounter a problem where I need to use Chrome for a specific website.
We're only discussing one particular website, though, aren't we?
Except for on the TV (where I use SmartTube), all of my Youtube activity is done with web browsers.
Otherwise: On both big computers and with my pocket supercomputer alike, that means Firefox and uBlock Origin. It works quite well for navigating Youtube's website and watching videos.
An old iPad that I have suffers from Apple's deliberately baked-in lack of choice, but it does handle Youtube's website very well with Safari and AdBlock.
It has been a very long time since I've used Youtube's app on any device at all.
If a company wants to sell you something, but wants to block access to information, the default position for everyone should be "it's probably because it's bad".
If I have an investment fund and I refuse to tell you about the current performance, I hope you would be sceptical.
If I try to sell you medicine and redact the information about whether it does what I claim, and block you from seeing how many people were poisoned from taking it, I hope that everyone would refuse to take it.
The insanity I'm seeing here from Tesla defenders is amazing. I can only assume they've fully bought in to the vision and tied assets to it and refuse to acknowledge that they might lose everything.
Until you get some Windows apologist who points out that their proprietary touchscreen that has multiple layers of DRM doesn't have Linux drivers and therefore Linux doesn't have good hardware support.
You have to be careful in the same way that you can't expect to wipe an M series Mac and stick Windows on it.
reply