[poshmosh]

Every framework have worked on for the last 12 years has bugs, breaks in certain situations. Every system in fact, i have worked on in 12 years has bugs and breaks. That is just the nature of software development.

You should be using frameworks instead of trying to reinvent things. It takes away decision fatigue and makes it easier for most teams to follow conventions that are already established.

[madamelic]

Not advocating for inventing your own thing but no need to get complicated if the needed solution is simple.

These magic-included frameworks are great to work with until you deviate from their prescribed path or just run out of road where the maintainers haven't gotten to that. There's really no need for a magic-included Lambda framework that makes AWS SDK calls as decorators, you are just asking for lock-in when that framework gets abandoned or you need a feature from a downstream dependency they haven't gotten around to implementing yet. If you kept it simple, you could 'just' bump your AWS SDK version and be on latest.

If you pick frameworks that are generally low 'magic', you can build your own road and it can be integrated into the rest of the application tightly. If you did this in a magic-included, it will generally be bolted on and imminently fragile to even slight framework changes (because the maintainers don't know or care about your hack).

[isoprophlex]

Not to be that "hurr hurr durr everything was better in the past" guy but nothing beats a box somewhere that you scp your code onto with a little 10 line deploy script in terms of speed, maintainability, cost control and overall simplicity.

I long for the good old days of /cgi-bin

Can't get decision fatigue if there's no frameworks or cloud shits to decide on.