Diseased Open Source Software Community - it's about ethics in Code of Conducts

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Linux 6.11 I2C Brings Arrow Lake H Support & Completes Slave/Master Transition (archive)
There are dozens of I2C host patches for Linux 6.11 to update the naming conventions used by the I2C code. That represents a majority of the changes this cycle. This is about removing the "master" and "slave" terminology and instead using "controller" and "target" terms. The master/slave to controller/target terminology change was also made upstream within the I2C v7 and SMBus 3.2 specifications.
Thank Floyd for these important changes!
 
It's not excitement. People remake applications all the time for various reasons. Different grep implementations have different performance and features.

Computing autism is the biggest enemy of computing.
I'll edit my post to include a screenshot later, but I like how the first thing that greets me on this page is ack!

Here's that screenshot. Why ack indeed:
Feature comparison of ack, ag, git-grep, grep and ripgrep.png
Anyway, my point is that grep is fundamentally uninteresting. Something that never occurs to these people is transforming the data into something more easily searched.
 
Last edited:
This is one of the biggest problems I have with it, you're mostly dealing with Rust as well compared to programming in general since you have a lot of enforced restrictions that you have to handle in a particular way rather than any sort of creative way that would still be correct.
Enforced restrictions are a Good Thing in programming. There's a reason well-organized projects use linters, static code analysis, tests, static typing, IaaC, and so on.
 
The excitement over a reimplementation of grep is just tiresome. Make something original for fuck's sake.
It is exciting because it is literally 6 times faster. 6 times. Literally saves hours of processing time when writing scripts that act on a huge amount of files.

I can give you something original, Nushell: https://nushell.sh/. Better than any posixshit shell, because it has types that actually do shit instead of everything being a string. And since it is in Rust, it can support Windows, MacOS and Linux thanks to the great ecosystem of crates. Much harder in C - can you even use a library without mass tinkering in it? No, because the build system of every C project is different. Cargo being THE standard is good because of this - it's fully featured and used by every project, making code sharing painless. The "muh bloated build system, i need to use bash" argument falls apart here - something being fully featured doesn't make it bloated, it makes it good (if it is used by everyone)

It has replaced python for me, on top of being my interactive shell. It is that good for scripts.

But I agree - if literally the only selling point your project has is X but in Rust, you are failing. Show me benchmarks, better error messages, a better interface and then I'll use your project.
 
Thank Floyd for these important changes!
I'm sure this won't get confusing as fuck. Like how with iSCSI the initiator is the client and the target is the server. It won't be confusing at all that the use of target in this context is actually the opposite of how iSCSI uses it.

If only there was a perfect set of terms to explain the relationship.
 
Until you find a case where Cargo is wrong, or doesn't do what you want, and then you're fucked.
Then you can write a build.rs.

Reminder:
QyBIbWE.png


You can't win by making your own "minimal" build system specifically tailored for a project, especially for something insignificant.

Bash is also more complicated than a Cargo.toml.
 
Then you can write a build.rs.

Reminder:
View attachment 6194137

You can't win by making your own "minimal" build system specifically tailored for a project, especially for something insignificant.

Bash is also more complicated than a Cargo.toml.
I don't know what a cargo is (from the sounds of it, it's a framework maybe), but all I know is you must write everything from scratch, stop being a niggercattle, be more like Terry. Write everything from scratch, no library.
unnamed.jpg
Bash is not a programming language, so lol. It's like saying Powershell or the macros in Powerpaint are a programming language.
 
6 times faster. 6 times
Where, when, and how? Not like it really matters anyways considering 90% of a scripts runtime is the latency that running 20 billion processes and piping them creates.
Better than any posixshit shell
A shell but it's typescript? The last gimmick shell "fish" was just shell but it types CTRL-R for you automatically. It died in the water because nobody is going to download some new shit incompatible shell to run your scripts.
Cargo being THE standard is good because of this - it's fully featured
It's fully featured if you're only interested in a single statically linked executable with either "release" or "debug" as its build options. God forbid you use dynamic linking, because Rust faggots literally do not care about that and will NEVER implement it. And before you go all usecase unclear on me, dynamic linking can't be replaced with static linking. You can run software built for a 20 year old glibc, you can link "OpenGL" and it'll magically load your specific graphics driver at runtime, you can load different versions of the same code designed for different microarchitectures or hardware. This is not nitpicking, there are multiple unfixable fuckups like this I can rant about like the entire language being implementation defined. Like the gnome devs, they copesplain that they're not needed because 90% of users don't require them. The attitude they have towards these types of things is why Rust in general will never be a serious systems language.
The "muh bloated build system, i need to use bash" argument falls apart here
Makefiles are so much simpler and so much more powerful. They can build anything you want, they are ACTUALLY fully featured. They're going to outlast Cargo because they're a tool that can and have adapted to change and are not hyper specialized and designed for one use case. If the Rust people weren't hacks they could've designed a better build system that even non Rust users would want to use for their projects, like Zig did.
Then you can write a build.rs.
This just seems to statically link C objects or generate more rust code that'll still be built with cargo.
 
I don't know what a cargo is (from the sounds of it, it's a framework maybe), but all I know is you must write everything from scratch, stop being a niggercattle, be more like Terry. Write everything from scratch, no library.
How many compilers have you written, nigger?
 
  • Thunk-Provoking
Reactions: UERISIMILITUDO
It is exciting because it is literally 6 times faster. 6 times. Literally saves hours of processing time when writing scripts that act on a huge amount of files.

I can give you something original, Nushell: https://nushell.sh/. Better than any posixshit shell, because it has types that actually do shit instead of everything being a string. And since it is in Rust, it can support Windows, MacOS and Linux thanks to the great ecosystem of crates. Much harder in C - can you even use a library without mass tinkering in it? No, because the build system of every C project is different. Cargo being THE standard is good because of this - it's fully featured and used by every project, making code sharing painless. The "muh bloated build system, i need to use bash" argument falls apart here - something being fully featured doesn't make it bloated, it makes it good (if it is used by everyone)

It has replaced python for me, on top of being my interactive shell. It is that good for scripts.

But I agree - if literally the only selling point your project has is X but in Rust, you are failing. Show me benchmarks, better error messages, a better interface and then I'll use your project.
I think widespread corpo adoption of Rust is just going to cause a chudstorm to swamp the trannies

Just on the basis of all the racist Indians in the motherland alone who would storm in. There's not enough white male troons to deal with the horde of pajeets.
 
The problem on KF is the most spergy people are arguing who seemingly don't have the experience to be taken seriously and incorporate trendy identity politics into everything.
That's not the problem. Everybody else has forced politics into everything (changing "offensive" coding terms, requiring CoCs, etc.). The hobbyist programming space has now been dominated by so-called "marginalized" peoples (mostly transgenders), which not only force leftist politics onto everybody, but have become a big enough part of this to enforce their personal morals as rules in many communities.

I think the rampant and sudden change from how things used to be to how they are now is very much just untreated autism, and in a space where basically anyone worth their salt is autistic, they get drawn to it. Problem is, these people often don't have friends, and when they go online they see these "accepting" communities (poggers community, breadtube community, LGBT community, et al.) and join them, and from there, some of them end up falling down, and some end up realizing it's all intentionally predatory.
 
Everybody else has forced politics into everything
Including some users on KF who cannot separate the technology from some of its users.
The opposite mentality of sticking with outdated tech to stick it to trannies and globohomo ensures those people will be left behind. It's an incredibly immature way to look at things and that behavior bleeds into online discourse with both sides of the same coin. Both of these types of people then cause the drama posted in this thread.
 
Back