Saturday, July 21, 2007

iPhone hackers work for Apple

It's been widely reported about various progress in the hacking of the iPhone. A couple of days ago Engadget reported that apparently a hacker named "Nightwatch" has compiled and launched his very own application on the device.

In order to accomplish this feat "Nightwatch" has constructed an ARM/Mach-O toolchain that henceforth can be used by others to follow his example and consequently have third party native applications running on the iPhone instead of just Web 2.0 apps running in the Safari-browser.

Of course this is a positive breakthrough since developers and iPhone-owners have been screaming for an API and the possibility to develop and run real apps on the iPhone. But it shouldn't come as a surprise to anybody. As with all such things they are always broken sooner or later, it's just a matter of how long the apparatus can resist the efforts of it's hackers.

But most of all, I'm very sure this came as no real surprise to Apple. In fact, I'm positive they counted on this happening sooner rather than later, and they surely will reap the major benefits from it.

By releasing a device that's received more pre-release hype than anything I've ever seen before Apple has assured (almost at least) it's success and that it will sell millions of it. By then refusing to give third party developers access to an API or an SDK they've assured that the caffeine-crazed hackers of the world will do their best to break into the device and have it run third party software. Once there is a fairly stable way of developing apps for the iPhone, which shouldn't be far away now, a new market opens up which while not feeding money directly into Apple it does making their money-making product even more desirable. And they've done nothing themselves to make this happens except release the phone and withhold the API, all the real work the hackers have done for them. So basically, they've been working for Apple all along. They've just not gotten paid a dime for their hard and commendable work.

Another positive thing in this scenario, from Apple's point of view, is that as long as no official API or SDK has been released they don't have to deal with support and complaints regarding third party applications. It's not their fault if you installed and ran some app on your iPhone that made it go up in flames since it's not their toolchain that built that app and they certainly didn't license it.

So even if it looks like Apple 0 - Hackers 1, it's really the other way around if you think about it.

Tuesday, July 17, 2007

Twitterer and widget maker

The past couple of days I've been playing around with Twitter and it's API. It's pretty simple to use, hardly astrophysics or anything, and with the widget for Blogger looking like ass I decided to hack my own. And so I did.

The fruits of my labour are plainly visible to the right in this blog. It's nothing fancy, just some basic HTML, CSS and Javascript, but I think it looks pretty good. And if anybody gives a damn the code can be downloaded from here.

In the days ahead I'm gonna pleasure myself (oooh...) by writing a Twitter-applet for the Gnome desktop as well. Now don't misinterpret the sudden focus on Twitter. I don't think I'll ever be an avid twitterer (is that a word? probably not) and I'm not exactly falling head over heels with excitement over the thing. I just wanna play around with some free API:s, and for that purpose this one is as good as any. Also, anything that allows me to interact using the command line gets a "yay!" from me.

curl -u someaccount@somedomain.com:somepassword -d status=Posting+to+Twitter+using+curl+is+teh+shit%21 http://twitter.com/statuses/update.json

Thursday, June 28, 2007

GPL 3 launches on the 29th of June!

Now this release is way more important than all the iPhones in the world!

And there will be a live stream too.

Wednesday, June 27, 2007

I hate the iPhone

It's not even out yet (unless you're special) and I've never seen one in real life, but damn, do I ever hate the iPhone.

To be more precise it's not the actual gadget I hate as much as all the exaggerated hype and media hoopla surrounding it. For goodness sake people! It's a friggin' cellphone! It's not some magical device that will bring peace, stability and prosperity to the Galaxy.

Goddamnit, there are actually people camping outside of the Apple Store on 5th Avenue in New York already, just to be the first to get one. I'm sorry, but that's simply retarded.

Every damn tech news site I read is completely drowning in iPhone-spam (i.e. repetitive articles about how awesome it will be) and I'm just sick of it. On top of it all now that's it's just a couple of days until release the reviews are starting to pop up. I wanna puke.

But it's not just the hype that gets on my nerves, it's also the fact that I don't see what is really that special about the iPhone. Sure, it's most certainly a nice gadget, Apple's stuff usually is one way or another, but it's not that great. I mean, calm down people.

