I think we need all support we can get to fight Google on this, so I welcome Brave here actually.

Use this link to avoid going to Twitter:

https://nitter.kavin.rocks/BrendanEich/status/1684561924191842304

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 3 years ago (7 children)

The chrome javascript engine? V8 you mean? That's used in Node, it basically powers most, if not all, of the modern web lol

  • source
  • parent
  • hideshow 7 child comments
  • [–] 2 points 3 years ago (4 children)

    Node is far from the most popular. Majority of websites run on PHP.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 3 years ago (3 children)

    Hence the modern. Most modern websites nowadays don't use php anymore, at least for their FE

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 3 years ago (2 children)

    Laravel is modern enough. If you're talking bleeding edge web dev, that's actually on elixir with Phoenix

    Not sure how you count how "modern" something is considering PHP still has new versions and cut lots of releases

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 years ago* (1 child)

    Good point, I had forgotten node uses v8. It's powering servers that run node, sure. Not every website uses node. Lemmy I think is rust backend and kbin uses PHP.

    But I mean browser specific rendering. They all follow ECMAScript standard but there are things outside of it. In the past __proto__, a way to get an object's prototype, only worked in Spidermonkey. Or how the ECMAScript doesn't specific what order the elements in a for...in loop shows up. Today these are little minor things

    They aren't particularly important right now (besides hunting weird bugs) because Google follows the standards more or less. But give Google 100% control and you will start seeing dark patterns slip into the javascript itself

  • source
  • parent
  • hideshow 1 child comment