[–] 3 points 3 days ago* (2 children)

I guess I would have thought panic would trigger other threads to abort as well. Admittedly I haven't really done any multithreading in Rust. I was thinking it was more like exit(status) in C/C++ that immediately terminated the entire process. Exception unrolling in general I feel is something that should be avoided if you care at all about error conditions.

If panics are isolated to one thread, then I guess mutex poisoning is a better default error case than a deadlock where the process never exits. An entirely independent thread might still be unaware the rest of the program has crashed though.

  • source
  • parent
  • context
  • [–] 7 points 3 days ago (5 children)

    In my opinion, catching a panic is a mistake in the first place. They're meant to be unrecoverable anyway, so if you want the program to keep running, use Result types or return errors some other way.

  • source
  • [–] 7 points 1 week ago (1 child)

    That was definitely back before Apple went crazy with their whole closed ecosystem. Apple II feels a lot more like linux these days considering the amount of documentation available about the hardware. And parts aren't locked down with serial numbers like in the iPhone...

    I had a lot of fun as a kid messing with an Apple IIgs. One of the games I had was "Thexder", and you can probably guess where I got my username.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago (1 child)

    You made a good point about integration. There's a lot of scenarios where a business might use software as-is, meaning there's nothing to contribute back. Many libraries are flexible enough a user might never encounter a reason to make changes.

    ffmpeg for example is the core of the vast majority of video processing applications. I use it all the time, and have even benefitted from being able to read the source code, but I've never had a reason to change it.

  • source
  • parent
  • context
  • [–] 10 points 1 week ago* (1 child)

    It's more that I didn't really care what happened with the code, because at the time AI training wasn't a thing, and I like the idea of contributing to the open source community. If my project ended up saving someone time at their job, or inspired other hobby devs to do something, then it was worth publishing.

    Now, more than likely my code will just get scraped into an AI dataset without any credit, and no human will ever notice or care about the original.

  • source
  • parent
  • context
  • [–] 8 points 1 week ago (4 children)

    I used to select MIT primarily to keep my name associated with the code. The idea being if companies picked up my projects and used them in their products, it would be a good thing to have on my resume, and could land me a job.

    I'm at a very difficult point in my career now, and the days of this xkcd are probably coming to an end. Nobody wants to use libraries anymore, they just vibe-code their own.

    Now I'm reconsidering publishing my personal project source code at all, because I've rarely got contributions, and lets be real, a non-commercial license won't stop the code being stolen anyway.

  • source
  • parent
  • context
  • view more: next ›