Activity Log
hackers.town: 2024-07-03 Wed 05:41
@spinningthoughts Cuzu, Kuzu, or Cozo?
Given the naming schemes out there I wanted to check whether it was a typo or an undiscovered database.
hackers.town: 2024-07-03 Wed 05:44
@grmpyprogrammer the main test I use is “do I have time for this person’s nonsense? No? Bye.”
And honestly when I’ve answered with a tentative yes, I usually end up being wrong and they get blocked a few hours or days later.
hackers.town: 2024-07-03 Wed 05:49
@PsyChuan As somebody who’s always been me but mainly refined into something closer to how I wanted to see myself, I’m delighted when folks do a more profound healing transformation in their lives.
hackers.town: 2024-07-03 Wed 07:38
The secret Tucson game archive
hackers.town: 2024-07-03 Wed 08:01
Curious whether a Windows Dev Drive would make a difference in #Logseq startup time. It’s supposed to be optimized for quickly accessing lots of small files.
Cloned my graph to the new path. Loaded it from the new location. Restarted Logseq because it’s easily confused when switching graphs.
I didn’t take a stopwatch to the experience or anything, but startup on my 1,187 page graph from basic NTFS C:/ takes 15-20 seconds, and 5-10 seconds from the ReFS Dev Drive.
hackers.town: 2024-07-03 Wed 08:22
Fine I’ll time something. Added simple time.Since(start) style timing logic to the Logseq graph-parsing Go code I wrote last night.
against graph files on NTFS drive: 1.07s
against graph files on ReFS: 1.05s
Well that’s not impressive. What if I write the encoded JSON to a file instead of STDOUT?
on NTFS: 308.02ms
on ReFS: 262.68ms
Not as dramatic a difference as I saw starting Logeq, but handling files on ReFS is consistently faster at least.
hackers.town: 2024-07-03 Wed 08:24
dangit my brain is gonna make me reboot into linux now
hackers.town: 2024-07-03 Wed 08:39
unsurprising news
same code, same graph, both pulled from remote so all’s same as on Windows
on ext4: 192.1ms
hackers.town: 2024-07-03 Wed 08:49
@spinningthoughts Well their persistent claim is that the graph files will remain the ultimate source of truth.
As for whatever gets stuffed in SQLite, there’s EDN libs for most of the common languages.
aannnd honestly? My brain is gradually moving me towards my own interface to the graph files, including writes. I want to improve the interface and I don’t find Electron + ClojureScript + Datalog interesting enough to merit the learning curve.
I’m an API dev mostly. So I want an API-first PKM that other tools can build on.
hackers.town: 2024-07-03 Wed 08:50
@spinningthoughts I found Kùzu, Cozo, and Cayley on the same day, and I’m always getting them mixed up.
hackers.town: 2024-07-03 Wed 09:02
@spinningthoughts It’s part of why I keep coming back to Logseq: everything is either a block or a page, and judging by their export JSON even pages are just special blocks. Tag? That’s a page. Property? That’s a page.
It’s a simple enough foundation that I can build my own assumptions and conventions without breaking the structure. Sort of LISP-y. (The UX is where everything goes to heck, but yeah. Simple structural logic.)
Contrast with Obsidian etc where there’s pages, with content and properties, and never the twain shall meet — unless you forcibly link to a page in your property. Tags are their own namespace. It added more overhead to my processing logic.
hackers.town: 2024-07-03 Wed 09:20
@spinningthoughts exactly. I am sufficiently old school that I remember being able to show document structure (sort of a “tree + markup codes”) in whatever mid-90s word processor I was using, and that model stuck with me.
hackers.town: 2024-07-03 Wed 09:35
@spinningthoughts Yep I could see a REPL being handy, at least as a debugging tool!
Mostly pondering flags and context management for a CLI tool, which could maybe run in daemon / server mode for multiplayer.
Inspirational starting points come from Joplin’s multiple interfaces and how nb utilizes existing system tools.
hackers.town: 2024-07-03 Wed 10:44
WordPerfect was my favorite word processor. So I’m a little disappointed I only learned how excellent Bruce Bastian was just now, after he died.
“Keeping his home base in Utah, Bastian spent the next three decades as a philanthropist and activist, donating millions of dollars to support organizations and causes related to the arts and LGBTQ issues, including Equality Utah, the Utah Pride Center and the Human Rights Campaign.”
@estherschindler
https://hachyderm.io/@estherschindler/112723732706203627
hackers.town: 2024-07-03 Wed 14:00
Wanting to do a thing with go that requires learning cgo which also means catching up on 20-ish years of C and C++ developments, or at least enough of them to understand the code I’m trying to connect to.
hackers.town: 2024-07-03 Wed 15:25
Spent about three minutes with manual cgo efforts before I started looking around for code generation tools. c-for-go has been entertaining me for the last hour or so.
hackers.town: 2024-07-03 Wed 15:28
@grmpyprogrammer My career has been a rollercoaster that should probably be shut down for violations of health, safety, and fire codes. OTOH I’ve mostly had fun, been able to help some folks out, and folks I care about got to have a more comfortable time on this earth than they might have otherwise.
Worth it.
hackers.town: 2024-07-03 Wed 16:04
Oh heck it built successfully wtf do I do now.
hackers.town: 2024-07-03 Wed 16:06
@lmorchard I’m on it!
hackers.town: 2024-07-03 Wed 17:06
It worked?
WTF
Mind you it’s using an automatically generated cgo interface built by c-for-go using some pretty naive rules, and my main code is at least twice as many lines as it should be — even considering that it’s Go.
Nevertheless, I repeat for emphasis: WTF
hackers.town: 2024-07-03 Wed 17:32
My READMEs are more like warning signs.
hackers.town: 2024-07-03 Wed 18:10
@farah I get it.
This morning I spent half an hour looking up electrical infrastructure terminology for the alt text of a two second joke toot.
hackers.town: 2024-07-03 Wed 18:54
@web_goddess that is so cool!
hackers.town: 2024-07-03 Wed 19:33
@maddiefuzz @Jetengineweasel
Parsing is involved in one project.
I’m think this thread should maybe go in the README.
hackers.town: 2024-07-03 Wed 20:20
@genehack Could be worse.
I’m pretty sure it could, anyways.
hackers.town: 2024-07-03 Wed 20:23
Okay so doing strange things with a niche library is definitely easier on the Arch-based Linux partition than on Windows (native or WSL).
hackers.town: 2024-07-03 Wed 20:24
@genehack this would also have been valid.
hackers.town: 2024-07-03 Wed 20:41
@genehack erm? Well I’ve got exactly one iron anywhere near any sort of heating element, with a referral by sungo to his workplace.
But considering the scope and quantity of my applications for the last year and limbo interview pipelines during that time —
nah I’m still at “erm?”
Yay I think?
hackers.town: 2024-07-03 Wed 20:44
@genehack I mean if one of the ghosts wants to come back out I am not gonna argue!
hackers.town: 2024-07-03 Wed 20:57
because sometimes you want your tunes a little pensive
#NowPlaying
hackers.town: 2024-07-03 Wed 21:14
@yojimbo I honestly don’t know. Sims started to lose me around issue 150. Kept along a little longer because Gerhard’s backgrounds are damn gorgeous, but the wall of proto-MRA text panels became more and more common, and I just lost interest.
hackers.town: 2024-07-03 Wed 22:01
@genehack oh and also also I got disoriented and distracted by the mysterious “considering an offer” but hey thanks for saying kind things!