Archive for the ‘tech’ Category.

An important milestone in space travel

Falcon 9 Maiden launch

Falcon 9 Maiden launch

About a couple years ago, in an argument on space and science, I took the position that the government should invest more in science, and space travel. I lost the debate.. the government has no business using public funds for endeavours like these, and that it’s only true calling should be maintaining liberty. Everything else would follow.

I’ve since watched the evolution of SpaceX, through it’s many failures, rallied on by  it’s gritty founder and chief Elon Musk.

“We’re not going to cut and run if we have a few issues. We’re not going to cut and run if we have a lot of issues. We’re going to see this through.”

Elon’s been called “a Renaissance man in an era that needs them.”. Read a very-well written profile of him at GQ.

Yesterday, SpaceX successfully launched it’s indigenously built Falcon 9 into orbit.

Congratulations, Elon Musk. Many more successes to you.

Apple vs Adobe

Apple 1984

Big Brother from Apple's 1984 Ad

It’s time to take a stand on the battle between Apple vs Adobe.

Short Answer : Adobe. Read on for the long answer

Apple’s position in the debate is that Adobe’s Flash is closed, a battery hog, performs badly on mac/iphone, not touch oriented and that it will create developer fragmentation (developers would be at Adobe’s mercy to pick up new features provided by iPhone OS). Read this in much more detail on apple’s site, but I think I’ve covered the major points of the argument.

Adobe responded to this with a public “We Love Apple” campaign. That got a +1 from me for sheer wit, passive sarcasm, and a poetic counterattack. But do the various points it’s founders make hold up?

Let’s look at Apple’s points, and Adobe’s reply to them.

Openness

Apple’s contention is that Flash is closed, while their little-boy HTML5 (an industry open standard) is Open.

I think Joe Hewitt captured the point I want to make quite well:

I’ve been hard on Flash, but we should all thank Macromedia/Adobe for 10 years of picking up the slack of the W3C, Microsoft, and Mozilla.

I’ve worked on Flash (back at version 5). It was a wonderful tool, and being interested in Animation and Programming, allowed me to create various things very easily with some drawing and ActionScript. It had no competition. From what I hear from respectable sources, the technology has only improved since.

HTML5 is a nascent technology. For all these years Adobe’s (ex-Macromedia’s) technology kept the more-dynamic-content needs of the web filled. While I abhor the jumpy, stroke inducing Flash ads on the net, I recognize them as only being a small part of the role it played on the web. It allowed the creation of beautiful content, like you can see at Orisinal.com.

The web was quite happy to accept Flash when there was no alternative. Adobe respected this, and provided groundbreaking tools to create flash content. As it states in it’s reply, the file formats and specifications are open. So .fla, .swf, etc could potentially be created via other tools. No competitor could match the power of Adobe’s Flash IDE. Sure, the formats were Adobe’s and they had a head start, but it’s been a decade since these technologies were born.

I’m OK with proprietary tools, when the underlying file formats are open. You can create a bitmap with Gimp or Photoshop. What I admire is Adobe didn’t employ Microsoft-esqe owning of both the format and the tool, as the latter did with their document formats. Adobe won on their tool’s technical merits, and that should be commended. Apple is looking to win this argument simply on business tactic of blindly rejecting competing technology. This is a shitty (and bone-headed) move.

Battery Hog, Bad Performance

Apple claims Flash is a battery hog. There’s no reason not to accept this. Adobe, via it’s reply, agrees, by pointing out that performance has improved, as it now uses hardware acceleration.

Adobe also points out that Apple did not provide necessary APIs until recently to make hardware acceleration possible. If this is true, and I don’t see a reason otherwise, Adobe did alright in my books. How can Apple complain about the lack of a feature, when they didn’t provide the means for implementing it.

Of course, another point to note would be Adobe’s reply rings hollow. Mac has only recently gone primetime.. it was delegated to a sub-5% market share until the recent Mac OSX releases. Adobe perhaps saw no need to invest in such a small part of the pie. Linux has API to access HA, and Flash on my Ubuntu x64 still sucks. Could it be that Linux has too small a market-share for Adobe to care?

Security

This is judgment call. Yes, Flash has had many vulnerabilities published. However, I don’t think it’s on a scale to warrant it’s elimination from a platform. It’s advantages far exceed the negative of the vulnerabilities.

It should also be noted that exploiters go after the big fish. Microsoft suffers with Windows. So does Adobe with Flash. Adobe has maintained a good record of fixing issues, and issuing updates. This is as it should be.

Not Touch/Multitouch oriented

This is just a silly argument. Of course Flash content hasn’t been written for multitouch. Here’s some news.. so wasn’t HTML and AJAX content prior to Iphone and Android. The web evolves. So do interfaces and tools.

Adobe announced they would make “the best tools in the world for HTML5″. Adobe better. It’s in their interest to do so, and their argument on building the best tools on open standards gains more weight. They seem to have bet on technical innovation so far on all products they make, and there’s no reason to change direction. The practice works.

