This looks pretty cool! What was the hardest part about building this?

hey, thanks!

I guess there were a couple of things that I found as tricky:

- deciding on the right way to represent sources and destinations was hard, before landing on URIs I thought of using config files but that'd also add additional complexity etc

- the platforms had different quirks concerning different data types

- dlt stores state on its own, which means that re-runs are not running from scratch after changing the incremental strategy, and they require a full refresh, it took me quite some time to figure out how exactly to work with it

I think among these the hardest part was to get myself to build and release it, because I had it in my mind for a long time and it took me a _long while_ to build and share it :)

wow, that sounds like a lot! Is that your full-time job?

Thanks for this! I also like Pointer, although they have more and more sponsored stuff lately imo. Terminal trove sounds great, I like terminals a lot (who doesn't)

I feel you. Can you mention these exceptions - that's exactly what I'm interested in.

There's a few newsletters from government funding/innovation agencies and research groups that are worthwhile for me.

Plus the very lightweight one that my group puts out (of course!) as liaison between our local authority and local environmental groups... B^>

I see a Haskell project, I upvote.

Wasp team reporting to duty: https://github.com/wasp-lang/wasp

Open SaaS is still very new, but there are a couple that used the "old" version of it, which basically gave us an idea for Open SaaS. For example:

- CoverLetterGPT (https://coverlettergpt.xyz/) - generate a cover letter based on your CV and job description

- Etsy description generator (this one even got acquired): https://dev.to/wasp/from-idea-to-exit-building-and-selling-a...

No, both Open SaaS and Wasp are free and open-source, like most of the frameworks. If we manage to get the community adoption for Wasp, the next step would be to look into value-add services on top of it that can be monetized (our role models are companies like Mongo, Terraform or Databricks).

Thanks for sharing, Business Class looks really cool! As I mentioned in other comments, I think the situation in JS is similar to other technologies - there are a lot of oss boilerplates, but most of them don't offer the same level of polish and features as the paid alternatives. Also, a good portion of them is outdated or not actively maintained.

And that's exactly what we are going for, just with an open-source, community-driven approach.

I can imagine you had the same motivation when you created your boilerplate starter (not the oss/community thing, but above)?

That's an interesting point! What do you think would be a point when one would need to switch to Postgres?