apple

You are currently browsing articles tagged apple.

Do you remember the 1984 ad from Apple? I've embedded it at the bottom if you haven't. Anyways, the point is that I was trying to download the “free” Apple iPhone SDK today and apparently they require me to sign up first. I thought alright, that doesn't seem too unreasonable. Now I have the sign up form in front of me, and I just don't understand why the following fields are marked as “required”:

  • company: what if I'm NOT in a company? what if I'm NOT using the SDK for work related purposes? what if I just don't want to tell you where I work? Of course I realize I can always make this up, but why does Apple feel the need to pry on my professional/personal life so badly?
  • address: are you going to send me a check in the mail? As long as I'm not involved in a monetary transaction with Apple, they shouldn't be need my address. If they want to geo-localize interest in their SDK, I'm sure they are already doing that by logging my IP address. Again, I can make up an address but that's not the point (besides, I'm sure somewhere in the fine print they will have me click some check box that is a proof of my consent that the information I have submitted is accurate)
  • phone number: tele marketing?

Well guess what, the iPhone SDK is only available for Mac. So much for cross platform development and openness and what not.

httpv://youtube.com/watch?v=OYecfV3ubP8

Tags: ,

I'm sick of Linux being treated like a second class citizen. Hardware and software vendors alike almost proudly display “Supported for PC and Mac” tag lines. Technically, that doesn't even make sense, because both Windows and OS X can now run on pretty much the same hardware. And so can Linux. Even from a market share stand point, I can understand vendors' desires to advertise out of the box Windows support, but the market share of OS X is not substantially greater than that of Linux (specially if you put together all the different distributions).

But most importantly, I think it just being mean to the open source community. Consider the recent Safari announcement. Now it is well known that Safari is based on WebKit which has its roots in KHTML, the HTML renderer originally developed by the KDE community. To its credit, Apple has showed its interest in giving back to the community and WebKit and KHTML developers are collaborating to share their innovations.

But then why does Apple release Safari for Windows and Mac only? WebKit works fine on all platforms (both with GTK and QT) so there's really no good reason. For that matter, what about iTunes? Why isn't there an iTunes equivalent for Linux from Apple itself? Why does it want to alienate so many iPod and iPhone users who have Linux on their desktop? What about keyboards and wireless mice? Or monitors and hard drives and webcams and tablets and microphones? Or any number of the zillions of peripherals out there.

If you read the news, there is no dearth of evidence that open source in general, and Linux in particular, is impacting our daily lives more than ever before. Even if you don't realize it. From embedded systems to mission critical systems, from enterprise systems to the OLPC, from news papers to television stations, Linux and open source are every where. For a comprehensive in-depth article and lots of numbers backing these claims, I highly recommend this article by David Wheeler. How long will we have to wait before vendors finally accept that this is a customer base that they can NOT afford to ignore? How long will the community will have to keep proving itself over and over again that it is NOT a bunch of nerdy hobbyists who have no connection with reality?

Update: Here are some more resources on Linux/open source usage:

Tags: , ,

More and more people are using Mac's for development these days. As an example, a lot of the core developers from some of the leading web frameworks use Mac as their primary development platform. Several plugin and theme authors for Wordpress also develop on Mac. While this is a good thing, there is one particular side effect of this development that annoys me beyond relief.

It seems that the easiest way to archive something on Mac is to right click on your directory of choice in Finder and select “Archive as…”. This creates a Zip file, which then the developer can distribute to users. The problem is that Apple, like many other software giants, tends to twist and bend the user's will and interpret what the user wants to mean something else. In this case, the natural thing for the OS to do is pack up that directory, and ONLY that directory in a Zip file. But no sir, how can that be? How can Apple “transparently” embed some metadata in the Zip file so that if some other Mac user opens it in Finder, he/she can benefit from this metadata.

Apple does this by creating another folder suspiciously named __MACOSX at the root of your Zip archive. Here's an example (its the Cutline theme):

        0  02-02-07 12:37   Cutline 1.1/
    12292  01-31-07 17:16   Cutline 1.1/.DS_Store
        0  02-02-07 12:38   __MACOSX/
        0  02-02-07 12:38   __MACOSX/Cutline 1.1/
       82  01-31-07 17:16   __MACOSX/Cutline 1.1/._.DS_Store
       82  01-31-07 00:12   __MACOSX/Cutline 1.1/._ie6.css
      238  01-30-07 23:59   Cutline 1.1/ie7.css
       82  01-30-07 23:59   __MACOSX/Cutline 1.1/._ie7.css
        0  09-13-06 17:30   Cutline 1.1/images/
    12292  09-13-06 17:30   Cutline 1.1/images/.DS_Store
        0  02-02-07 12:38   __MACOSX/Cutline 1.1/images/
       82  09-13-06 17:30   __MACOSX/Cutline 1.1/images/._.DS_Store
    65705  09-11-06 15:55   Cutline 1.1/images/header_1.jpg
    34365  09-11-06 15:55   __MACOSX/Cutline 1.1/images/._header_1.jpg
    62867  09-11-06 15:59   Cutline 1.1/images/header_2.jpg
    33224  09-11-06 15:59   __MACOSX/Cutline 1.1/images/._header_2.jpg
    82708  09-11-06 16:01   Cutline 1.1/images/header_3.jpg
    34855  09-11-06 16:01   __MACOSX/Cutline 1.1/images/._header_3.jpg
    59780  09-11-06 16:03   Cutline 1.1/images/header_4.jpg
    33555  09-11-06 16:03   __MACOSX/Cutline 1.1/images/._header_4.jpg

This folder contains, among other things, thumbnails for images in the original archive. Now, this kind of unwanted, undesirable outcomes just really really annoy me. But I'll try to keep my cool, and present a systematic analysis of not only why what Mac OSX does is wrong, but also stupid and unnecessary:

  • No surprises: As a user, I don't like surprises, specially of the bad kind. If I request to archive a directory into a Zip file, thats exactly what I want. If I later unarchive that zip file, I should get my original directory back. Nothing more, nothing less. Any kind of unintended behavior is BAD.
  • We are not stupid: If I wanted you to stick in an extra folder named __MACOSX in my archive, I'd let you know. Your users are a smart group, don't insult them like this
  • I hate clutter: In my Wordpress themes directory, I unzip Cutline. If each theme starts creating its own __MACOSX folder, then my themes directory would soon get cluttered with needless garbage.
  • It breaks things: If MacOSX did something harmless, like embed some metadata (like Zip file creator) into the Zip file itself, I might have been OK. But creating an entire tree structure in the archive just breaks things, in ways more than one. As an example, if like Cutline, each Wordpress theme started creating __MACOSX folders in the root of the archive, then later if I install another theme, I'll get lots of errors and file name collissions because the new theme will also try to extract in the __MACOSX folder. Not only this, some programs (like Gallery and Wordpress) have the ability to load plugins/images directly from Zip files. As a result, I'll end up with unwanted images, themes and plugins in my setup. Not only this, it might actually just break your installation. Since you did not create the __MACOSX folder yourself, you don't know what is in it, and it might not always obey the expecations of the software.
  • Security: Again, you did not explicitly create that folder. What if someone creates a virus, that just modifies the default zip program on Mac to sneak in malicious payload via the __MACOSX folders in any new Zip archives you create? Apart from the security risk, its a time sink. Why should I go around cleaning up mess that I did not create? Software is supposed to make my life easier, not harder.
  • Redundant: From the looks of it, it seems that all of the data inside the __MACOSX folder is created from the original directory. No external information is used/needed. If thats the case, why oh why would anyone EVER need this stupid new folder? If some metadata is needed, it can always be reconstructed from the original on demand. This seems downright stupid to me.

Would someone, anyone, please explain Apple's intent and motivation behind this “feature”? What are the benefits (if any)?

Tags: , , ,

As you can see, I didn't blog about the last HoC class largely because I had to leave early for Surtaal practice, but it was a wonderful lecture and I encourage all those who are interested to look at the video/slides. Armando Fox is a great speaker – his slides were both amusing and insightful. I missed Steve's section on Antitrust but I think I've heard that material before from him from the earlier two courses.

Anyways, so for today's class we have none other than Steve Wozniak. He's shorter than I thought. He's not using slides. But he's speaking enthusiastically and passionately, so its really enjoyable just listening to him.

He's basically off on a tirade about his life, which is fair I guess since he had a pretty big role in the development of the personal computer as we know it today (and which happens to be the subject of today's class). His childhood was pretty fascinating apparently. When he was in 5th grade, his dad took him to these technology fairs – so at that early age he already knew about circuits and transistors. By the time he was 12 years old, he was already building simple circuits – for example, he built an electronic tic-tac-toe.

