keysersoze33

Most of the energy consumption comes from moving data between memory and compute units rather than the math itself. While HBM stacked on a silicon interposer was a signification efficiency improvement over traditional DDR, there's still room for improvement. The high energy costs will drive this further, e.g. near-memory/in-memory compute (PIM) or tighter 3D packaging and possibly optical interconnects. (And of course training/model optimisations)

A couple of points:

- Pipewire or Pulseaudio has nothing to do with XWayland, let alone Wayland (Pulseaudio is somewhat legacy and may not be maintained as well as it used to be)

- Zoom (the last time I checked, a while ago) wasn't really well implemented on Linux (came before xdg-desktop-portal, which has standardised screen sharing across DEs and only really prioritised the GNOME specific extensions.

- The engineering effort to properly support screen sharing on Linux is a _bit_ more complicated than other platforms as we have many DEs

- Browser based screen sharing is generally the best option on Linux imho

Interesting to see at the bottom/Step 5:

> Before providing the final response, create a compliance checklist to verify that every constraint has been met.

I wonder if just this statement causes the Gemini to ensure compliance or there's a separate post validation function

Admit it, deep down, our inner engeering child also wants to build a semiconductor clean room ;)

The takeaway is to vet new companies one is dealing with - even just calling them up and asking if they've AI generated any system which deals with customer/patient data.

This is going to get more common (state sponsored hackers are going to have a field day)

Unless political lobbying becomes significantly harder (globally), I don't think the growing gap between the wealthy and poor will change anytime soon.

Problem is, to tax the ultra wealthy more, it needs to be coordinated globally. Otherwise, the ultra wealthy just move to where the tax system is more attractive. Not sure if this will ever happen to be honest.

However, awareness of the problem is still important

I think most distros are waiting to see if upstream can rethink this first and evaluate what makes sense. Forking something like systemd is no easy task. Perhaps this just starts out as a patch removing the DOB changes. But in reality, distros don't want to face possible legal ramifications either. It's all a bit messy, and time will tell (I suspect for the better, but who knows).

Being 46 (and quite an active 46 year old, just finished a Skitour), am curious why the cutoff for these things tends to be 45?