I am intrigued but want to know more about how I might use it. Suggestion - lots of people like me are heavy airtable/coda-like users who setup relational DBs for various projects. Should I be looking at this to replace any of these efforts?
it is not so much about replacing stuff (although also possible) but more about abstracting everything into a general layer above all your databases. you can then query and writeback this layer and sutra then communicates with all your databases. you talk human language (objects, relations, actions) and sutra then translates this into every dialect the computer needs (csv, sqlite, pg, mssql, mysql, your mails... extendable)
This has got to be ragebait. If you do any serious software engineering, ontology is inescapable. Eg. I would like you to model software for the automotive industry without using ontology. Try it. There's a ton of concepts, terms, hierarchies to get through before you write a single line of code. Without ontology, you'd be shooting yourself in your foot every 5 minutes, I guarantee you that.
I understand not applying it to life, but have you run into specific issues with ontologies at work? Structured categorization and organization of information is good on first principles to me, provided that you can maintain it.
Hm. I think there are some commonalities that you can model within a company that guide how you should structure information for that company, but I think we might be talking about applying an ontology in different ways. If you don't order the information at all, it becomes impossible to retrieve when you need it.
the point is that sutra-os has also typed actions. that means you don't only link stuff but you execute the linked stuff against each other. it is like human language executed like lisp.
Few people think and reason with rigorous ontology in real life. That's why ontology is hard to popularize—but it's also exactly why most people drift through life mediocrity intact.
Readme is covered in slop hallmarks. LLM prose, LLM UI design. This just means I can generate something better and more preferential myself. The experience doesn't reflect any understanding of the domain beyond what I could generate. Not interested. Sorry.
The maintainer sets the tone. Contributor pull requests, if merged, may temporarily improve the state of the repo, sure, but they're much less likely to influence the maintainer's quality bar for the repo.
And so the current state of the repo, before anyone else contributes, must communicate that tone, because that is a trust-building exercise. What you have to communicate is, "I will cherish your efforts; I will not let them go to waste." The AI-isms in the repo currently communicate the opposite.
If you use a building you have respect for the architect, room-decorators, facility managers, cleaners and so forth. Doesn't mean a cleaner will expect room-decoration from the architect. Also almost nobody cherishes effort - only the work that gets done when playing a certain role for a certain time.
No, it's probably wrong. I don't think anyone able to model(structure) `user` properly without the context of the application.
And so the current state of the repo, before anyone else contributes, must communicate that tone, because that is a trust-building exercise. What you have to communicate is, "I will cherish your efforts; I will not let them go to waste." The AI-isms in the repo currently communicate the opposite.