Comments on: The 10 principles of Assembly Java http://blog.javia.org/assembly-java/ Mihai Preda on mobile applications Tue, 06 Jan 2009 09:35:32 +0000 http://wordpress.org/?v=2.3 By: Marco http://blog.javia.org/assembly-java/#comment-12644 Marco Sun, 06 Jul 2008 11:53:49 +0000 http://blog.javia.org/assembly-java/#comment-12644 All still highly relevant if you're trying for as much performance as possible. I'm writing a 3d game using mascot capsule, and even now in 2008 the hit from newing and method calls is enormous. As a result I performed many of the optimizations similar to the ones Mihai talks about and it's over doubled the game's speed. All still highly relevant if you’re trying for as much performance as possible.

I’m writing a 3d game using mascot capsule, and even now in 2008 the hit from newing and method calls is enormous. As a result I performed many of the optimizations similar to the ones Mihai talks about and it’s over doubled the game’s speed.

]]> By: Amir http://blog.javia.org/assembly-java/#comment-523 Amir Tue, 09 Jan 2007 17:04:09 +0000 http://blog.javia.org/assembly-java/#comment-523 Good work Mihai. On some of the many smaller handsets that we still have to support (our build list covers over 500 different j2me devices) then most of this post makes absolute sense. Our apps have to run on very very slow, 64kj devices with less than 200k heap. You're fighting for every byte on these devices, you better understand these concepts. And we'll be supporting these devices for at least another 12 months. Good work Mihai.

On some of the many smaller handsets that we still have to support (our build list covers over 500 different j2me devices) then most of this post makes absolute sense.

Our apps have to run on very very slow, 64kj devices with less than 200k heap. You’re fighting for every byte on these devices, you better understand these concepts. And we’ll be supporting these devices for at least another 12 months.

]]> By: Gary http://blog.javia.org/assembly-java/#comment-289 Gary Wed, 13 Dec 2006 09:57:07 +0000 http://blog.javia.org/assembly-java/#comment-289 You've certainly got the right approach to writing leaner, faster code, but you're missing the point with Java. It's supposed to be maintainable! I've been an assembler programmer for over 20 years so I can agree with what you're saying, but if you're going to do this kind of stuff in assembler, make sure you don't do it at the expense of losing maintainability. I can guarantee you that processor speeds will eventually catch up. You’ve certainly got the right approach to writing leaner, faster code, but you’re missing the point with Java. It’s supposed to be maintainable! I’ve been an assembler programmer for over 20 years so I can agree with what you’re saying, but if you’re going to do this kind of stuff in assembler, make sure you don’t do it at the expense of losing maintainability. I can guarantee you that processor speeds will eventually catch up.

]]> By: Antonio Terreno http://blog.javia.org/assembly-java/#comment-287 Antonio Terreno Wed, 13 Dec 2006 09:31:03 +0000 http://blog.javia.org/assembly-java/#comment-287 This post is pure rubbish!!! What the hell are the obfuscators/optimizers for? Better to have rubbish not maintainable code or maintainable code? This post is pure rubbish!!!
What the hell are the obfuscators/optimizers for?
Better to have rubbish not maintainable code or maintainable code?

]]> By: Javi.NET http://blog.javia.org/assembly-java/#comment-228 Javi.NET Thu, 07 Dec 2006 09:54:06 +0000 http://blog.javia.org/assembly-java/#comment-228 When you have to develop a real time communications, event oriented, with more than 20k code lines, using only a code populated of Jappo macros so with only a click in a selected ant file you can generate and compile the same code for four different j2me platforms (each one with different profiles)... and do it while you keep the code legibility because protocols upgrades are usual, a easier code maintenance, and highly reliability... you can only remember this principles as a far echo in your head. Sorry, but give me proguard instead now! When you have to develop a real time communications, event oriented, with more than 20k code lines, using only a code populated of Jappo macros so with only a click in a selected ant file you can generate and compile the same code for four different j2me platforms (each one with different profiles)… and do it while you keep the code legibility because protocols upgrades are usual, a easier code maintenance, and highly reliability… you can only remember this principles as a far echo in your head.

