Hash bang slash, bin s h,
c d slash dot config
When you know the keys to type
You can code without the hype
With #Ahsoka airing, I figured I should watch The Clone Wars to get more of her back-story. I watched all of season 1 but frankly it was an unbingeable slog. It's not really grabbing me, so I only watch 1 or 2 episodes at a time.
After season 1 I skipped to the end, or end of S6. So I see Yoda learning how to become a Force ghost. Cool, but how come Anakin became one, he never trained? I guess Yoda might have taught Obi-Wan at least. #StarWars #clonewars
nostr:npub1v4tnlhutlqcsv0m60vd5ux6j83e5g5nmpj4dsv4pekyszzzaemnqd5w5q2 chump change for him
nostr:npub1wdvqwwd0l27l57ea43ju0fmmvdeqlefj5m2y409hfk3t208k7s2sduhnkd yeah, being the outsider sucks. I've had similar experiences for most of my career, but it's more like "hey, the typical solution everyone uses sucks because of x,y,z and my solution is better" and getting largely ignored for the first few years. But eventually people start recognizing that "yeah, x,y, and z actually do suck" and start coming around. It takes persistence and years of patience to beat entrenched, established groupthink.
nostr:npub1wdvqwwd0l27l57ea43ju0fmmvdeqlefj5m2y409hfk3t208k7s2sduhnkd six months to years later - prime "I told you so" opportunities.
Everything relevant I have to tell you on this topic could be written concisely in a 500char toot, but I'm going to make you waste your time watching my video instead. https://mastodon.social/@thelinuxEXP/111070011303868097
Seeking opinions...
One of my old projects, RTMPdump, relies on OpenSSL for some crypto primitives, but the APIs it uses have been deprecated in 1.1 and newer. I'm wondering whether and how to support the newer versions.
Since we're supporting an ancient proprietary protocol, adopting new APIs to allow supporting newer encryption schemes is irrelevant. Avoiding weaknesses in older ciphers is also irrelevant, we have to use what Adobe used, and nothing else.
nostr:npub1yplatfrpk8f8nwnzs5cpvravmf4tzt7warlcdr092etcdythkyaqgy53vh ranks up there with touch-sensitive lamps
nostr:npub1v4tnlhutlqcsv0m60vd5ux6j83e5g5nmpj4dsv4pekyszzzaemnqd5w5q2 should've used "roles"
#LMDB data store, concurrent cache, etc., for #Eclipse https://rdf4j.org/javadoc/latest/org/eclipse/rdf4j//sail/lmdb/package-summary.html
nostr:npub16mzsp9vtc8h6e986507sw88q3xzq5pfjaff30r5wcgfprksnf03s65uzxf I worked on the Space Shuttle, which technically is not a rocket, it's more of a space plane. So not really a rocket scientist...
nostr:npub1xvegvr9nrwlhtq05h42f2av9xpm6afv7tth33ddlhyx4tl6p7j0s29lvum remake as in, identical performance as original?
I'd kinda like to see what clock rate you could hit with a 68020 on a modern silicon process. I suppose the ColdFire family is a hint already.
Might as well do Sun3x, with 68030...
This is a tune that for some reason I thought I learned off the Atlantic Fiddles CD many years ago, but recently when I dug up that recording I didn't find this tune on there, so now I have no idea where I got it from. Anyone else recognize it? It seems it's originally a highland pipe tune.
nostr:npub177j9vhl7gtcv64972mgp24r07pfn5phzf53u0k2ps6shgc53kd5qtc34u5 really amazing compared to other scifi films & tv shows from the same time.
nostr:npub1j8qshymu7a7rzm4tg4snqk4yrqy8fef4e7kjfv3s64jrmd3xnp7splma30
A Colombian judge used chatGPT in a ruling.
So chatGPT makes up answers out of thin air, those answers become part of public record, search engines index them, then you're done: no longer able to search for factual answers to questions.
https://www.theguardian.com/technology/2023/feb/03/colombia-judge-chatgpt-ruling
who could possibly have seen this coming... https://mastodon.social/@cynicalsecurity@bsd.network/111030157657101339
Aoine Shona daoibh!
星期五快樂!
Бақытты Жұма!
Happy Friday!
*this toot void where prohibited
nostr:npub1qnnjpjm3gctvgewlz0pc8hk8tzu0gewskh4fewgmuvjm9kw2l4usagw7ad Aside: I'm having a hard time accepting 18MB vs 2.7MB as an acceptable cost of not managing your own memory...
nostr:npub1qnnjpjm3gctvgewlz0pc8hk8tzu0gewskh4fewgmuvjm9kw2l4usagw7ad yeah, relative offset can avoid some of the reloc hassle but gets unwieldy for deeply nested fields.
nostr:npub1qnnjpjm3gctvgewlz0pc8hk8tzu0gewskh4fewgmuvjm9kw2l4usagw7ad
foo* recptr = map_alloc(sizeof(foo) + strlen(rec1.name) + strlen(rec1.phone) + 2);
recptr->name = (char *)(recptr+1);
strcpy(recptr->name, rec1.name);
recptr->phone = recptr->name + strlen(recptr->name)+1;
strcpy(recptr->phone, rec1.phone);
So recptr lives inside the fixedmap address space, and contains all of rec1's data in one contiguous chunk of memory. Then the record can be used directly from the map, with no deser cost.