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

help-circle






  • That was true a long time ago. And remains true in some places, but since we started pushing the different bins, things progressed on that front. Plenty of place have actual recycling facilities (although their efficiency is another topic). Of course, in some far away area, it is not practical to sort stuff, but it’s kind of a chicken and egg problem. Infrastructure see no point in making large facilities for processing recyclable if they’re not sorted, and people see no point in sorting their trash if the infrastructure isn’t available. Putting colored recycling bins everywhere to initiate the process was cheaper.











  • Wow, prejudiced much. The JS ecosystem evolved a lot over the year, and polyfills for most environment are next to non existant. The worst environment to me (react-native) do heavily use them, but they’re built-in anyway.

    Also, about stuff being slow when made in JS… people that make slow clusterfuck in JS would also make slow clusterfuck in other languages. React is guilty of that too, trying to re-implement core language features OVER the language itself, and that is stupid. Still, as with every language, it is possible to use it decently. You’ll never get to the point of raw optimized assembly performance, but even higher level scripting language can leverage JIT compilation and work well on any modern (<10 years) computer. Taking as an example the worst developers out there using the worst way to do things is not exactly a good benchmark.



  • Backward compatibility and not seeing the future. Some decisions are taken at one point in time, then a new use case show up, then a new paradigm evolve, then… etc etc.

    It’s really the same thing that holds back a lot of languages and libraries. And even when replacement shows up, old habits from devs and old projects maintenance keep all these things well alive too.