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/)F

FizzyOrange

@ FizzyOrange @programming.dev

Posts
2
Comments
1231
Joined
3 yr. ago

  • Microsoft has finally clapped back at the famous PS4 game share video, but in a very weird way

    Jump

  • To be fair the days when a game was "released" and that was that are also pretty much long gone. Big studios now rely on being able to patch bugs after release.

  • Open source is a thankless job and I think we've lost the plot on how we treat maintainers

    Jump

  • Well I disagree. If you create a popular project, and then are a complete dick about reasonable requests, then that seems like an immoral thing to do to me.

    Of course you're allowed to say "sorry I don't have time to work on this any more", or "I don't think this feature belongs in this project" or whatever. Totally fine. But there are still behaviours that IMO are not ok. For example if Homebrew decided to inject donation request code into every package it installs. Or if ffmpeg added code that detected porn and refused to decode it.

    "BuT iTs FrEe! They can legally do what they like!" Sure, but it still makes them a dick.

  • Why don't people use git properly?

    Jump

  • That's a lot of words. I think the reasons are pretty simple:

    1. Some people just don't care.
    2. The Git CLI is poorly designed e.g. the many different ways to delete something.
    3. Some Git concepts are very poorly named, e.g. the "index", "ours/theirs". This adds to the confusion.
    4. There are many Git GUIs but only a very small number of actually decent ones (if you're wondering: GitX, SourceGit, Git Extensions, and the Git Graph VSCode extension).
    5. There are a lot of idiots out there telling people not to use Git GUIs, when they are clearly the best way to learn how to use Git. Its easy to get into a mess if you can't see what you're doing.
    6. Git isn't actually as simple as us pros would like to think. The underlying model and even the implementation isn't too complex (I've written a Git client form scratch; not too hard apart from the lack of specs/docs). But you can easily get into a state where you're pulling from a remote and someone else has pushed to the same branch so you need to resolve that (oh btw don't do what Git tells you to!), and maybe it involves submodules too, and you basically need to fully understand Git's model and be pretty good at the awful CLI too to resolve it.

  • Open source is a thankless job and I think we've lost the plot on how we treat maintainers

    Jump

  • What arbitrary line of popularity suddenly requires me to support every use-case, by never breaking something in a project nobody is paying me to build?

    Not what I said at all.

    FOSS maintainers owe you NOTHING. Nada. Zip.

    Oh so it's either "nothing. Nada. Zip." or "support every use-case". Nice false dichotomy you've got there.

  • Open source is a thankless job and I think we've lost the plot on how we treat maintainers

    Jump

  • I disagree. If you make a project, put it out there for.people to use, and it becomes popular, you have some moral obligation not to dick over people who have come to depend on you. I'm not saying you have a moral obligation to e.g. provide free support forever or work weekends or whatever.

    You can think otherwise but IMO that makes you a bit of a dick.

  • Open source is a thankless job and I think we've lost the plot on how we treat maintainers

    Jump

  • I said morally, not legally.

  • GitHub Stacked PRs

    Jump

  • Freaking finally. (Well when it's actually released anyway.) Kind of crazy how long this super obvious feature has been ignored by all the forges. (Except Tangled, but that has other issues.)

    Also this is going to be a big differentiator compared to Gitlab or Forgejo.

  • Open source is a thankless job and I think we've lost the plot on how we treat maintainers

    Jump

  • See my other comment.

  • Open source is a thankless job and I think we've lost the plot on how we treat maintainers

    Jump

  • It wasn't meant to be comparable. It was meant to be a simple counter example to disprove "free => no obligations".

  • It's not me, it's the compiler!

    Jump

  • Wow. I wonder why nobody saw this before then? Op's code doesn't look unusual.

  • It's not me, it's the compiler!

    Jump

  • Wow that's pretty crazy. I guess this bug was only in nightly?

    Also I want to know more about this guy's crazy build system.

  • Rust sort_unstable_by with more complex closure unexpectedly shrunk binary

    Jump

  • Almost certainly prevents some inlining or loop unrolling or something like that.

  • Open source is a thankless job and I think we've lost the plot on how we treat maintainers

    Jump

  • I say thanks to open source maintainers all the time! 😄

    Anyway, while a wall of profanity and fuck you is clearly not ok, I do disagree with this:

    The maintainers ship this for free. People run production businesses on top of it, for free.

    Just because you offer something for free doesn't absolve you of all moral responsibility. I'm not saying you have a lot of responsibility, but "it's free so you can't complain!" is pure nonsense.

    Go and give some kids free poisoned sweets and see how far that gets you.

  • Qt Bridges: Public Beta for the Rust Bridge Is Out!

    Jump

  • Slint is pretty much the spiritual successor to QtQuick. I think it's written by people that used to work for Qt, it has a similar design (GUI focused DSL with automatic reactivity), and they are even using the same business model - basically free except for embedded use (cars, petrol pumps, PoS etc.). But without the decades of baggage Qt has and with support for Rust from day one.

    It can even use Qt as a backend somehow.

    I had a go with Slint because it does look impressive but tbh the amount of setup you have to do is just a bit too much compared to something like gpui-component. Probably worth it for a bit project I guess.

  • Qt Bridges: Public Beta for the Rust Bridge Is Out!

    Jump

  • Not really in practice. In older versions I have done it, but they really don't want you to. The binaries are only distributed as shared libraries, so you at least need to build Qt from source. And also whenever I build recent Qt apps even with QtWidgets it has a load of plugin files and other nonsense that it needs.

    I'm sure it's possible with enough work but it's not simple like with fltk or egui or gpui.

  • Rust Gets a Commercial Network with Microsoft, Google, AWS, and OpenAI Onboard

    Jump

  • Riiiiight. You might want to look up what Hitler actually did. It was just a little worse than anything these companies have done. Just a smidge.

  • Rust Gets a Commercial Network with Microsoft, Google, AWS, and OpenAI Onboard

    Jump

  • No. Rust is extremely popular in industry so corporations are supporting it.

  • AI Software Development Is Near-Impossible

    Jump

  • don’t think I’ve found anything that saves time

    Then you're doing something very wrong. I'm yet to be convinced about AI coding for long lived projects, but for throwaway scripts, visualisations, one-off conversions and basically anything that doesn't need to be maintained long term it absolutely saves a mountain of time.

    Stick your head in the sand all you like...

  • I Think They Are Lying To You

    Jump

  • They're not lying, they're exaggerating. Obviously coding isn't solved but I don't think the fact that that is an exaggeration is going to save our jobs from becoming agent wranglers sooner or later.

    I'm not happy about it but I'm not going to stick my head in the sand and pretend it isn't happening either.