Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MO
Posts
1
Comments
248
Joined
2 yr. ago

  • "DI frameworks" are Satan's farts. Classpath-scanning nonsense that turns compile-time errors into runtime errors. Not only is your Ctr still coupled to your Svc, but both are now coupled to Spring.

    Let's qualify this: DI frameworks that use configuration files to specify the dependencies are Satan's farts. You can use the DI pattern but do the injection in source code to get full compile-time type checking and all the benefits of a fully packaged JAR or similar binary. The root of the evil is having text files as part of the packaging, and not having the tooling to treat those files as part of the source code at build time.

  • As I was discussing this with my partner we summarised this as:

    Humans have always had the capacity for violence and murder; as populations grew, acts of violence could be larger, both in terms of number of combatants and also length of time of continuous fighting. This is a progression of:

    • Small bands of people skirmishing with neighbours to
    • Towns sending small raiding bands to
    • Cities fielding an army for a summer campaign to
    • Empires furnishing professional armies and sending them on multi-year campaigns, to
    • Nation states using advanced logistics to maintain millions of soldiers in the field for years at a time.

    Somewhere between city-states and full modern nation states, there have been full on campaigns of genocide. But genocide can be thought here definitionally as only possible with some significant number of people.

    Unfortunately there is a deep dark part of the human psyche that has always been with us.

  • I hear what you're saying, but there's a counterpoint to this.

    In prehistoric times, population densities were low. In mesolithic times (hunter gatherers) there were simply no concentration of people large enough to wipe out or to do the killing. Nothing could be called genocide at this time.

    In neolithic times (the first farmers) violence was definitely a part of life. Some early towns do show signs that they were destroyed. But again, population densities are low enough that the scale of violence would not be enough to call 'genocide'. It's a town burnt down with everyone murdered, not a 'people' - whatever that might mean at this time. This is not about egalitarianism - it's population density.

    However as we move to the bronze age, there are definitely signs that large scale events occur that might fit into the modern concept of genocide but archeological evidence is severely lacking. The main line I would argue is that the male lines of the neolithic farmers in Europe are hammered and almost completely replaced with the Yamnaya Y chromosomes across a huge expanse - from the east european plains to the Iberian peninsula. Genetic continuity with the neolithic farmers is maintained though indicating that male newcomers were having children with local women, and very few male locals had children. During this event the culture changed hugely - burial patterns, material goods, etc.

    I don't know if we can call this genocide - at least the full modern concept - because these changes took centuries to roll out across the expanse of Europe, but they speak to local conquests and, at the very least, the newcomers prevented local males from having their own families. At worst you can imagine a constant expansion of this new culture taking control of new areas, killing the men, taking local women as concubines and eradicating their gods, customs and ways of living. Quite a lot of genocidal checklist items ticked off there.

    By the mid to later bronze age, genicide is definitely a widespread thing, recorded in many texts.

  • Elon sounds like he's experienced, skilled and is approaching things from a theoretical or ethical or other grand point of view. He used to impress me with his approach on building an electric car company with full self-driving vehicles in the 2010's. I wasn't a full believer, but I thought he was competent and wanted Tesla to succeed.

    Then he went and bought Twitter. As a software engineer all my life, and in the startup scene, and having worked in a failed social media platform, I have some experience. Everything he's said about Twitter is crap and everything he's done is stupid. And the results speak for themselves.

    I've seen people say that Elon sounds great about things they don't know too much about. But when the topic comes to things they do understand, Elon clearly is wrong.

    He started his career with hundreds of millions of dollars, and he bet it all on a couple of businesses be bought (he was never a founder, always a purchaser).

    Basically he's been lucky twice (Paypal and Tesla), but each of these won 10-100x on his initial stake.

  • Note the caveat:

    With PYTHON_GIL=0 set, I spot-checked a few tests and small programs that don't use threads. They all seem to run fine, and very basic threaded programs work, sometimes. Trying to run the full test suite crashes pretty quickly, in test_asyncio

  • Their arguments included the size of the web page, and the time to display the first content, both of which were significantly better in Nue when compared to Tailwind.

    By all means argue on what is important (because what is important for your projects may be significantly different from mine), but there were many points that the author was highlighting, not just the separation of concerns. And for my projects, all these concerns are important.

  • Disagree with your disagreement. I also have an M1 and was a quite early adopter (within 3 months of launch). It was really snappy compared to my Intel Air it replaced. From the get-go. Even for apps that were still x86 code.

    Things definitely improved over the next 9 months, but I was and am a really happy camper.

  • This is exactly the answer.

    I'd just expand on one thing: many systems have multiple apps that need to run at the same time. Each app has its own dependencies, sometimes requiring a specific version of a library.

    In this situation, it's very easy for one app to need v1 of MyCleverLibrary (and fails with v2) and another needs v2 (and fails with v1). And then at the next OS update, the distro updates to v2.5 and breaks everything.

    In this situation, before containers, you will be stuck, or have some difficult workrounds including different LD_LIBRARY_PATH settings that then break at the next update.

    Using containers, each app has its own libraries at the correct and tested versions. These subtle interdependencies are eliminated and packages 'just work'.

  • Exactly. And all the core internet encryption and signing algorithms are fully open source. Eg RSA, AES, DIffie Helman. And these are the algorithms the US (and most other western) governments require when sending data to or from or within there servers.

  • Exactly!

    While the continents might look like they fit together, and the rock types and ages and fossils match at key points all down the coasts from Canada/Scotland all the way down to South America and South Africa, how on earth (sorry) would you explain how the continents are thousands of miles apart?

    One theory posited the earth spinning so fast centrifugal forces ripped ehat would become the moon out of the Pacific, sucking Eurasia and America into the void.

    That's a Randall Monroe WhatIf if ever I saw one. Think of the energy involved! All life on earth would be extinct.

    So these theories were laughed out of scientific court. Until Vine and Matthew's seminal paper on magnetic stripes being mirrored over the mid ocean ridge showed there had to be something forcing the plates apart.

  • This is common enough to have a name in several industries. In SW Dev it's called 'bikeshedding'. If you have a name for it, it's easier to call out to your seniors and peers - and you should call this out and help the meeting move on to more useful matters.

    I'd suggest informally discussing this with people around you - enough people that you (or someone else) can safely say "let's not get trapped in bikeshedding" in the meeting and getting immediate agreement.