Sorry, but give me proguard instead now!

]]> By: mobmash blog » Blog Archive » links for 2006-12-07 http://blog.javia.org/assembly-java/#comment-226 mobmash blog » Blog Archive » links for 2006-12-07 Thu, 07 Dec 2006 00:28:27 +0000 http://blog.javia.org/assembly-java/#comment-226 [...] The 10 principles of Assembly Java (tags: mobile java j2me software development) [...] […] The 10 principles of Assembly Java (tags: mobile java j2me software development) […]

]]> By: Cedric http://blog.javia.org/assembly-java/#comment-225 Cedric Wed, 06 Dec 2006 19:49:40 +0000 http://blog.javia.org/assembly-java/#comment-225 Would have been fine advice five years ago, now most of these points are moot (and those that are not are taken care of by the obfuscator anyway). Premature optimization is still the root of all evil... -- Cedric Would have been fine advice five years ago, now most of these points are moot (and those that are not are taken care of by the obfuscator anyway).

Premature optimization is still the root of all evil…

–
Cedric

]]> By: TomSoft » J2me mobile development practices http://blog.javia.org/assembly-java/#comment-222 TomSoft » J2me mobile development practices Wed, 06 Dec 2006 09:01:37 +0000 http://blog.javia.org/assembly-java/#comment-222 [...] It’s a long time that I am in the mobile industry, before J2me, and at a time where cell phone where not a mass market product!I’ve followed the evolution of mobile development practices, especially in Java. So I agree partially with this article: The 10 principles of Assembly Java who gives good hint and tips for mobile development, but I also think that hopefully most of them will start to disappear slowly.It’s a really strange industry, where on one hand people are talking of “MobileAjax” as the killer app, where the cost of one Ajax line is probably equivalent to the cost (in terms of CPU, memory used,battery) of a full Midp1.0 application, while other are strugling with putting everything in a single class to fit in constrained devices. [...] […] It’s a long time that I am in the mobile industry, before J2me, and at a time where cell phone where not a mass market product!I’ve followed the evolution of mobile development practices, especially in Java. So I agree partially with this article: The 10 principles of Assembly Java who gives good hint and tips for mobile development, but I also think that hopefully most of them will start to disappear slowly.It’s a really strange industry, where on one hand people are talking of “MobileAjax” as the killer app, where the cost of one Ajax line is probably equivalent to the cost (in terms of CPU, memory used,battery) of a full Midp1.0 application, while other are strugling with putting everything in a single class to fit in constrained devices. […]

]]> By: mihai http://blog.javia.org/assembly-java/#comment-176 mihai Tue, 28 Nov 2006 09:53:13 +0000 http://blog.javia.org/assembly-java/#comment-176 Enrique, thank you and I'm honored to find my article linked on your blog. I was surprised and a bit embarassed to have my post exposed in the public, when I was thinking that it's only me and my wife who's reading my blog :) So I was quick to post a <a href='http://blog.javia.org/?p=32' rel="nofollow">disclaimer</a>. Anders, your observations are right. The 'guidelines' were an intentional exageration of the normal usage. Yes, self-contained classes are good for reuse (I do this too), and StringBuffer to avoid instantiation is less extreme (and easier to use) than a char array. The all-static singleton is likely a bad idea. And exceptions are unavoidable, but should be used with measure. Enrique, thank you and I’m honored to find my article linked on your blog. I was surprised and a bit embarassed to have my post exposed in the public, when I was thinking that it’s only me and my wife who’s reading my blog :)
So I was quick to post a disclaimer.

Anders, your observations are right. The ‘guidelines’ were an intentional exageration of the normal usage. Yes, self-contained classes are good for reuse (I do this too), and StringBuffer to avoid instantiation is less extreme (and easier to use) than a char array. The all-static singleton is likely a bad idea. And exceptions are unavoidable, but should be used with measure.

]]> By: Marc godin http://blog.javia.org/assembly-java/#comment-175 Marc godin Tue, 28 Nov 2006 08:54:18 +0000 http://blog.javia.org/assembly-java/#comment-175 Nice to see your blog Mihai regards Nice to see your blog
Mihai
regards

]]>