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/)B
Posts
2
Comments
150
Joined
1 yr. ago

  • Clocking trans folk by poor fashion choices is easier than by their face.

  • Trans women have their own subculture regarding clothing. Teenage male fantasies have a bigger influence than main stream women’s fashion.

  • They downvoted him for telling the truth.

    Lemmy is an echo chamber.

  • It’s all reposted stuff from elsewhere.

  • r/politicalcompassmemes

    r/IsraelPalestine

    r/livestreamfail

    r/all

    r/popular for select countries.

  • Nice conspiracy theory.

  • Lingerie, drugs, snacks, toys, etc. cost money!

  • Take a strong dose of magic mushrooms and ketamine to get that experience.

  • Never use numbers when calculating dates. Use the data formats and constants the calendar library provides.

  • The waste and corruption in private industry is mind bogglingly huge compared to the public sector.

  • How did Heartbleed and Goto fail happen in OpenSSL then?

  • Start with it standing in the morning. Lower it when you feel like it. Then after lunch start standing again, lower over time.

  • Lots of open source software uses arcane concepts because lots of it is old. See Xorg as a prime example. That was outdated 20 years ago already.

    Closes source software gets exploited and hacked all the time. They take security seriously as well.

    Look at OpenSSL and the heartbleed and similar high profile security failures for how even using high profile open source software is not automatically more secure.

  • You theoretically can see the code. You don’t actually look at it. Nor can you even have the knowledge to understand and see security implications for all the software you use.

    In practice it makes little difference for security if you use open or closed source software.

  • Vintage

    Jump
  • ADB was superior.

  • Deleted

    Permanently Deleted

    Jump
  • Java has been running serious server software since the mid 1990s. Think WebObjects running on Solaris. Lots of business stuff with big databases still run infrastructure like that.

    Java still has the big advantage of being machine agnostic. No need to recompile for ARM or Intel.

  • Deleted

    Permanently Deleted

    Jump
  • Early Swift was very slow to compile and start. The debugger was nonfunctional.

    Otherwise it was pretty usable. Especially since it got to leverage the huge libraries written for Objective-C.

    Which meant it lacked some basic collection types. A Swift native Set was introduced with Swift 3 IIRC. Before that you had to bridge back and forth between Swift and Objective-C. Sometimes leading to unexpected behavior at runtime.

    In Objective-C if an object reference was nil, you could send it messages (call methods) without a problem. Swift however did away with this. Optionals had to be explicitly unwrapped. So if the annotations weren’t correct, Swift code would crash at runtime where Objective-C would have been fine. Lots of bugs related to that existed.

    Swift peaked around version 4. Since then, they have been adding kitchen sink features and lots of complexity to feel smart.

    I still would have preferred an Objective-C 3.0. Chris Lattner was a C++ guy and never really understood Objective-C culture and strengths.

  • You can generate the code with a simple macro.

  • Always put a ticket number in the commit message. That can make it much easier later to find out what the context was for some weird solution.

  • sh.itjust.works Main Community @sh.itjust.works

    Unresponsive/Slow post submissions and upvotes leading to errors and duplicate posts