empirewindrush

4 ms·

1. 1.▲
   by empirewindrush 12y ago

   Hey now, Cortana is a really cool use of a property they had access to. One of the perks of being a huge, diverse (in the product / market sense) company.
2. 2.▲
   by empirewindrush 12y ago

   You are right. I jumped on it without giving the author the benefit of the doubt. This is one of those things that I personally have been burned by, and I wanted to save other from falling victim to the same mistake.
3. 3.▲
   by empirewindrush 12y ago

   The issue is that this: val future1 = asyncService1() val future2 = asyncService2() val future3 = asyncService3() val future4 = asyncService4() val resultFuture:Future = for { //For-comprehension r1 <- future1
4. 4.▲
   by empirewindrush 12y ago

   Cool. Like I mentioned this is still better than the before case. This is a super confusing area of Futures for most people, especially the newer Scala users. I got burnt a couple of times by this. It might not be obvious how creating the f
5. 5.▲
   by empirewindrush 12y ago

   This is wrong. Well not wrong but it doesn't work the way it seems the author thinks it does. For comprehensions de-sugar in a way that isn't really great. See the first answer here. http://stackoverflow.com/questi
6. 6.▲
   Natural Language Proccessing on Hadoop with Python(empirewindrush.com)

   1 points by empirewindrush 13y ago|0 comments
7. 7.▲
   The Play Framework and CORS(empirewindrush.com)

   3 points by empirewindrush 13y ago|0 comments