[–] 4 points 10 months ago* (last edited 10 months ago) (1 child)

The problem is not the conclusion*. The problem is that the method used to reach it is terrible.

As you say, you could look at license popularity on GitHub, and the author should have done something like that, but even those statistics have to be interpreted carefully:

Each data point corresponds to the rank of a license based on the count of unique developers who uploaded code to a repository subject to the terms of that license during a given quarter.

In other words, this measures how many developers are commiting code under each license, and thus is more of a reflection of the popularity of software under each license, rather than the licenses themselves.

Perhaps a more meaningful measure would be how many (unique) repositories are created with each license, since a developer commiting code to a repo does not mean that they favor the license of that repo. I couldn't find numbers for 2025, but amusingly these totals from 2020 suggest that no license is the most popular license, followed by MIT and then Apache

* The majority of my own code is MIT, by a large margin-

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

    The way to really optimize Python code, is by reducing the amount of Python code in your program, since Python itself is dog slow. Instead, you want to offload as much of the work as possible to modules written in compiled languages. So completely switching to Rust, or another compiled language, is simply taking that strategy to its logical conclusion

  • source
  • parent
  • context
  • [–] 1 point 11 months ago* (last edited 11 months ago)

    I'm sure that these are gems, but they are not hidden; going by Steamdb, these games are all in the top 3% most popular games on Steam, based on the total number of reviews:

    • Toem: 9,500 reviews on Steam
    • Ghost of a Tale: 5,000 reviews on Steam
    • Lost in Random: 5,000 reviews on Steam
    • We Were Here: 31,000 reviews on Steam

    Almost forgot: I don't think that I can name a truly hidden gem, but Deathbulge is pretty good and has a mere 360 reviews on Steam. Which is still more than the vast majority of indies, of course.

  • source
  • parent
  • context
  • [–] 9 points 11 months ago (1 child)

    My point was taking a picture of a box of rocks doesn’t prove the rocks were there before you opened the box. And if you disagree, explain your reasoning.

    Those rocks don't look igneous to me, so they have most likely been there for millions, if not billions of years before they opened the box

  • source
  • parent
  • context
  • [–] 17 points 11 months ago*

    How the fuck can it not recover the files?

    Undeleting files typically requires low-level access to the drive containing the deleted files.
    Do you really want to give an AI, the same one that just wiped your files, that kind of access to your data?

  • source
  • parent
  • context
  • [–] 13 points 11 months ago

    What do you want me to write?

    To meet the bar set by onlinepersona, you'd need to write safe C code, not just some of the time, but all of the time. What you appear to be proposing is to provide evidence that you can write safe C code some of the time.

    It's like if somebody said "everyone gets sick!", and some other person stepped up and said "I never get sick. As proof, you can take my temperature right now; see, I'm healthy!". Obviously, the evidence being offered is insufficient to refute the claim being made by the first person

  • source
  • parent
  • context
  • [–] 11 points 11 months ago

    I'm surprised that you didn't mention Zig. It seems to me to be much more popular than either C3 or D's "better C" mode.

    It is “FUD” if you ask why it’s still const by default.

    I'd be curious if you could show any examples of people asking why Rust is const by default being accused of spreading "FUD". I wasn't able to find any such examples myself, but I did find threads like this one and this one, that were both quite amiable.

    But I also don't see why it would be an issue to bring up Rust's functional-programming roots, though as you say the language did change quite a lot during its early development, and before release 1.0. IIRC, the first compiler was even implemented in OCaml. The language's Wikipedia page goes into more detail, for anyone interested. Or you could read this thread in /r/rust, where a bunch of Rust users try to bury that sordid history by bringing it to light

    Makes memory unsafe operations ugly, to “disintensivise the programmer from them”.

    From what I've seen, most unsafe rust code doesn't look much different compared to safe rust code. See for example the Vec implementation, which contains a bunch of unsafe blocks. Which makes sense, since it only adds a few extra capabilities compared to safe rust. You can end up with gnarly code of course, but that's true of any non-trivial language. Your code could also get ugly if you try to be extremely granular with unsafe blocks, but that's more of a style issue, and poor style can make code in any language look ugly.

    Has a pretty toxic userbase

    At this point it feels like an overwhelming majority of the toxicity comes from non-serious critics of Rust. Case in point, many of the posts in this thread

  • source
  • parent
  • context
  • [–] 10 points 1 year ago

    That's not quite true: Yes, your $99 license is a life-time license, but that license only includes 3 years worth of updates. After that you have to pay $80, if you want another 3 years worth of updates. Of course, the alternative is just putting up with the occasional nag, which is why I still haven't gotten around to renewing my license

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