At the same time, you can break your JSON into relational tables so you can also operate on it in traditional ways.
79 karma · joined July 26, 2011
At the same time, you can break your JSON into relational tables so you can also operate on it in traditional ways.
"According to a recent report from Pacific Crest Securities, a Portland, Oregon-based investment bank, orders for components used in Amazon's standard e-readers have fallen 75% from the bank's previous expectations."
It seems like the problem is that you're not using MongoDB in a sharded setup to begin with. For good or bad, MongoDB targets the scale where you need sharded and replicated setups. In other words, a large enough operation to require multiple servers for data storage. If you need the opposite of that, which is multitenancy, MongoDB is not going to be a good fit.
On the other hand, MongoDB has always been sold as a rapid prototyping and easy to iterate datastore, which is attractive for people working on small projects. Then they have an "oh shit" moment when they run into operational issues.
So take that for what its worth. Don't be surprised if Google ends up allowing carriers and manufacturers to provide more customization with Nexus phones and be more lax with update timelines.
You can be honest, correct and still turn people off.
http://blog.joda.org/2011/11/scala-ejb-2-feedback.html?showC...
I don't question the intent of the Scala community. There's no mystic group of evildoers there trying to degrade newcomers. But the mailing list is very intimidating. It doesn't feel like a place where newbies can come in and ask "How do I do a 'foreach' loop?".
This is unfair. If I create a framework cal Java.js and make it possible to create a httpserver by running server.start(8080, aCallbackObject), does that make Java great? One day someone might make node.js "configurable" via a configuration file (that is not written in JavaScript). Will having a configuration file make node.js less useful?
> Note also that the http snippet from earlier isn't inheriting from an http.Server base class or anything of the sort.
That is also unfair. You typically don't use inheritance in JavaScript because you can compose objects or clone from a prototype. There is no static analysis of classes, which in the main benefit of classical inheritance. Programming via callbacks is simply the JavaScript style. This might even change when the language provides better support for classes, or when more people write their node.js code using CoffeeScript.
> If software ecosystems are like economies then core libraries are at best government bureaucracies and at worst nationalized state corporations.
This is very subjective and I strongly disagree. There is a great advantage in using a language and framework that has a strong core library and a common way of doing thing, especially when you start building teams or start recruiting people to maintain legacy code. If anything, Node should start including more batteries, such as a module for concurrency.
PS - Here's the thing. I am really excited about the event driven nature of node.js and the community. However, I am new to node.js and I want to see quality critical analysis of its strength and weaknesses. If you are going to tell me its great, you better have pretty solid reasons. This article simply doesn't cut it.
As a hobbyist programmer, my advice is that you should not limit yourself to one language. If you are a Java guy, you can still learn a very different language like Python, Lisp, or CoffeeScript. I believe that once you feel competent with a few different languages, you will begin to see through the language war BS and understand the roles of Java in the world.
public View getDropDownView (int position, View convertView, ViewGroup parent)
convertView - the old view to reuse, if possible. Note: You should check that this view is non-null and of an appropriate type before using. If it is not possible to convert this view to display the correct data, this method can create a new view.
The presence of the unintuitive 'convertView' object is caused by the underlying VM and the unpredictable GC nature. This demonstrates that implementation complexity can lead to a complex interface.
IMO the design of the interface is an implementation. A language that is complex to implement will lead to complex interfaces.
That is not to say that Android has no virtues of its own. I prefer Android for more than just brand identification.
Take a look at the APIs of some of the libraries you are likely to use, before you get scared off by how complex the syntax can potentially be.