- OpenTyrian (likely available in your package manager)
I’m a Christian, a dad, an open source fan. I have a blog: https://daviewales.com/
I mainly use Python, so my workflow is the same on every OS: Neovim and a shell, usually one of each in a vertical split. This transfers nicely to remote SSH sessions too, and even works in Termux on my phone!
Have you investigated whether it’s possible to test your cross-compiled builds in Qemu, rather than copying them to the host?
I think they said in the release article that they were going to roll 115 out slowly because it’s such a big change.
My 3 year old daughter has a 2010 MacBook running AntiX. She knows how to boot it, press Enter on the dual-boot screen, and is getting close to being able to select Stardew Valley from the app menu. She also enjoys playing GCompris.
I have a git repository in ~/dotfiles
, and symbolic link the ones I want as I need them. I’ve only just started tracking my dotfiles and I’m not super disciplined with it yet, so I still have slightly different setups on each system.
The first step is to make sure your hardware is supported. I’ve found the linux hardware database to be invaluable getting new systems configured. The site is overwhelming at first, but the easy path is to just click the big ‘Probe your computer’ button and follow the instructions. Once you’ve done a probe, you’ll get a web-page with a listing of all your computer’s hardware and the support status. Even better, you get links to additional drivers or kernel modules required to get stuff working which isn’t supported out of the box.
I’d suggest maybe wait for 4.1. I just started playing with 4, and hit a bug where Godot will hard crash whenever you try to view the Terrains tab if you’ve created terrain sets, used them in your scene, then deleted the terrain sets.
Hanukkah of Data by the Visidata team was fun.
Can I suggest duckdb?
You can start out writing SQL directly on top of CSV and Parquet files.
But then if you want/need to do something more complicated, you can import duckdb
into Python, keep running the SQL you already wrote, convert it to a Pandas or Polars dataframe, transform it, then query the result in SQL.
But how do you authenticate to your secret manager? How do you prevent evil scripts from also doing this?