By the time he was in high school, he was so advanced in electronics that his high school teacher arranged for him to take electronic classes at a nearby college. He also started programming in Fortran when he was in high school – probably one of the few kids in the entire world to be programming a computer at that time. One of the first programs he wrote was the Knights Tour.

He then got his hands on the manual for the PDP-8 and fascinated by it, he started designing his own computers. Of course he could never build and test those designs, but still, think about it – a high school kid, actually designing a full-fledged computer!!

He says that by the end of high school, he had designed and re-designed so many computers, and optimized so many existing designs that he was convinced that his designs were more compact and efficient than any other designs out there. He knew that he knew more than what could be taught in any electrical engineering course in college.

He was planning to go to tech schools like MIT for college, but he was visiting Colorado and he was so enamored with the snow there that he decided that he would only apply to Colorado. He was crazy about programming. He cost his first year college a lot of money in computer bills. He had to take a year off after his second year (which he did at De Anza, not at Colorado) working for a company to make enough money to finish college and get a car.

Wozniak met Jobs sometime during his college years. He says Jobs was more “liberated” than he was (in context of the Hippie movement prominent in California at the time). He went to Berkeley for his 3rd year college. They made “blue boxes” using which they could basically tap into the telecom system and make phone calls anywhere in the world without having to pay for anything.

