tholm

Interesting looking at the data, the questions always seemed to peek in March. Anyone have insight into that?

Because sounding skeptical and "clever" is more important to some people than providing meaningful and relevant insight into the topic at hand.

Using an LLM for this seems excessive when there are well established algorithms for detecting high entropy strings.

Great list! For me it kind of highlights how saturated this space is.

That's awesome to hear! I'm really excited to see the framework ecosystem grow.

Having worked heavily with gRPC before I like how syntactically similar WIT is to proto. Looks like its time to start experimenting more with web assembly component interop :).

Frameworks recent dig at "upgradeable" storage in the new m4 mac mini made me chuckle, upcycling an old macbook shell is even better.

Very fun to play with, Nice UI as well. Well done!

Worth noting that most of the terraform documentation for classic pulumi providers (providers build on top of TF providers) is still relevant to Pulumi.

Thanks for that, there is no pricing as it's a FOSS framework not a platform. But I get where this is coming from. Nitric currently makes money working with enterprises on cloud solutions using the framework. We do accept sponsors on github maybe that's something we could include as a pricing page?

The framework is backend focused and there is OIDC configuration you can include for authenticating requests to the backend https://nitric.io/docs/apis?lang=python#api-security but nothing at the moment for frontend auth (but always looking for new feature ideas).

I think your point on testimonials is good, the goal is trying to build trust in what we've built using feedback from our community, is there an alternative that you've seen or like better?

Avoiding vendor lock-in was the initial goal of the framework. But we've found that most of our existing user base are actually focused on a single cloud only but find developing with infrastructure from code makes their development experience much smoother, but they still get the benefit of portability from using the framework.

Given the scope of it's potential I'd even say the current state is embryonic.

Many of the problems stated might also be opportunities for innovation and disruption.

General advice though for any startup without getting into the specifics of any industry is to build an audience first if you can. You'll have a major head start on traction if you do, this can take a few forms but presenting yourself as a thought leader in the space you're looking to create a startup in is the best way, this could be via a newsletter, blog, podcast or general social media presence.

You can then use that platform to interact with your audience to find problems and ideas that resonate with them, and look at forming a startup and product ideas around that.

Thanks for that, will look at posting a Show HN for this.

Looking for some fresh eyes to take a look at this guide, its the first part of a series for building an AI Podcast using a framework that I author.

The more I've used Golang over the past few years the more I've come to appreciate the simplicity of its design and its lack of syntactic sugar.

It's made me realise that much of the sugar I was writing in other languages didn't make me more productive or my code more readable, in many cases it was actually the opposite and the usage of that sugar was more about writing more "succinct" code that was in the long run harder to understand and maintain.

Can you elaborate? I think that would be helpful for others seeing this and I can get the article updated based on your feedback.

Thanks so much for taking the time to write such detailed feedback. This is really useful and exactly the perspective I was hoping someone would look at it from :)

Recently relaunched the landing page for an OSS project that I work on, and am looking for feedback and first impressions.

Trying to fix issues we've had where the purpose of the project is misinterpreted, and trying to see if there are any gaps that can be addressed etc.

Thanks in advance for any feedback/comments :)

The article isn't discussing replacing Terraform or suggesting Terraform isn't for developers. It's stating that Nitric brings the ability to create executable documentation for Applications, the same way that Terraform does for Infrastructure provisioning.

Interesting take, what would be the benefit here? If the application code writes to a resource and you change the permissions externally without updating the code you've essentially broken the application.

It's very similar to encore, with the exception that the deployment engines are fully open source and extensible.

https://github.com/nitrictech/nitric

Not quite, actually more like Pulumi's old cloud framework https://www.pulumi.com/docs/clouds/aws/cloudfx/

Resources are documented using abstract cloud concepts in code, and then provisioned by a deployment engine. The nitric deployment engines are actually build on IaC such as Pulumi/CDKTF.

Just wanted to take the time to appreciate this comment. It is a rare thing when someone takes the time to read beyond the headline, and decide to dig deeper to understand something. Thank you.