Ovidiu Iliescu * Software Developer

Google Chrome Extension : Remember my location

2009-12-13T12:22:14Z

A Google Chrome extension that helps you keep track of your navigation within a website.

For example, let’s say you’re happily browsing the Dilbert archives when suddenly your house catches fire. Before you run for your life, you can use “Remember my location” to save the address of the comic you’re currently viewing. Later, when the fire is gone and you come back to dilbert.com, you can restore the saved address and resume viewing from where you left off.

Furthermore, each website gets its own save slot, so you can use “Remember my location” to keep track of your navigation within all the websites you visit. Simple and neat!

This extension is much better suited for this purpose than bookmarks becasue :

it’s context-sensitive to the website you’re currently on
you don’t have to search through your boomkmarks (the “Restore last location” button is one click away)
you won’t have to deal at all with managing bookmarks

Get it here.

Also, this is my first Google Chrome extension.

Webcam + Clever Software = 3D Scanner

2009-11-26T10:41:55Z

This video was embedded using the YouTuber plugin by Roy Tanck. Adobe Flash Player is required to view the video.

Found it here .

Happy birthday to me!

2009-11-11T14:27:18Z

Happy birthday to me! I’m 22 now, but I don’t feel a day over 20!

Now working for Enough Software

2009-11-04T13:14:16Z

I don’t usually talk about my ongoing projects, but this one is definitely worth mentioning: I have very recently started working for Enough Software, the makers of J2ME Polish.

I’m obviously very excited about this, since I now have the opportunity to participate first-hand in improving and expanding one of the mobile industry’s most well known pieces of software.

This will definitely be a great experience!

A very impressive quine

2009-11-02T22:44:44Z

To quote wikipedia, “a quine is a computer program which produces a copy of its own source code as its only output.”

I’ve seen a couple of interesting quines in my life, but this one definitely deserves the crown.

Kudos!

Blast from the past

2009-10-19T12:49:27Z

Because I was feeling a bit nostalgic this morning (probably because of the awful weather outside), I decided to take a little trip down memory lane. Here are some of the places I visited:

Video nostalgia : Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, Part 7, Part 8 .
Best video games magazine ever .
A huge collection of software and emulators can be found here .

If you don’t already know what the ZX Spectrum is, read about the hardware and the man behind it .

Enjoy! In the mean time, I’ll go make me some hot cocoa …

The imminent death of J2ME ?

2009-12-12T17:53:14Z

The iPhone, Android, Blackberry, Symbian and Windows Mobile platforms seem to be all the rage these days. Everyone’s talking about them, everybody’s using them and everybody’s praising their state-of-the art capabilities.

In fact, some even believe that they will bring with them the death of J2ME, citing the platform’s age, speed and primitive API as its mortal weaknesses. While there is some truth to these claims (J2ME is pretty old, and more modern platforms do have some pretty cool applications running on them), make no mistake about it: J2ME is not going anywhere anytime soon.

Find out why after the jump.

I must admit, when the iPhone was first launched I got a little bit concerned about the future of J2ME. But, as I spent more time thinking about the matter, my fears pretty much vanished. In fact, in the years since the iPhone was launched, I was unable to find a single solid reason for which J2ME might become extinct. For your entertainment, here is a list of some of the most commonly cited causes for J2ME’s imminent death, along with an explanation of why they’re wrong (for simplicity’s sake, I will refer to the iPhone, Android, Blackberry, Windows Mobile and Symbian platforms collectively and generically as “the iPhone”) :

“J2ME is slow when compared to the iPhone” – J2ME is only a standard. It can’t be slow, and it can’t be fast. What can be slow (or fast) is the hardware running J2ME. Sure, a $600 iPhone is faster than a $100 J2ME-enabled regular phone, but that’s not really a fair comparison. The fastest J2ME enabled devices of today can provide performance levels on par with those offered by the iPhone, at a very competitive price.
“The J2ME API is not nearly as powerful as the iPhone’s” – This is extremely false. In the beginning J2ME was limited (it was developed a decade ago for the devices of the day), but over the years it has been extended and upgraded to keep up with the times. Sure, at first we didn’t even have floating-point support, but things have changed and today stuff like 3D graphics, integration with the phone’s contacts, calendar and filesystem, multimedia and bluetooth support (take that, iPhone!) are commonplace features. More advanced features, like GPS and touchscreen support (available since the MIDP 1.0 days !), are quickly gaining ground.
“J2ME suffers badly from device fragmentation issues” - this is pretty much the only legitimate claim on the list. However, good coding practices, attention to detail and tools like J2ME Polish can pretty much take care of this. At the same time, if you try to run a state of the art J2ME application on a 5 year old device and find that it doesn’t work because the phone does not have enough resources or it is missing some API’s, you really can’t blame that on J2ME. Question: do you think that an application for the iPhone 6.0 will work on today’s iPhones ? Me neither.
“J2ME applications can’t match the look and feel of the iPhone” - One word : TWUIK .
“The iPhone has an ever-growing userbase and will eventually kill J2ME” - As iPhones get cheaper, so do J2ME phones. As the iPhone gets more powerful, so do J2ME phones (for example, the next generation of J2ME devices, those that will feature JavaFX support, should be pretty powerful). As more iPhones are sold, many more J2ME phones are sold at the same time. As the iPhone specs are improved, so are the specs of J2ME phones. As more clever applications appear for the iPhone, clever applications appear for J2ME also. For example, have you seen some of the latest augmented reality applications on the iPhone ? J2ME had stuff like that way back in 2006. Unless the iPhone somehow magically becomes dirt-cheap, it doesn’t stand a chance to kill J2ME.
“J2ME is not as flexible as the iPhone” – Let’s compare a standard J2ME phone with a current generation Apple iPhone! I don’t have to jailbreak my J2ME phone to install “unapproved” applications on it. Nor do I have to wait for proper bluetooth support (it’s already here). And, from a business standpoint, J2ME is the most flexible platform around simply because it has the largest userbase and the cheapest devices.
“With so many platforms around, J2ME’s market share is going to dwindle” - Regular phones support J2ME. Symbian phones support J2ME. Windows Mobile phones support J2ME (albeit not directly). Blackberry phones support J2ME. The only platforms that do not yet support J2ME are Android and the iPhone. Even if these two somehow manage to gain a 50% market share (we’re talking about 50% of all mobile devices), that still leaves J2ME with a 50% marketshare. Enough said.
“Everyone is switching to the iPhone and there won’t be enough developers left to work with J2ME” - The cost of entry for J2ME development is almost ZERO (you only need a computer running Linux) and for that money (again, $0.0) you can get a mature, fast and full-featured development environment (Netbeans, for example). Being low-level and simple, J2ME is easy to learn. Being old, there is a lot of freely available information on the Internet. Being the most widely available mobile platform, you get the largest possible userbase for your applications. These reasons alone should attract a constant following of developers.

