• 1 Post
  • 173 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle
    • AFAB = assigned female at birth; basically because they happened to have a vagina at birth, so they were supposed to like pink and dolls and a lower paycheck and whatever else society has decided the female experience should be like.
    • AMAB = assigned male at birth
    • NB = non-binary; a person that identifies neither as male nor as female. They might be something in the middle, or they might be something completely different.
    • femme = basically the way women have traditionally looked or behaved (long hair, pink etc.)
    • fundie = fundamentalist Christian; basically very conservative, very eccentric people with world views they claim to be traditionally Christian
    • bussy = boy pussy; the anus of a man, or it may also be used to describe the vagina of a transmasc person
    • transmasc = transmasculine; a person who was assigned female at birth, but who rather identifies with masculinity and may have taken measures to be perceived as such (clothing, hormones, surgery etc.)



  • Big difference to the Wikimedia Foundation is how much money they need. The Mozilla Corporation (which develops Firefox) has around 750 employees.

    Optimistically, only 500 of those are devs and work on Firefox. If you pay those a wage of 100,000 USD, that makes 50 million USD of costs just for wages.

    Firefox has less than 200 million monthly active users, so everyone using it would need to donate $0.25, or alternatively 1% of users would need to donate $25, yearly.

    That’s a lot of money to hope people donate, and this is a very optimistic ballpark estimate.


  • Yeah, the amount of money they get from donations is so tiny compared to what they need for developing Firefox, that they don’t even divert it for Firefox.
    They use it for activism, community work and in the past, they’ve also passed it on to other open-source projects, which are also important for the web but don’t have the infrastructure or public awareness to get donations directly.



  • I mean, if we’re talking about all those problems, the no-type-annotations issue is rather specific for Python, JS/TS and Ruby.

    But in general, I feel like there’s somewhat of an old world vs. new world divide, which happened when package registries started accepting libraries from everyone and their cat.

    In C, for example, most libraries you’ll use will be quite well-documented, but you’ll also never hear of the library that Greg’s cat started writing for the niche thing that you’re trying to do.

    Unfortunately, Greg’s cat got distracted by a ball of yarn rolling by and then that was more fun than writing documentation.
    That’s the tradeoff, you get access to more libraries, but you just can’t expect all of them to be extremely high-quality…







  • I’ve been telling all the juniors we have, that they’re free to use a GUI tool, but they do not get around learning the CLI. If you fuck up or Git breaks, you’ll need to look up how to unfuck it and that’s where the only help you find is for the CLI.

    In particular, it’s also been my experience that you rapidly come into a situation where suddenly you’re the Git expert and need to help others. If you only know one specific GUI, you can only help others who use that GUI. If you know the CLI, you can help anyone.

    It also happens that you need to interact with Git repos on a server where you simply won’t have a GUI.

    And yeah, given that whole opinion, personally I seriously do not care to learn a GUI in addition to the CLI.




  • As I see it, the difference is that we now have capable game engines freely available. Indie studios can, for the most part, offer the same quality of gameplay. AAA studios can only really differentiate themselves by how much content they shove into a game.

    In particular, this also somewhat limits creativity of AAA games. In order to shove tons of content into there, the player character has to be a human, the gameplay has to involve an open world, there has to be a quest system etc…




  • The guy keeps on picking on Go, which is infamous for having terrible error handling, and then he has the nerve to even pick on the UNIX process return convention, which was designed in the 70s.
    The few times he mentions Rust, for whatever reason he keeps on assuming that .unwrap() is the only choice, which’s use is decidedly discouraged in production code.

    I do think there is room for debate here. But error handling is a hellishly complex topic, with different needs between among others:

    • short- vs. long-running processes
    • API vs. user-facing
    • small vs. big codebase
    • library vs. application code
    • prototyping vs. production phase

    And even if you pick out a specific field, the two concepts are not clearly separated.
    Error values in Rust usually have backtraces these days, for example (unless you’re doing embedded where this isn’t possible).
    Or Java makes you list exceptions in your function signature (except for unchecked exceptions), so you actually can’t just start throwing new exceptions in your little corner without the rest of the codebase knowing.
    I find it quite difficult to properly define the differences between the two.