I backup my Obsidian vault weekly by blindly committing the stuff in `.obsidian` and then reviewing the changes to the `.md` files themselves. It's not version control, per se, but at least a backup and record.
Yes. This is the modern equivalent of “I searched the web and this is what it said”. If I could do the same thing and have the same results, you’re not adding any value.
Though this is unlikely a scenario that happened, I’d equate this with someone asking me what I thought about something, and me walking them over to a book on the shelf to show them what that author thought. It’s just an aggregated and watered-down average of all the books.
I’d rather hear it filtered through a brain, be it a good answer or bad.
> A while back there was a rewrite language that was posted (white on black theme site) that was similar but more geared towards coding problems and less on lit programming. I don't remember the name but it was equally as interesting. If anyone recalls what it was it'd be greatly appreciated.
Oh very cool, not what I was thinking of but it definitely fits my description. The one I was thinking of was text/code based. Thanks, this looks fun too.
I did this for MBTiles, for storing (at the time, raster) map tiles at Mapbox. I was working on the iPad wing of R&D early in the company and we were focusing on offline mapping for the iPad. Problem was, moving lots of tiny map tiles (generally 256px square PNGs) was tedious over USB and network. We had a thing called Maps on a Stick for moving things around by USB, but it just didn’t scale well to the iPad interface & file transfer needs.
Bundled the tiles into SQLite (I was inspired by seeing Dr. Hipp speak at a conference) and voila, things both easy to move and to checksum. Tiles were identified by X & Y offset at a given (Z)oom level, which made for super easy indexing in a relational DB like SQLite. On the iPad, it was then easy to give map bundles an application icon, associated datatype from file extension, metadata in a table, etc. At the time, I was fairly intimidated by the idea of creating a file format, but databases, I knew. And then making some CLI tools for working with the files in any language was trivial after that.
Thanks. Shortly afterwords, I started collaborating with a few folks and it definitely was a team effort to push it forward (icon design, UTFGrid spec, node-sqlite & server-side adoption...). It's still a very satisfying solve for the problem.
PHP contributed hugely for me. I was writing a lot of Perl for web apps from about 1996 to 1999, when PHP really took hold and was an improvement in almost every way, right down to including PCRE regex functions. Perl felt clumsy compared to PHP, especially for MySQL and other relational DB stuff. PHP was built for the web.
I have an HP-15c as well as a 16c and I've been using the latter on a daily basis while writing a byte-level network protocol client. I'm getting faster by the day and on the verge of writing some programs for shortcuts on the calculator. I still use the excellent PCalc as well, but seem to be faster on the physical calculator, which is kind of surprising.
When I was writing a shareware program in x86 assembler and doing a fair amount of bit twiddling, the 16C was really handy. Presumably I still have it around somewhere.
reply