Just by reading not much more than the specs on Apple's website I quickly find the following serious flaws:

  • It's just a GSM-phone, i.e. no 3G. That sucks.
  • No videocamera, and that means no videochat. This from the computer manufacturer with the largest install base of webcams of all. Suck-o-rama.
  • It can't send MMS-messages. Come fucking on! Can you say "medieval technology"?
  • The camera is just 2 megapixels. Hardly impressive.
  • No support for other video-formats than MOV and MP4. That means no DivX/XviD, which means it's hardly an ideal video playing device. More suckage.
  • You can't use songs as ringtones. Wow, that's really fresh for a cellphone released in 2007.
  • No removable battery. Are you kidding me?
  • Non-expandable storage space. No memory-cards, nothing. Oh man, more suckage.
  • Apple decides what provider you can use, not you. Suckfest deluxe.
  • And finally, taking into account all of the above, it is way too expensive.
  • Being a programmer myself I find the lack of an API for the iPhone very disturbing. Sure, Steve says it's all gonna be webapps run from within the phones browser, but no matter how awesome the web2.0 and AJAX revolution is there are still a shitload of things that simply can't be done with webapps. So yes, a real API would be nice.

That said, will someone please give me one real valid reason why this should be seen as such a revolutionary and a must-have item? Yes, I've seen the demo-movie on Apple's website and I know all about the snazzy touch-screen and its glorious sexiness. But hey, the fact that Apple make great user interfaces shouldn't come as a surprise to anyone and still, no matter how awesome the GUI is, it doesn't make up for the lack of features.

Or are you gonna spend the time you would sending MMS-messages to your friends flipping windows about and pinching stuff on the screen instead? And instead of videochatting with your peeps, maybe you can watch a video and gasp in awe when the movie pivots automatically as you rotate the device? Wow dude, that's real productive and worthwhile.

There is basically nothing that the iPhone does that my Nokia N80IE can't do, or at least nothing really significant, and it does everything noted above that the iPhone doesn't. In comparison the new wonder from Apple is a technological cripple. My cellphone (or any other phone out there) is however not enjoying the most tremendous tidal wave of hype ever like the iPhone is.

So for $499 I could buy a phone that compared to my current cellphone more or less sucks but has the power to make all Apple-fanboys wet themselves in awe? No thanks.

And please stop yapping about it. Really. STOP.

Tuesday, June 12, 2007

It's all about the wireless baby

The last passage from this article nicely delievers a buzzkiller of truth to Eye-Fi's upcoming wi-fi memory cards:

There are currently digital cameras on the market that offer built-in wireless networking, but they haven’t exactly taken the world by storm. Given that you can buy a 2GB memory card for less than US$30, you’ve got to wonder whether consumers will be willing to cough up US$100 just so that they don’t have to go through the hassle of hooking up a USB cable.

Very true, but the sad part is that personally I would easily fork over an additional $70 for some wireless sexiness. You see, I'm a sucker for anything wireless.

Indeed I am. I'll readily admit that I'm a total sucker for any and all wireless gadgets. It's like a disease. I just can't help myself. I just find the "no need for cables"-thing so cool, even if it is hardly a new and revolutionary thing by now. It doesn'tmatter if I really need the gadget in question or not, if it's wireless it is just that much sexier to me and I want it bad.

I remember fondly back in the eighties when our family got our first TV that came with a remote control. It was the coolest thing ever! Just imagine the joy of not having to get up and walk over to the TV when flipping the channel! Now that's life changing technology if there ever was any.

Bluetooth, wi-fi, even infrared, I love them all. Sweet wireless technology be mine, now and forever.

Friday, May 25, 2007

Not quite dead

In a recent article Computer World lists the "top 10 dead (or dying) computer skills", some of the spots on the list I agree with but some I don't.

One that I totally don't agree with is number six, "C programming". Anyone who claims that the C language is dead or dying simply doesn't see the software industry for everything it is and doesn't understand how many different kinds of software there is out there.

Fine, you might not see the latest snazzy web applications from Google being written in C or even a huge amount of desktop-applications for that matter (even if I believe that quite a lot of the Linux/Unix-apps are written in C, the Linux-kernel for one). But that doesn't mean there isn't a shitload of software everywhere around us written in C.

