I would also definitely recommend to get started with learning Rust. You will need to learn more concepts along the way, but you can still learn about them while you’re coding Rust.
Or rather: I always found it most productive to learn about concepts, while I’m actively using them in a project. So, I would even recommend to jump into Rust now, try to tackle a few smaller projects, and then continue learning general concepts later.
Capsaicin (the chemical that causes the heat sensation in chilis) is soluble in oil, so it can definitely play a role.
In my experience with maths, there’s a whole bunch of different conventions all over the place, so it might’ve genuinely been how they were taught, even if you were taught differently…
Oh yeah, that was my assumption, for sure, too. I was just playing devil’s advocate for the trenchcoat theory, because it’s funny.
I mean, probably happens a lot that the bones of different dinosaurs end up next to each other.
Would it happen for every T-Rex fossil in the same way? Well, less likely…
Sort of in the vein of Pixar movies is also Big Buck Bunny, which I had to think of. (With the caveat, that I’m the opposite of a movie person. 😅)
But well, it’s only 10 minutes long and freely available, so IMHO definitely worth watching.
You can do so here, for example: https://en.wikipedia.org/wiki/Big_Buck_Bunny#Plot
Not entirely sure, if ReactOS would count. Its documentation has a section on WiFi and one of the screenshots on their webpage shows Firefox, but that looks to be a rather old version of Firefox, so no idea if modern versions of it work, too, well, and how well the whole WiFi business works, too.
Well, and one could argue that it’s part of the Windows family.
Yeah, similar to VR, they have their use, but compete with technology that pretty much everyone already has, so when push comes to shove, people will use what they have.
Really my biggest frustration is that it isn’t transparent what’s generated and what’s not. If a human wrote the code, then I want to teach them, especially if there’s glaring logic issues in the code.
But at the same time, the most likely cause for glaring logic issues, is if they generated the code. And then it’s just a complete fucking waste of my time to try to teach them.
I’d say we’re not there yet, but yeah, LLMs and image generators have accelerated it to the point, where I expect it to only take a few more years.
Gonna be interesting. There’s definitely going to be some enclaves, like invite-only places (in particular messengers), and potentially the fediverse won’t be worth targeting directly. But we do get lots of second-hand content here from places which are worth targeting, so yeah, will probably still notice the change here in one form or another.
We could start sending radio waves there and if something happens to be alive there, the response wouldn’t arrive until 300 years from now. 🫠
Oof, I was just talking about making things declarative there. If you want to configure it the old-fashioned way, like you would on other distros, then those difficulties don’t apply.
In more general terms, though, it’s a bit of a double-edged sword. The Nix package repository has more packages than other package managers: https://repology.org/repositories/graphs
So, the chance of finding an obscure software, that’s already packaged, is rather high.
Here’s the online package search, if you want to check the availability of some of the obscure software you use: https://search.nixos.org/packages
But then, yeah, the flipside is that, from what I understand, you can’t just download a random executable off of the internet and run it, because of the Filesystem Hierarchy Standard not being adhered to, as the post also mentions.
You can set up Flatpaks, and I believe AppImages would work, because those also live in their own FUSE filesystem. Well, and there is ways to emulate the FHS layout to get normal applications to run, too.
But yeah, way out of my field of expertise there. I have only one software installed which isn’t packaged for Nix, which is a program I wrote myself.
And to get sufficient FHS emulation for that, I just needed this line in my config:
programs.nix-ld.enable = true;
More complex programs will need a bit of extra configuration: https://wiki.nixos.org/wiki/Nix-ld
(I could also add a flake.nix file into my software’s repository, though, which would make it so it could be installed straight from my repo, as if it was packaged.)
Screenshot the document, then paste it into a new document.
…I am just joking, I have no idea what they mean either. 🙃
Welp, I posted my hot take that impl Deref is similar to inheritance as a meme in !rust@lemmy.ml: https://lemmy.ml/post/42514248
Now, let’s see how many feathers get ruffled. 🙃
Oh wow, what the hell. I’m not actually familiar with C++ (just with Rust which gets similar reactions with the ampersands), but that’s insane that it just copies shit by default. I guess, it comes from a time when people mostly passed primitive data types around the place. But yeah, you won’t even notice that you’re copying everything, if it just does it automatically.
And by the way, Rust did come up with a third meaning for passing non-references: It transfers the ownership of the object, meaning no copy is made and instead, the object is not anymore allowed to be used in the scope that passed it on.
That’s true, except for data types which implement the Copy trait/interface, which is implemented mostly for primitive data types, which do then get treated like C++ apparently treats everything.
Yeah, I can understand the frustration. IMHO the Home-Manager way of doing things has some merits:
That last point is one that’s particularly relevant for me, because KDE Plasma’s configuration files are largely terrible. Home-Manager, together with Plasma-Manager, is the only sane way I know of, to automate the panel configuration in KDE.
But yeah, if you don’t use software with terrible configuration files, then I can certainly understand preferring dumb templating. I have also decided against using the Home-Manager-specific modules in places, or might only translate into the Home-Manager-specific module when I actually want to vary configuration values between two machines.
Just to give a quick impression of how terrible the KDE panel configuration is, this is a snippet out of the fittingly-called plasma-org.kde.plasma.desktop-appletsrc file:
[ActionPlugins][0]
MiddleButton;NoModifier=org.kde.paste
RightButton;NoModifier=org.kde.contextmenu
[ActionPlugins][1]
RightButton;NoModifier=org.kde.contextmenu
[Containments][1122]
activityId=f588743a-9bab-4f56-8f90-3616085ab6e0
formfactor=0
immutability=1
lastScreen=1
location=0
plugin=org.kde.plasma.folder
wallpaperplugin=org.kde.color
[Containments][1122][Wallpaper][org.kde.color][General]
Color=#79740e
Ah sorry, that doesn’t actually show any of the panel configuration, because KDE mixes configuration for the panel and desktop widgets and the Activities feature (like workspaces, but with separate wallpapers and widgets for each Activity) all into the same file.
So, here’s a snippet that actually shows the panel configuration, from just a few lines below the first snippet:
[Containments][1807]
activityId=
formfactor=3
immutability=1
lastScreen[$i]=0
location=5
plugin=org.kde.panel
wallpaperplugin=org.kde.image
[Containments][1807][Applets][1808]
immutability=1
plugin=org.kde.plasma.showActivityManager
[Containments][1807][Applets][1810]
immutability=1
plugin=org.kde.plasma.pager
[Containments][1807][Applets][1810][Configuration][General]
showOnlyCurrentScreen=true
showWindowIcons=true
wrapPage=true
[Containments][1807][Applets][1811]
immutability=1
plugin=org.kde.plasma.panelspacer
[Containments][1807][Applets][1812]
activityId=
formfactor=0
immutability=1
lastScreen=-1
location=0
plugin=org.kde.plasma.systemtray
popupHeight=432
popupWidth=432
wallpaperplugin=org.kde.image
What those numbers in e.g. [Containments][1807][Applets][1812] are? Ah, they just count those from 0 to infinity, whenever you add a widget through the UI.
And in case you were wondering since when INI allows for nesting section keys via [multiple][brackets]: It doesn’t. That’s a custom extension of the INI format, specifically in use by KDE.
Like, man, I love KDE for its features, but this is the stuff of nightmares.
I guess, if you come from garbage-collected languages, you might be used to not needing the ampersands, because everything is automatically a reference in those…
Ah yeah, via deref coercion, which is also called “auto-dereferencing” at times. Not to be confused with “auto-referencing”, which is also a thing[1].
You can do some wild shit with deref coercion. And when I say “wild”, I guess, I’m talking about the most normal thing for Java devs, because well, it’s a lot like inheritance. 😅
Basically, this concept of being able to pass &String into a parameter that takes &str also applies to the self parameter. Or in other words, methods implemented on str can also be called on String, as if String extends str.
And well, obviously you can also make use of that yourself, by writing your own wrapper type. You can even “override” existing methods in a sense by re-defining them in the wrapper type.
I had to play around a bit with it myself, so here’s a playground: https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=af65ed396dec88c8406163acaa1f8f8d
The rule of thumb I always tell people is that they should generally put owned data into struct fields and references into function parameters.
Never used one…