4 ms·
This is akin to my pet peeve dev team blog post: We had to scale our $STANDARD_LANG application. Turns out it wasn’t fun. But you know what is fun? Writing ti
by awb 5y ago
This is akin to my pet peeve dev team blog post:
We had to scale our $STANDARD_LANG application. Turns out it wasn’t fun.
But you know what is fun? Writing tiny, non-essential MVPs in $SHINY_LANG. We haven’t tried scaling our $SHINY_LANG apps yet or deploying to production, but we’re excited about the future and we’re enjoying coding again!
- raverbashing 5y agoIt's even "funnier" how then they try to take $SHINY_LANG to its extremes and expect it to work flawlessly. And they don't try to understand it or work around it. "No optimizing, only performance." I remember some people getting bit by some Go stuff early on. Things take time. It will get there when it gets there. Then they come to HN and create a "why $technology sucks" when they a) didn't read the manual b) didn't match their requirements with the capabilities of the lang c) had unreal expectations Don't buy the shiniest Tesla then use it as your building contractor car. Especially when you like to overload the rear axis and pretend that's just not an issue.