Yes! since that Simon Willison article, I've slowly been easing all my scripts into just using a uv shebang, and it rocks! I've deleted all sorts of .venvs and whatnot. really useful
The uv shebang is definitely the killer feature for me, especially with so much of the AI ecosystem tied up in Python. Before, writing Python scripts was a lot more painful requiring either a global scripts venv and shell scripts to bootstrap them, or a venv per script.
I’m sure it was already possible with shebangs and venv before, but uv really brings the whole experience together for me so I can write python scripts as freely as bash ones.
I'm a hugeeee LunchMoney fan. It's a solo dev and she does great! Hooked a few friends on it as well. This has been a lifesaver for insight into my financials and it's super flexible.
I switched from a decade old spreadsheet to YNAB. Then it went subscription and online only. It relied on the Adobe Air runtime which stopped working in macOS several years ago (32-bit only).
I haven’t looked at firefly yet, but I really want something that allows me to forecast expenses, and realize them as they occur and automatically adjust forecasts accordingly.
There is a script to patch YNAB 4 on macOS. You will need your serial number (but that should be enough, the script _should_ download the applications). After this, you can archive all the binaries for more safety (AdobeAir, patched YNAB, etc.)
That was my thought as well. I normally resist subscriptions, but given how much effort I went through each month to get my spreadsheet setup to work, it seems well worth it.
Widescreen laptops were a phase, but they're rapidly falling out of fashion.
Being able to see more text (webpages, news articles), and longer lists (email inbox, code) is more important to more people than having a laptop that can watch movies. Split-screening on a laptop is rough no matter the dimensions. In the best case scenario you have a wide laptop and you see two panes, but a miniscule amount of rows on each pane.
Squarish laptops have been a breath of fresh air for me.
Obviously manufacturers haven't been eradicating useful screen ratios for no reason, I've just never seen anyone publicly admit to being the cause. Would you also like to take the blame for glossy screens, chicklet keyboards, and non-replaceable batteries?
> Obviously manufacturers haven't been eradicating useful screen ratios for no reason
For me 16:9/10 is way more "useful" than 3:2/4:3 ever was (had that for ages, wouldn't go back). I love being able to have two different things side-by-side, e.g. an editor and a terminal, on a 13" screen, at a font size I can still read well. I definitely wouldn't buy a square-ish laptop screen.
And I'll take anything that's more square than 16:9 personally.
16:9 is great if I wanna watch movies all day, unfortunately for the apparently unaware laptop industry, I need to also work a little bit sometimes.
Thankfully Apple never jumped on the stupid 16:9 bandwagon with their laptops. Now if only some monitor manufacturer would wake up and start making 27"+, 16:10, 4K+ monitors with 120hz+ refresh rate then I'll literally instantly buy 5.
A poor cope for being forced to use a media consumption format. In order to make full use of the ratio ill-suited to productive work, you are compelled to adopt a specific workflow involving two windows being open at all times. Great, that stackoverflow search page can stay open. Do yourself a favor: pivot one of your cursed resolution monitors and open a source file on it in full screen. That is how many text rows you lost in the war on general purpose computing.
The resource I recommend to people looking to move from wet lab to dry lab stuff is https://www.biostarhandbook.com/. From your post history it looks like you already have some programming experience, so you could skip the first few chapters which are just a linux intro. I don't think it has all the best practices, but I think it's the most comprehensive overview that starts from square 1 and fills in all the gaps no one tells you when you first start, for example the "Common data types" chapter.
1. `uvx --from git+https://github.com/httpie/cli httpie` 2. https://simonwillison.net/2024/Aug/21/usrbinenv-uv-run/ uv in a shebang