Programming thread

  • 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
i have now realized that the funny i tried to make wasnt as funny nor entertaining as i thought it would be
i sincerely apologize for the negative emotions my post may have caused

i still prefer eupl though
 
"stallman is jewish" boohoo nigga why does it matter. are you going to throw out your computer because a jewish person might've worked on it?

stallman's work with the fsf is the sole reason we don't eat even more shit from proprietary companies like microsoft then we do now. if jews got together and threw billions of dollars at the linux kernel i would allow them a little genocide as a treat
If you want to do any Jew-free computing you're going to have a very hard time:
I hate niggers just as much as any white nationalist but they should do a little more research on all the "white" inventions they are proud of
Stallman is the second whitest person after Terry. You are clearly a nigger simply for hating Stallman and his achivements towards freedom.
Or is he?
terry-a-davis-chad-vs-virgin.png
 
If your FOSS licence isn't +NIGGER you aren't even trying.
 
Is neovim any good for powershell? The program is only meant to run on Windows machines but I am not on Windows myself.
I have been developing this project for years on a VM in the powershell ISE because I'm a lunatic, but it's become a more major part of my job since it's gotten useful enough that everyone wants to utilise it, and that means I have to have standards.
My baby's all grown up, it's not just my personal little multi tool anymore :feels:
 
Is neovim any good for powershell? The program is only meant to run on Windows machines but I am not on Windows myself.
I have been developing this project for years on a VM in the powershell ISE because I'm a lunatic, but it's become a more major part of my job since it's gotten useful enough that everyone wants to utilise it, and that means I have to have standards.
My baby's all grown up, it's not just my personal little multi tool anymore :feels:
Alacritty on Windows works just fine, or any other Windows tty emulator.
 
InMyStaticallyTypedLanguage.png
Reattached because of how wrong it is. Bottom case doesn't fail. There's no segmentation fault if the pointer goes to a char*. You just get the first {32,64,...} bits interpreted as an "int". You have to eg. inject an int as a char* to get a segfault. But then even void* doesn't resolve it. It breaks my brain to think how someone could be this wrong. There's more here too that I'm not mentioning. Not gonna type it all out. I'm just astounded at human stupidity. Flummoxed, even.
 
Isn't that just the BSD license with (or perhaps without) extra steps
To quote wikipedia:
The BSD license is a simple license that merely requires that all code retain the BSD license notice if redistributed in source code format, or reproduce the notice if redistributed in binary format. The BSD license (unlike some other licenses e.g. GPL) does not require that source code be distributed at all.
This happens to present the same dilemma about forcing users to use specific licenses when redistributing.

So to answer your question, it's effectively without extra steps. There are no steps for users except to enjoy the stuff freely given to them. Or they can hate it; it's their choice. I'm not their mama. I'm not nearly fat enough.
 
It breaks my brain to think how someone could be this wrong.
What do you mean wrong? _It's C_.

C just segfaults all the time for no reason at all, especially when pointers are involved, and that's why we need to re-write the entire universe in Rust.

Unlike C, Rust is **100% safe** and has never had any bugs or exploits. _Fact_.

Such mistakes aren't possible with Rust as `rustc` simply wouldn't compile such obviously broken code!

Only C could have a CVE rated 10 on the Richter scale! 🤣🤣🤣 https://app.opencve.io/cve/CVE-2024-24576
 
View attachment 8105928
Reattached because of how wrong it is. Bottom case doesn't fail. There's no segmentation fault if the pointer goes to a char*. You just get the first {32,64,...} bits interpreted as an "int". You have to eg. inject an int as a char* to get a segfault. But then even void* doesn't resolve it. It breaks my brain to think how someone could be this wrong. There's more here too that I'm not mentioning. Not gonna type it all out. I'm just astounded at human stupidity. Flummoxed, even.
Probably made by some retarded uni student who has to use C for a course. 99% of programming memes are made by retards.
 
Back
Top Bottom