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

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Alright I guess that won't work, so let's try a different tact.

How would you go about making a joke language called STAINLESS that is marketed as vastly superior to Rust but is effectively just C but with some of the bits renamed?
 
How would you go about making a joke language called STAINLESS that is marketed as vastly superior to Rust but is effectively just C but with some of the bits renamed?
i assume write a c compiler but fuck up several bits along the way
 
Rust is less complex than C despite providing "more power".
That is one bold statement to make.
Would you also say it's easier to make a Rust compiler than a C compiler? (from scratch)
step 1 of making c good is probably giving it a lisp-like syntax
If you define "good" as never getting complaints, you're definitely right.
There are only two kinds of languages: the ones people complain about and the ones nobody uses - Bjarne Stroustrup
 
If you define "good" as never getting complaints, you're definitely right.
people do use lisp though
i have also observed that most of the people who complain about it all the time have never used it
the history of programming has been a long struggle from fortran niggers that don't understand why somebody would have functions to where we are today (nigger programmers barely accepting lexical closure) and eventually we will have to convince the retards to use s-expressions like we were meant to, instead of following the siren song of the mathniggers and their gay retarded infix syntax
 
On one hand C has a fantastic legacy and was developed by generations of men and women that I have tremendous respect for.
On the other hand it would be really funny to have Rust be the most popular language for +NIGGER projects
 
I want my next computer to boot straight into FORTH.
The 1980s called, they want their ideas back.
Jupiter-ACE_small_system_(modified).webp
 
That is one bold statement to make.
Overly generalized as you're right to prod at. I meant from a syntactic point of view. The notion of the C preprocessor is something Rust does away with and simplifies. So there's a whole pass that's done away with.
 
"A little bit more complicated" is basically C++. The problem is that you don't want more complicated than C, syntactically speaking. C is already much more complex than any of its competitors in terms of implementation details, save C++. Rust is less complex than C despite providing "more power". But you correctly perceive that there's a market for "C but a bit less complex". Most go "C but a bit less complex and a bit more high level" (ie. Rust, Jai, Zig, Nim, whatever), but very few go "C but a bit less complex and a bit more low level".
Too bad D never really took off. It was largely a reaction to the complexity of C++ and it was supposed to be a "Better C". It actually does ship with a compiler mode called exactly that. Technically still usable today, but I don't think it's suddenly going to take off. It has some niche users and that's about it.
 
Too bad D never really took off. It was largely a reaction to the complexity of C++ and it was supposed to be a "Better C". It actually does ship with a compiler mode called exactly that. Technically still usable today, but I don't think it's suddenly going to take off. It has some niche users and that's about it.
Didn't it have the issue of its spec or its reference compiler being proprietary and closed source? Or am I thinking of another language who's adoption was hampered by that?
 
Troons have been raiding the pull requests section of the Linux kernel's Github mirror for the past days. Pull requests aren't accepted there but since there is no way to disable opening a PR on github it's a completely unmoderated shitposting area.

One of the largest now is one titled " transgender lesbians please dm me" (archive). Over 600 replies from 200 people, almost all of them exactly of the kind you think they are, some posting Discord usernames and pictures to go along. (Viewer discretion advised for the last part)
Are you fucking kidding me. TTD. Forever and always.
 
I worked professionally with Forth a long, long time ago and my mind keeps looping back to that language to the point that I made a forth-based computer a few years ago. It's an impossibly elegant language which always will stick with me. It's great for implementing distributed computing, it's great for writing drivers, it's great to whip up communication protocols, or truth tables for some logic. It's even great to write fast, complex programs like an text editor. All on the fly and ad hoc, without restarting or compiling anything, on everything that has just the faintest processing power and a few kb of RAM. I always say this to everyone when forth comes up: Learn it (there isn't really anything to learn), solve some problems with it. Read the excellent book "Thinking Forth". It'll make you a better programmer no matter what you primarily do, 100%.

Funnily enough, lisp landed with me only relatively late in life, even though in a way, they're two sides of the same coin. I also just recently discovered smalltalk and it's another of these elegant languages I'd recommend looking at.
 
View attachment 7945031

Fortunately a lot of the photos have been deleted, this thread should be archived quite fast.


This alone is the biggest problem with the "put rust in X" crowd. Open source software is open source. Anyone can take it and rewrite it in their favourite language. Same applies to closed source, you can write a clone. But you better have good reason to mix two mutually exclusive languages in a single project, because in 99% of cases this gives no advantages and makes it more difficult to build the project. Thats how you end up with currycode that builds only on a specific version of Ubuntu LTS or other retarded concepts that plague modern DevOps.
linus went through and personally closed all outstanding PRs 6 hours ago. I'd love to know what was on his mind as he did it.
 
Troons have been raiding the pull requests section of the Linux kernel's Github mirror for the past days. Pull requests aren't accepted there but since there is no way to disable opening a PR on github it's a completely unmoderated shitposting area.
I wish this would've been enough of a stink that Linus would have a juicy rant to post on the mailing list, but that's :optimistic:
 
Back
Top Bottom