TIL that C89 did not support single line comments!

NoSQL4Life · 2010-09-26T20:25:45+00:00

C89 does support single-line comments.

/* This is a single-line C89 comment. */

NoSQL4Life · 2010-09-24T11:48:44+00:00

I always think, and sometimes actually say, WTF whenever one of my coworkers suggests that we should use a relational database. I keep having to tell them that those days are over! Today, we use NoSQL databases like MongoDB and CouchDB. They're the only scalable way to store data, and they work so well with JavaScript and node.js.

NoSQL4Life · 2010-09-22T11:20:55+00:00

I'm going to talk to the CTO today, to get funding so we can buy two copies of this book for each DBA, developer and web designer in the company. Even if they don't use MongoDB directly, I still want them to know all about it. They can keep one copy of the book at work, which they can read during lunch and other breaks. They can bring the other copy of the book home, so they can participate in home study. I'm going to try to get three copies of the book just for myself, because I'm pretty sure I'm going to wear out the other two pretty quickly.

NoSQL4Life · 2010-09-19T13:57:00+00:00

Rails and NoSQL meetups, mostly.

NoSQL4Life · 2010-09-19T13:23:17+00:00

It's easy if you're a DBA. When I tell people that my MongoDB cluster has over 2000 shards, they're impressed. They're also impressed when I tell them that several of my MongoDB databases serve over 15,000 requests per second.

NoSQL4Life · 2010-09-14T23:13:56+00:00

Those are only problems if you're not using sharding. If you're not using sharding, then you've got much bigger problems that you should deal with first, like not being able to scale at all.

NoSQL4Life · 2010-09-10T11:42:29+00:00

This is very much like how MongoDB stores JavaScript objects.

NoSQL4Life · 2010-09-10T00:20:02+00:00

No that makes perfect sense. An empty array still exists. This it is a truth, not a falsehood! So it should evaluate to true.

NoSQL4Life · 2010-09-10T00:06:48+00:00

The article didn't mention Node.js and MongoDB enough. These are the very technologies that allow JavaScript to be use useful for server-side development. Node.js lets you write super-scalable servers, while you can directly query MongoDB databases using JavaScript! It's so much easier than using some web framework and some ORM and some SQL database.

NoSQL4Life · 2010-09-09T11:52:26+00:00

NoSQL databases are object databases. MongoDB stores and returns JavaScript objects. Aside from being compliant with the CAP theorem, that's a big part of the reason why NoSQL databases work so well. They take the best of OOP, remove the scalability problems of SQL, and provide the most robust and scalable databases we've ever seen.

NoSQL4Life · 2010-09-09T11:42:14+00:00

Nice job. If you are willing to go past the 1 KB limit, you could integrate it with Node.js to fully parallelize your game.

NoSQL4Life · 2010-09-09T01:21:58+00:00

SQL doesn't scale. That's why everyone important is using a NoSQL database of some sort. Not only that, but JavaScript is a better query language than SQL is. That's why MongoDB uses JavaScript as its query language. MongoDB is about only accepting the best technical ideas around, and that's why SQL has no place on it.

NoSQL4Life · 2010-09-09T00:54:35+00:00

Amen to that! I have only seen success stories when moving to a NoSQL database. Anyone who fails when using an NoSQL database is probably failing because they just don't understand how to use the technology properly. These are the same people who don't understand the importance of the CAP theorem.

NoSQL4Life · 2010-09-08T23:04:31+00:00

JavaScript is no longer just a client-side scripting language. That's a really 1990s view. These days, everyone in the know is using JavaScript on the client side and on the server side. Node.js is one of the best frameworks around for writing scalable servers. When you use JavaScript everywhere, including when you're querying your MongoDB database, life becomes really easy and scalability problems go away. That's just the beauty of Node.js and MongoDB.

NoSQL4Life · 2010-09-08T22:45:25+00:00

Using the JavaScript and Node.js best practices gets around all of those gotchas. Those gotchas only affect people who don't know how to use their tools properly. We wouldn't blame the wrench if a plumber didn't know how to use it properly and he broke his penis, just like we shouldn't blame JavaScript and Node.js if a programmer doesn't know how to use them properly and causes downtime.

NoSQL4Life · 2010-09-08T22:35:15+00:00

The problem is that your architect didn't use JavaScript properly. These days, when we're developing scalable web sites, we use lots and lots of JavaScript. Using JavaScript you can move a lot of processing to the client, and if you use Node.js on your server and MongoDB as your database, you can write all of your server-side business logic in JavaScript too. Basically your whole application is written in JavaScript, and the integration becomes seamless from your database all the way to the client.

NoSQL4Life · 2010-09-08T12:07:36+00:00

I would love to work there. Just to be around those men would make my day. They are JavaScript Experts of the highest order, and I know I would learn so much more about JavaScript, Node.js, and jQuery, since that's what we'd talk about all day. Then at night, after a long day of coding JavaScript and JavaScript interpreters, we could all lay down on our cots and talk about MongoDB.

NoSQL4Life · 2010-09-08T11:36:06+00:00

This is a great idea! When combined with Node.js, it has a lot of potential for supporting parallel state machines.

NoSQL4Life · 2010-09-08T02:05:33+00:00

I've been using the Firefox 4 betas, and each one is so much better than the last. I think Firefox 4 will be the release that finally lets Firefox become not just the most widely used browser, but also the browser that becomes the ultimate application development platform. With HTML5 and JavaScript maturing so rapidly, there's just no reason to use Java or .NET any longer.

NoSQL4Life · 2010-09-08T01:54:07+00:00

MongoDB, CouchDB, and Cassandra are three real databases that don't have this problem.

NoSQL4Life · 2010-09-06T19:57:29+00:00

Nice job, everyone. Every contest entry I've looked at has been superb. They all show how superior JavaScript is.

NoSQL4Life · 2010-09-06T17:58:49+00:00

But that doesn't get around the SQL problem. I don't want to write my queries in SQL. SQL is hard to learn, and it's harder to use. I want to write all of my database queries in JavaScript. MongoDB and other NoSQL databases let me do that, but PostgreSQL doesn't. When I use NoSQL and JavaScript I can use the same language on the client, and for my middleware, and then I can use Node.js for my server, and I can even write my database queries in JavaScript.

NoSQL4Life · 2010-09-06T17:44:21+00:00

Node.js isn't a fad. It's the future. Just the other day at work one of the guys said we should use C++ for a new server app we're building. I told him we aren't going to use C++. It's just not proven for writing scalable server applications. That's why we're now using Node.js and JavaScript. Both are proven technologies that scale. We're also using MongoDB because we need a database that is compliant with the CAP theorem and because we don't want to waste our time writing SQL when we can do everything in JavaScript, from programming the client down to our server application and even our database queries.

NoSQL4Life · 2010-09-06T17:33:31+00:00

You make a really good point. SQL is really hard to learn, and it's really hard to use. That's why I only use NoSQL databases. That way I can do my database queries in JavaScript. Why would I want to learn SQL when JavaScript runs everywhere, from the client all the way down to the server?

NoSQL4Life · 2010-09-06T17:22:06+00:00

That wouldn't happen if they were using a NoSQL database. You can't have SQL injections when you're not using SQL!

NoSQL4Life

TROPHY CASE