[–] 5 points 2 months ago (1 child)

That would be good but it's not a magic solution to this problem. They would just move the exploit to runtime. Yeay you don't get hacked if you compile and never run your program.

You can counter that there are some situations where the program is run sandboxed, e.g. if you're compiling to WASI or microcontroller firmware or whatever. But those are a tiny minority of cases.

  • source
  • parent
  • context
  • [–] 13 points 3 months ago (2 children)

    Yeah... I have 100k rep (almost exactly!) and I don't use it any more. It doesn't have the network effects, so even if there is a question that AI can't answer (which does still happen despite what some people seem to think), I don't go to Stackoverflow, I go somewhere else. A forum, GitHub repo discussions, even IRC once (OpenOCD still uses that for some weird reason - they were extremely helpful though).

    It had a good run. RIP.

  • source
  • [–] 3 points 3 months ago

    It's not that it's a bad idea, it's more that it's basically impossible at this point.

    Bazel can't use Cargo, CMake and so on for downloading & building packages because it is trying to do cross-language builds the right way - a single build graph that includes everything. No other third party package managers/build tools actually exposed their build graphs - only commands to perform builds, which are too coarse for Bazel.

    To put it simply, its necessary if you are doing things at the scale of Bazel.

  • source
  • parent
  • context
  • [–] 6 points 3 months ago

    Python is one of the worst offenders here. I don't think Python's poor behaviour should excuse Lua's.

    But I can also see why Python is making breaking changes - a lot of Python is so bad it really makes sense to clean it up. I dunno if Lua is in that situation.

    Anyway I think I would look to other languages like Go, Rust, Java, C++ which do a much better job. I don't think Go or Rust have any backwards incompatibilities (at least very very few) and C++ has a small number but they're for stuff that is truly ancient or almost completely unused. It's totally possible if you care about it.

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

    Yes but that tracks issues of all severities and with all of GitHub's services of which there are a great many. Also "days since incident" is a terrible metric because it doesn't capture how long the incidents last.

    For example the latest incident is that copilot had degraded performance with Fable due to an Anthropic issue. It only last 18 minutes, only affected part of a part of their service, and it wasn't even their fault!

    That's very different to "all of GitHub is down for 7 hours".

    So yes. I am not sure GitHub is worse.

  • source
  • parent
  • context
  • [–] 1 point 3 months ago

    Ah yeah looks like the latest 19.1 release from June.

    But it also seems to suggest it's only a UI change. Is is possible to do stacked MRs across forks? Does it not still suffer from the flaw GitHub has (or had, hopefully) - you create one MR, myfork:feature_0 -> upstream:master. That's fine, but then you want to create the second MR targeting the first MR, myfork:feature_1 -> ???:feature_0, only you can't. feature_0 doesn't exist in the upstream and there's no point creating an MR targeting your own fork.

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