To my knowledge most embedded software is written in C. Things like controller software for household appliances, cellphones and such things, devices like that all have a fair chunk of C spinning through their circuits.

Another great example is GNU/Linux-software. The Linux-kernel is written entirely in C I believe and so is most of the apps that make up the GNU-toolset.

So basically, C is not dead or dying. Claiming that almost makes you an idiot.

The claim that the languages Cobol and ColdFusion are dying however, I can basically agree with that. They're not dead though. I don't think it's fair to pronounce a language like Cobol as dead since there is still so damn much software out there that's written in this archaic language.

The reason there's still many mission critical pieces of Cobol code, or any dying language for that matter, running out there is simply that there are a heck of a lot of legacy systems that haven't been upgraded, rewritten and so on. The reason for that is, in my experience, that most companies are cheapskates.

Rather than invest the time and money in upgrading an ancient system they have their developers spend time on patching the system with horrible work-arounds and crappy add-ons just to keep it going. If anybody were to suggest a complete redesign and rebuild of an existing system somebody close to the company's finances probably would say "Why? It still works, doesn't it?" and shut it down with a suggestion of patching it some more if there are any problems with it.

Pretty much the only thing that'll convince the people at the top of the company food chain that a new system needs to be developed is if the old one crashes and burns completely. When that happens though, the software people are most likely to be blamed for it and having a shiny new software bundle in place and up and running will be something that will be expected of them in a snap more or less.

I really wish that the people handling the money in companies that rely on IT for their business had a little more knowledge as to what IT and software is about and how it works. That way we'd see less and less of things like medieval systems running Windows 3.11 software patched into oblivion, and I can guarantee you that most developers would me happier with putting in some extra hours building something new and exciting than spending their days fixing and working around the short-comings of ancient code bases.

Friday, May 11, 2007

I don't get how some people still have jobs

I don't get how some people still have jobs. Not with the moronic things they think up and say. Like this guy, HBO's chief technology officer Bob Zitter, who probably makes millions every year.

His latest mindvomits are possibly the stupidest things that've been said the past week (I can't be sure though, haven't checked up on George W. Bush in a while). It's already been reported on in plenty of places online (here, here and here for example) and the verdicts are unanimous, the man has no concept what so ever of what DRM is or the kind of problems people have with it.

To him DRM is just some acronym that he's been told will help HBO make even more money. He doesn't give a shit about the crippling and annoying effects of DRM and I'm seriously questioning if he even knows how pissed off the public is with it.

Digital Consumer Enablement, would more accurately describe technology that allows consumers "to use content in ways they haven't before," such as enjoying TV shows and movies on portable video players like iPods.

Wow, that's a load of bullshit so thick and heavy that it can't even be shoveled with an industrial strength shoveling-machine. Way to go Bob. You really are a retard.

Please tell me Bob, about these "enabling" effects. What is it that I can do with the media I lawfully buy that isn't possible without it being maimed by DRM?

I'll tell you what: NOTHING. Absolutely nothing. The consumer doesn't want DRM, you do and only you. DRM, DCE or whatever you call it is a contraption put in place to limit what the consumer can do with the product that he's bought and paid for. It does jack-shit against piracy.

If I was to download an illegal digital copy of a movie I could most likely play that movie in any of my multimedia-devices (Xbox, cellphone, DVD-player, computer, etc.). The same would not be possible with a movie bought and downloaded from iTunes Store for example. It only plays on a select number of devices and using special software. So consequently the only people annoyed with DRM are the ones that obey the law. The pirates don't give a rat's ass, their media is free to play on any multimedia-device with support for the encoding-format of the mediafile.

Many of the most monumental struggles throughout history one way or another have to do with freedom. Somebody wants freedom, while somebody else refuses to grant it to them. This is the very same thing. The consumers want the freedom to use media they've paid for in any way they choose, the media-corporations will not let them.

But believe you me, sooner or later the consumers will get fed up with it and the media-corporations will be the ones suffering losses in revenue and possibly even bankruptcy if they don't get their heads straight in time.

It's time they wake up and realize that the old economical models that have kept them afloat for the past century need to be revised for the digital future, and the sooner the better.

No more DRM. Free all media now.

Oh, and Bob... I hope you lose your job very soon. You sure as hell don't deserve it you idiot. Fuck off.