ajakhu

5 ms·

1. 1.▲
   by ajakhu 14y ago

   This is a nice addition. Thumbs up to this.
2. 2.▲
   by ajakhu 14y ago

   1) A NoSQL database best suited our project. So, the non-nativeness was a hurdle. Neo4j bindings for Python used JPype, which was rather unmaintained. And I read at some places that it was a bad idea to mix python-java (especially using the
3. 3.▲
   by ajakhu 14y ago

   Neo4j.
4. 4.▲
   Ask HN: I have an idea, how do I find team-mate(s) online?

   5 points by ajakhu 14y ago|5 comments
5. 5.▲
   by ajakhu 14y ago

   The API problem will still exist even if we switch to PyPy or Cython.
6. 6.▲
   by ajakhu 14y ago

   No, we didn't have any experience with Scala/Lift/Play. We were aware of the learning curve of scala. But what we thought was in the the best interest of project. I've read about the problems ingoing with Scala, but the benefits outweigh th
7. 7.▲
   by ajakhu 14y ago

   We had integrated redis in our project for server side caching. And I'd like to clarify that Python was being slow for regular cases (atleast not as fast as we wanted it to be). As we were newbies to web development (although we have a lot
8. 8.▲
   by ajakhu 14y ago

   Yes, we were planning for Scala/Lift only.
9. 9.▲
   by ajakhu 14y ago

   No, there isn't a C API for the DB. So, that put C out of the picture for us.
10. 10.▲
    Ask HN: Python vs Scala for a fast web-project

    9 points by ajakhu 14y ago|14 comments
11. 11.▲
    Find an integer not among four billion given ones(stackoverflow.com)

    9 points by ajakhu 14y ago|0 comments