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

help-circle


  • What you are mentioning is forcing companies to comply when selling inside the EU or California. The EU does not force companies to comply with their specifications outside of the EU. Companies simply do so because it is convenient.

    The EU cannot decide how cars should be made that are sold in California. If they tried, I bet the US government would have something to say about it.

    What the EU can do, is exert influence to get other governments to adopt the same rules. This already happens with a lot of countries surrounding the EU. But asking another government to adopt rules, is wildly different from forcing companies to adhere to those rules inside the borders of another government.


  • Not entirely. There still exists trade agreements, and diplomatic pushback.

    Forcing companies to make products to a certain specification, would mean the EU is attempting to regulate other markets. Markets it has no direct governance over. While it may come from good intentions, it still invades the authonomy of the governments that should have governance over these markets.

    Much better would be to work together with other countries, and help these countries implement similar rules, and enforce them together. Like, pretty much that the EU is doing for its members in the first place.







  • The problem with C++ is not the lack of safety features. It’s the ever lasting backwards compatibility that is keeping it both alive and down at the same time.

    Having to support 50 year old code, is going to limit any restriction you place. But it is usually the restrictions that make a language good.

    Example: You can write perfectly good modern C++ code without any pointers. But pointers are so ingrained into the language, that it is impossible to remove them.



  • But I love coding at work?!

    The problem is that every living entity in a 10 kilometer radius around me, seems to be hellbent on getting me to do anything but coding. Refining work estimates, fixing badge access rights, fixing a driver issue, telling people that you cannot do 1000 things at the same time, teaching the new developer how shit (doesn’t) works, mangling Jenkins into a functional state again, explaning that thing I did a year ago but is only now used (it was very high prio a year ago), writing documentation that noboby ever reads, progress meetings, specialty group meetings, knowledge sharing meetings, company wide meetings, etc.



  • Europa Universalis IV and Stellaris. For exactly the same reasons.

    I spend way too much time in those games. Hundreds of hours each. But the end game is just too much of a slog. You already won, so there is no challenge; the framerate tanks into unplayable territory; and the micromanagement to manage the late game wars and economy becomes insane.

    But starting with a different empire, and doing early/mid game again is awsome!



  • You can look up what the acronym AESA means without unstanding it.

    Take two speakers that are next to each other. If they emit a tone of the same frequency, the sound will “add up” and be louder in some directions, and cancel out to some degree in others.

    A phased array radar uses the same concept, but now on electro magnectic waves, instead of sound waves. And with much more than just 2 emitters. By carefully choosing the phase of the signal in each emitter, itnis possible to both choose a single direction that receives the strongest signal, and to tighten the spread around that direction (creating a pencil beam). This is what the dish is for in standard radars.

    If these phases can be fully controlled electronically, you can steer where you are looking, and swap between wide and narrow search beams in an instant. However, that is not a trivial thing to produce. So cheaper phased array radars use mechanical systems, or partial electronic steering (example: only horizontal steering).





    1. Threads federates
    2. Threads hosts 99% of all content and all users.
    3. Threads releases and update that allows a new feature. Example: they add buyable threads gold, that you can reward to a post or comment.
    4. The rest of the fediverse can’t implement this feature, and is inherently left behind in terms of features.
    5. Threads releases an update that breaks federation. 99% of the users do not notice.
    6. It takes Threads 3 months to fix the issue.
    7. Go back to step 5.

    Every non-Threads participant will have less features, and is constantly struggling to keep up with the changes and bugs of Threads. Result: the fediverse cannot grow. Only the most stubborn anti-Meta users will accept the objectively worse experience, just to avoid using Threads. But the average user will just use Threads, instead of joining Mastodon, Kbin, Lemmy, or any of the many other fediverse instances that Threads can federate with.