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!
2. Essentially yes, Stelvio is wrapper around Pulumi, using it mainly for state management and as an escape hatch in cases you might need something not supported.
3. Yes we do, there's `CloudFrontDistribution` component but it's not documented as idiomatic way is to use `Router` [1] & `S3StatitWebsite`[1] components and `custom_domains` [3].
4. Currently only v1. v2 (http) and websockets on the roadmap
5. Yes when you link resources we provide default permissions but these can be fully modified https://stelvio.dev/concepts/linking/#customizing-links
If you want to link existing dynamo table that is NOT created with stelvio and link it to lambda that's currently not supported, meaning you'll not get automated permissions. Although it would be possible so we might support this use case if there's interest.
Thank you for good questions. If you have any more questions/feedback or need help hit us email at team@stelvio.dev Happy to talk.
Even if he does, how kind will it take him to add new functionality? For instance AWS both announced durable lambda functions and CFT support the same day
I just checked, pulumi does have a good track record of keeping up with AWS. But using a non industry standard framework (Stevio) just doesn’t make any sense from a long term portable career perspective.
While I’m not a fanatic about which one I use out of the major ones. My last three projects were CDK/Typescript, Terraform and CloudFormation with my own collection of utility scripts I’ve used over 5 years to make it act more like TF. But the CFTs are standard.
True, I have written my share of CloudFormation custom resources.
Funny anecdote: it was faster for an SA when i was at AWS to create a Terraform module and have it merged into Terraform than it was for us to wait for AWS to add support for the same resource in CloudFormation. They are getting much better now
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.
Adding that this just gets worse when databases are peppered with direct access by vibe-coded applications that don’t look at production data or gather these insights before deciding “yeah this sounds like the format of text that should go in the column with this name, and that’s the column I should use.”
And now there’s an example in the codebase of what not to do, and other AI sessions will see it, and follow that pattern blindly, and… well, we all know where this goes.
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!
It’s also possible to work on projects, or in languages, or on systems where resource consumption isn’t a high concern. I wrote cobol for sun and hpux and these big old systems had plenty to go around. Important software comes in all shapes and sizes, as do their developers.
I think there's a gap between an inspector turning in a report and the repairs being prioritized, funded, and executed. Out here in Oregon we had a tunnel collapse and kill the inspector (this was back in 1999). News reported that the tunnel was inspected twice the year before it collapsed.
I have to disagree as you have no evidence to support your position.
Based on the information provided, it seems highly unlikely to me that a guy who passed up an easy payday for a baseball would get an attorney friend to lie for what is likely going to be a very small claim. He still attended the game, and another game a couple days later, which likely rules out substantial suffering. So, given the low potential payout what would be his motivation? Simplest explanation is the guy just fell through an ill-maintained bridge. Could happen to anyone, really!
This confused me for a while, having two separate "products" which are sold differently, but can be used by the same tool.