@Suiseiseki__dup_8529@freesoftwareextremist.com
2026-01-02 11:28 UTC
Replies (22)
-
@phnt@fluffytail.org 2026-01-02 11:32
@gnu2 The thing is, I would expect from a software project that is probably the most matured overall from all free software and open sores software, to be the most stable. But somehow it isn't. Technically it's not a GNU issue, but a maintainer of GNU software issue. Which is mostly IBM or to be more technically correct Red Hat. And also a lack of competition for GNU. As an example GCC was quite stagnant in development until LLVM/Clang became good enough, which prompted more GCC development and now they are on par again. More GNU projects need competition, because so far the overall GNU mentality that radiates on the Internet, including on Fedi with a certain user in this thread, is why update something that is already perfect. Something needs to shatter that perception of reality, because nothing GNU is perfect.
-
@phnt@fluffytail.org 2026-01-02 11:38
@fluffy@fsebugoutzone.org @Suiseiseki@freesoftwareextremist.com @p@fsebugoutzone.org @bonkers@nerdculture.de >these are characteristics of people with early onset alzheimers and dementia. He's just too autistic to realize that he can be sometimes wrong. The usual reply of his to the previous sentence is: I've been clinically tested to be not autistic and I'm never wrong.
-
@nigger@detroitriotcity.com 2026-01-02 12:02
@p@fsebugoutzone.org @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de message passing inter computers is good, but within a computer, shared memory is all you have. cargo with partial compilation, dynamic libraries and whatnot is actually the one thing I don't like about the language. with retarded libc wrappers you could have memory safety but that would have overhead. the point about rust is that there isn't any. oh, just theoretically you can have memory safety if you use this toolchain and re-architect all your programs and convince upstream to do the same as well. :shrug: rust's error handling is actually modern. programming languages had magic values, null and try/catch shit for ages. and nobody says rust is groundbreaking in any one thing, it's that it used its timing to learn from and combine all the best parts to be better than any existing language. object oriented programming is also a style, but you can't really do it without struct pointers. same deal for functional regarding iterators with methods and lambdas. rust macros are closest to lisp's, not Cs. I brought up :rms: being a kike because he's the one that decided that gcc should be unusable as a library, to force people to use it directly rather than as part of a proprietary pipeline. one such use was for a new language, which use LLVM satisfied.
-
@nigger@detroitriotcity.com 2026-01-02 12:19
@p@fsebugoutzone.org @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de compiler diagnostics are part of feedback. and I had GCC do that to me recently, where I changed a function from int to float, but forgot to change it's input in the signature to a float rather than an int. all good, truncate that shit, I didn't need the decimal point anyway. ironically, rust is more explicit than C. GC is very important to mention. rust has memory safety *without overhead*. that's the whole point. as does ada, but the u.s government didn't want that to be actually used by people. your reading comprehension isn't home? whether rust is good didn't even matter for my point, only that it was enabled by apple being less jewish than stallman.
-
@nigger@detroitriotcity.com 2026-01-02 12:40
@p@fsebugoutzone.org @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de okay, it's probably better implemented for other reasons. still 10x better.
-
@NonPlayableClown@postnstuffds.lol 2026-01-02 12:41
>"Thinking this language is shit is projection because it's obvious the real reason...IS JEWS." Oi vey guess we know who runs big code. 🤣 I'll stick with RISC-V then :NerdyDanielS:
-
@collappsar@fediverse-lite.com 2026-01-02 12:48
@p@fsebugoutzone.org @nigger@detroitriotcity.com @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de Tony Hoare found when he gave people the option of using bounds checking with some overhead nobody turned it off because the benefits outweighed the cost.
-
@nigger@detroitriotcity.com 2026-01-02 13:14
@p@fsebugoutzone.org @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de right, bounds checking is the exception. but use after free and so forth are not resolved with runtime overhead. >You say that like you're being sarcastic but you are literally suggesting that for Rust instead of some hypothetical libc thing that you have constructed as a strawman. No, the libc thing was with regards to haskell etc. that was for static analysis, which I presume CSP is as concerning actual usage. it has to actually be used, and it isn't. and to have it start being used, you need to rewrite, and re-architect. at which point you may as well do so in rust. for the fourth time, rust is not merely memory safe. it is memory safe without reference counting. >So? Who the fuck cares? well, the authors of all the software that uses clang instead of gcc because it's not headed by a greasy jew who sabotaged his own project so it would be useless to any dev other than himself. https://lists.gnu.org/archive/html/emacs-devel/2015-01/msg00027.html my emacs config framework uses clang for this because of stallman's spiteful design lmao.
-
@phnt@fluffytail.org 2026-01-02 13:18
@p@fsebugoutzone.org @nigger@detroitriotcity.com @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de >No, I knew you had a rainbow-colored prompt before you posted a screenshit of your macbook, sir. A Luke Smith one no less. I know, because I also stole it :D
-
@nigger@detroitriotcity.com 2026-01-02 13:19
@p@fsebugoutzone.org @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de >What are you, 20? When you have learned more languages, you will be able to understand that style transcends language. You haven't seen someone do FP in assembly language, you haven't understood what REST really is, you don't actually understand the machine. 十年早いんだよ。 sure, if you pass around the address of a byte array you can call that an object, but a high level programming language can do better regarding ergonomics, and rust does
-
@nigger@detroitriotcity.com 2026-01-02 13:23
@yaboisugoi@fsebugoutzone.org @Suiseiseki@freesoftwareextremist.com @p@fsebugoutzone.org @bonkers@nerdculture.de that's a community problem. rust has a code of conduct and a dozen discord servers for its community as well, I don't care, I either regard the technology or I don't. the guy behind your second paragraph is just an obvious troll, because defending rust will annoy people
-
@NonPlayableClown@postnstuffds.lol 2026-01-02 13:45
> I demand that IPv6 be repaired before anyone else adopts it. Seconded
-
@takao@shitposter.world 2026-01-02 13:46
@p@fsebugoutzone.org @nigger@detroitriotcity.com @phnt@fluffytail.org @Suiseiseki@freesoftwareextremist.com :rokalife:
-
@nigger@detroitriotcity.com 2026-01-02 13:51
@p@fsebugoutzone.org @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de sudo grep hides the "oy vey linux says you can't read that file!" errors and another useful thing ripgrep does is use the gitignore, which makes it really useful for IDEs, and is one of the things a programming language is better at than shell scripting yep, those are different, almost all of them will break when they see a filename with a space in it. grep -r being the exception
-
@phnt@fluffytail.org 2026-01-02 13:52
@p@fsebugoutzone.org @nigger@detroitriotcity.com @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de https://github.com/LukeSmithxyz/voidrice/blob/master/.config/zsh/.zshrc#L5 luke-smith-proprietary-sink.mp4
-
@Whitewall_Blasphemy@poa.st 2026-01-02 13:57
@p@fsebugoutzone.org @yaboisugoi@fsebugoutzone.org @nigger@detroitriotcity.com @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de >Even the U.S. Federal Government has come out in support for rust I can see where this is going.
-
@Leyonhjelm@shitposter.world 2026-01-02 15:59
@p@fsebugoutzone.org If a programming language cares who uses it it’s not a real language. It’s a club. And one I want no part of. @nigger@detroitriotcity.com @Suiseiseki@freesoftwareextremist.com @yaboisugoi@fsebugoutzone.org
-
@phnt@fluffytail.org 2026-01-02 18:58
@p@fsebugoutzone.org @amerika@annihilation.social @nigger@detroitriotcity.com @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de The commerical connection from ISP at work doesn't even allow V6 transit, because some of the upstream pops don't support it. At home, my fiber connection doesn't have any V6 transit either. The transitional services aren't deployed on either ISPs side.
-
@Economic_Hitman@shitposter.world 2026-01-02 16:18
@p@fsebugoutzone.org When an Irony Enjoyer :chad2: explains the joke to an autist
-
@mangeurdenuage@shitposter.world 2026-01-02 19:56
@p@fsebugoutzone.org @nigger@detroitriotcity.com @Suiseiseki@freesoftwareextremist.com @Mamako@tsundere.love Microsoft made protocols :shrug:
-
@latein@cawfee.club 2026-06-18 12:22
@p@fsebugoutzone.org @nigger@detroitriotcity.com @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de I see what you mean by this now, I started working on my own language and I see that compilers are trivially distributable so having a compiler written after 2010 that isn't is retarded. my plan is to have the main interpreter spawn interpreters and pass messages, source code is a message, errors are messages, the target code is a message, and then all I'd need is to make the interpreter agnostic to whether it's reading its characters from a char*, file handle, pipe, TCP connection etc. (and the other way for linking from memory region, filename, network etc.) I've got picrel to read first before the CSP text but I will do that, sounds like it'll be invaluable for when I start writing schedulers and whatnot
-
@latein@cawfee.club 2026-06-18 22:10
@p@fsebugoutzone.org @nigger@detroitriotcity.com @Suiseiseki@freesoftwareextremist.com @bonkers@nerdculture.de this is not a bytecode VM, such resources are still interesting but this is a ast walking VM, with fundamental semantics identical to C's so that it'll be trivial to transpile to C and JIT hot loops into machine code that way, even without giving JIT explicit VM support beyond FFI. this is the only reason I'd bother as "low level lisp with C constructs as primitives" doesn't seem to be a thing yet. well, except for carp but that sounds like it replaced GC herpes with mandatory ownership and borrow checking turbo-AIDS, when my original purpose was just an ergonomic C wrapper