> The easiest way is to start by putting everything into one file. You can start simple, defer some decisions, and evolve your project with time.

This is something that most even senior developers don’t grok. Default so called project starter scripts of the node world don’t help either.

The more structure you build before you know wth you’re doing, the more difficult you’ll make life for yourself down the line when you inevitably have to refactor code.

Little confused - I’ve been using fractional scaling on Wayland for 6 months now!

Meanwhile my personal installation is 8 years old. It was initially installed on a desktop on btrfs and has since moved between three laptops and across to ext4 and now xfs. 150K lines in pacman log file. I love it.

GDPR applies to any company that offers services to EU residents. It doesn’t matter if the company has any presence in the EU.

Now, that means EU may not necessarily be able to force the company operating in a different country to pay up but if a company has any significant EU customer base, I assume they will play ball.

One wheel scooter are generally more dangerous than their two or more wheeled counterparts because upon software bug or power loss, all control is lost. At higher speeds, serious injury is very likely.

> Under an agreement with the tribal government, Tesla will train tribal members to serve as service technicians.

> But with 574 federally recognized tribal governments in 35 states, Tesla’s new strategy could do a lot to close that advantage.

Fuck ye!

Implementation of EVERY service on AWS is unnecessarily complicated. Not an exaggeration. Making things simple takes considerable consideration and effort, and that costs money. AWS is a nano-margin business. As long as something works and doesn't fall apart, they ship it.

> Elon is a fake person created by VCs to fulfill their goals.

I'm gonna give you a bucket full of benefit of doubt and assume you mean nothing negative by this. I'm all for fake people fulfilling VCs goals if that means we can have better and more exciting future (which Musk has delivered to date).

It's worth mentioning that many other "real" people with "no" hidden agendas have done ... jack shit over the past 20 years. :)

What did he deliver?

Assuming you’re sincerely asking this to learn, I suggest you ask Google, and read some Wikipedia to boot.

Ok, his rich family gave him some money to invest and got lucky with paypal. Then he became a hypeman for Tesla and routinely lied about full self driving in order to keep Tesla from bankruptcy and produced unsafe and poorly built cars. Then lied about trucks, roadsters, and solar roofs. He's speed running the history of tunnels and trains and will find out that, yes, putting independent cars in a tunnel is a dumb idea. Hyperloops? Seriously? Buying twitter blue checkmarks only to introduce another checkmark for verificaiton. Hm..Space-X is sorta futuristic? He hasn't proven reusable rockets have saved orders of magnitude of money.

It’s undeniable, no matter what you think of the character, that he created huge momentum in the transition to EVs.

Also, rockets.

What are alternatives to Falcon Heavy?

My humble boot installer, no explicit bootloader, straight to the kernel:

    #!/bin/bash
    set -ueo pipefail

    # Remount EFI partition read/write and restore to readonly when done

    trap 'mount /sys/firmware/efi/efivars/ -o ro,remount &>/dev/null || true' EXIT
    mount /sys/firmware/efi/efivars/ -o rw,remount &>/dev/null || true

    # Remove all existing Arch Linux entries

    efibootmgr | grep 'Arch Linux' | grep -Po 'Boot\K\d+' | while read -r bn; do
      efibootmgr --delete-bootnum -b "$bn" &> /dev/null
    done || true

    # Install boot entry

    efibootmgr --verbose \
      --create --disk /dev/disk/by-id/nvme-abcdef --part 1 --label "Arch Linux" \
      --loader /vmlinuz-${_linux} \
      --unicode "initrd=\\intel-ucode.img initrd=\\initramfs-linux.img OTHER-KERNEL-BOOT-PARAMS"

EDIT: added initrd boot params

If you want to add an initrd, create an EFI payload: https://wiki.archlinux.org/title/Unified_kernel_image#Manual...

$ stub_line=$(objdump -h "/usr/lib/systemd/boot/efi/linuxx64.efi.stub" | tail -2 | head -1)

$ stub_size=0x$(echo "$stub_line" | awk '{print $3}')

$ stub_offs=0x$(echo "$stub_line" | awk '{print $4}')

$ osrel_offs=$((stub_size + stub_offs))

$ cmdline_offs=$((osrel_offs + $(stat -c%s "/usr/lib/os-release")))

$ splash_offs=$((cmdline_offs + $(stat -c%s "/etc/kernel/cmdline")))

$ linux_offs=$((splash_offs + $(stat -c%s "/usr/share/systemd/bootctl/splash-arch.bmp")))

$ initrd_offs=$((linux_offs + $(stat -c%s "vmlinuz-file")))

$ objcopy \

    --add-section .osrel="/usr/lib/os-release" --change-section-vma .osrel=$(printf 0x%x $osrel_offs) \

    --add-section .cmdline="/etc/kernel/cmdline" \

    --change-section-vma .cmdline=$(printf 0x%x $cmdline_offs) \

    --add-section .splash="/usr/share/systemd/bootctl/splash-arch.bmp" \

    --change-section-vma .splash=$(printf 0x%x $splash_offs) \

    --add-section .linux="vmlinuz-file" \

    --change-section-vma .linux=$(printf 0x%x $linux_offs) \

    --add-section .initrd="initrd-file" \

    --change-section-vma .initrd=$(printf 0x%x $initrd_offs) \

    "/usr/lib/systemd/boot/efi/linuxx64.efi.stub" "linux.efi"

The resulting linux.efi" can be added directly with efibootmgr, and contains the kernel boot parameters (cmdline)

uh - you just specify the location of your initramfs in the kernel boot params and that's it, no need for all the above

You hadn't specified it at first, so I thought it might be helpful to provide a more complete example with different parts (like the initrd) and offsets, with a gummiboot stub

Having kernel and initrd separate makes things more complicated and brittle.

Also a secure boot setup is much more difficult this way.

I for my part love the UKI. Never had a simpler boot setup!

> a secure boot setup is much more difficult this way.

Is it? Don't you just sign the bootable kernel image that already has the initrd and command-line built in?

Oh, I guess if you're using Microsoft as a CA I can see why that would be tricky.

I think this is a misunderstanding. I've said secure boot is much more difficult in case kernel and initrd are separate.

In case of a UKI it's very simple of course. Just sign the boot image.

That's why I love the UKI. :-)

> It is simply (physically) not possible for the existing cameras to see the area directly in front of the car.

Think about how a human driver does it, given his/her even worse vantage point. They model what's in front/behind the car from afar and remember what's where as they approach it. There are other signals as well, such as continuation of a kerb, etc.

I think people keep forgetting that Teslas run hundreds of ML prediction tasks all the time. Watch recent AI day and their talks about "occupancy network" to get a sense of the car's ability to:

1. Construct 3D model of its surrounding in real time; 2. Remember occluded sections based on what's it's seen previously.

Human driver constantly turns head around to where he is Mos likely to hit something.

Well, the car has 360 degree camera view, with far wider coverage than a turning head in a driver seat.

And more importantly, it sees in all directions at all times.