louischatriot

The ability to use the console in the current frame is also one of the killer features imo. Nice work Mozilla.

Sorry to be blunt, but I am always amazed by what this kind of stories have in common: trusting people without a contract (or at least a signed agreement). Even if it's your best friend who's going to hire you, don't accept promises such as "you'll get rich once we hit it big". Sign a contract stating how much of the company you own, what the vesting schedule is, acceleration upon change of control etc.

There are some assholes out there, so stop being naïve. This is a very good cautionary tale about what happens if you do.

Always interesting to see new people try to approach the summary problem but I find these summaries have the defects common to automatic keyphrase extraction summaries: they feel very artificial, and are usually not accurate. The summary of "four steps to Google" is a good example.

I hope this kind of technology sees the day but I'm very skeptical about it working on general-purpose content and not just structured content such as news, as it does today.

That's very good news. Microsoft often get a lot of criticism for their products, most on IE. But they are still able to make bold moves that go in the right directions. That's not the case for all companies their size.

Huh, that's simply not true. On unemplyment, you get 57% of your salary for as long as you've worked with a maximum of 2 years. You have to be actively looking for a job, including monthly meetings with the administration and the more you wait, the lower the bar becomes for the job they will force you to take.

This system is far from perfect, and this country is definitely not the best place to create a company. But let's not spread crazy rumors like this.

Yep. I also made a small script that automatically transfers all your data from a NeDB to a MongoDB: https://github.com/louischatriot/nedb-to-mongodb

You can use that once you've outgrown NeDB.

I should stress this more in the README ... The key difference is that NeDB is a "real" (meaning with an actually powerful query and update language) database that is written in pure javascript. That's not the case for the other engines that need you (your users actually) to install a third-party DB or compile it. That makes prototyping, distribution and packaging much easier, and that was the main motivation (appart from fun) for this project.

I was referring to the fact that the syntax is the same so if you don't know the NeDB syntax you can play with the MongoDB REPL. Appart from this there is no connection between the two.

Thanks :)

It's true that it's easy to package such applications for unix systems, but it's much harder on Windows. What makes Node Webkit great is the fact that it's cross-platform with very little pain, and in that case having the DB in the JS code makes packaging a breeze.

Great to hear :)

Thanks! To answer your questions:

a) and b) The database is loosely coupled with the query language implementation, so it could be possible to change the query semantics without breaking it. That said I have other priorities for now (some adaptation for Node Webkit, porting it to the browser).

c) NeDB queries return vanilla objects or array of objects , on which you can use all the underscore functions you want.

d) Depends what you want to do. If you want to write a REPL I think it shouldn't be too difficult, and it may be a good idea to do one. In the meantime, since the API is the same as MongoDB's, you can learn NeDB using MongoDB's REPL :)

I think it's better now, it handles as least 1.4GB in the heap. That said if you have a database with more than, say, 300MB of data, I think you need a more large-scale database.

As an aside, I'm considering enabling large datasets for NeDB as some users asked, but that would be a lot of work so I'll wait for more requests.

I see why you would think that, this part of the README is not well formulated and I'll change it. What I mean is that is similar to SQLite since it is an embedded database, but the key difference is that it's pure JS so you don't need to compile or install anything, which makes it very handy for Node Webkit, low concurrency Node.js webapps an rapid prototyping.

That's true, but I want to stress Node Webkit because NW apps are probably one of the best usecases. Also, there is a bit of helper code specific to Node Webkit, so that you don't need to worry about where the data is stored.

Thanks! I am finishing a small helper that will enable you to specify the location of the datafiles relative to the directory where Node webkit stores data. You should find it helpful.

It's not supposed to work with cluster and using it with multiple programs that update/remove/insert docs will cause unexpected behaviour, although no data corruption since the datafile is append-only.

But if you need multiple programs to use your DB at once you need a more powerful solution such as MongoDB. The goal of NeDB is to bring DB features to desktop apps or low concurrency webapps, not replace Mongo and the like.

I may need to choose another name, you're not the first one to ask this :) I pronounce it letter-by-letter as it is an acronym for "Node Embedded DataBase"

The goal in this particular case is to have all your code in a single language for easy distribution. If you write and distribute a Node.js webapp or Node Webkit app (which I guess you don't since you don't like JS!), needing your users to also install whichever DB you use is a pain for them (esp. for desktop apps with Node Webkit, users may not be developers). That's the reason I built this.

Thanks! The syntax is the same as MongoDB's, so that developers used to MongoDB (most Node.js devs are) can get started on NeDB right away.

With the rise of very fast javascript VMs, lots of things can now be done in the same language, javascript. That doesn't meand everything should of course, but a Node Webkit app is definitely a case where I want a JS DB instead of a native one. Less powerful of course but less of a pain for my app's users.

It's true there is little overlap between these two categories. But I found that the low-level work I do (such as the db mentioned above) helps me understand better and be faster at high-level, "real world" work (such as my startup's website and API tldr.io).

I agree with the OP but I still think the power of algorithms and datastructures should not be understated, as they power most of the software everyone (including "organizational" coders) use, e.g. databases.

For example, I'm writing a pure JS database (https://github.com/louischatriot/nedb), and using indexing I was able to speed it up hundreds fold. That's clearly not something I could have done without knowing about self-balancing binary search trees.

I also think that knowing algorithms does make you a better programmer, even if you don't use them on a daily basis.

At last !

The article ends with "this sector needs innovation". Even though it does, what it really needs is better (and tighter) regulation. The situation in the US (costs through the roof, a lot of people that can't get medical care), health is something that can't totally be left to the private sector.

I needed yesterday :) Well done.

It would take too much time to do it yourself, and if you're no security expert you will miss vulnerabilities anyway. This project is a better answer: http://nodesecurity.io/

Now there is! Seriously, although there are alternatives that do part of what your player does on Windows/Mac, there is nothing of the sort on Linux. Definitely make it cross-platform.

I am working on a similar project: a persistent database in Node for Node projects, with no external dependencies. That means you can use it with a simple require(), no external software needed.

This is useful for small projects that don't need the power of a behemoth like MongoDB and want to be installable by a simple git-clone + npm install

I am very interested in feedback on it! https://github.com/louischatriot/nedb

You don't need to read 500 pages to understand the core of regex. "The core" means "what you will use 99% of the time". You need 11 minutes: http://www.youtube.com/watch?v=hwDhO1GLb_4

Consulting pays well (very well) but of course it doesn't scale. I made my first $10k doing that.