If Flash were on iPhone, you can bet the content written on it would support, and indeed be optimized, for touch.

Will Fragment Developers, and put them at Adobe’s mercy

This is is most telling of all of Apple’s points. Apple, by this argument, accepts that Adobe has very good tools, and a huge community that depends on these tools. They’re scared Adobe would attract more developers than their own. In effect, developers for it’s platform would generate business for a different vendor.

I think Apple is wrong here in their assumption that Adobe would not pick up new features. With millions of developers buying your tools, a good way of selling more tools would be to implement features developers want. The market would take care of this. Apple seems to think it wouldn’t.

So what’s Apple’s move? Outright ban of non-Apple tools. That should be enough right?

Unfortunately, this move by apple is by far the biggest “bad thing” in all of the above. It shows their openness arguments were paragraph-fillers. They proped openness up an altar, only to take a big dump on it afterwards.

Imagine if Intel only allowed developers to write for their chips on Assembly and C. “That’s the only way you’ll get access to all underlying features”, they would say. “Those Pythoners have not yet implemented this cool new stack counter we added. You want to use our shiny new stack counters, right?”

Free and open specifications and standards are more important than open software. The former will lead to the latter, and competition would be on technical merit alone. I dont grudge Adobe the massive amounts of money it makes by producing wonderful tools that make creating content easy. I love open source, but I can live with a technically better solution, when an open source solution doesn’t cut it.

Apple’s letter, constantly sprinkled with ideas that don’t stand introspection, reads like a call to arms. Adobe’s response is a far more rational and level-headed take.

Jon Stewart said it right. Apple, go take a look at your 1984 Ad. Then take a look at your iPhone store, look at your dev SDK, look at the guy whose porn app you blocked, look at a competing app by google you were too scared to accept, and tell me: Are you the girl in red shorts, or “The Man” on the screen?

Nexenta Core Platform 2 released!

I’ve been neglecting my blogging duties, but I’m back on track. Lots of things have happened in the recent times, but the big news today is the release of the Nexenta Core Platform 2. This release has been a year in the making, and took a lot of hard work.

We’ve also produced a short comic, with our very own hero, Nexentaman, to walk you through NCP. Click below to read the comic.

The Adventures of Nexentaman

The Adventures of Nexentaman

Links

Nexenta homepage: http://www.nexenta.org

Artwork and Wallpapers: http://www.nexenta.org/os/SpreadTheWord

IRC : #nexenta on freenode

Go ahead, test drive Nexenta, and spread the word

Oracle acquires Sun

Oracle has aquired Sun.

There were weeks of speculation of a buyout by IBM, which generated loads of discussions on the opensolaris forums. The biggest fear was IBM buying Sun, and killing off competing products. Sun and IBM competed on many fronts.. Opensolaris vs AIX, Eclipse vs Netbeans, Mysql vs DB2, Power vs Sparc, etc.. not to mention the server hardware market.

Sun’s price-tag was nothing to IBM.. it could’ve bought Sun out with a week’s revenues. The talks fail, Oracle swoops in, and grabs Sun. A /. comment sums it up..

Sun = Poorly run company with great products
Oracle = Masterfully run company with shitty products

I wonder how that DNA is going to come together…

I wonder too.

Sun’s range of technology and products dont overlap with Oracle, atleast not to the extent it did with IBM. This means that Oracle is looking to expand to have hardware solutions, and provide a complete stack (or the less probable alternative where it does not expand, and simply blew billions.)

Sun has had issues with marketing their amazing range of technologies.. Linux (and brands like RedHat/IBM/Ubuntu) are still considered the face of free software.. an arena where the majority of the code, by a large margin, has been contributed by Sun. Oracle seems to have a marketing department that seems have a clue.

My personal interest is in Opensolaris’ future. Things looked bleak with IBM who would prefer AIX and/or linux, given their investment into those technologies. Oracle, on the other had, has a very good track record on Opensolaris, and an integrated Oracle/Opensolaris solution would be powerful indeed.

Oracle’s presentation on this can be found here. Quoting points relevent to Opensolaris:

Slide 4

Consistent with Oracle’s strategy to provide complete, open and integrated systems
Optimize Solaris and Oracle for better performance, reliability, and manageability
Open Storage built with industry standard servers and components
Expands Oracle’s range of products, including servers and storage
..

Slide 5
Sustain Solaris as an industry standard OS for Oracle software
Continue Open Storage and Systems focus and innovation

That should quell any fears of Opensolaris going kapunk. Here’s looking forward to a bright future, and continued innovation in Opensolaris land.

