• 0 Posts
  • 696 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle
  • No.

    EVs are more efficient than the low range for the motorcycle. If you charged your EV with a portable gas generator, your efficiency is comparable to an ICE motorcycle. Most grids at this point are quite a bit less CO2 intense than a personal generator. That cuts significantly on the CO2 impact.

    The only upside to a motorcycle is the reduced energy requirements for manufacturing. But lifetime, an EV will be the clear winner.


  • Pretty hard to guestimate as it’s anywhere from bike efficiency to more than ev efficiency.

    What makes it hard is capacity. A fully packed electric train will be the most efficient transport mechanism. A mostly empty fossil fuel train can be as bad or worse than ICE vehicles.

    If you have one available, then it’s probably your best bet to lowering impact.


  • Yup, this is perhaps surprising to some.

    Bikes win hands down by being the most efficient form of energy usage for transport. Walking requires a lot more calories to travel the same distance you can go on a bike. Those calories come from farming and that (diet dependent) very quickly can outpace any lifetime savings from using a bike. A bike is about ~99% efficient at converting energy into motion.




  • It’s a mess. You first run into bandwidth problems on the incoming streams. But you also run into a problem with the device support matrix.

    If you say “We’ll support H.264, H.265, AV1, AV2” and “We’ll support 480p, 720p, 1080p, 4k”. Now you’d be asking the clients to do 16 different encodes to upload.

    This gets more complicated if you add more streams or supported formats. You also end up needing to coordinate that with the client.

    AFAIK, the way youtube currently handles this problem is they have dedicated encoders for live streams and fast encoding. For popular videos they do a second step where they do a more full matrix to optimize viewership.

    IDK what youtube does for storage (if anything).



  • Bluetooth is one of those things that is a crapshoot in linux. A big part of that is because the bluetooth protocol itself is a giant train wreck. It requires a stupid level of integration into the OS to do basic stuff (It should have just been effectively what Wifi Direct is). It also doesn’t help that the linux audio stack is kinda fucked.

    Sleep/hibernate is also somewhat of a crapshoot because it’s a very weird protocol.

    For some linux hardware these things work pretty well, but for others it can be a nightmare to make work properly.

    FTR, I’m currently using KDE plasma + pipewire and that works pretty well for me with my bluetooth devices. But I realize that’s probably also somewhat due to me having good hardware for linux in the first place.








  • For stoves, the thing that breaks is the control board. Hot + electronics is bad.

    An induction stove avoids most of that problem because the hot happens in the pot and not inside the stove.

    But I agree, there’s not much reason a stove can’t last 50 years. In fact, my parents have a 50 year old resistive stove that still works.

    Washers have the most to go wrong of things you listed.






  • I threw linux on an old laptop. Lemme tell you, the thing really just flies now. Under windows the fan was constantly kicking on because of all the bloat and extra garbage running. Now, the fan only kicks on when I kick the laptop into high performance mode (keeping the clock speed maxed out).

    The boot speed is also insane. There’s like a 2 second boot delay from off.

    It’s great to know I now have a laptop that will be supported for the next 40 years. Everything works perfectly.