Earlier quoted context omitted.
How do you figure?
I believe the insinuation is that if you're actually building a serious app that might actually benefit from NoSQL, then you should host it on a serious machine and not some shared hosting solution. Basically conflating the idea that NoSQL is for 'real projects' and that only 'amateur hour' hosts have no compiler.
CodernityDB — pure Python, NoSQL, fast database
41–50 of 52 posts
Re: CodernityDB — pure Python, NoSQL, fast database
#42The only thing that turns me off to a product more than a poor website is poor English in the documentation. If English isn't your primary language, PLEASE get someone that speaks it fluently to either write your docs, translate your docs, or edit what you've written.
pretty rude. why don't you offer to help?
Of course, if we won't help with problem in an open source project, we shouldn't feel entitled to a fix either.
Re: CodernityDB — pure Python, NoSQL, fast database
#43"CodernityDB pure python, NoSQL, fast database" Is the fact that it is written in "pure Python" really the most important thing to reenforce after the name of the product itself? Why would I use this over established products like Riak, Redis, MongoDB, etc?
Although pure python seems great for some apps, for a piece of software I'd like to be highly optimized, it seems to hit the wrong sweet spot -- it means a larger memory footprint and less robust multi-threading than other pure language implementations. When things need to work fast and tight in python, most implementations duck down to C, like numpy and scipy. Or maybe I've been out of touch with improvements to CPy…
Re: CodernityDB — pure Python, NoSQL, fast database
#44Re: CodernityDB — pure Python, NoSQL, fast database
#45Earlier quoted context omitted.
I believe the insinuation is that if you're actually building a serious app that might actually benefit from NoSQL, then you should host it on a serious machine and not some shared hosting solution. Basically conflating the idea that NoSQL is for 'real projects' and that only 'amateur hour' hosts have no compiler.
NoSQL is targeted at extreme performance. So, yes, it sounds like a reasonable assumption.
Re: CodernityDB — pure Python, NoSQL, fast database
#46Re: CodernityDB — pure Python, NoSQL, fast database
#47Re: CodernityDB — pure Python, NoSQL, fast database
#48Earlier quoted context omitted.
> Is the fact that it is written in "pure Python" really the most important thing to reenforce after the name of the product itself? It's definitely a selling point for Python programmers, because it's so easy to use with your Python projects. You just set the package requirement and you're done, it will work in the same environment wherever your app works, upgrades are a piece of cake, no need to worry about platfor…
The thing I like most in python is not python itself but a "pythonic way". "Pythonic" > Python. In my opinion, it's not "pythonic" to use DBMS, just because it written in python. So the "selling point" is flawed. Disclosure: I'm using python since 2006. I've made a lot of evangelizing it. It is my weapon of choice for many tasks. And I will never use python for many other tasks. (Don't tell me about PyPy or Stackless…
I get your point and I'm all in for being language-agnostic when it comes to the tools I have to use, but that doesn't change the fact that convenience plays a role when you are in a point where you can't affort a long-term decision process. the best technology to quickly launch something is most often simply the one you know.
Re: CodernityDB — pure Python, NoSQL, fast database
#49http://labs.codernity.com/codernitydb/design.html#how-it-s-b...
Re: CodernityDB — pure Python, NoSQL, fast database
#50A cursory glance through the code revealed a bug: https://bitbucket.org/codernity/codernitydb/issue/1/_rev-not...
You can learn a lot about a community, a product, and a company based on how they respond to bug reports. Promptness, formality, details and politeness are all incredible indicators about what's going on under the hood.