Hacking Mac OS X
Bill Hamm writes "DB is carrying a deep interview with Jonathan Rentzsch, who created an open source technology to allow other developers to inject their code into any running process to alter its functions and written papers for IBM to program the PowerPC correctly. The interview is huge and technical, and all over the place in terms of content. Some of the things discussed are the reasons for corporate America's resistance to buying from Apple, software optimization, the importance and history of 10.4's Core Data, why WebObjects is no longer relevant, the status of PowerPC compilers, and why Mac OS X's Finder should be killed off."
I wouldn't be surprised if Core Data apps don't get AppleScriptablity for free-to-cheap circa 10.5.
Seems like this is the promise of Automator - once every app can understand Applescript, every app can interact with every other, without the user.
concrete5: a cms made for marketing, but strong enough for geeks.
Ok feel I feel I need to address this.
1) I use my iBook everyday in my "corporate America" Job
2) 'Mac' is not a company
. Error messaging was minimal ("sad mac"? please.)
3) the 'sad mac' was to indicate a hardware failure of some type, and it gave a diag code to lookup. Im not sure what kinda of failure code you are looking for from the built in ROM software. Perhaps you would like a blue screen filled with unintelligible register contents?
4) Ejecting a disk, well then I ask should there have been a separate 'eject media' icon?
5) One button mouse. Dont like the mouse go buy a 2 button mouse. they work just fine. However i get the distinct impression you dont use a mac anyway.
6) Auto sizing windows: this behavior is a personal preference, Some windows I want large, some not. Based on your previous comments you seem to be upset that Apple makes some choices for the user that are personal preferences, but when they dont make this one you are upset about that also.
Mac offered compatibility with windows networking very late in the game
7) Im not sure im getting the point of this one. If the complaint is that Apple (see #2) didnt add windows file sharing until osx, this seems to miss the point of this screed about 'Corporate America'. From a corporate network POV, the server is supposed to be set up to talk to the clients, the clients have no onus to be peer to peer compatible with other clients, otherwise you lose the central control that is predominant in the corporate arena. Of course to be fair you would also have to complain that PC work stations haven't added any non MS windows compatibility.
I can only assume by your context that you mean wintel x86 as corporate workstations, so I have to base my comments on that assumption. I suppose its possible you mean some stripped down unix workstation from like 1998.
You claim to 'like' macs, but your things you dont like seems to be picayune at best. For all of these things that you believe that would get in the way of your 'corporate' workflow, it seems as if you have never tried to do such a thing to begin with.
I feel that you are using this 'corporate' thing as a bag you can fill up with a bunch of complaints and use it to bolster your beliefs.