dynaQ VS TiddlyWiki

I wouldn’t consider it idiomatic Go (and not something I recommend for use in production), but for fun, I built dynaQ (an abbreviation for dynamic querier) as a PoC of an extension to the database/sql core package erasing the need to model your DB results or use an ORM. There’s minimal reflection used to keep things performant, you can pass in an option whenever creating the new dynamic querier to auto-detect a time value from your database with a custom format (or take it’s default), and more.

But that’s why I built dynaQ. No need to pre-model your returns and it’s just as performant as the standard library ;)

I don’t have a contributor guide written for either of them, but feel free to help with the few issues in either this or this package I’ve written and released. They’re super simple things, but I’ve been rather busy at work and in life. So I haven’t had the time to address them. If you want to contribute, feel free to send me a DM with any questions!! Otherwise, just fork the repo(s) and just open a PR once you’re ready for the changes to be merged. I’ll review it asap!!

Nice!! Looks like a great companion to this module that I wrote and released recently!!

As far as projects to study go, I’ll start off with a shameless plug of two Go packages I’ve written, myself. This one is for converting between RGB (and other color space formats) to the nearest matching DMC thread color. This one is admittedly an extremely unidiomatic package (it’s completely opposite of how you should do things in Go) for supporting dynamic queries in Go without headaches or pre-defining “model” structs to hold each row of your query results. It’s something that can be useful, but it’s also built to showcase making the language work for a use case it wasn’t originally meant to support. If you wanna take a look at them, feel free. Also, I suggest looking at the testify repo. It’s an EXTREMELY popular testing library, and it’s also structured well.

I’ve created a package as an extension of the database/sql package in the stdlib for supporting dynamic queries without headaches in Go without having to predefine the structs. So you might be able to take some pointers from how I accomplished this

A couple of days ago, someone asked about why using dynamic queries in Go was such a headache. And after reading through the comments, looking at code, and studying others’ frustrations with this issue, I decided to tackle it. And that’s how dynaQ was born!!

It’s called dynaQ. It allows you to use dynamic queries on a database, with database transactions, and more, without having to pre-define any model structs to hold the returned data. It also allows for variable query arguments, as well as the ability to use custom time formats in your database and configure that format whenever creating a dynamic querier. Take a look and give it a shot!! I think you’ll be pretty pleased with the result

> What does ownership mean here?

It means owning the code and the data. With webapps, the code and data are hosted and owned, the users do not own the code, cannot run it independently. This is a clear dileneation between owner and user, and the owners can use that clear line to create artificial scarcity of various kinds. (The most popular being the subscription SaaS model). It's also easier to defend your IP since end users never see your binaries.

I like to make my software single html files whenever possible. People can just save them and run them locally. Havent met anyone who cares yet though.

I like that idea a lot, and I care. I think others care, but yes, it's a niche interest. Take a look at https://tiddlywiki.com/ for an example of a fairly successful project that uses the single html format running locally. However it suffers from limitations on File|Save which often requires a separate runtime of some kind to support.

Another project that approaches this ideal is https://redbean.dev/, @jart's tiny, performant, featureful single-file webserver. In this case the "single file" is a server executable + zip whose state must be updated on the command-line, but I think hits a sweet spot in terms of practicality, and a global minima when it comes to minimizing dependencies. (Redbean bundles SQLite and Lua so it's also possible to do through-the-web state updates as in a traditional webapp.)

My own project, Simpatico, aspires to be something along these lines. Eventually your browser tab is both a client and server process, connecting via websockets to other connected browsers, storing all state locally. I call this pattern "monomorphism", a play on the "isomorphic" javascript SPA. The server[2] is currently written in ~1 node file, but eventually I would like to port to redbean (and greenbean, the websocket version of redbean, but it isn't quite ready yet). The server grew several features to support a fast, practical BTD loop using markdown[1], and safe, performant execution on the public internet[2], but ultimately I'd like to pare it down to serving a single html file and allow the connected clients to provide all diversity of experience. I've used it to explore all kinds of browser apis, from crypto[3] to svg[4] to writing my own libraries (combine[4] and stree[5]). And it's all running locally, and easily hosted on a $5 VPS, and its all open source.

1 - https://simpatico.io/lit.md

2 - https://simpatico.io/reflector

3 - https://simpatico.io/crypto

4 - https://simpatico.io/combine

5 - https://simpatico.io/stree

I use TiddlyWiki. It's a portable editable wiki that doesn't require a web server or web hosting. You open it from your computer, edit it, and save it. You get all of the linking that you'd expect to see in a wiki, and it's super readable and easy to use.

It is a single-HTML-file TiddlyWiki instance that runs in a web browser (offline as well as online), meant to be downloaded and stored wherever suits you best. Everything that you see when working in BASIC Anywhere Machine (everything that makes "BAM" work as an IDE and all BASIC programs) exist in the one HTML file.

TiddlyWiki still works as intended: https://tiddlywiki.com/#GettingStarted but there are so many different clients to run on. Mobile or Desktop ? What OS? What Browser?

This effort https://val.packett.cool/blog/tiddlypwa/ is remarkable as the mobile side of saving is not as robust as on the desktop side of things and there is a scaling limit on performance as the number of tiddlers grows. Also the syncing between tw documents between different desktop/mobile clients can be a challenge with diffing.

Since then I've moved back to plain vanilla vim for a wiki (map gf :tabe ) but tw.html is still good for data other than plain text and TiddlyPWA https://tiddly.packett.cool/ is a great effort to revisit TiddlyWiki again.

You should check out TiddlyWiki as it’s designed around the concept that small linkable notes are the best way to organize.

https://tiddlywiki.com/

It’s html based so you can access it in the same way you would access a website but it can be locally stored. Saving is a bit tricky but there are multiple solutions detailed on their site. https://tiddlywiki.com/

Hi, you can use tw on nodejs with npm package tiddlywiki....