> your application and experience could be still even faster without compilation I doubt it. Compilation actually improves developer experience and speeds up t

> your application and experience could be still even faster without compilation I doubt it. Compilation actually improves developer experience and speeds up the process of releasing apps because you have a standardized way to release your app to production. I seriously can't understand the hate against compilation because it's never been a roadblock for me, especially these days when most builds take a few seconds on slow CPUs. I guess it's cool to hate things for no reason. > Frameworks also come at a substantial cost. They are highly restrictive, super massive, and almost always unnecessary. This is highly subjective. Frameworks have been nothing but a huge productivity boost for me. For example, I can spin up feature-complete API using FastAPI in a few hours instead of spending weeks building my own framework to do the same thing. > People tend to prefer frameworks when they lack the confidence to build without them Doubt it. People mostly choose frameworks because they want to get work done instead of wasting their employer's money on non-profitable endeavours. > for those of us that frequently measure things large frameworks are always a net negative Could be that you're measuring the wrong thing. At the end of the day, engineers need to ship features so that the company can generate revenue. Frameworks are great at facilitating that process. I'm no Math expert but this seems like a net positive to me.