Hacker Newsnew | past | comments | ask | show | jobs | submit | moox's commentslogin

This is great. It will definitely make it a lot harder for them to defend copyright issues in court.


Probably caused by someone that was trying to find an SQL injection. It's not really that big of a deal, it's a pretty big edge case to filter out non-relevant searches.


Although this makes practical sense, maybe OP is more motivated to work for companies that make society better versus large corporations that pay a lot.


To me a startup isn't about the money, but introducing my idea to the world. The idea of satisfying a need is enough.

That being said, the money is still a great incentive since you're taking a huge financial and personal risk, but you can still live pretty damn well with $500k/year.


I would say both. Browsers are a mix of a client facing UI and business logic.


I browsed some of his commits and there's a lot of aesthetics and refactoring. Without him the scala project might quickly become hard to maintain.


I'm taking Coursera's Introduction to Functional Programming with Scala and Machine Learning classes and Udacity's Intro to Parallel Programming class. All out of interest.

I really recommend Machine Learning, this is my second time taking it (taking as a refresh). It really gives a good introduction on how to predict or classify data.

If you want something more practical, Introduction to Functional Programming with Scala is really informative, teaches you Scala and gives you another perspective on how to make functions and classes. It's definitely a great course for recursion lovers.


Your folks were wrong. They lock on the collection and only on some types of queries.


No, they lock the entire database for every write.

"MongoDB uses a readers-writer [1] lock that allows concurrent reads access to a database but gives exclusive access to a single write operation."

"Beginning with version 2.2, MongoDB implements locks on a per-database basis for most read and write operations. Some global operations, typically short lived operations involving multiple databases, still require a global “instance” wide lock. Before 2.2, there is only one “global” lock per mongod instance."

source: http://docs.mongodb.org/manual/faq/concurrency/


Yes that's the part that just kills me. It was a system-wide lock, and now it's just per-DB. I just don't see how anyone can take that seriously.

Also, why bother with a buffer pool manager when you've got mmap, right?


If you're having issues with scaling and performance, you're most likely using MongoDB the wrong way or for the wrong reasons.


Begging the question. If this is true anyone having trouble with mongo for legit reasons can be labelled as "using it for the wrong reasons."


He could also be using it the wrong way. Although MongoDB has faults, most of them are well known and developers are warned. MongoDB is far from being perfect, but the most common reason people hate on MongoDB is because they did things the wrong way or for the wrong reasons.


Aka "no true Scotsman" fallacy


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: