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/)BI
Posts
0
Comments
766
Joined
2 yr. ago

  • It took a wrong turn in the 90s. There's been no real feasible way to fix it without breaking the web for many decades now. Some things are just forever despite their problems, like QWERTY.

  • This meme is really only true for things like Slack where the app is just the webpage in an app, and even then it's not quite true because Electron is a lot heavier than a webpage because it has to now run the webpage and the app - which I think is terrible.

    But then also, Electron enables actual apps to be developed using web standards - which I think is great.

    TLDR: Use Electron to make apps, not glorified webpages.

  • My sense is that this argument primarily holds for teams without thorough code reviews. For individuals or teams with good reviews, TypeScript adds little except for complex code or massive rewrites. I'm not saying it adds little in absolute terms, but that it adds little once you account for the overhead of using it.

  • This is the core thesis of the article:

    It's true that sometimes you have to write non-trivial types to convince the compiler that your data is correct.

    That's okay. Creating maintainable code with high quality often requires putting in the hard work.

    There's no real substantiation of the claim; just the claim itself.

    Yes TypeScript is onerous but that's just alright.

    Maybe it's true but it's a weak argument.