(At this point, the “lecture” really sounds like excerpts from iWoz, not really an academic prose on the advent of the PC from Apple's vantage point. Probably it'll better fit into the lecture as things proceed, but right now its simply an interesting story)

During their Berkeley days, Jobs and Wozniak thought of selling the blue box on campus. So they did some door to door marketing, never got caught and sold a bunch of blue boxes.

Later Woz got his hands on one of the first legendary HP calculators (those which could do non-trivial math – calculus, for example). Woz was later hired by HP as an electronic engineer to work on calculator designs. In order to test his calculator designs, Woz also worked on simulators for the calculators. HP had one huge shared computer to run these testing and debugging routines.

He was a hacker par-excellent – he built a LOT of stuff on his own: he built a pinball machine, he built his own electronic Pong game (complete with TV display and controls). Out of this Pong machine, he designed a keyboard-video interface that was a cheap and better replacement for the expensive teletype machines. Jobs and Woz would later sell this terminal design to a Mountain View based company.

Later he designed a one player Pong game (better called Bricks) in 4 days that he and Jobs later marketed. Recall in those days games were not really like any other program – things had to be hard-wired and stuff had to be coded in hardware. Very little software abstraction.

Woz was part of a “Homebrew” computer club where people interested in microprocessors met and talked about things. Jobs came to Woz saying that they should start a company to build self-contained components – a printer circuit board (PCB) which would have the basic functionality like keyboard input/output, video displays etc. Jobs secured a $50,000 order for their first PCB (morphed into Apple I).

Woz designed the Apple II from scratch. It would be the first low cost small computer with high resolution color display. He infact wrote down the entire BASIC interpreter by hand because he couldn't afford a computer to type it out and compile it in. Jobs basically ran the business side of the company, while Woz led the technical side.

The first Apple ][ didn't have a floppy drive, nor floating point BASIC. So they later worked on a floppy drive controller (in two weeks) but got the floating point BASIC from Microsoft, which Woz says was a big mistake for Apple because it was licensed from M$ for 5 years. Apple also wrote the first “home” oriented application – they wrote a checkbook manager, probably the world's first consumer finance application as well.

Tags: , ,

Nifty! Apple converts Australian mine into iPod

March 28th, 2006 by Diwaker Gupta | 1 comment

« Older entries