Conversation
Notices
-
Embed this notice
≠ (amerika@annihilation.social)'s status on Sunday, 19-May-2024 18:09:23 JST ≠ @taylan @Suiseiseki @p @romin @sun
A lot of us use older technologies because (a) they are everywhere (b) they work for the parameters involved and (c) newer unproven technologies do not offer significant advantages.-
Embed this notice
kuteboiCoder (kuteboicoder@subs4social.xyz)'s status on Sunday, 19-May-2024 18:09:09 JST kuteboiCoder @not_br549@jollyville.net @tyler@nicecrew.digital @blueberry@fosstodon.org @MK2boogaloo@lab.nyanide.com @kirby@lab.nyanide.com
I love #shitposting in my #git commitsPleroma-tan likes this. -
Embed this notice
Tyler (tyler@nicecrew.digital)'s status on Sunday, 19-May-2024 18:09:10 JST Tyler That's a cool life story Mayne
King shit -
Embed this notice
Jolly Rancher (not_br549@jollyville.net)'s status on Sunday, 19-May-2024 18:09:10 JST Jolly Rancher I need to log off the shitpost network and figure out how git works. I have this idea that it's like the RCS we used on the telco project, but every time I look at a git repo, I can't find the actual code .. just a complicated tree with a bunch of meta-information. Gotta be some code in there somewhere Pleroma-tan repeated this. -
Embed this notice
Jolly Rancher (not_br549@jollyville.net)'s status on Sunday, 19-May-2024 18:09:11 JST Jolly Rancher I was kidding about Elixir, anyhow. Last time I did any real coding was in the '90s. I did some TMS320 assembly in the '80s, used Turbo Pascal at home, and poked around some other things like Forth (and a derivative, Fifth). I took a course in Ada (because reasons), but thankfully never needed to use it for anything. Ugh. And then in the '90s, worked for a while on a telco infrastructure project. It was mostly in C, good old K&R C, on an i960 ... cross compiled from a Sun network running Solaris. I maintained a make file for the project. Little sed and awk one-liner scripts needed maintenance now and again.
I sort of imagine Elixir to be like that MMI ("Man Machine Interface") interpreter the telco project was building. Unreadable, unwriteable, but the old telco guys could speed-type it..
Since 2000, I got promoted up way past my competence level, and shuffled papers until retirement a few years ago. -
Embed this notice
Jolly Rancher (not_br549@jollyville.net)'s status on Sunday, 19-May-2024 18:09:12 JST Jolly Rancher too lazy to scroll back, here :-) -
Embed this notice
pistolero (p@fsebugoutzone.org)'s status on Sunday, 19-May-2024 18:09:13 JST pistolero @not_br549 @amerika @Suiseiseki @taylan @romin Well, I did cover the most recent complaint I had about Elixir a few posts up. -
Embed this notice
Jolly Rancher (not_br549@jollyville.net)'s status on Sunday, 19-May-2024 18:09:14 JST Jolly Rancher Elixir FTFW! -
Embed this notice
≠ (amerika@annihilation.social)'s status on Sunday, 19-May-2024 18:09:15 JST ≠ @p @Suiseiseki @taylan @romin
I never found Perl objects to be confusing, but the documentation could be so.
Lua is just fun. It's a language designed almost like HyperCard for minimal barriers.
Then again, this also gets graphics art majors (Hitler was an art student) into writing code, which is bad.
PHP was awesome when it was a template system for Perl. They tried to make both Perl and PHP into Ruby, missed out on that goal and also adulterated the languages. -
Embed this notice
pistolero (p@fsebugoutzone.org)'s status on Sunday, 19-May-2024 18:09:15 JST pistolero @amerika @Suiseiseki @romin @taylan
> I never found Perl objects to be confusing, but the documentation could be so.
Well, tell Larry Wall; he's the one that thinks objects confuse people. I thought Perl's object system was a little baroque, but Perl is baroque.
> Lua is just fun. It's a language designed almost like HyperCard for minimal barriers.
I think in a slightly better world, JavaScript would not exist, and we'd be using Lua. (In an even better world, we'd have a very nice bytecode VM.)
> Then again, this also gets graphics art majors (Hitler was an art student) into writing code, which is bad.
Well, if Hitler had learned to code, maybe he wouldn't have been such a fuck-up that he needed to kill himself.
> PHP was awesome when it was a template system for Perl. They tried to make both Perl and PHP into Ruby, missed out on that goal and also adulterated the languages.
I don't know, Perl 6 looked all right. PHP never did. -
Embed this notice
pistolero (p@fsebugoutzone.org)'s status on Sunday, 19-May-2024 18:09:16 JST pistolero @amerika @Suiseiseki @romin @taylan
> We could mention the giant fuckup that Perl 6 was in here somewhere.
:larry: Way before Perl 6 was released, Larry Wall joked that someone had snuck around and released Perl 6 already and called it "Ruby" and the hackers lol'd, and then the humorless dicks got involved and he had to walk it back and say "Objects are confusing!" (If we're talking about OO Perl, I'd agree, but Perl 6's object system seemed fine. People don't seem to have trouble with objects in Lua.)
> Or the recent giant fuckups by whoever administers PHP.
Well, it's PHP. -
Embed this notice
≠ (amerika@annihilation.social)'s status on Sunday, 19-May-2024 18:09:17 JST ≠ @p @Suiseiseki @taylan @romin
We could mention the giant fuckup that Perl 6 was in here somewhere.
Or the recent giant fuckups by whoever administers PHP. -
Embed this notice
pistolero (p@fsebugoutzone.org)'s status on Sunday, 19-May-2024 18:09:18 JST pistolero @amerika @Suiseiseki @romin @taylan You know, I have Ruby that I wrote during the 1.6 days that still runs fine under 3.3; I have C that I wrote in the 90s that still runs fine. All of the Go I have ever written. Perl scripts, too: I have not written Perl in years, but it all still works. Not a lot of languages manage that kind of stability. -
Embed this notice
≠ (amerika@annihilation.social)'s status on Sunday, 19-May-2024 18:09:19 JST ≠ @p @Suiseiseki @taylan @romin
This is why I use a lot of older tech and of course write Perl for kicks. -
Embed this notice
pistolero (p@fsebugoutzone.org)'s status on Sunday, 19-May-2024 18:09:22 JST pistolero @amerika @taylan @Suiseiseki @romin Yeah, xz underperforms in terms of output size: depending on what you're compressing, bz2 is smaller sometimes. xz is faster in the default configuration because it's parallelized, but the "p" in "pbzip2" is "parallel".
The relevant thing for me was that if I want the data to stay accessible, I want a compression algorithm that is old enough to have more than one implementation. The xz vulnerability demonstrated that the risk was real.
xz_meme_formats.png
-
Embed this notice