I always bring my backpack personally.
Hawk
I've always had an easier time jumping into an oop code base, then eg a lisp one.
I hear people when they say they don't want their data mixed in with their logic but The pressure to structure code Is very nice.
Element is a complete disaster.
Like, completely unmaintained and broken.
Matrix works over i2P and Tor, just proxy the service.
P2P chat could include retroshare but it's not really a solution due to a variety of ux issues.
I wasn't aware of that. I've even seen vendors using it.
I know it's E2EE and open source but there is a lot of Metadata.
What other limitations does it have?
Well, it would still be a vector. So some standardisation.
Perhaps another perspective is where to draw the line in terms of expected expertise.
Half-baked is a bit unkind. Sway is quite performant, stable and lean.
Use Quartz and Obsidian because it’s easy. If not mcdocs.
Yeah if it's just for Plex something like Endeavour OS would be pretty much painless.
Definitely easier than fighting a key.
Well it's there, in one loooong print out. It's not as bad as I'm making it out to be, however, I went back to python unfortunately.
The crucial issue with Julia, no error messages.
So I use Julia for things that need to be fast (e.g. moving hdf5 to SQL and ffts) but I use python for everything else (except ggplot).
ThinkPad or framework