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
Posts
2
Comments
1232
Joined
3 yr. ago

  • How does it work, then?

    I'm assuming that's a genuine question... Normally when people develop a feature they do it once and then it's "done" and any changes to that feature have to go through the whole feature request -> it's low priority -> wait 10 years cycle before they actually happen.

    Essentially, you have to do it right first time or it might never be fixed.

  • It’s an alpha release.

    You really think they're going to revisit this? That's not really how software development works.

    It’s an alpha release.

    I was talking about Flatpak.

  • It’s as easy as pie too; they show up right there on the boot menu:

    <screenshot of KDE followed by apparently random numbers>

    I really don't understand why people have this little awareness of usability. Show the freaking date normally! At least add hyphens.

    We tried Dolphin and Konsole as Flatpaks for a while, but the user experience was just terrible.

    Yeah I'm fairly sympathetic to Flatpak. It's way closer to how software should be installed by users. But I have yet to actually use it successfully. Is it really ready?

  • Still need an adapter though. Kind of blows my mind that they still haven't made it so the stock RPi can use anything better than SD cards.

  • We went past that point many years ago. This is way overdue.

  • They're probably pretty good for CRUD apps, which do tend to be like 50% boilerplate, but also I also wouldn't characterise them as "bullshit". Boring maybe.

  • I think it's both true that you can't really write an entire app with just AI... At least not easily.

    But also I don't buy that AI doesn't make me more productive. I'm not allowed to use it on my actual code but I have used it several times to generate one-off scripts and visualisations and for those it can easily save hours. They aren't software I need to edit myself though.

  • Sure but you don't normally run GCC or Clang directly; you make, and that normally does optimise. I think a closer example is CMake which doesn't enable release mode by default.

    MSVC is usually run from Visual Studio which makes it obvious which mode is being used so the default doesn't matter so much.

    As for "all the other compilers", Go optimises by default. It does seem to be the exception though...

  • It’s slower for two very good reasons (better static analysis and better feedback).

    Apparently that's not really the reason. cargo check is usually quite fast.

    I also wouldn't say Rust code is slower than C. It wins in some places (e.g. strict aliasing) and loses in others (e.g. bounds checks) but in practice it's usually much faster because it's so much easier to use fast containers (not just linked lists everywhere), fast libraries, and multithreading.

  • Tbf this mistake comes up so often I do wonder if cargo should have defaulted to release builds. It seems to be what beginners expect.

  • One mistake they did unfortunately ship though is bind patterns that look like variable names.

  • Definitely a promising language, and I tried to write something with it a year or so ago. It's clearly still in the "research language" phase though; "hello world" took about 2 minutes to compile.

  • Headache isn't a word I'd associate with Rust. More with Ruby or Python (at least until uv mostly saved us).

  • Yeah I agree. Presumably they don't do that though because you'd end up with pages of nothing but ).

    I never understood why they don't add just a little syntactic sugar. You don't need much to take it from a mess of brackets to something comprehensible.

  • Rust is fairly well known for not having footguns (except async Rust at least) and for not being a headache.

    I guess it can be more complex than something like Python or Typescript though. I would say that extra complexity is not a big deal compared to the pain you'll have to deal with working with a language as niche as Nim though.

  • I just use Rust for this. You can make the binaries fairly small if you put a bit of effort in. Plus it's not a niche language, and you get the benefit of a huge community. And your code is pretty much fast by default.

    The only real downside is the compilation time, which is a lot better than it used to be but still isn't great.

  • I dunno I would say Lisp syntax is probably the worst option. Or APL style.

  • Seems like they allow () code blocks too, so it's kind of the worst of both worlds...