So what does all this mean? Well, certainly there’s plenty of competition for J2ME. And certainly a lot of developers are focusing on other platforms, to capitalize on their growing marketshare. And, as a developer, it would be wise to take a peek at the competition and learn something about development on other platforms.

But, just like Windows in the desktop world, J2ME has a huge userbase and enough features and flexibility built-in to safely place it in the #1 spot for a long time to come. For these reasons, J2ME simply cannot be ignored if you’re targeting the mobile world. You can always release a high-end version of your application for the iPhone and its limited userbase, but you’re probably going to be much better off releasing a J2ME version for the masses first and see how it catches on. With the proper development team and tools, your J2ME application can look just like its iPhone counterpart on high-end devices, while still running on lower-end devices (albeit without the fancy look and feel). If nothing else, this fact alone will ensure J2ME’s survival.

Why I think JavaFX will fail

2009-08-02T20:30:00Z

Long story short, JavaFX is Sun’s attempt to compete with technologies like Microsoft Silverlight and Adobe Flash/Flex/Air by finally bringing Java’s UI capabilities into the 21st century. It’s great in theory, it’s great for the Java world in general, but I don’t think it’s going to be so great in practice.

The reason I’m saying this is because JavaFX simply doesn’t have a place on the modern map of computing. I mean, let’s look at the facts:

Flash clearly dominates the web. The ubiquity and maturity of Flash gives developers virtually no reason to switch, especially when considering that most users don’t even know what Java is, let alone have it installed on their computers.
On the desktop side of things, Air is pretty cool, however technologies from Microsoft (like WPF and Silverlight) have a greater chance of catching on. Sun is left way behind because of the large downloads and long start up times usually associated with Java. Remember, we’re talking mainstream users here.
Great UIs need great visuals, and these in turn need powerful image processing tools. Adobe has time proven software under it’s belt, like Flash, Illustrator and Photoshop. Microsoft is making an effort to catch up (though it’s arguable how successful this effort will be). Sun has nothing. And regardless of what you’ll say, there will always be more “cooperation” between Photoshop/Illustrator and Flash than there will be between Photoshop/Illustrator and JavaFX.
Consoles and other similar devices have built-in web browsers. These web browsers usually run Flash. And I don’t think they’re going to switch to Java anytime soon.
The only real chance JavaFX has is in the mobile world, and Sun knows it. In fact, Sun says JavaFX will be available on mobile devices starting sometime in 2009. However, they don’t specify on what class of devices JavaFX will run. Unless they somehow manage to get it running properly on mainstream devices, they’re ship is sunk. Let’s face it, if you’re going for a high-end device, you might as well use it’s native API. Or go for Flash. Speaking of Flash, my old Nokia E50 can happily run FlashLite content right now.
Serious (read: “enterprise”) users don’t need JavaFX. At all.

Bottom line, unless Sun somehow manages to pull a magic rabbit out of a magic hat, I simply don’t see how they can make JavaFX really catch on. I admit I like the idea of JavaFX, but something tells me I’m not going to like the reality of it.

Incredible J2ME Voxel Engine

2009-07-31T13:15:14Z

This is by far the coolest piece of J2ME software I’ve seen lately:

This video was embedded using the YouTuber plugin by Roy Tanck. Adobe Flash Player is required to view the video.

According to the video description, this uses no 3D API whatsoever. It’s just simple J2ME code. I’m absolutely stunned.

Why I love J2ME

2009-07-31T16:53:17Z

Programming J2ME is a very tricky business, much more so than regular desktop programming. Because you have limited resources, most of the time you simply don’t have the luxury of wasting them. Granted, sometimes you can get away with using RAM and CPU cycles like there’s no tomorrow, but any serious number-crunching in J2ME requires you to be a really, really clever coder. You have to use all the tricks you’ve got : clever memory allocation techniques, clever ways of speeding up your computations, clever ways of storing your data, even clever ways of displaying information. Not to mention you have to handle device-specific issues, of which there are a lot. There’s no question about it, J2ME programming can be (and often is) difficult, inconsistent and perplexing.

So why do I love it ? Well, plenty of reasons. It always keeps me thinking while I work. It doesn’t allow me to get rusty, because I always have to tackle new challenges and learn new tricks. It gives me the satisfaction of literally holding my work in the palm of my hand. It makes me feel great because I can create some very cool stuff despite the very restrictive environment. It fuels my imagination, because J2ME means computer programs that you can carry around and use wherever you are. Last but certainly not least, it makes me feel like a real programmer (without the convoluted and hieroglyphic-like coding style).

Why do you love (or hate) J2ME ?