MarginaliaSearch VS lowdefy

> I think a larger concern is how you'll address the Bus Factor going forward

I can't speak to how much energy it is to go from code to serving requests, but FWIW the code is AGPLv3 and seems to be updated regularly https://github.com/MarginaliaSearch/MarginaliaSearch/blob/v2...

Regarding the last sentence: The problem is that capitalism knows no limits. Sure, it would be nice to pay a monthly subscription for genuinely good and desirable content/search results...

But what if the CEO of the service provider needs another $5m bonus? What if the stock needs to go up so that the shareholder gamblers can get more dividend paid? What if all of a sudden the service gets bought out?

The truth is that what you are seeking is more likely to come from someone who is just passionate about it with not that much motivation based on profit. That doesn't mean that this entity or person can't be financially supported but it gets problematic when profit is the _main_ incentive.

For a good example of an interesting search engine built by a single guy, see Marginalia: https://search.marginalia.nu/

Have you heard of https://www.marginalia.nu/ in general, and especially the https://search.marginalia.nu/ from there?

There's a decent amount of people still keeping the fire burning for the "old web." It takes a little digging, but it's out there.

Some links for you:

* https://wiby.me/ — search engine that emphasizes simple/plain/hobbyist pages. Try the "surprise me" link a few times.

* https://neustadt.fr/essays/the-small-web/ — article, "Rediscovering the Small Web"

* https://search.marginalia.nu/ — author (hangs out on HN sometimes, too (marginalia_nu)

Actually, here's a link to a similar discussion on an old HN thread: https://news.ycombinator.com/item?id=30783391

I built a recipe detector. You can, you know, train some sort of AI model to do this like with fasttext, or maybe do naive bayesian inference, but as it turns out, you can also:

https://github.com/MarginaliaSearch/MarginaliaSearch/blob/ma...

It works annoyingly well.

For some values of "nobody"; this westerner enjoys https://search.marginalia.nu (in addition to more common engines) and has high hopes for the new site browser:

Result ranking takes a lot of variables, and factors like excessive tracking and affiliate links is one of them in my search engine.

You can poke around in the result valuation code here: https://github.com/MarginaliaSearch/MarginaliaSearch/blob/ma...

#1 cause in the decline of Google maybe. https://search.marginalia.nu/ seems to manage though, so maybe Google just doesn't care.

Congratulations on shipping.

I see a lot of focus on startups, AI tools, productivity hacks, tech stacks, etc. What audience do you have in mind? I personally find that the most interesting sites on HN are outside of your scope here (examples: https://ciechanow.ski/, https://neal.fun/, https://search.marginalia.nu/).

I'm really enjoying reading through the docs and the tutorial. We've created Lowdefy, a config web-stack which makes it really simple to build quite advanced web apps. We're writing everything in YAML, but it has it's limitations, specifically when doing config type checking and IDE extensions that go beyond just YAML.

I've been looking for a way to have typed objects in the config to do config suggestions and type checking.. PKL looks like it can do this for us. And with the JSON output we might even be able to get there with minimal effort.

Is there anyone here with some PKL experience that would be willing to answer some technical questions re the use of PKL for more advanced, nested config?

See Lowdefy:

https://lowdefy.com/

https://github.com/lowdefy/lowdefy

Awsome! With Lowdefy we tried to build a low-code framework that works like code. We’ve developed a schema in which to define applications and we’ve built all kinds of apps for enterprise customers. Massive, advanced CRM systems, call centre solutions, ticketing systems, a light MRP, all kinds of survey apps and so many dashboards. Even our docs and our website are Lowdefy apps!

Give Lowdefy a try and reach out it you have any questions or want to see what is possible :) (We need to invest a lot more into content and examples, bootstapping is a grind!)

https://github.com/lowdefy/lowdefy

Also add Lowdefy onto the list https://github.com/lowdefy/lowdefy

co-founder here :)

100% this. And yes, good documentation takes a lot of investment but it pays off like compound interest. But with that done, it becomes even more important not to pull the carpet for no good reason, you are building a tower and documentation is at the foundation.

We’ve built Lowdefy [1] as an open source project and documented it with all effort, 200 pages of docs. I often forget why or how something works and then jump to the docs. This investment keeps on paying of as we use Lowdefy to build customer apps, new devs in the team typically take less than two week to get up to speed and start making contributions, the sharp ones, just a two or three days.

This year, we’re extended our documentation onto customer apps aswell, with flow diagrams, state machine definitions, detailed field level explication schema definitions, and end user test procedures. The key here for this documentation is detail. It should be easier to reach for the docs and the the answer, than to dive in the code and interpret it.

1 - https://github.com/lowdefy/lowdefy

https://github.com/lowdefy/lowdefy Co-Founder here.

Check out https://lowdefy.com/ they even have a sample survey app as one of their examples.

You can build an app that would do this

Lowdefy is a low code tool that uses AG Grid as a block component, allowing you to create apps which render data in AG Grid without a lot of coding knowledge. There is a Lowdefy example using AG Grid here.

Shameless plug, also check out Lowdefy - https://github.com/lowdefy/lowdefy

I’m also going to jump in here and say try Lowdefy https://github.com/lowdefy/lowdefy - co-founder here.

We take a different angle and believe that low code should still work like code. We focus on a developer first approach.