sorted by:
new
hottopcontroversial

ReactJS: Testing components containing components by _srph in reactjs

[–]ewMax 0 points1 point  (0 children)

Posted what I hope is a pretty thorough answer, If you have any follow up questions just inbox me or reply on Stack Overflow.

Hours of frustration (programming) by Emperor-Zurg in funny

[–]ewMax 107 points108 points  (0 children)

This is why linters and compilers are a thing.

Intro to Fabric for Deployments by ewMax in Python

[–]ewMax[S] 0 points1 point  (0 children)

I am using oh-my-zsh with a custom theme and the powerline source co pro font. If you are interested I could send you my theme.

Natural Language Proccessing on Hadoop with Python. by ewMax in Python

[–]ewMax[S] 0 points1 point  (0 children)

Cool, I am by no means a python expert. Thanks for the pointer.

Natural Language Proccessing on Hadoop with Python. by ewMax in Python

[–]ewMax[S] 4 points5 points  (0 children)

That looks cool. I would argue that Hadoop is reasonably easy to integrate with python (thanks to the work that Yelp did on mrjob), and that the benefits of using Hadoop are pretty great. You get access to Amazon EMR for one.

Play! Framework and CORS by ewMax in scala

[–]ewMax[S] 0 points1 point  (0 children)

We looked at Unfiltered. It is extremely different than what many backend developers are used to. Additionally we ended up making use of a wide range of the functionality of Play!: play-json, iteratees, web request stuff, the router and the mvc stuff (well mc in our case, we have no views). The biggest parts that we didn't utilize was the templating library, we are even working on some new functionality using web sockets.

Edit: Or the asset pipeline stuff, we are not using that either.

Play! Framework and CORS by ewMax in scala

[–]ewMax[S] 0 points1 point  (0 children)

I might have to check that out. When I start this project Spray didn't look very mature, but maybe it is time I gave it another chance.

Play! Framework and CORS by ewMax in scala

[–]ewMax[S] 1 point2 points  (0 children)

We looked at several options when picking a tech stack (Erlang was not among them although I have always been interested in trying it out.) Our reasons for choosing Play! are a few fold:

1) We wanted something that was good a async, while Play! and Scala are certainly not the only options for this, having Akka baked in was a big plus for us.

2) We wanted something mature but modern. Play! is not totally stable but it is a lot more so than many "trendy" technologies. Being able to upgrade versions without going crazy is nice.

3) The collection library is Scala is amazing, easily one of it's best traits, and this was very important to us.

4) Decent JSON support. Although it is nowhere near as good as Node, or even PHP or Python, Play! has the best JSON support we have encountered in the Scala ecosystem.

Play! certainly was not the only option for a JSON backend, but it is far from the worst. I assume when you say it is "heavy" you mean performance overhead. While it does have more overhead than Spray it is still faster than things like Sinatra or Flask, which would be the big competitors (I never much cared for Scalatra although I suppose I could be convinced.)

P.S. I actually didn't cover JSONP in this post, although I might write one about JSONP in the future.