> Quantum Leap plans to run FreeBSD on contemporary laptops as a hypervisor-like solution using Bhyve to virtualize other operating systems, including Linux and Windows.
Are they gonna sell laptops running FreeBSD with a virtualized Windows guest as "more secure" to the US government?
>To be clear, systemd-boot doesn't replace GRUB, in that systemd-boot can only boot other EFI binaries, so it still requires the kernel to be compiled as a UKI. A GRUB setup with a regular vmlinuz + separate initramfs in root partition (or boot partition that's not the ESP) can't be replaced with systemd-boot directly. You first need to switch to a UKI-in-ESP setup.
Install arch with a couple of different bootloaders and disk layouts, and you'll learn it all. The simplest option is potentially systemd-boot + an unencrypted rootfs.
And you usually get lumbered with some shitty thing like github actions which consumes one mortal full time to keep it working, goes down twice a month (yesterday wasn't it this week?), takes bloody forever to build anything and is impossible to debug.
> Because you’re already using other software that has LLM integration
Oh really, which software would that be? And which other LLM-enabled software connects production environments or has access to auth credentials/tokens?
I don't want LLMs to parrot back code from other projects without understanding what that code does and what my code does. I don't want it to parrot back irrelevant slop.
And I especially don't want it to parrot:
rm -rf $BUILDDIR/ && ./build-project.sh
and just hallucinate the assumption that $BUILDDIR is already defined.
But GitHub doesn't ship copilot as a separate binary. So the threat vector of “AI has no place in my VCS get it out it increases the surface area” is there. So it’s okay for github to have copilot but not iterm2 to have codesierge? Doesn't add up.
The point here is about compliance. I agree it’d be stupid to pipe the output of an LLM to a terminal’s command line. But people are saying they can’t use iterm2 now because compliance says no AI and having an mdm-secure way to disable the functionality is not enough because _there could be a bug_ or something. Yet they’re checking commits, in presumably the same compliance regime, into other software with AI features.
Sadly there isn't on Linux. There is on Mac - Ctrl-K. But for some reason nobody on Linux has realised how useful it is. It's actually even better than `reset` because it works at any time.
I think you're conflating SHELL with TERM because the OS has nothing to do with what hot keys your terminal emulator supports (the OS wouldn't dictate hot keys available for shells either, but popular Linux distros don't tend to default to Zsh like macOS does).
A terminal emulator is the software application you use to bring the command prompt up. So a terminal emulator is operating system agnostic.
Granted there are some macOS only terms out there like iTerm2 and Apples own Terminal. Just as there are terminals that haven't (as far as I'm aware) been ported to macOS, like xterm. But there's plenty of cross platform terminal emulators too, in fact most are cross platform.
I'm not conflating anything. On Mac you can press Ctrl-K in any terminal emulator and it will clear the terminal and scrollback. On Linux no terminal emulators support this (except Kitty it turns out - as mentioned in the other comment).
Sadly Kitty is very bare-bones. Not really for me. And I can't choose to use Kitty in VSCode.
Care to elaborate? I had an impression that it's a pretty complete piece of software. I've been driving it daily for more than 1½ years, and I'm pretty happy with it.
Well the first two things I tried that are present in pretty much all software - scroll bar and Ctrl-F to find, did not exist. There's no menu bar at all in fact.
I didn't even realize, I don't see a need for it anyway.
> Ctrl-F to find, did not exist
That's because Kitty has something much better:
> Sometimes you need to explore the scrollback buffer in more detail, maybe search for some text or refer to it side-by-side while typing in a follow-up command. kitty allows you to do this by pressing the ctrl+shift+h shortcut, which will open the scrollback buffer in your favorite pager program (which is less by default).
> There's no menu bar at all in fact.
Which is a big plus. Emacs has a menu bar (and a toolbar), and I obviously turn them off, because they take up screen real estate.
That shortcut opens HISTORY, hence it is ctrl+shift+H. And if the terminal emulator used up ctrl+f to implement find, it would mean that no terminal program could use ctrl+f to implement find. Maybe next time before you try to imply other people dont know UX, pause, and consider if you know what you are talking about. Incidentally, using the term UX itself, generally is a good signal that the person that is using it doesnt have a clue what they are talking about.
And ctrl+shift+f is the same as ctrl+f for you? The point of using "identical" keybindings is to ease discoverability across programs. ctrl+shift+f and ctrl+f are not identical and therefore there is no point to doing that.
And pretty much anyone that has to deal with internet commenters using the term UX thinks that, not just me.
Ctrl+Shift+F is commonly "find in all files" so it's a logical shortcut to try. In addition, adding Shift to a shortcut to get around this exact problem is also common. For example Ctrl+Shift+C/V are common copy/paste shortcuts in terminal emulators on Linux.
Wide events described in this article seem to equal structured logging but a more loose dumping ground. So yeah to an extent it has this problem, just more so.
How does tracing? Are folks adding PII to spans? I suppose you could but I'm not sure why.
I would argue the benefit is also it’s declarative, done forever, and your machine becomes relatively bulletproof.
Dev environment issues are a thing of the past, once you’ve defined your configuration.
If something is broken with a package, I don’t have to figure it out myself —- I just rollback, wait for someone to fix it upstream in nixpkgs and pull down the patch later.
At least in my opinion, the leverage here isn't about directly saving time in some hypothetical universe where you set up new devices every week.
It's about confidence in your ability to quickly bootstrap a productive system and the relative freedom/security that flow from knowing it.
When you know you can be productive this quickly without access to a backup or a working device, you have relative freedom and security from a decent spectrum of manufacturing defects, hardware failures, disasters, accidents, thieves, and so on.
reply