a couple years ago lunduke documented that gnome redirects money donated to develop GNOME Desktop into left wing charities and untraceable consultant payments. always accuse your enemies of what you're doing.
Timeline
Post
Remote status
Context
24
@sun I'm like three out of eight-ish sections into a rant blog on why free software sucks now and I can't tell if it's even worth my time to include commentary on Omarchy at my own peril. DHH is one of the perpetual boogeymen of these people, and if they don't want to hear "you're making the computing experience worse," they certainly won't want to hear "the dude's a fucking poseur why are we making semi-weekly seethe blogs to post on lobste.rs about him to give him all the attention he wants?"
@idiot I don't have much commentary on dhh or omarchy other than as far as I can tell he hasn't said much that a giant portion of the country doesn't consider that controversial, but greatly bothers people that want a very strong progressive tech monoculture.
@ageha @idiot @sun people like him who developed systems and frameworks in the 00s era look like idiots because the 90s disconnect between academia and people-who-just-wanted-to-get-things-done was still very hard
this also applies to ruby itself, nowadays it's trivial to be aware of cutting-edge runtime and compiler methods with a bit of work even if you choose not to use them, back then everything was black magic outside academia
this also applies to ruby itself, nowadays it's trivial to be aware of cutting-edge runtime and compiler methods with a bit of work even if you choose not to use them, back then everything was black magic outside academia
@whiteline @idiot @sun
don't remember 00s that way. was still outside uni chatting on fora and searching things, but feeling was "hardware constraints gone but people piling garbage on garbage, so still no performance gains. need to care about these things
the oop craze was strong, but felt that was more eminating outwards from academia rather than reverse, students pushed on java early and adopting python and ruby because of that
don't remember 00s that way. was still outside uni chatting on fora and searching things, but feeling was "hardware constraints gone but people piling garbage on garbage, so still no performance gains. need to care about these things
the oop craze was strong, but felt that was more eminating outwards from academia rather than reverse, students pushed on java early and adopting python and ruby because of that
@ageha @idiot @whiteline Java is shitty bit it was infinitely better for enterprise software than C and C++, that is an objective fact.
@snacks @idiot @whiteline @ageha nobody wants to hear it but fresh university graduates could shit out working software very fast in Java and it wouldn't have the basic security and memory issues that plagued C programs.
@sun @snacks @idiot @whiteline
students i knew definitely couldn't, brittle template generators barfing incomprehensible things and layers of "enterprise ide" preventing people even learning version control
students i knew definitely couldn't, brittle template generators barfing incomprehensible things and layers of "enterprise ide" preventing people even learning version control
@whiteline @ageha @idiot @snacks OOP is bad if you're a good programmer and good if you're a bad programmer.
@sun @idiot @whiteline @ageha it isn't even that bad, stuff like fat structs is very similar, you just need better control of how they land in memory and not go wild with inheritance
@snacks @idiot @whiteline @ageha also contrary to popular opinion it is not even really that slow. It's certainly a lot faster than ruby on rails. It was ass-slow when computers were still double megahertz
@sun @snacks @idiot @whiteline @ageha it is slow as molasses. ruby on rails isn’t even a low bar, it’s absolute rock bottom. luajit is faster than java, especially on non-x86. neither has any hope of keeping up with gcc/g++
@sun @snacks @idiot @whiteline @ageha (modern C and C++ are also not what they used to be and shitting out working stuff got much easier)
@sun @snacks @ageha @whiteline @idiot honestly i’m a lot more excited for C29 because it’s getting so much good stuff that’ll make code safer and more elegant while the C++ committee prefers to add more reasons for senior devs to slap junior devs on the wrist
@mia @snacks @sun @whiteline @idiot
un, few big issues just inherent to c, but modern c dealing with nearly all small things i ever had to complain of it, very cool
un, few big issues just inherent to c, but modern c dealing with nearly all small things i ever had to complain of it, very cool
@ageha @snacks @sun @whiteline @idiot my biggest issue with C is libc. the language is pretty solid
@ageha @snacks @sun @whiteline @idiot it’s this unfortunate combination of inflexible (e.g. only one memory allocator) and poorly designed 80s-era crap (everything about locales, signals, i/o primitives…)
which is also unfortunately just how posix works. the syscall interfaces are already shit and there’s not much libc could do to make them less ugly.
@mia @snacks @sun @whiteline @idiot
a c-like with modern namespacing and modules, nice types and type inference (explicitly bypass-able for low level suppose), a few syntax tweaks around e.g. function declaration to make fun pointers less pain, and yeh stdlib that's organised well (like elixir or janestreet ocaml) + nicer threading and io
would be pretty ideal language for me
a c-like with modern namespacing and modules, nice types and type inference (explicitly bypass-able for low level suppose), a few syntax tweaks around e.g. function declaration to make fun pointers less pain, and yeh stdlib that's organised well (like elixir or janestreet ocaml) + nicer threading and io
would be pretty ideal language for me
Replies
0Fetching replies…