Things have changed quite a bit in the past 30 years!
I encourage you to peek at their changelog (https://www.sudo.ws/releases/changelog/) for more insight into why this project is still under active development.
Interesting product! Not sure if I'm getting this right, docs seem pretty sparse so please forgive me. Here are a couple questions:
1. Do you support tagging resources?
2. You mention provisioning Pulumi resources, are you "simply" a wrapper around Pulumi? If so, are you relying on Pulumi for state management or does Stelvio have it's own state manager?
3. Do you support cloudfront? Imo this is a vital service for building even small production apps, esp if you are serving static assets out of S3.
4. I saw references to API Gateway v1, do you also support v2?
5. One of the cool features is that you're able to handle all the IAM stuff, but can that also be easily modified? Like, if I want to create a new lambda that interacts with an existing dynamodb table, how would I describe that with Stelvio?
Sorry for the pile of questions lol but you got my attention :) You have a lot of competition in this space and I'm curious to see how your project will evolve. Best of luck!
Exploring a codebase tells you WHAT it's doing, but not WHY. In older codebases you'll often find weird sections of code that solved a problem that may or may not still exist. Like maybe there was an import process that always left three carriage returns at the end of each record, so now you got some funky "lets remove up to three carriage returns" function that probably isn't needed. But are you 100% sure it's not needed?
Same story with data models, let's say you have the same data (customer contact details) in slightly different formats in 5 different data models. Which one is correct? Why are the others different?
Ultimately someone has to solve this mystery and that often means pulling people together from different parts of the business, so they can eventually reach consensus on how to move forward.
Mikeal was instrumental in helping me get established in the node community when it was super tiny. Being around him was a joy! He made those around him feel part of something special. He made me feel like I belonged.
I was a camp counselor at node camp three years in a row. He created such a magical experience that I cried when I got home, I wanted to live in nodecamp forever. I still do.
Seeing some of the folks posting in here makes it hurt worse. I have so many memories, like I remember all of us riding the bus back and forth to the camp, so much laughter and fucking around. Hanging at each others houses, going to meetups, and just being part of something special. Talking shit thru pull requests. Late night dorking around on meatspac.es etc etc etc I could go on for days.
Ex-cobol guy here, the work was a blast! I was working on the Lawson erp for a non-profit, mostly customizing the software for their specific use case. I loved it because the tools were crazy, the language limited, and the system itself was high value to the org. Debugging took forever but the fixes were often really small changes. I often had to go into the database (oracle) and clean up the data by hand. Such fun!
I crave novelty and have a love for bad technology. I was an early nodejs adopter and loved es4 but newer versions of the language is too easy to use lol!
This confused me for a while, having two separate "products" which are sold differently, but can be used by the same tool.