|
nite time dinosaur posted:There's 3 languages I use at work (primarily anyway): Java, JavaScript, and Scala. Scala is probably my favorite. The worst case scenario with Scala code, in my experience, coming from a more imperative Java background, is that I am essentially writing succinct Java programs with more immutable references, as typing "val foo" is much easier than typing "final Foo foo." The best case scenario is, a more functional style is adopted and code is easier to reason about and there is usually less chance of a weird bug and overall debugging time is less - assuming you or whoever else is proficient at reading the syntax and has some experience with and is anticipating referentially transparent (read: no side effects) methods. I will admit that the first time you see a nested map/for-comprehension with a pattern match wrapped in a Future, it's a little but eventually you get used to it and find that a lot of problems are much easier to solve when you think of them in terms of streams. I was actually looking at that course (https://www.coursera.org/course/progfun) and I am definitely going to be taking that on as a side project. It was probably difficult because the professor is the creator of Scala. Cryolite posted:I'm learning Scala coming from C# and this is exactly the type of stuff I'd like to eventually be doing too, bonus points if it's in Scala. Is your company by any chance in the Baltimore/DC area? can't pm you and you have no way to contact you in your profile.
|
# ¿ Feb 4, 2015 00:18 |
|
|
# ¿ May 13, 2024 06:11 |