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

[Kiwi & Cow]

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.

It's obvious you're talking about me, just sayin' if you got a problem with my shitposting we can talk this out bro.

My initial few comments a few pages ago were in response to Cola guy and weirdass PFP guy tryna persuading his opponents that his coding cult is the best because Null uses it. It's fucking annoying, happens too often here and I'll make sure to make it a fucking problem. There was no opinions on politics anywhere by this point, just facts. Maybe except older posts past that point IDK.

After that, and starting with this post I was just reiterating what I said and demonising the language for its relationship with trannies because I was hoping they'd relent and fuck off. If you like Rust that much why not make a thread for it?
After Null replied, (BTW directly contradicting his own statements just because he probably doesn't want to be here,) I went full shitposter mode I literally gave no fucks anymore.

I can't speak for what other ppl said, but all you need to know is rusty fanatics want you to convert to Rust and shit's pissed me off. If you love your toy language so much, don't be a sore asshat everytime someone says anything negative about it because it's used mostly by troons.
Apparently it's not the first this thread got derailed by these guys, they did it before and caused it to get marked as infected, congrats gents. Maybe with enough of your rust autism maybe you'll finally get rid of the troons infesting github.

Also final note bad analogy. Windows XP is outdated and if you stick to it you're a retard. C++ is still widely used and gets updates to this day while Rust is again the same thing, but easier to use and with its own limitations becos they removed core components that were in C and C++. I don't care I don't use any of these languages, the only 1 I had ever used was C# because of gamedev yaddy yadda, but I like to stick it to retards who are being preachy pricks.

Same reason I'd stick it to WEBP tards (I can guarantee they're also on KF, you know who you are), people say it's better and maybe it is, but I'll never use it, I don't want to use, I see no benefit in using it over PNG and ontop of alldat it's fucking annoying when forums like KF don't support it so I got to change it back to PNG. Fuck these cunts and fuck the cunts who are so obsessed with a computer language they're arguing till the bitter end how much you got to use it over everything else.

 

[The Mass Shooter Ron Soye]

https://kiwifarms.st/threads/programming-thread.41367/

This appears to be the better thread for sperging about Rust, C++, etc.

 

[AnOminous]

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.

That's probably why I've been baffled by it. Almost everything I've encountered from some soydev in Rust is some rewrite of something that often is actually even worse than the original, and it seems like whenever I look up the coder their pfp is a fucking pony or something.

 

[geckogoy]

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 finally figured out what was bothering me about this, how does this make logical sense? Thats pretty much always going to be IO bound unless the implementation truly and terribly sucks, how is there any way to possibly 6x that?

 

[Shalalallah Akbar]

I finally figured out what was bothering me about this, how does this make logical sense? Thats pretty much always going to be IO bound unless the implementation truly and terribly sucks, how is there any way to possibly 6x that?

Regex can occasionally be terribly slow when certain pathological patterns and inputs are used due to the amount of backtracking that has to be done, could be that instead of IO. Here's a link.

 

[DavidS877]

I finally figured out what was bothering me about this, how does this make logical sense? Thats pretty much always going to be IO bound unless the implementation truly and terribly sucks, how is there any way to possibly 6x that?

I spent 30 seconds checking and, yes, for at least one sample it's contrived:

Here is a straight-up comparison between ripgrep, ugrep and GNU grep on a file cached in memory

For that file it says 13GB, ~1 second for the rust one, ~6 for GNU grep. For a 6Gbps SSD the file read time would be ~17 seconds, so that would not be able to improve(assuming you can do IO and grep in parallel like most computers) For an NVMe, sure that would likely be an improvement, maybe.

Of course if you're really searching stuff often we have these fancy things called 'databases' which can optimize and index.

 

[anustart76]

Of course if you're really searching stuff often we have these fancy things called 'databases' which can optimize and index.

Don't use the tried-and-true DBs like Postgres or MySQL, make sure to only use the latest Mongo(loid)DB slop, or even better, proprietary services like Snowflake that leak all your data!

 

[Kola]

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.

Huh? Fish is very active and has a constantly growing number of users. Don't tell me you didn't know you can use a shebang to run your scripts with whatever shell you want? Otherwise I don't know how this is supposed to make sense, you can use whatever shell for whatever use case you want.

 

[RGBCube]

Huh? Fish is very active and has a constantly growing number of users. Don't tell me you didn't know you can use a shebang to run your scripts with whatever shell you want? Otherwise I don't know how this is supposed to make sense, you can use whatever shell for whatever use case you want.

