Ubuntu designer proposes getting rid of quit from app menus....

Matthew Paul Thomas over at the Connanical blog seems to be saying that he wants to phase out the quit option from Linux App Menus.  It's kind of confusing becuase the topic is.  As a replacement or enhancement for quit he proposes changing the Close functionality of all programs to quit the application when the user closes the last window in it's set of windows.  The thought behind this is that with today's processing power and larger installed memory the need to quit applications isn't needed.  The problem is the model he is trying to compare to is that of Android and iOS.  These aren't really fair comparisons since I can't really have more than one or two screens on my Original Droid.  So you can't run into the problem of having 30 seperate windows within a single application.  I use quit/exit most often to get out of the office fast at the end of the day.  I don't want to have to jump through all my open windows to close them all.  I want to click File->Quit(Exit) a few times and go home.  

At least they aren't banning the quit menu option.  As always Connanical is pushing the UI bounds and trying to achieve new things.  It's an interesting idea but it will take a lot more convincing to get me to be a convert.  It's a long but interesting read so check it out.

Need a quick pick me up for a slowing application?

If the application you are having problems with does a lot of reading and writing to files a quick fix might be to use a RAM based file system.  Yes that precious RAM we all love to have for our apps might be better spent creating a temporary file system.  If you then copy the often written to application files onto this RAM based file system you should see tremendous performance increases.  With systems running the Core i7 architecture the boost could be even higher because of the higher RAM speeds and lower latency between the CPU and the chips.  The only way to find out though is to give it a try.  To do that you will need a RAM Disk of some kind.  I found this how to over at Linux Mag that should be a good starting point.  While I haven't done these exact instructions, I have done this before and they seem to be correct.  As with anything though your mileage may very.  Test your solution thoroughly before implementing this in a production environment.  Remember you are dealing with RAM and if you have to reboot anything not saved off from that RAM Disk will be lost.

How do you do web development correctly?

I support web development for a living and here are my thoughts about what you need to do it right.  After almost 15 years of supporting pesky developers I have learned a few things.  In this article I try to help you understand what you should plan to have and do.  Check out and participate in our discussion about the proper setup of web development environments.  Let us know how whether or not you agree with our thoughts in this post.  The story is right here.