4 ms·
Without getting into a huge my language vs your language debate: I agree that this isn't the RIGHT attitude, but it's not about me learning Lua per say, it's a
by rbranson 16y ago
Without getting into a huge my language vs your language debate: I agree that this isn't the RIGHT attitude, but it's not about me learning Lua per say, it's a reality of writing code in the real world for real projects.
- KirinDave 16y ago> I agree that this isn't the RIGHT attitude, but it's not about me learning Lua per say, it's a reality of writing code in the real world for real projects. Lots of people write robust, real world code in languages they are only casually familiar with. That is how you learn a language well. The other reality you're facing here is your career. While it is gradually slowing, our field moves quickly. You need to be constantly studying and reading and learning to be any good at it at all. The reality is: grow and keep up or stop and be left behind. To me, a new language is an opportunity. “What insights do these people have?” “What new design patterns will I learn?” “What can I take from this to my daily coding jobs?” They excite me.
- rbranson 16y agoAgain, I agree with you on all points. I can't count on my hands the number of languages I've tried out and written a decent bit of code in, learning things along the way. However, that doesn't translate into "I should use this platform for a business-critical application."
- KirinDave 16y agoSeems strange to decide on node.js if that's the problem. Node.js is by far less proven than Lua.
- silentbicycle 16y agoNo kidding. Lua has been used in production in industry for over 15 years. http://www.lua.org/history.html http://www.lua.org/history.html