Skip navigation

Tag Archives: open source

My firefox extension called “Request Access” has been hosted in and sites. I have not submitted this open source extension for hosting. I am happy to note that it is found useful to some one. You can find more details and download from and

Today’s The Hindu report on IT Trends talks about 3D Printing. You can make 3D plastic objects at home as per your design. This printer makes you to capture the existing object like cell phone casing, boxes, plastic casing for fragile materials which are more common in households. Though this technology is used in Industry for prototyping, it has become available to lay man also with the cost around $5000 from .

Dr. Adrian Bowyer who is behind this technology has promised to release the technology under GNU license. That’s great! This price tag will come down to $400 since other manufacturers too start manufacturing the 3d Printer based on open sourced technology.

Courtesy: The Hindu


Searchmash is the test bed for next generation google search. This site is owned and operated by Google, Inc. It is called Google Search 2.0. It’s look and feel and presentation are designed such a way that it is easy to explore the data we search. It is worth to test this site.

I have developed a search engine plug-in for Firefox, to search using this site. I have done nothing more than running a wizard provided by searchy. In this site, look for searchmash and download the plug-in. It will prompt you for adding the searchmash search engine plug-in. If you agree, immediately you can see searchmash search box in the drop down search engine list at the top right corner of the Firefox.

The Microsoft has released Windows CE 6.0 version yesterday. The most exciting feature for me is the share kernel source (Since I don’t do any active platform building nowadays, I don’t bother much about other features in this shiny new version. You may refer this link for more info on that.

Why I consider open kernel source as important feature in Windows CE? Reason is obvious. Windows CE is not a Server or Desktop oriented OS, but it is closely bound with hardware of the system. In my ex-profession, our team had to live with Windows CE. We intended to tune the OS to our ever changing requirements, the effort continues still. Since we have struggled a lot with debugging device driver code and not knowing the limitation of Windows CE API (which is a small sub set of Win32 API), this is definitely a big boost to my friends who work in that project still. The following are expected impact due to shared kernel source on any Windows CE based project:

1. Hard core developer of Platform builder, who takes care of configuring the system according to the hardware configuration will get more help from the kernel source which sits very much in his own IDE. Debugging the kernel mode drivers will no more be a nightmare.

2. Windows CE kernel can be customized for smaller foot print and better performance. This is absolutely necessary in the embedded world.

3. This will pause the people who intend to move to Embedded Linux for technical compulsion, and have them to re look at Window CE. The chances for support to Windows CE from both technologist and management are very well there.

4. The Shared Source License has been simplified which may affect the production cost of the end product. Any body who knows, can post a comment on this. Here is a link on license details.

5. Getting a shared source kernel for paying big $$$$ for microsoft is reasonable now… happy to see this :-) :-)

Happy kernel hacking, my dear Windows CE friends!

Today I read the Cathedral and Bazaar by Eric S. Raymond. It has nice quotes especially for open source programmers but equally holds true for closed source programmers also. Here are the quotes:

1. Every good work of software starts by scratching a developer’s personal itch.
2. Good programmers know what to write. Great ones know what to rewrite (and reuse).
3. If you have the right attitude, interesting problems will find you.
4. When you lose interest in a program, your last duty to it is to hand it off to a competent successor.
5. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
6. Release early. Release often. And listen to your customers.
7. Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.
8. Smart data structures and dumb code works a lot better than the other way around.
9. If you treat your beta-testers as if they’re your most valuable resource, they will respond by becoming your most valuable resource.
10. The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.
11. Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong.
12. Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.
13. Any tool should be useful in the expected way, but a truly great tool lends itself to uses you never expected.
14. To solve an interesting problem, start by finding a problem that is interesting to you.


Get every new post delivered to your Inbox.