Formerly /u/Zagorath on the alien site.

  • 0 Posts
  • 185 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle




  • Okay but they often don’t give users what they want

    You should see the state of Firefox on iPad OS. I started using it earlier this year after they finally rolled out support for multiple windows—a feature Safari added in 2019 and Chrome had only a few months later.

    Nice that they finally have this feature, but the browser itself is nearly unusable. It stutters constantly and freezes, locks up, or force reloads with some regularity. In a way that Chrome and Edge (and I assume Safari, though I have never really used that) never do.

    Or on desktop OSes, a website I frequented around 2016–2018 used the column-span CSS property, which Firefox didn’t get around to implementing until December 2019.

    It’s been very clear for some time that, whether it’s because they stretch themselves too thin or some other reason, Mozilla has been failing to continue to deliver an excellent product for their users.





  • Yup absolutely. I mentioned web APIs because that’s what I’ve got the most experience with, but .h files, class library public interfaces, and any other time users who are not the implementor of the functionality might want to call it, the code they’ll be interacting with should be tailored to be good to interact with.


  • If the doco we’re talking about is specifically an API reference, then the documentation should be written first. Generate code stubs (can be as little as an interface, or include some basic actual code such as validating required properties are included, if you can get that code working purely with a generated template). Then write your actual functional implementation implementing those stubs.

    That way you can regenerate when you change the doco without overriding your implementation, but you are still forced to think about the user (as in the programmer implementing your API) experience first and foremost, rather than the often more haphazard result you can get if you write code first.

    For example, if writing a web API, write documentation in something like OpenAPI and generate stubs using Swagger.



  • We could have used the tilde, which has been used in formal logic & maths for negation in very many contexts for a long time.

    It’s used instead in C and many C-like languages for the far less useful bitwise negation. Of course, we could have had it work in the same way as bitwise vs logical and & or, by dialling up the symbol. Which would have massively improved its visibility compared to the bang.

    But for some reason, no. They chose the bang instead.







  • A century or so of oppressed masses and greedy elites did it.

    True, and that’s important context if you’re trying to get a deeper understanding of how Julius Caesar came to have the power he held before his assassination.

    But there’s enough of a problem you can see even if you just start at Julius, which is what I was concentrating on in my previous comment. The parallels to Trump are terrifyingly on the nose.