seglo

6 ms·

1.
by seglo 13y ago
I think one of the biggest learning hurdles when coming from Java is getting used to using the functional collection types. I remember when C# first introduced linq-to-objects my reactions went from disgust, to fear, to total and utter acc
2.
by seglo 13y ago
We weren't looking at FP languages specifically. We also were leaning toward something that could be run on Linux.
3.
by seglo 13y ago
There wasn't really a vote, but we did have a group forum where objections could be raised. People who weren't onboard with Scala were in the minority and most of the arguments raised didn't hold much water.
4.
by seglo 13y ago
We had two teams in separate physical locations. We worked together occasionally, but most of the time projects were fully staffed at one location or the other. The Scala change was fully supported at one of the office and not the other.
5.
by seglo 13y ago
The process change was top down, yes, I think that's the only way it could have succeeded IMO. However, the Scala change was bottom up and by developers. The Mindshare acquisition is a recent event that postdates our technology change
6.
by seglo 13y ago
That's incorrect. The technology change was bottom-up, by developers. Simon didn't intervene with his technical direction until we already had a couple of Scala projects under our belts.
7.
by seglo 13y ago
Definitely a nugget of Java humour worth preserving and sharing. Glad you liked the post :)
8.
by seglo 13y ago
I'm sorry you interpreted it that way. It wasn't a disaster and internally the general consensus was that it was a great success. I've made some amendments to my post to provide some more context to our initial process chan
9.
by seglo 13y ago
I'm sorry this is how the article came across to you. Given similar sentiments from others on this thread I'll see if I can amend it to make it more clear. When our CTO came onboard I meant to say that he gave a hard look at our
10.
by seglo 13y ago
I'm glad you enjoyed the post, thanks. In the beginning there wasn't an initiative to migrate away from .NET. Management encouraged us to try new technologies all time and the BeetleJuice spike seemed to me like a good opportunit
11.
by seglo 13y ago
I've often said the same thing to .NET advocates at Empathica. In terms of language constructs, C# is closer to Scala than Java is to Scala. However, IMHO Scala still offers more than both combined. :)
12.
by seglo 13y ago
Scala can work great in a large development team. Your sentiments about poor readability and maintenance have little to do with the technology itself; you could say this about any programming language. People new to a technology have a ten
13.
by seglo 13y ago
LINQ is a fantastic DSL akin to Scala's collection types. Odersky gives C# the nod as one of the few other traditionally imperative languages to have such a rich way of transforming data in his Functional Programming with Scala course
14.
by seglo 13y ago
Java to Scala is definitely an easier and more natural transition to make. I agree 100% with your sentiments.
15.
by seglo 13y ago
OP here. Thanks for your feedback. The Technical Strategy email was sent out about midway through our adoption of Scala. I didn't explain the dynamics of our larger development department much in my post, but at that time we were ess
16.
Questions and Comments about cull.io
2 points by seglo 14y ago|1 comments