Oh man! I hate CF! The scummy gatekeepers.
Oh man! I hate CF! The scummy gatekeepers.
He didn’t just wash off his hands. When asked in an interview about a moderator who edited a trans user’s profile to intentionally misgendering them (yup, even that’s not off limits for their mods), he justified it saying that ‘It’s not like using the N-word or something’. (For context, the n-word itself was innocuous. It gained notoriety due to its misuse by bigots like this).
There are several such examples - repeatedly even after being called out. I don’t belong to any diversity groups. But I don’t care if they make the world’s best operating system. I will stay well away from it if only to avoid any interaction with such a group. They’re a bit too happy about harassing people (not just transgenders either).
Arch guide expanded in scope IMO. The choices are way more than in the past. However, it’s good quality and easy to read. I implore you to skim it, even if you don’t try it out.
Nvidia is a mess on Linux in general, though it’s gradually improving. They decided to neglect everything that the other GPU manufacturers and the community were doing and roll out their own buggy concepts.
This really isn’t the fault of Mint. PopOS works with it just because its developers System76 also has a line of nvidia based hardware. However, as I said before, nvidia is slowly starting to implement the standards and situation on other distros like Mint will gradually improve.
Meanwhile, I’m curious. What hardware did you try Mint on?
I wonder what happened to Tails - the one that started it all.
I do recommend Gentoo (haven’t tried Funtoo) for the academically inclined. It’s a beast to maintain, but you’ll soon find yourself at ease with configuring and compiling your own kernel, configuring your packages and even making some yourself.
It isn’t as hard as people make it out to be - if you gradually push your boundaries. In particular, it’s good if you already use Arch.
Why are sensitive or critical hospital systems loaded with bossware? That itself is a breach of medical safety regulations and medical privacy. If such bossware fails for whatever reason - even sabotage, it’s on the leach class. Prosecute them for murder.
In that case, it’s time for the average workers to sabotage the bossware. Let the leech class solve the problem they create.
I thought IBM was still stuck with Watson. Have they moved on?
The problem is that all of those interdependent parts and software that are dependent on it become entrenched. There is no freedom to replace individual parts with an alternative because something else will break. That’s what I call ‘Modular in theory, monolithic in practice’.
For anyone looking to learn git, the official book and site are thorough and exceptional. You can even download the eBook for free. While there’s no harm in using other sources to learn git, don’t use them as an alternative to the canonical source.
I wonder if these trillion dollar companies offer support contracts for astroturfing on social media on their behalf. I can’t think of any other way so many people are supporting their sociopathic attitude.
The devs don’t take an issue with the ticket being filed. They’re irritated by one particular reply which sounds like “My million dollar product depends on this bug fix. Please do that for me”. MS isn’t offering a solution. They’re asking for one.
To be fair MS offers an amount for the fix. Most companies just bully the devs instead. However, I don’t think it’s quite fair (though legal) to offer one time payments for a core library that they use.
Those same companies tell you that their products that you paid for don’t belong to you. You are just buying a license to use them. Sadly, this asinine concept is spreading even to hardware markets.
I think it’s fair to ask them to take their own bitter pill. They should also invest without owning.
The hack is still not fully understood and is being analyzed. It doesn’t help that Github suspended everything, including the original maintainer’s account (who is believed to be a victim of social engineering).
Anyway, you will eventually see a post mortem. I’m willing to bet that it’s going to be as phenomenal as the hack itself. The case and its investigation is going to be a classic case study for all security researchers and security-minded users. Anyway, I doubt that the attackers will ever be found. Jia Tan, Jigar Kumar and others are going to remain as ghosts like Satoshi Nakamoto.
They really ought to have version masking like in Gentoo portage.
Peter Thiel is insolent enough to say out loud what these companies practice - ‘competition is for losers’. These quasi-monopolies aren’t here to provide the best value - quite the opposite. They want to kill all competition by any dirty tactic and then use the diminished choice to wring the customers of every penny they have. They want to extract maximum revenue by making sure that their inferior solution is the only option customers have.
This problem isn’t solvable by market regulation alone. The world has enough a*****es around who will climb to the top of successful companies and find ways around the regulations. They’re being as bad as they can, while skirting the limits of what’s illegal. My main gripe is with the engineers, programmers, technicians and all technical creators who enable these scumbags. It’s not hard to see that supporting a proprietary solution amounts to yielding the consumers’ bargaining power to a monopoly. Despite that, they keep making these choices. For example, it’s not uncommon to hear senior engineering managers or technical-lead level employees saying, “I know that Chrome is spyware and I want to quit it. But this <stupid-webservice-at-office> works only on Chrome”. I feel like screaming at them that if they’re too incompetent to demand a change at the level they’re at, they’re in the wrong profession.
If you’re a technical creator, your choices matter. It affects a lot more people than you alone. But more often than not, I see such creators surrendering principles in exchange for convenience. They hold as much responsibility as the market-abusers in making the world the way it is now.
Interesting that they started dictating what you can and can’t do with YOUR program! Consumer rights are a joke to these quasi-monopolies.
CUDA is an API to run high performance compute code on Nvidia GPUs. CUDA is proprietary. So CUDA programs run only on Nvidia GPUs. Open alternatives like vulkan compute and opencl aren’t as popular as CUDA.
Translation layers are interface software that allow CUDA programs to run on non-Nvidia GPUs. But creating such layers require a bit of reverse engineering of CUDA programs. But they are prohibiting this now. They want to ensure that all the CUDA programs in the world are limited to using Nvidia GPUs alone - classic vendor lock-in by using EULA.
Gitlab is very complex and a heavy resource hog. You probably don’t need it. Most small to medium enterprises can comfortably host their projects on lightweight forgejo or gitea (speaking from experience). They even have functionality similar to github actions. If you need anything more complex, you are better off integrating another self hosted external service to the mix.