He probably hasn't used anything other than Windows command prompt. Stop engaging and actually make fun of some retards like Drew.

 

[HootersMcBoobies]

Huh? Fish is very active and has a constantly growing number of users.

I think I've used it for well over 10 years at this point. It's an amazing shell. It's not just "auto ctrl+r." It shows you predictions based on the directory you're in (prioritizing the previous commands in that directory). It comes out of the box with some pretty amazing defaults for history and searching, without needing a ton of custom zshrc shit. You can use alt+arrows to jump back and forth in your visited directories stack. It's honestly a really good shell and it's only gotten more stable over the years.

 

[unhealing wound]

Huh? Fish is very active and has a constantly growing number of users. Don't tell me you didn't know you can use a shebang to run your scripts with whatever shell you want? Otherwise I don't know how this is supposed to make sense, you can use whatever shell for whatever use case you want.

Sorry I assumed he wanted to use it for scripting because he was talking about grep performance and types, and I have never heard of a fish script despite it being hyped up so hard. Buffed interactive shell sounds like a good idea though it also seems like it'd be annoying unless you can use it over ssh with a local config like that emacs thing.

 

[CrunkLord420]

The only bad thing about webp other than shitty support is the lack of higher bitdepth (for heightmaps and stuff) and the ambiguousness of lossless vs. lossy vs. palette mode within the library itself (IIRC it's been awhile since I worked with libwebp). In my usecase, which was palettized lossless images, webp outperformed png by like 25%.

Meanwhile everyone cries about it because lazy devs I guess.

 

[UERISIMILITUDO]

Reminder:

Oh look, the cargo cult made up their own version of Greenspun's tenth rule:

Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.

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

Who needs a build system? I just dump all of the Ada I've written in the same directory, and the compiler finds everything for me. Any decent language either provides something that does this kind of thing, or it clearly doesn't need it to start.

Of course if you're really searching stuff often we have these fancy things called 'databases' which can optimize and index.

Blah blah blah, UNIX philosophy, blah blah, flat files, blah blah, suckless, blah blah, simple. They don't do it because they're retarded.

The only bad thing about webp other than shitty support is the lack of higher bitdepth (for heightmaps and stuff) and the ambiguousness of lossless vs. lossy vs. palette mode within the library itself (IIRC it's been awhile since I worked with libwebp).

Oh, and the flaws in the reference implementation don't help either:
https://blog.cloudflare.com/uncovering-the-hidden-webp-vulnerability-cve-2023-4863/ (archive)

Image files contain compact information about the shape of the Huffman tree, which the decoder uses to reconstruct the tree, and build lookup tables for the codes. The bug in libwebp was in the code building the lookup tables. A specially crafted WebP file can contain a very unbalanced Huffman tree that contains codes much longer than any normal WebP file would have, and this made the function generating lookup tables write data beyond the buffer allocated for the lookup tables. Libwebp had checks for validity of the Huffman tree, but it would write the invalid lookup tables before the consistency check.

Libwebp is a mature library, maintained by seasoned professionals. But it's written in the C language, which has very few safeguards against programming errors, especially memory use. Despite the care taken in the library's development, a single erroneous assumption led to a critical vulnerability.

Google covered its ass and left everyone else high and dry. A single bounds check would've prevented this unacceptable shit but, as we know, retards never learn. C language programmers may as well be the lolcows of the programming universe.

Meanwhile everyone cries about it because lazy devs I guess.

Fuck Google, its shitty protocols, and its shitty formats.

 

[RaincoatWithAHat]

Alright guys, where do you get your diy hrt?

 

[Autism Contractor]

C language programmers may as well be the lolcows of the programming universe.

You write a lot about hating C languages, so maybe I should sit down and learn one. If it pisses you off enough to learn whatever the esoteric fuck ada is then it's probably a pretty strong language.

Also implicit tranny rust hate post for good measure. If you're too coom brained to manage memory then you deserve to get your buffer overflowed.

 

[UERISIMILITUDO]

If it pisses you off enough to learn whatever the esoteric fuck ada is then it's probably a pretty strong language.

That's a foolish attitude. Regardless, here are some manuals:

https://www.gnu.org/software/c-intro-and-ref/

https://www.gnu.org/software/gnu-c-manual/

I took Stallman's advice and started reading these, many years ago, but learned the simplicity of the C language to be a lie in doing so; thus, I continued with Lisp, also taking his advice.

Have fun learning about sequence points and everything else. Here are two esoteric constructs in the C language one must learn to have mastery over the language; the first is Duff's Device:

void
copy (char *to, char *from, int count)
{
  if (count <= 0)
    return;
  int n = (count + 7) / 8;
  switch (count % 8)
    {
      do {
        case 0: *to++ = *from++;
        case 7: *to++ = *from++;
        case 6: *to++ = *from++;
        case 5: *to++ = *from++;
        case 4: *to++ = *from++;
        case 3: *to++ = *from++;
        case 2: *to++ = *from++;
        case 1: *to++ = *from++;
        } while (--n > 0);
    }
}

Duff's device is well-known compared to Pigeon's Device:

int pigeons_device(int a, int b, int mode) {
    int result;

/* Isn't C a wonderful language? */
    switch (mode) {
        case 0: if (gloop(a, b)) {
        case 1:     result = arfle(a, b);
                    break;
                } else {
        case 2:     result = barfle(a, b);
                    break;
                }
    }
    return (result);
}

The author of that article included this nice control-flow diagram:

If you're too coom brained to manage memory then you deserve to get your buffer overflowed.

This sentence is pure retardation, to put it simply. Stop writing like a fucking retard. Masturbation has absolutely nothing to do with the manual management of memory. I write machine code for fun, notice that last word, fun. Computers exist to automate work, and manual anything has no place in a serious process except where absolutely necessary. Go work for Crowdstrike.

I'd like to write a longer post, bitching about wading through C language header shit, TIOCSWINSZ, and other worthless shit, but I'll leave it at this.

 

[Autism Contractor]

Masturbation has absolutely nothing to do with the manual management of memory.

Would you happen to have been classified as Asperger's?

Computers exist to automate work, and manual anything has no place in a serious process except where absolutely necessary. Go work for Crowdstrike.

You say this but I'm willing to bet the issue was caused by an automated test returning a pass. Or is was standard rent-a-pajit activity.

Thank you for the C examples though. If only I had a project that required anything more advanced than python.

 

[The Real Slim Shady]

Have fun learning about sequence points and everything else. Here are two esoteric constructs in the C language one must learn to have mastery over the language

Both of these constructs are easy if you understand the control flow of the language, doubly so if you have a vague idea about what machine code is being generated. If you do not know how this works, you do not know how imperative languages work. The second example is somewhat abusive of the syntax, but valid and i would not call it unclear. If i was to for some reason use it in production code i'd make sure to add a comment explaining it.

Duffs device is nothing more than a jump table. The other construct is just a Duff's device used inside an else if.

What is so difficult to understand "if this, then program execution jumps to that line"? And if you want to go down the theoretical road they would work the same on a turing machine with an infinite tape - "if this, then go to that cell". I agree that program execution suddenly jumping into a middle of the loop can be surprising but it is a valid flow and if you know what you are doing and it makes sense then its OK.

 

[UERISIMILITUDO]

Both of these constructs are easy if you understand the control flow of the language, doubly so if you have a vague idea about what machine code is being generated.

Sure, I've written machine code like Duff's Device before, and it's not difficult to understand.

The second example is somewhat abusive of the syntax, but valid and i would not call it unclear.

It's totally bizarre coming from any other language.

What is so difficult to understand "if this, then program execution jumps to that line"?

So, I've introduced these constructs to C language programmers who had used the language for years unawares of such things. It's deeply unsettling when one realizes how loose the syntax is. I won't even bother to write an example in another language, because it just wouldn't make any sense. In no other language of which I'm aware is it possible to break these constructs into pieces and place these pieces across the boundaries of another construct in this way; this is because most languages very clearly specify how things work. Even in Forth one doesn't write code like this.

Again, it really makes no sense to even try to think of these things in another language; that's how queer they are. Now, it's not hard to write a jump table in other languages, but it's not done by shoving a loop through a case construct like this; it really just makes no damn sense. Besides, it's not as if these constructs are actually useful; every efficient memcpy routine is written in machine code, and I don't even know for what Pigeon's Device is good, beyond perhaps some irrelevant micro-optimization.

 

[teriyakiburns]

So, I've introduced these constructs to C language programmers who had used the language for years unawares of such things.

That's because these are the sort of hyper-optimisations that don't really achieve much and only exist for bragging rights. Every language has some quirky little construct like this, which someone invented purely because they could, that might achieve a half microsecond improvement. It even says "a special way to use switch", indicating that it's not normal. And as the other one says: Why might one want to do that? The simple answer is "because one is a pigeon". You're only singling these out in C because hating C is your autistic fixation.