3 ms·
That is always a risk if a team decides to pick up a new language but does not make the effort to learn the language properly. At work we are going through a si
by Insanity 7y ago
That is always a risk if a team decides to pick up a new language but does not make the effort to learn the language properly. At work we are going through a similar Java - Go transition, so I know :(
- noir_lord 7y agoIt's always a problem when people shoe-horn a non-idiomatic approach from one language into another. It makes me wish the language creators wrote a single none-trivial 'this is how we intended it to look' project. When learning a new language I find as many big projects written in it as I can and spend time exploring them. It helps but there is often no guarantee those projects are doing it idiomatically either.
- chubot 7y agoLooking through the Python standard library or Go standard library should be a clue not to use Java idioms, but yes I realize those habits are hard to break. I have seen Java-in-Python and it is indeed painful.
- noir_lord 7y agoThe problem with reading framework and library code is that it's very coupled to what it is, so while it's interesting and valuable to read it's not really the type of code you'd see in a business app or whatever.
- JamesBarney 7y agoYeah I've tried this several times and the code written for the std library is so different from LoB code(because the domains are so different) that you can only learn a small % of possible idioms from them.