Conventional wisdom: “It’s a toy! Fine for internal tools, but you couldn’t possibly write real production code that way.” In 1998, they said that about Java. In 2006, they said it about Rails. What are they saying that about today?
-
Show this thread
-
Non-rhetorical question
It was briefly node, but not anymore, given the large amount of BigCo buyin of the node ecosystem.
So what is it?22 replies 3 retweets 30 likesShow this thread -
Replying to @sarahmei
I feel like we kinda past that. Tools like docker now allow developers to sneak whatever they want to production. Long history of opensource projects that became highly successful and widely used in production before hitting 1.0 (often being as low as 0.2) also helped.
1 reply 0 retweets 1 like -
Replying to @listochkin @sarahmei
I have another non-rhetorical question, for both of you: What does it say about software eng as a maturing field, that easy-to-learn "toy" tools quickly became mainstream deployment tools?
1 reply 0 retweets 0 likes
I don't know, really.
1. We have better tooling around monitoring and troubleshooting, and thus are more bold.
2. We have so many libraries! Our toys often stand on giants' shoulders.
3. We have better dev tools in general. It's hard to screw up when rust compiler yells at you 
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.