At the Eclipse Foundation, we tend to eat our own dog food. Foundation employees use Eclipse itself to generate content for the website (I can’t speak for individual project teams, but I’m pretty sure that most of them do as well). In particular, we use PHPEclipse to create and edit most of the content (which makes pretty heavy use of PHP).
If you’re using RCP or even Eclipse itself, you’re using SWT. So… who’s using SWT? Lots of folks are. Ian Skerrett gave some examples of folks using RCP (and SWT by extension) in an blog entry several months back.
I guess that the name “Rich Client Platform” should be a tip-off that applications built using RCP technology can extend beyond the desktop. Essentially… if you have a client, it seems that you should probably also have a server.
In my previous posting, I suggested that “scavenging, borrowing, and blatantly copy code” is the staple of modern software development; this is, of course, true. However, there are caveats to consider, both legal and technical.
In response to my Friday posting, RefuXsaid “Linux is cheap if your time is free”. This statement is, of course, absolutely correct. However a similar statement about the cost of your time can be made about operating systems that you have to pay for.
I’ve been given this pretty cool Linux desktop system to play with. It wasn’t until I started to download Eclipse 3.1 that I realized it was a 64 bit installation (the Eclipse download page detects the operating system). Cool, I thought. The system even came with a Java Runtime Environment (JRE) installed, so I was good to go. Or so I thought.