Take care,
Cos
P.S. The original formatting of the article was preserved, because java.net's blogging system is simply lacks of many essentials.]]>
Open SuSe Linux:
However, technologies such BSP (
Another lesson I learned from the above observation, is that despite
of popularity of the platform quality processes might be done equally
or less successful, especially in the world of open source software.
Anyways, it's being rather a long post. And I'd like to draw a
conclusion now.
Sun JDK is getting to open source quite soon. Considering all examples
above I could tell, that Sun JDK's quality process might be
implemented in one of already known models. However, "already known"
doesn't mean "perfect" or "sufficient".
Thus, I would love to hear your ideas, suggestions, comments,
outbursts, etc. Please post them here or just send me an email to
kboudnik@gmail.com]]>
There is yet another way to somehow guarantee the quality of an
application. You can do constant static analysis of your code, which
will give you some sense of security too. I'll be writing about
different static analyzers next time. Stay tuned to see info about
Coverity, Klocwork, FindBugs and some others. There was an article
recently in one of online technology news sites. The article was
comparing Klocwork vs. Coverity. Frankly speaking, I read it twice and
didn't get a clue of what was the difference between those two :-)
Looks like the open source market is getting more and more hot nowaday. This recent thread on Debian's list
shows that when development community is trying to get things easier around, someone suspects that a lawyers can be in a position to cause a harm.
From that tiny snippet
"...If Sun would commit to putting that interpretation in their license, that would be one thing. But as an aside as it is, with no legal standing, who is to say that other lawyers or a judge wouldn't decide it means something entirely different?..."
I conclude, that the old saying is still correct "The law is like a shaft: it will point wherever you can turn it" :-)
Pardon my ignorance, but it seems like freedom of open source and official rulings are still as good mix as water and oil. Public wants one thing, but the governing entities might know better what is the best for that very public.
Take care,
Cos
Take care,
Cos]]>
В переводе статьи о прогнозах Уоррена Баффетта (http://www.izvestia.ru/economic/article3092694/) автор перевел вот такую фразу "...an industry leader in the metal cutting tools business..." вот таким вот образом "...компания по производству лезвий из тяжелых металлов для кухонной промышленности..."
Это будет покруче "pure virgin wool" как "шерсти непорочной девственицы"
Круто, японцы просто отдыхают
]]>I'd visited CTIA conference recently. Actually, this was my first time experience with that kind of technological forum ever. It's totally different from development conferences - it's so about money. It stinks of money, if you will. It seems like all these business people at pumping a lot of cash into almost any wireless-like technology or software application. It's like the nineties of last century: if you had a word 'Internet' somewhere on your business plan - you're likely to get some crazy funding.
Anyways, at that even in Las Vegas, NV, I saw a lot of interesting wireless stuff presented by respectable companies like RIM (gosh, I love their phones!), Nokia, LG, Samsung, Motorolla, NTT Do-Co-Mo, and many others. The software side was represented by a variety of service providers and SDK makers like QualComm. Even Microsoft wasn't ashamed to bring their killer PocketPC smartphones (nice name, isn't it? Perhaps all other's are dumbphones) to the expo. And it is a killer by the way it assassinates those small gizmos.
But what hit me a lot is that I didn't see the main player of the
JavaME's field: Sun Microsystems didn't appear at the
CTIA. And believe me - I was looking hard!
The company, which had created the most popular software platform in
the world; powering as many as 2.5B Java devices around the globe had
only one session in all three days of second biggest wireless
technology conference ever.
The session was about
NetBeans
Mobility 5.0 However, it was taken away to the Harrah's casino (perhaps, hidden from
Microsoft's corporate spies or something): neither Sun Microsystems
nor NetBeans brands were listed in the conference catalog; neither
NetBeans or Sun's info hasn't been posted on the CTIA web site; clerks
at the info booths weren't aware about such a pod at
all.
To give you some comparison ground: QualComm is supporting about 40+ OEM manufacturers. This gives us roughly 600 headset models (according to one of their marketing folks). And they had a big setup, a special all day long development seminar, etc. One more fact: there are as many as 200+ mil. of cell.phones owners in the US. So, do your math...
So, I'm kinda wondering what is the message JavaME community will be getting by this de-marsh? Does it simply mean, that Sun Microsystems starts paying more and more attention to the mobility tools development or something else?
But on a bright note, I'd like to mention, that a number of software development companies are still looking toward JavaME platform. I was talking to a few folks from that side of the fence, and they seem to be quite excited about what they are able to do with JavaME now. A particular interest is coming from wireless social networking developers - Java platform is greatly simplifying the user experience and reducing the development cycle for them.
By the way, the wireless social networking is blooming nowadays. I met a very promising and proactive group of folks from VCEL, Inc. who did a very first truly wireless social networking platform in this country. And it's all using JavaME (well, they've might be using Java for their server side too, instead of scripting :-). They are supporting about 20+ MIDP2.0 headsets from different manufacturers and providing a whole new way into people social communication. It's so cool! And I'll write more on this particular topic later...
See yall soon,
Cos]]>
The blog, I believe, will be a real first hand's value-add for existing Java VM resources, about modern VM techniques, tools, security features, co-existence with .NET, etc.
There isn't much right now, but the folks will carry on fast, I think.
You can find this new information resource at at the official Sun blogging site
So, if you have colleagues or friends, who are suffering without such information, written in Russian - please pass by my message or simply the URL above. Let's wish them good luck and God speed!
--
Thanks
Cos]]>
Sometime you might want to take a quick look and find out what exactly
has been changed in your (or somebody's else code) between two
versions. Why? Well, if you want to focus your test development on the
new API only it might be a very sound idea. I'd spoke about
some of other methods to help you to achieve
better software quality
Well, there are some methods to do so. E.g. you can use "Since" tags
from a Javadoc Well, good if you have any...
Or you can store your product API's snapshot like RefactorIt does. Boy, what if you didn't create this snapshot in a first place and now you badly need one? "Sorry partner - no can do for ya..."
Anyways, the idea was on the surface as usual:
In one way or another
build a list of all public (protected/private/static/etc.) methods in
your software. You can use grep or javap
along with grep for these purposes. Don't forget to do this for both
versions of your application - it's about the difference, right? :-)
Now, you have these API lists, you just need to compare them. And again it's up to you: you can use Unix diff command, Emacs ediff, or vimdiff. I'd wrote that self-explanatory Perl script (feel free to modify it, criticize it, or merely throw it away). Fix &open_file()'s loop if your API lists weren't created in the form of "filename:method signature" per line...
#!/usr/bin/perl
if ($#ARGV != 1) {
print "Please supply two lists of APIs you want to compare\n";
exit 1;
}
my %diff = ();
my $left = &open_file ($ARGV[0]); #Presumably, the earlier version
my $right = &open_file ($ARGV[1]); #Presumably, the latest version
foreach $file (keys %$right) {
if (!exists $left->{$file}) {
$diff{$file} = \@{ $right->{$file} } ;
} else {
@l_stuff = @{ $left->{$file} };
@r_stuff = @{ $right->{$file} };
foreach $r ( @r_stuff ) {
if (&is_there($r, @l_stuff) != 1) {
push @{ $diff{$file}}, $r;
}
}
}
}
foreach $d (keys %diff) {
@extract = @{ $diff{$d} };
print "$d\n @extract\n";
}
#=========== Some subs
sub is_there () {
my ($search, @list) = @_;
for (@list) {
return 1 if $_ eq $search;
}
return 0;
}
sub open_file () {
local ($name) = @_;
open FILE, $name or
die "Can't open specified file!$name\n";
my %ret = ();
while () {
($key, $value) = split(':', $_);
push @{ $ret{$key} }, $value;
}
return \%ret;
}
Of course, there's always an expert opinion. Or you can ask an author of an application, or eye-roll it yourself. But isn't that much simpler to load your computer with the stuff it can do better then a human being?
CU,
Cos]]>
%E2%80%9Cfor left " and
%E2%80%9Dfor the right one