Have you found appdata/local/Application Data? It’s a “conjunction point” that you can only find via the command line, and only exists for backwards compatibility. It points to appdata/… Do not EVER try to gain access over all your files in appdata/. It’ll break due to that conjunction point.
I’m confused why you’re asking for feedback. You already chose Svelte and Sveltekit, no?
Here’s my feedback anyway: I like Python and dislike Javascript. Yes, Python is slow (though that can be offset via Pandas, among other libs) but it’s relatively painless. Unlike JS, which is quite painful to work with. JS libs also come and go every few years, whereas Python’s seems a bit more stable in that regard.
But it also depends on whether I’m part of your target audience - who is your target audience?
I unironically prefer apt over pacman, simply because my monkeybrain got addicted to running pacman -S (that was how to update, right?) and I dropped in productivity. apt is just “nah fam, there’s nothing new for you” most days, which gives me the quiet time I want and need.
I ran Manjaro BTW. It was nice while it lasted, but Debian is my new friend now.
Probably not often, but as a Debian user, it’s a PITA to get back to where I was before I fucked up my system. Nix(OS) sounds like a future investment to me, just in case I ever fuck up and need to get back to where I was ASAP. Been there once already and it was NOT fun.
That was from a professional standpoint BTW, privately I’m still a dirty Windows pleb, because that’s what I’m most familiar with.
PS: I’m already using a dotfiles repo, which already saves me a ton of time in settings things up.
I’m slowly learning Nix, and I’ve learned that Nix has more packages available than any single distro could ever deliver: https://repology.org/repositories/graphs.
It even has more than AUR (Arch User Repository, BTW)
Also, regarding better formats: parquet is relatively nice. Smaller files, though not human readable. Use parquet if you read often, or have IO issues (file “too large” as CSV).
What’s even the “gold standard” for logging stuff I guess?
structlog. Or just Structured Logging in general.
Don’t do:
logging.info(f"{something} happened!")
But do
logging.info(“thing-happened”, thing=something)
Why? Your event will become a category, which means it’s easily searchable/findable, you can output either human-readable stuff (the typical {date}, {loglevel}, {event}) or just straight up JSONL (a JSON object/dict per line). If you have JSON logs you can use jq to query/filter/manipulate your logs, if you have something like ELK, you can insert your logs there and create dashboards.
It’s amazing - though it may break your brain initially.
I see an Arjan video, I upvote. This guy really boosted my Python knowledge during my Junior years.
rockstar
We fixed that one: https://codewithrockstar.com/
OK, but why would I use this over ABCs? (Abstract Base Class). Or is it just different?
Ubuntu is a gateway drug to Arch.