Don’t forget the cop and the brown-children-bomber. Although maybe austerity cuts will make that one job as well.

Whenever I need to provide an estimate, I ask everyone on the team for their gut feeling, take the second-largest estimate and multiply by 1.5. Seems to work pretty well. (if you can’t tell I don’t know what I’m doing with management)

Are you sure you understand how PGP works?

Are you sure you understand how PGP works?

Can you share the exact error?

the third is only a problem if you’re already looking for a problem.

“Is vacation 28 days” should not be a question, it should be the minimum mandated by law. “Will you work weekends” should rarely be a question, it should be heavily regulated and only allowed for positions where it’s truly required (and never to compensate for management fuckups).

Feels like they are both made up scenarios for rage-bait.

Actually for both of them, the conclusion is correct. “The second they’ll get a better offer they’ll vanish” - no shit, this is how it works under capitalism. Want to keep them? Make a better offer. “The second they find someone to do the same for less pay, they’ll fire you” - no shit, this is how it works under capitalism. Want to make that harder to do? Join or organize a union, and otherwise fight for your labor rights.

I’m doing Nix consulting-type jobs - it can mean anything from simply packaging some stuff for Nix and making a devShell to refactoring existing Nix-based infra (which can be hundreds of thousands of SLOC) to building entirely new developer UX, CI/CD and even production deployments on Nix/NixOS. I’ve also been paid to implement some cool features into Nix itself, fix bugs, etc. I’m really quite happy with the job, even though it could probably pay more :)

Eh, probably if Guix becomes significantly better I’ll switch to it (from NixOS). I really like how seriously they take user freedom, bootstrapping (only 357 bytes of binary to bootstrap everything else from source!) and consistent user interfaces (scheme everywhere). But unfortunately the package repo is just not big and mature enough yet, and declarative configuration options are not as good as they are with NixOS. My job is also Nix-related, and that’s another major reason I’m staying for now.

No, it’s not. It’s a word predictor trained on most of the web. On its own it’s a pretty bad search engine because it can’t reliably produce the training data (that would be overfitting). What it’s kind of good at is predicting what the result would look like if someone asked a somewhat novel question. But then it’s not that good at producing the actual answer to that question, only imitating what the answer would look like.

I’m surprised it took this long. The world is crazy over AI, meaning everyone and their grandma is likely trying to do something like this right now. The fact it took like 3 years for an actual vulnerability “discovered by AI” (actually it seems it was discovered by the researcher filtering out hundreds of false positives?) tells me it sucks ass at this particular task (it also seems to be getting worse, judging by the benchmarks?)

I don’t know anything about astal, and not much about lua, so I’m afraid I can’t help you here.

Truth be told, I’ve very rarely specifically audit code of projects I use. Sometimes when something is broken or is missing a feature, I will go in and try to remedy that. On a couple of occasions I’ve noticed other bugs that I then fix too.

The only exception to that are when I’m using some random script I’ve found on the internet - I will read through it to see what it does. This is somewhere between “software I download” and “copy-paste development”, as I will often also tweak the script to suit my needs better.

I don’t think it’s humanly possible for a single person to audit everything they are using. There are millions (perhaps even hundreds of millions?) SLOC in any desktop Linux installation, it would take decades of effort to even skim all that for obvious faults, let alone properly audit it. If you are crazy enough to use something like Dusk OS, then I could see it, but how many people are?

a mobile OS that basically eschews backwards compatibility

I have an app built for Android 4 running on my Android 15 device. It looks ugly but it works. Of course other apps will not be so lucky, but some backwards compat is absolutely there.

a desktop OS that can still run 30 year old applications

Not really, Microsoft is steadily breaking old stuff. For example lot of 10-15 year old software that was doing something hardware-related would be broken now due to driver signing changes/restrictions (e.g. WinRing0 things).

the most popular OS

It’s barely the second most popular OS, after Android. iOS is pretty close behind it. And yet the amount of complaints Windows gets seems to be far higher than that of Android.

Touchscreen (and 2-in-1) support in general is quite good, both Gnome and Plasma (two most popular “desktop environments”) support it well. It should be about as responsive as it is on Windows, because the response time generally comes from hardware and not software. However, I must warn you that I’ve had a similar HP 2-in-1 (although a different model) and there simply wasn’t a Linux driver for the touchscreen so it didn’t work at all; all the other tablet-like features worked fine. I would first check on a liveUSB - the touchscreen should work there the same as it will on the installed distro. If it doesn’t work, well, there’s your answer.

one thing I think that may help is creating that file during the build process

This is certainly an option, but I would only use it as a last resort as it means recompiling the project every time you want to change the theme. It’s quite easily done though, you can use overrideAttrs on the package in your home-manager module to pass in the desired colors.

Your understanding is correct, you have to read that file (~/.config/astal/scss/thmees/astel.css) from your app somehow. I’m just guessing that @import might be compile-time, in which case you’ll have to do it some other way, by reading this file at runtime and using it to configure the colors. If @import is runtime itself, perhaps you need to pass the entire path instead of using ~, like @import "/home/mobsenpai/.config/astal/scss/themes/astel.scss" or something.

How are you importing it in your nixos config? I don’t see any references to astal in there.

I try building this astal config using nix build (just to try to test it) and it creates a result folder inside the astal folder, where i have its flake and configs, see the astal repo, those are the contents of the folder. But there is no check.scss file gets created in the scss/theme/ folder.

That sounds right, nix build on that flake by itself wouldn’t produce that file. You would have to import that home-manager module to your config and then switch to that config, and then the file will be created in your homedir, in ~/.config/astal/scss/themes/astel.scss to be specific.

If by GNUIX you mean GNU Guix, they yeah it’s good enough. I’ve tried it on real hardware and didn’t find any issues. I would consider switching to it, but my day job is Nix-related so I’m running NixOS to make things easier. The learning curve is really steep for both Guix and Nix but I think their approach is great in the long term and worth investing some time into.

read a filename from the user

Honestly for something repetitive like this I’d suggest trying to avoid user interaction completely. It’s probably better to get that info from the DVD drive itself (blkid -o value -s LABEL /dev/dvd), or if that fails assign a number.

First they came for 486, and I did not speak out - because I’ve never actually owned a 486…