• 0 Posts
  • 251 Comments
Joined 3 months ago
cake
Cake day: March 23rd, 2025

help-circle
  • squaresinger@lemmy.worldtoMemes@lemmy.mlTransmission Error
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    4 minutes ago

    Zionism is the one thing where anti-semites and Jews (at least zionist Jews) agree.

    Zionist Jews want it because it gives them their own country where they are not persecuted.

    Anti-semites want it, because it means that the Jews are not in their country.

    That’s why even the literal Nazis supported zionism. Every Jew in Israel was one less Jew in Germany.

    You get the same thing still today with the most right-wing politicians supporting Zionism/Israel. On the one hand because it’s a way to keep Jews far away and on the other hand because it can be used as a “I’m supporting Israel, so surely I can’t be a Nazi. Anyway, let’s go shoot some Muslims.”-kind of excuse.






  • Tbh, the vast majority of performance issues don’t come from the language but from the application itself.

    While python is clearly slower than rust when it comes to pure native performance when doing exactly the same things exactly the same way and only within the language itself, the same isn’t necessarily true in the bigger picture.

    • Python uses C modules under the hood. A lot of the functions you call actually utilize C with C performance.
    • Lower level languages allow the programmer to fail harder. While perfect low-level language code usually runs faster than perfect high-level language, the same cannot be necessarily said for bad or average code. For example, it’s really hard to make an actual memory leak in Python. It’s super easy to do so in languages without built-in memory management. The same applies in many other cases too. Python just gives you a lot of already-done tools that you only have to use, while other languages allow you to build the tools from scratch, which is easy to mess up.
    • Most performance is lost due to using wrong algorithms or data structures. It’s quite common when optimizing that you e.g. manage to eliminate a nested loop or something like that (e.g. loops hidden inside functions you call), and suddenly you improve performance by a factor of 1000. The same can’t be done by switching languages, where even the most inefficient languages are only maybe 10x slower than the fastest languages.

    So independent of the programming language, investing time in optimizing can improve the performance much more than using a faster language, and it’s much easier to make perfectly optimized high-level language code than perfectly optimized low-level language code.




  • Tbh, immigration isn’t the worst “solution”.

    We do have an overpopulation problem. Well, an overconsumption times overpopulation problem, really.

    We could fix that by either consuming less (which we apparently, as a species, really don’t want) or by having fewer people (which we apparently really want).

    So, in the end, reducing population isn’t a real problem. Even if the population shrinks by 50% each generation (~25 years, for the sake of the argument), there will still be 250mio people left even after 5 generations. The trend should probably be reversed sometime then, but until then it’s really not an issue on the species survival aspect and it would actually be really good for the planet and our long-term survival.

    But until then we have mainly one problem: our economic system is based on infinite growth, which can’t work. So again there are two main solutions: either we bring in people from other countries, who benefit from a higher standard of living here while supporting our economic system, or we get rid of the real parasites and freeloaders in our societies: the ultra rich. And again, for some reason we really don’t want to get rid of the rich.



  • Park and ride is what that concept is called.

    Even with low parking fees and low public transport fees, you need to incentivize their usage even further by e.g. adding a city toll, so that people have to pay when going into the city by car.

    But even then it’s not really THE big solution. In Vienna, for example, about 450 000 cars cross city lines into the city each morning. An average parking spot in a garage is about 12.5m² plus 7.5m² of space to access it, so ~20m² in total.

    That’s a total of roughly 9km².

    That’s about 2% of the total area of Vienna, and currently it’s provided by thousands of parking garages and parking lots distributed all over the city.

    But if you were to build that on the outskirts of the city, the park and ride facilities would have to be enormous.

    Even if you build 5-story parking towers that’s still roughly 2km².




  • Beware, what you are comparing vsync off with vrr.

    You have four options when it comes to screen refreshes:

    • Vsync off, VRR off: you get frames as fast as possible, no latency, but also tearing
    • Vsync on: the frame rate gets synchronised with the screen refresh rate. That means, sometimes the game will wait for the screen, leading to a lower frame rate (limited to the refresh rate of the screen) and slight latency, but no tearing
    • VRR: the game can lower (not raise) the refresh rate. Compared to Vsync maximum refresh rate it will lower power consumption and do nothing else
    • Triple buffering. Needs to be implemented by the game, not by the OS. Provides maximum frame rate and no tearing with minimal latency.