Andrew-Dufresne

It's a great tool. All the information is stored inside a web page, which in turn means I can view it on any device that has a browser.

But what makes it more powerful is scripting support. One can not only customize its look and feel using CSS but also modify its behavior with scripts. Its scripting system is very powerful, for example, one user has a build a version control system for the TW notes using the TW scripting language.

For example, when Google shut down their free RSS readers, a lot of new RSS readers popped up.

NewsBlur, which existed even before the shutdown, had to close free accounts sign up temporarily to cope up with the heavy traffic it started to receive after RSS reader shut down.

After using Vim for couple of years, I recently made a switch to Emacs. Sometimes I regret it. I definitely miss Vim modal design and keybindings. Compare Vim's J (join lines) with Emacs go to the lower line and press ^ to join it with the upper one.

To copy a line in Vim you just have to press 'yy' but there is no copy line command in Emacs out of the box. What you can do is C-k, C-y, i.e cut a line into clipboard and paste it back to have copy line effect.

But trying and learning different tools is obviously useful. Emacs introduced me to ido-mode and org-mode. Now that I know of the possibilities, I can search for and use similar plugins in Vim.

Thanks. This makes sense. Numbers of similar files will surely increase with the increase in the number of users.

Also, there could be several users who do not consume the allocated space completely all the time. Using your argument, this too will have positive effect on their revenue model.

It IS brilliant!

The article you quoted is confusing for me. It says they store only one copy of each file and serves it to all requests originating from different users. Sounds good!

But how can it be viable? Like most files in my account are personal. Only few are such that others too might have them. Isn't it same for everyone? I think most people have mostly unique files in their account.

So how can dropbox rely on the model mentioned in the link?

Besides subsystems, tools like make and nmake utility can also reduce the compile time.

Make figures out automatically which files it needs to update, based on which source files have changed. It also automatically determines the proper order for updating files, in case one non-source file depends on another non-source file. As a result, if you change a few source files and then run Make, it does not need to recompile all of your program. It updates only those non-source files that depend directly or indirectly on the source files that you changed.