Cake Solutions Blog

Pattern Matching, Destructing, and ADTs are amazing. Inference is much better and not just for local variables. for comprehension is the equivalent of LINQ syntax which is nice, very powerful when working with asynchronous calls. Higher Kinded Types combined with implicit parameters are the two aces in the hole that make it an asbolute definitive win when heads up against C#. When I had to switch back to C# in my last job (some projects were scala, some C#) this was what I missed the omst. Combining the two gives you the 'type class pattern', which is pretty much the first time i've actually seen composition and code sharing just work without the cruft of an 'OO' like framework. http://www.cakesolutions.net/teamblogs/demystifying-implicits-and-type…

You can load balance your app for 3.5k $ on additional server. By reducing load, time spend in GC will be less. Additionality by having more hardware you can use more aggressive strategy[0]. [0]http://www.cakesolutions.net/teamblogs/low-pause-gc-on-the-jvm

Oh, cool! I've seen examples of the Reader monad in Scala, but we use the Cake pattern for dependency injection (self types and multiple inheritance) http://www.cakesolutions.net/teamblogs/2011/12/19/cake-pattern-in-dept…

Cake Solutions - A BAMTECH Media Company | Manchester (Visa, Onsite)| London (Visa, onsite) | New York (Remote avail) Senior Scala Developers | (Senior) DevOps | SRE Lead Until last year (2017) Cake had operated as a Scala Consultancy, helping businesses globally build Reactive, Distributed and Resilient Systems using our hybrid Agile method of small cross functional teams. We're big advocates of the tech community, and have been blogging, hosting meetups and presenting/sponsoring conferences for 5 years. We were acquired last year by BAMTECH Media, and are now building the next-gen DTC media streaming platforms for partners like ESPN+, Disney, Riot Games, and EuroSport, as well as migrating existing partners (MLB, NHL, MLS, WWE, HBO) to our new multi-tenant platform. Most of our current roles are at the Senior level (Scala, DevOps, SRE) so we would like engineers who have experience with functional programming (futures, category theory), DevOps who have experience with micro-service architecture (Docker, Jenkins, AWS). https://www.cakesolutions.net/careers Any questions to me [email protected]

"This is a really useful distinction to draw (in many ways it's more important than when the two types support different methods, because it's easier to get the two confused), and as far as I can see would be completely impossible in Go." Per jbooth, it literally couldn't be easier (three characters shorter than Haskell even!), and I'm also not sure what this has to do with what I said, since I was talking about accidentally implementing interfaces and you're talking about deriving new types that you then do not add any methods to. "Implementing the same kind of injection by multiply-inheriting in a traditional OO language isn't as crazy as that article seems to think - in fact, it's exactly how the cake pattern works in Scala." First, it's my article. Second, based on my admittedly quick reading of http://www.cakesolutions.net/teamblogs/2011/12/19/cake-pattern-in-dept… it looks an awful lot like Scala is doing the same thing Go is here, declaring a set of interfaces (called "traits" in this case) that one thing implements, not actually multiply inheriting. "Multiple inheritance" is a particular thing, not a vague word salad phrase. "Again, I really think this is just culture. If you write Java the way you write Go - ignore the JavaBean conventions, don't abstract things that don't need to be abstracted - you end up with very similar code." I'm really not convinced. Given the large number of distinct Java cultures that have arisen, surely at least one of them would…