![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
You say that as though it’s a bad thing. 😆
You say that as though it’s a bad thing. 😆
One detail about Rust in the kernel that often gets overlooked: the Linux kernel supports arches to which Rust has never been ported. Most of these are marginal (hppa, alpha, m68k—itanium was also on this list), but there are people out there who still use them and may be concerned about their future. As long as Rust remains in device drivers only this isn’t a major issue, but if it penetrates further into the kernel, these arches will have to be desupported.
(Gentoo has a special profile “feature” called “wd40” for these arches, which is how I was aware of their lack of Rust support. It’s interesting to look at the number and types of packages it masks. Lotta python there, and it looks like gnome is effectively a no-go.)
Large organizations always have politics—it’s human nature. 1700 people is quite a large organization. Therefore, the kernel maintainers have politics. The presence of politics always means that some people will get stomped on unfairly.
This is all business as usual, in other words, and it will not go away. At best, you can shift the culture of the group and the politics along with it, but that takes time and effort and people-handling.
For files? An unholy amalgam of snake, kebab and dot, depending on what exactly I’m trying to convey. (I still have much-ported files around with DOS 8.3 filenames, so they’re truncated scream case (SCREAMIN.NAM), but I don’t actively name files like that anymore.) The important thing is to separate the words/sections while using characters that are valid without escapes in both ext4 and vfat if at all possible.
For variable names, camel or Pascal case (depending on language convention) if I think anyone else is going to read it. Flat case for code I don’t think anyone else is ever going to see (don’t do this—it has left teethmarks in my ass from time to time and will do the same to you).
Some individual window managers are full-featured enough to be somewhat usable as program launchers all by their lonesome, such as awesome, fluxbox, and openbox. There’s also Enlightenment, which is somewhere between a bare WM and a DE. If you really want to play with standalone WMs, start with something from this paragraph.
Other WMs need a bunch of other things like dmenu and feh piled on top of them to get a useful environment. i3 is one of these. You can find and fit together enough software pieces to get a fairly full-featured environment out of one of these setups, but it’s more work than just installing the core portions of a DE.
Figure out first whether you’re dealing with X or wayland (hyprland is a wayland compositor, which is slightly different from a window manager). Read guides, and especiallly stay away from things that say they’re “lightweight” or “minimalist” until you’ve read the documentation and know exactly what you’re getting into, as they tend to be for advanced users. If you just want to play around and have no particular problem you’re trying to solve, just look for live CD/DVD/USB images you can boot inside a VM and save yourself some work.
TDE has had occasional discussion and ruminations, but no action yet. Porting it is complicated by the fact that it has its own widget set (TQT, forked from QT3), which would have to be worked on first and is currently undergoing some unrelated rewriting.
The likelihood of any wayland milestones for TDE being set before the end of 2024 is very low unless some major distro completely drops X support.
I consider bootloader attacks a very low-probability threat, and quite honestly I don’t trust the average board vendor to produce anything that’s actually secure anyway. If I were in the habit of carrying a laptop back and forth across international borders I might feel differently, but for a desktop stuck in a room in Canada that hardly anyone enters when I’m not present, Secure Boot is a major hassle in return for a small security gain. So I just don’t bother.
Dude, I’ve worked with all these interpreters. The JVM’s startup is slow, although there’s been some improvement since the version 1.1 that I started out with. The interpreter speed is quite good once it gets going, so it remains a good choice for long-running or interactive programs where the startup is insignificant as a fraction of total program run-time, but if you’re running a script that takes only a fraction of a second to execute, the JVM’s startup can lengthen the time by an order of magnitude or more. Horses for courses and all that—I wouldn’t write a complex interactive GUI program in Perl, either.
Technically, you could bundle a Perl script with the interpreter on another system using pp
and run the packed version on systems with no installed Perl, but at that point you might as well just use a compiled language.
Last I checked, the JVM was larger than the standard Perl and Python interpreters, and had a much worse startup time (which is bad for short scripts).
If it really is a .doc file and written in an ASCII-compatible encoding as most English-language documents are, opening it in a hex editor (or a non-codepage-aware text editor like the Notepad on a W10 or earlier Windows machine) will show an indecipherable proprietary header followed by the text in the file, possibly with a single space or “junk” character between each letter depending on the exact version of Word and system encoding it was written with. There may be occasional additional stretches of markup junk. At the end, there will be a footer with occasional decipherable text strings like “MSWordDoc” and font names.
If you open a .docx file in such a program, you should get a typical zipfile signature: the letters “PK” at the beginning of the file, followed by a lot of gobbledegook. If you don’t get that “PK”, it probably isn’t a .docx.
(I’ve looked at a lot of MS file guts, for both curiosity and information extraction purposes.)
Because they don’t want ignorant end users to blame them if the ancient, unpatched version of GRUB that’s at issue is used as part of an exploit attacking Windows boxes.
I wonder if there’s a Gentoo binpkg host for i486 specifically, since it might almost be practical then. (Or you could set up your own.)
Also out of the loop, but my guess is that Wayland hasn’t defined a specific API for the purpose yet, and their security model doesn’t allow programs to see the content of other programs’ windows. X11 doesn’t attempt to keep programs from seeing what other programs put on screen, so no specific API is needed there.
Actually, if you check deep down in the list of installables, you’ll find that Gentoo still supports the even less capable i486 variant. A laptop from 2010 is positively a spring chicken compared to some of the things it can be made to run on. Itanium is only being desupported because it’s being dropped upstream by the kernel and other chunks of the toolchain (and the only actual hardware they had to test on died a while ago).
date
is the command for setting the system date and time from the command line. Nothing to do with formatting, beyond the fact that it presumably applies system locale settings when echoing date-time info.
I only need it for the very occasional testing of open-source software on Windows, using the precanned VM images provided by Microsoft (last I checked, they had none for qemu, or I would be using that instead). And if you’re using software commercially, you’d better be damned sure you understand the licensing before setting up. A company of any size will have lawyers vetting that anyway.
In other words, I don’t disagree with you, but those issues don’t matter for my use case.
Raw qemu at the command line for the one I use on a daily basis (not recommended for the average user). VirtualBox if I need to spin something up quickly but don’t expect to need to keep it past the current testing cycle.
ext4 on all hard disks, but my installs are all several years old at this point, and I might choose differently if I were starting over from scratch. The boot partition on the ancient laptop might actually be ext2; I don’t remember and it’s certainly old enough that that might still have been preferred Gentoo procedure when I first set it up. Removable media might be ext3, ext4, or vfat, depending on compatibility needs and how long ago I formatted it. If I buy an SD card or USB stick that turns out to be preformatted in exFAT, I reformat it before use to ensure everything can read it.
They’re all solidly reliable filesystems (well, except for the vfat), but perhaps not the most featureful.
Assuming that it works out, yes, this might fix the problem. On the other hand, I remember gcj, which kind of quietly vanished after a while, so I prefer to reserve judgement until gcc’s Rust implementation is ready for production use.