home.social

#ecl — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ecl, aggregated by home.social.

fetched live
  1. #ecl on embedded system retrospective. author decides on c++ eventually, but still a nice read. #lisp

    frogsaregoated.nfshost.com/pro

  2. #FediFC #Soccer #Football #ECL @[email protected] Both of the remaining matches in Rome are in a rain delay - Staodubtseva and Waltert have left the court so that could be it for the day - so I thought I'd catch up with this incident in your match ...

    RE: https://bsky.app/profile/did:plc:4vziktoq7p6jd3i5l3wtmfab/post/3ml7hzb23ak2b

  3. An idea to defeat #GenerativeAI in #FreeSoftware:

    Just use a #ProgrammingLanguage that isn’t popular (e.g. #Haskell or some #Lisp dialect) to write your code, but publish human-readable intermediate form of that code in the public code repositories (e.g. the C programming language). Share the actual source code privately with trusted contributors in non-public branches, and require GPG signatures on actual contributions.

    You could argue that not sharing source code is against the GPL, but the GPL does allow you to share the code as a hard copy printed on paper and sent over snail mail. Or you can just wait until the person asking is an actual human that you can trust not to use the source code for LLM training.

    LLMs are unable to learn unpopular programming languages because they don’t have a sufficient corpus of training data to learn how to code it, so if your receive a contribution in C, thank the contributor but inform them that they will have to rewrite the contribution in your Lisp dialect before you can accept it.

    #Scheme dialects like #Gambit , #Chicken , and #Bigloo would work well for this. So would a #CommonLisp implementation that translates to C such as #ECL . Although keep in mind that the idea is to use a less popular language, so you may have to further obscure these languages a little bit, but not in a way that would be difficult for humans. For example, using a macro system, you could use df instead of define, rename types of things like string? to utf8str?, use generic functions with mulitple dispatch so append will work on strings, lists, vectors, and bytevectors. Small tweaks like this might throw-off an LLM asked to write source code in Lisp.

    #tech #software #LLMs #LLM #FOSS #FLOSS #OpenSource #SchemeLang #R7RS

  4. I was 100% sure that I order my play booster box of Lorwyn Eclipsed in English but I now have a German box sitting on my table...

    I need that box for a home event on Saturday (1 day after release). I'm a bit annoyed 😩

    It's not that I don't speak German (it's my native language) but I like the English cards more.

    #magicthegathering #ecl #lorwyneclipsed #mtg #boosterbox

  5. In unserer neuen Folge nehmen wir Euch mit in die Geschichte des neuen Sets "Lorwyns Finsternis". Was das Gleichgewicht zwischen Lorwyn und Shadowmoor stört und wer dahinter steckt – das erfahrt in unserem Story-Überblick: tastymtg.de/tsty076-die-story-
    #mtg #ecl #mtgecl #wizardsmagic #lorwyn #lorwynsfinsternis

  6. @screwlisp

    Thank you.
    I have the nagging feeling that it isn't absolutely, positively portable to use `unsigned long long' and `uint64_t' interchangeably, now and forever, but I Am Not A Language Lawyer (IANALL™) and that is off off topic anyway.

    I am sure that the implementation at hand that takes care of such embedding of C or C++ fragments is completely sane.
    I replied from the user's perspective, but aesthetics is in the eyes of the programmer, of course.

    #CommonLisp
    #ECL
    #EmbeddedC
    #NumericTypeNamesInC

    @ramin_hal9001