Agree that the types accomplish basically exactly what I want.
If it gets a decent community / ecosystem I think it would be a frontrunner for sure, especially for web apps.
One potential issue is that the runtimes it targets are not that great at processing - they fanout well on BEAM but may not be the best for heavy processing. Not a deal breaker but smth that others like F#, OCaml, Rust can outperform in if the other attributes do well.
Anecdotally I think AI is quite good at langs with lots of training data: C#, TypeScript Rust.
I also think it's much better with languages with more guardrails and clear syntax: think expressive types (sum types), brackets, and linters / compile checks.
Rust has expressive types and lots of compile checks to avoid classes of bugs via ownership / lifetimes and I think makes it a very good tool for agents to use.
That might land with native unions but it's not there yet. There's workarounds with OneOf and Dune but those are kind of messy.
I think expressive types on dotnet are possible - I am a big fan of F# and those types are very good. So I think C# will get there but I can't say it's there yet.
I really like it for building backends but I haven't found the frontend story as compelling. Currently I use F# for my API and then use a standalone frontend (currently SvelteKit) to try and get the best tool for backend / frontend.
Q: How's your experience been with F# frontends? I'm assuming you're using Fable?
I've been building MVPs for the past yearish with this stack. Some of these choices are newish / smallish but it's the simplest, most enjoyable stack I've tried so far.
I find .NET to be great for backends though maybe not as great for frontends (there's just better stuff out there). So I use the best tool for the job and that typically means using something else for frontend.
- Solopreneur / Indie Hacker / Tiny SaaS scene. This is more an implementation strategy of my dreams of Financial Independence but I find these communities have large overlap. Building small, sustainable solutions to real-world problems to make a decent living. Not glamorous, but lots of freedom. Communities: IndieHackers and lots of people on Twitter.
- Simple Code. I think most system architectures / frameworks / languages are suboptimal - either being hard to reason about or a pain to code in, etc. So this bucket is about trying to find technologies that actually best support their usecases, regardless of what their adoption looks like. This led me to two scenes: Svelte / SvelteKit for frontend and F# for backend / general purpose programming and is now how I build pretty much all my apps (see: https://cloudseed.xyz). The subreddits for both these communities are good.
- Creative Coding / Technology - I used to be more involved here but now am more of an observer. Basically trying to use the power of computing to create cool things - mostly artistic. This comes in a range of forms but typically procedural / generative art is at the core. Subreddits r/generative and r/creativecoding are pretty active
This is cool! Great to see you've had some success here!
I've built something similar for my favorite tech stack but haven't had any sales yet. I find it useful in my own projects and I've seen other similar projects make some money (like JumpStart Pro for Rails) so thinking it's something around my positioning / offerings rather than full lack of a need.
Some things I think you're doing really well:
* Great sales copy and documentation
* Great aesthetics -> adds to "trust"
* Message bot for feedback
Qs:
* Q1: Did you do any customer research to help determine what features to build?
* Q2: What did you find (if anything) is the biggest reason people choose to use boilerplate rather than rolling their own?
For those interested -> CloudSeeed - SaaS boilerplate for Sveltekit + .NET + Postgres - https://cloudseed.xyz/
Agree that the types accomplish basically exactly what I want.
If it gets a decent community / ecosystem I think it would be a frontrunner for sure, especially for web apps.
One potential issue is that the runtimes it targets are not that great at processing - they fanout well on BEAM but may not be the best for heavy processing. Not a deal breaker but smth that others like F#, OCaml, Rust can outperform in if the other attributes do well.