[Of course, bigger pundits than me have had to eat their hats on their predictions.. all of the above is pure personal speculation.. don't buy stocks based off this]

Gnome on NCP2

I mentioned in a previous post that GUI related packages were being populated into the NCP2 repository. Since pictures are a thousand words:

Gnome, GIMP and Irssi running on NCP2

Gnome, GIMP and Irssi running on NCP2 (not to mention the Heron)

Huge thanks to dtbartle, who has actively been porting Gnome into the package repository. Why not hop into #nexenta and say thanks.

Theres also other window managers being populated at the moment. Small ones like Enlightenment (e16) and 9wm are fully in.

PS: Also another round of hackthon is in the plans. Stay tuned for more.

Autobuilder Update

The last time I mentioned the Nexenta autobuilder, it was just opened and not fully completed. That changed recently.

The autobuilder is now in the works and since the beinning of the week has been chugging away tirelessly, working on Ubuntu Hardy’s 8.04 repository. The result.. over 2500 packages now reside in Nexenta’s contrib repsoitory. Going at this rate, we should have triple this amount by the end of next week.

The autobuilder is built to scale, and all of the work is shared between 2 nodes. The pace of package porting will increase with more packages. Do you have a machine free for the autobuilder to use (and have the bandwidth to spare)? Drop in on #nexenta or the devel mailing list, and we’ll help you setup. Look for Tim Spriggs (aka rootard). We’re still a good while away from Ubuntu’s 20000 packages.

The autobuilder will however not work for packages that need to be ported to Opensolaris/Nexenta. These should be few and far in between. It does fishily sound like another hackathon.

Devzone article on OSnews

I just published a devzone article on OSnews.

Devzone

Devzone

From the blurb:

Devzones, short for development zones, is a type of virtualization found in the Nexenta distribution. It can be used to define a base developer environment, which can be easily cloned many times. These copies can easily be destroyed and recreated. Devzones are built upon Opensolaris Zones, which are extensions of a chroot-like environment for the entire installed system. In other words, it allows for virtualization of an Opensolaris environment (and variants of Linux), without the performance hit that is generally associated with virtualization. This article gives a practical introduction into using Devzones. Read more on this exclusive OSNews article

The devzone homepage: http://devzone.sf.net

Let Me Know

Let Me Know

Let Me Know

My friend Nitin has a knack for entrepreneurial stuff.

One of his expliots had been the Let Me know website at letmeknow.wordpress.com which was a platform used to notify students from around the country about opportunities that come up. The world before let me know meant various events, shows, scholarships, contests, etc needed to be printed on posters and pasted on school notice boards. Let Me Know changed that and turned into a one stop shop for all such information.

I can vouch for this because I heard of BITS, Goa tech fest this way, and built a robot which won accolades :) . So there.. add Let Me Know to your RSS feed, or subscribe to their notifications by entering your mail at the website (its better than regularly checking the site).

PS: The robot reminds me, I still have the Spots, the motor, the ICs, solder and the metal casing. I should plan on some hardware hacking one of these weekends..

KDE4 on Windows

I’ve been following the KDE4 release for sometime now, and have been amazed at the great work done by the developers. The UI looks amazing, and the attention to detail has been magnificent. I was pleasantly surprized when one of the BOSUG members saw KDE4 and asked.. “Is that OSX?”

But this post is about KDE4 on Windows. I’ve been following the blog Introducing KDE4, Luis Augusto, which is a screenshot oriented tour of various KDE4 software. The latest entry talks about KDE4 on windows, and the screenshots speak for themselves.

http://introducingkde4.blogspot.com/2008/12/introducing-kde-4-on-windows.html

Dolphin on Windows

Amarok on Windows

Amarok on Windows

If you’re interested in what is potentially the next generation of Desktop on the Unix/Linux platform, add this blog your feed reader.

Devzone and Autobuilder now open

Devzone

Devzone

If you’ve kept track of the latest in the Nexenta community, or logged into our build machines, you’ll know about a neat little set of utilities we have built on top of Opensolaris Zones. Devzones are a simple concept which allow you to create a custom zone, and creating multiple copies for developers.

Devzone

The devzone package is now available online from sourceforge under the GPL2 license.

We’ve been adding new features to make administration simple. Devzones will be built into the upcoming NCP2 Beta release.

Meanwhile you can take a look at what’s cooking in the background at the below address, or checkout the latest from SVN

Project page: http://sourceforge.net/projects/devzone/

SVN: svn co https://devzone.svn.sourceforge.net/svnroot/devzone devzone

AutoBuilder

The autobuilder project too has been hosted on sourceforge. This is a distributed way to build those humongous apt repositories for your Ubuntu sized distro.

Client nodes can request for packages to build. This is almost fully complete and is already functional as a web based view of debain apt repositories. Give it a try at http://builder.tajinc.org/

Project page: http://sourceforge.net/projects/autobuilder/

SVN: svn co https://autobuilder.svn.sourceforge.net/svnroot/autobuilder autobuilder

I’m working on a simple tutorial for devzones, and it should be published shortly.. so stay tuned for that. Meanwhile, spread the word.

Thank Tim Spriggs(rootard) for these tools. If you have any questions, or want to participate, join our IRC channel at #nexenta@freenode (there’s a web based interface here).