I think it would still make sense to compare with those table formats, or is the idea that you would only use this if you could not use a table format?
MAXSTACK: Web framework for rapidly building SaaS apps with AI - trying to enable the next wave of 'fast-fashion saas'. Think of it like better-auth is doing for auth, I want to do for the rest of SaaS
- comes with common SaaS features pre-built (crud, blog, auth, etc.)
- import templates from the framework until you want to customize them
- create forms with just a zod schema
- good docs, typescript interfaces, a CLI for common tasks, and MCP for your AI agent
If you're building something now or want to - I'd love to help. Could use the experience to make things easier through my framework.
I'm glad there's vibe coding available to non-tech founders so they can build the equivalent of high-fidelity prototypes. May not be MVP worthy yet, but at least it gets them started.
SaaS vendors do these business value assessments, which are useful to the executive buyer and the vendor. The issue I find with them is customers don't want to do them in collaboration with the vendor since the vendor will use that to justify higher prices. 'Outcome' and 'business value' seem somewhat synonymous - so maybe need to focus on the business value more closely (and all the modelling that goes into that). I don't know if all of the billing needs to go through this, but perhaps discounts or bonuses could - at the very least helping with retention.
Glad to see focus being put on keeping humans in the drivers seat, democratizing coding with the help of AI. The syntax is probably still too verbose to be easily accessible, but I like the overall approach.
Feedback on the name: I didn't think that it would be about containers. The other platforms you mentioned are more descriptive (jsfiddle, db-fiddle, Go playground, and Rust playground)
Not only is Dimitri an amazing engineer - he's also great at building community and event/video production. Michigan Typescript meetups and videos have a level of polish that goes over and above
What's sad here is that this dispute isn't likely to make Wordpress any better, but rather send money to lawyers and reduce enthusiasm for the OSS project.
There's a lot of possible choices presented to the user, some of them totally out there like 'Ximenia'. Maybe there should be fewer choices, or can group them by what the author might guess are the common choices (where I can focus my attention), then a group with the less common choices. More elaborate things are possible like dynamic grouping and using web/LLM searches to come up with the initial choices.