Explain how this achieves you stated goal of providing a seamless dev environment for all devs #264
Unanswered
sharpninja
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The choice of platform or programming language often boils down to return on investment over time. The over time part is where platforms like .Net or Java win out over C++, Rust, Python or JS. Their incredible breadth and depth of standardized resources greatly smooth the peaks and valleys of costs for hosting and labor over time. The README seems to infer that these platforms should reuse libraries from other platforms to prevent reinventing the wheel. That seems like a good plan for capital investment but absolutely terrible during the maintenance cycle where hosting and maintenance are an expense. Under this philosophy, if someone implements a new paradigm in Ruby, you would use Tea to glue the Ruby implementation into an Asp.Net service, which would result in a massively outsized portion of response time being devoted to the Ruby dependency. The only way to fix that is faster (more expensive) hosts, destroying ROI over time. Am I interpreting this incorrectly?
Beta Was this translation helpful? Give feedback.
All reactions