MeanEYE

Actually no. Wire wrapping prototypes were made like this. This also looks like an old ISA card as well, from which period this method of prototyping was still in us. It’s also the method in which the Apollo’s guidance computer was made and that one survived a lot harsher conditions than desktop PC, and survived.

VLC, it’s in the name.

Intel driver is the key to the problem. They have no memory leak issues as others did. At least not ti such a degree.

There’s no benefit in having RAM sitting idle and empty. Si Linux caches a lot of things.

You use Chrome for everything including writing code and notes. Different outcome was unexpected really.

While true, Git also supports symlinks, so nothing is stopping you from having modules/ directory or something similar and then in link part of it elsewhere in your project.

X.org hasn’t been network transparent for more than a decade. Ever since SHM and DRM1 and 2 were added X.org was network capable but not transparent.

It’s possible that limit is either gone or vestige from a bygone age and they are hashing passwords properly now. Either way they do seem like they take security seriously.

Any service that limits maximum length of the password means they are not hashing them. Which is a scary proposition, especially for such a huge service.

Ah, that’s the “your problem” approach to security.

Because as per usual they don’t understand security. I have started choosing my bank based on software they have. If software looks competent, that’s my most significant influence.

They think rooted device = insecure device, but at the same time PC is even less secure and yet all the business users use them and more to the point have passwords written on a sticky note glued to the screen. My old bank at one point “upgraded” their software system and then started asking me for weird characters in password and then asked for maximum length which was the final sin I allowed them to commit. Left them that week.

Not only proton, but unless you are rocking custom engine, pretty much all of them support Linux out of the box. It’s usually middleware that poses an issue and most importantly developer’s inexperience with the OS, which means they can’t provide tech support for their product.

Which is why you shouldn’t do that. Dependency nightmare is a real problem many developers face. More to the point they impose it on you as well if you are by any reason forced to use their software. Well established libraries are gateway to this. People are getting out of their way to complicate lives to themselves and massive amount of others just so they could avoid writing a function or two. Biggest absurdity I like to point out to people is the existence of is-number NPM package, which does that. It has 2300 dependent projects on it!!! Manifest file for said package is bigger than the source. And the author had the hubris to “release it under MIT”. How can you claim copyright on num - num === 0?

On all the projects I manage I don’t allow new dependencies unless they are absolutely needed and can’t be easily re-implemented. And even then they’d have to be already in the Debian respository since it’s a good and easy way to ensure quick fixes and patching should it be needed. Sometimes alternative to what we wanted to use already is in repo, then we implement using different approach. We only have few Python modules that are not available in repo.

Managing project complexity is a hard thing and dependencies especially have a nasty habit of creeping up. I might be too rigid or old-school or whatever you want to call it, but hey at least we didn’t get our SSH keys stolen by NPM package.

Ultimate ergonomics at the cost of entry speed.

There is an exploit which addresses copy pasting things in terminal. Where you’d copy one thing, but when pasting you get more than you bargained for. Any decent terminal would ignore \n for this reason or at least not treat it as pressing enter.

What is right clicking on terminal going to do?

I legitimately expected Terry’s TempleOS.

No. Since each partition gets its own UUID, it means it’s generated by the OS on creation, no matter the number of partitions. On boot kernel will scan all UUIDs and then mount and map according to them, which is sightly less efficient method than naming block device directly, but far easier for humans and allows you to throw your drives to whichever port you like.

Same experience I had. nVidia is not a complete deal-breaker but people just don’t realize how many small nagging issues owning nVidia card entails. Switching to AMD was an eye-opening event for me. Then I realized how often I got annoyed by old card.

My thinking exactly. That’s your card not working one day out of every 10. Imagine having issues once a week. I’d burn that card with termite and never look back.