ckmar

Drop the "G". The best UI for AI Agents is a physical UI (not a graphical UI). Do something like PikaCube [0] and disrupt the mouse.

[0] https://pikacube.pages.dev/

Nice, I had seen that. Ideally it wouldn't be something that sits on my desk. I want to hold it and talk to it and build spacial awareness with it. But fits many of the goals. I'll have to give it a try!

PikaCube is a thought experiment "solution" with a website one-shot from claude code. I don't want to make something like it, I want to buy something like it.

Have you seen unfluence? https://unfluence.app

Read the manifesto [0] or check out the product walkthrough video [1].

[0] https://unfluence.app/about

[1] https://www.youtube.com/watch?v=mFZ8zcF8r8M&ab_channel=Craig...

Have you seen Pure ORM? It's an ORM that purely does object relational mapping.

You write SQL but instead of getting back flat and potentially-collided data, you get back pure objects which are properly structured.

https://github.com/craigmichaelmartin/pure-orm

> The SQL is not really the point. It's about the rows and objects, moving the data from the objects to the INSERT statement, moving the data from the rows you SELECTed back to the objects.

If anyone is looking for this "pure" ORM (no query builder API) in Node there is https://github.com/craigmichaelmartin/pure-orm

One line of code which is specific in what it catches:

    // Either foo or someError will be defined
    const [foo, someError] = itry(someFn, SomeError);

Instead of nine lines which feel like they are working uphill against the language: dealing with variable scoping issues, deeper nesting, and footguns like forgetting to re-throw.

    let foo;
    try {
      foo = someFn();
    } catch (err) {
      if (err instanceof SomeError) {
        // do something with error
      } else {
        throw err;
      }
    }
    // use foo

TLDR; Evanesce is a tool to provide Static Route Generation (SRG) by disappearing your web framework for opt-in routes and building the HTML for a route in the background when a dependency of the route changes.

I made a platform[0] to support natural "word of mouth" recommendations - where you can discover what your trusted family and friends recommend.

It's called unfluence to connotate the inversion of influence from social media ad networks, to individuals.

[0] https://unfluence.app

Big fan of queries being written in SQL and yielding pure, properly structured business objects.

An example of this approach is PureORM[0]

[0]https://github.com/craigmichaelmartin/pure-orm

unfluence.app FTW. Search for recommendations in your own trusted network.

[0] https://www.unfluence.app

I am soft-launching unfluence.app in the coming weeks. It's live now, though not yet marketed.

It is a platform for finding and sharing recommendations within your own trusted network. I'd love to hear your feedback!

You can read more about it on the home page[0], from its inspiration, comparisons with existing solutions, to a down-the-road monetization model that aligns with the network.

It is being built by Kujo - a brand in the lawn care industry, and so is seeded with products and brands for that community. The initial launch will be within the lawn care community. However, the platform is community-agnostic and supports creating communities for any groups.

[0] https://www.unfluence.app

The idea is not to develop a better search engine[0], but to no longer relegate product reviews to a search engine. Rather than an opaque algorithm as the trust factor, why not social (+n degree) trust?

[0] https://twitter.com/paulg/status/1477760548787920901

What are your thoughts on using social trust for this? EG https://app.kujo.com

I would certainly hate for devs to hate on this top-secret pure orm project [0].

[0] https://github.com/craigmichaelmartin/pure-orm

You don't really own anything, except there is a system that recognizes you paid to own something.

NFTs just decentralized that "system" to a blockchain.

An overview of the new card: https://9to5google.com/2021/05/18/google-chrome-new-tab-page...

Oh interesting! I'll have to check it out!

YOLO

Yeah, when you're doing the 1% of super complicated stuff, definitely don't use this (and opt for the underlying database driver directly). But when you're doing the 99%, it's great! Unlike with stateful ORMs, there is no temptation to do the 1% using some obscure orm methods and never heard of option params. Just write the sql.

PureORM[1] is an implemented thought experiment on what a "pure" object mapping library would look like - where you write regular native SQL and receive back properly structured (nested) pure business objects.

It would contrast against traditional ("stateful") ORMs which use query builders (rather than raw SQL) to return database-aware (rather than pure) objects.

The name pureORM reflects both that it is pure "ORM" (there is no query builder dimension) as well as the purity of the mapped Objects.

[1] https://github.com/craigmichaelmartin/pure-orm