• 0 Posts
  • 27 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • I’m pescetarian, so I will eat fish, most of what I eat is either vegetarian or vegan. So it’s certainly easier for me than you. But here’s the thing, I was brought up this way, therefore I don’t like the taste of meat and don’t want imitation stuff either.

    But I have no difficulty with this at all. A lot of dishes just have meat in them, but they really don’t need it, they’re good without it, it’s not the base of the dish. The foods in shops that are prominently labelled “vegan” or “plant based” are primarily meat and dairy alternatives, because there’s no need to label all the other things that have always been inherently plant based. At least in recent years it’s becoming trendy to label these foods “plant based” that would never have had meat in them anyway, it makes it clearer, but it’s not always the case and there’s no real need to.






  • "1" + 2 === "12" is not unique to JS (sans the requirement for the third equals sign), it’s a common feature of multiple strongly typed languages. imho it’s fine.

    EDIT: I did some testing:

    What it works in:

    • JS
    • TS
    • Java
    • C#
    • C++
    • Kotlin
    • Groovy
    • Scala
    • PowerShell

    What produces a number, instead of a string:

    • PHP
    • SQL
    • Perl
    • VB
    • Lua

    What it doesn’t work in:

    • R
    • C
    • Go
    • Swift
    • Rust
    • Python
    • Pascal
    • Ruby
    • Objective C
    • Julia
    • Fortran
    • Ada
    • Dart
    • D
    • Elixir

    And MATLAB appears to produce 51, wtf idk



  • So what’s the deal with GNU? When I first saw it, I was sure the G was silent, or formed a dipthong, like gnat or gnocchi or gnaw or gnarly or gnome or just any word starting with gn in English. But IRL, I’ve only heard it pronounced with a hard G, same with Gnome.



  • Usually they’re building the website with browserlist and polyfills, and they specify how old a browser they wish to support, usually by analysing percentages of public usage, or they allow types only supported in newer browsers. Meaning if they use a feature only available in newer browsers, then it won’t be automatically backported to support older browsers.

    But that’s only if they actually use those features, they’re just available to them. And it’ll only break in those places they do use them, which could be quite little of the site.

    So often it’s just “we can’t guarantee it’ll work in your old browser and enough of our users use newer browsers that we’ll block you and not care”.