home.social

#implementations — Public Fediverse posts

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

  1. We’re hiring a PhD student!
    Join us at COSIC KU Leuven to work on secure hardware implementations protected against physical attacks.
    Details
    👉 esat.kuleuven.be/cosic/vacanci
    #hardware #implementations #cosic #kuleuven #choosecosic

  2. @AndyScott

    You're talking about how the way memory/object tracking and reference counting is done in the Python core, which in one implementation of Python is itself written in C, correct?

    Responses:

    1) Not all Python #implementations are in C. Some are inherently memory-safe.

    2) In #CPython, the object lifetimes and #reference counting rules are well-understood and #documented, are maintained by a large core of developers who understand them, and have been tested with trial-by-fire by millions of users and millions of Python programs over decades. If you write an application in C or another memory-unsafe language and do your #memory handling yourself, it's code by one person, tested by at most a few people, and newly written - maybe not documented, and probably not with all the #bugs already shaken out of it.

    Analogy: you need a boiler to operate your steam engine. You can use one designed by an engineer who has been doing boilers for twenty years, and manufactured by someone who has done nothing but that for the same length of time -- or you can cobble one together by yourself for the first time, not knowing the engineering behind it, and just hope it doesn't explode the first time you bring it up to pressure.

  3. 'QDax: A Library for Quality-Diversity and Population-based Algorithms with Hardware Acceleration', by Felix Chalumeau et al.

    jmlr.org/papers/v25/23-1027.ht

    #qdax #qd #implementations

  4. How do we call a #test that can test two or more #implementations of an #interface with the same test code?

    They call it "Testing interface contracts" here: baeldung.com/java-junit-verify

    IIRC, I heared a different term in the past, but I cannot remember it. #followerPower

  5. @ska @schmonz

    I haven't. I sent a message to the #qmail list, replying to something or other, some time back, in which I described the lasting legacy of qmail as its #design, not its #codebase, and suggested perhaps a group project to maybe modernize a couple of design things - small! - and then start with fresh #implementations of the components to add #features or whatever - and noted they don't all have to be in the same implementation language etc.

    [...]

  6. @ska @schmonz

    I haven't. I sent a message to the #qmail list, replying to something or other, some time back, in which I described the lasting legacy of qmail as its #design, not its #codebase, and suggested perhaps a group project to maybe modernize a couple of design things - small! - and then start with fresh #implementations of the components to add #features or whatever - and noted they don't all have to be in the same implementation language etc.

    [...]

  7. @ska @schmonz

    I haven't. I sent a message to the #qmail list, replying to something or other, some time back, in which I described the lasting legacy of qmail as its #design, not its #codebase, and suggested perhaps a group project to maybe modernize a couple of design things - small! - and then start with fresh #implementations of the components to add #features or whatever - and noted they don't all have to be in the same implementation language etc.

    [...]

  8. @ska @schmonz

    I haven't. I sent a message to the #qmail list, replying to something or other, some time back, in which I described the lasting legacy of qmail as its #design, not its #codebase, and suggested perhaps a group project to maybe modernize a couple of design things - small! - and then start with fresh #implementations of the components to add #features or whatever - and noted they don't all have to be in the same implementation language etc.

    [...]

  9. @ska @schmonz

    I haven't. I sent a message to the #qmail list, replying to something or other, some time back, in which I described the lasting legacy of qmail as its #design, not its #codebase, and suggested perhaps a group project to maybe modernize a couple of design things - small! - and then start with fresh #implementations of the components to add #features or whatever - and noted they don't all have to be in the same implementation language etc.

    [...]

  10. It is a pure #shit #sandwich. All the other use cases they give are the #mustard and the #pickle, put there to hide the #taste of the sandwich.

    I personally #recommend you *not* eat a shit sandwich, even if it has fantastic mustard and is served with a really amazing pickle.

    They describe it like it will be a wonderful, #open playground, full of #free and open #implementations, and that #websites (and #ad #exchanges... cough) therefore won't be able to use it to #abuse #users.

    3/x

  11. Recently I've had a conversation with my Tech Lead about what kind a I am.
    He gave me only 2 options:

    1. One who builds big forms and first, and then distinguish particular
    2. One who creates parts, then builds huge blocks from them, performing in order to the

    I am the 3rd one - who build an application as the data flow comes.
    And what a programmer are you?

  12. Go-Fed: Past, Present, and Future

    CJ

    The Go-Fed suite of libraries implement the ActivityPub protocol in the Go language.
    […]
    Go-Fed takes to heart the philosophy that the ActivityPub specification left opportunities for further evolution of its core ideas.
    […]

    VIDEO
    conf.tube/videos/watch/952f9ce

    Q&A SAT 17:00 UTC
    remote questions now:
    socialhub.activitypub.rocks/t/

    #go-fed #gofed #activitypub #fediverse #implementations #apconf2020