Slashdot Mirror
Mac OS X 10.2 Technote Released
Etcetera writes "Apple has released their Mac OS X 10.2 (Jaguar) Technote chock-full of useful information about the API and technical changes in Jaguar. Interested parties will find lots of neat stuff in here... including the idea of storing kernel panic info in NVRAM and writing it to a logfile on reboot."
I've always thought that cursors should be in a vector format and then be scaled to whatever size the user wants.
:)
But then again... no one ever listens to me...
Wiwi
"I trust in my abilities,
but I want more then they offer"
> including the idea of storing kernel panic info in NVRAM and writing it to a logfile on reboot
AIX has done this for years. Another example of what you can do when you control hardware and software.
xinetd is hardly "best of breed" -- it's had one security hole after another.
The original BSD inetd (particularly the one in OpenBSD) is a far more secure program. The xinetd code is REALLY UGLY (look for yourself if you want a real shock).
foo
In order to reduce application launch times, the kernel now maintains information about the working set of an application between launches (in "/var/vm/app_profile"). Pre-heat files are meant to be transparent to the user; however, developers who are constantly re-working their applications may find that their pre-heat files are getting large. The files may become clogged with out-of-date profiles on applications who's versions have changed. As a result, developers may find that it is good to clear out the old pre-heat files on test machines once in a while. To do this, become super-user and do a rm -r /private/var/vm/app_profile and then reboot. app_profile is the directory which contains the profile files. The directory is automatically re-created on reboot. (r. 2847332).
Hmm. Wonder if this will slow down my nightly upgrade of Chimera, Mozilla, etc?
W
-------------------
This is my SIG. There are many like it, but this one is mine.
I never gave Apple's stuff a second thought until OS X ... but bringing up a nice, friendly shell on [splutter...cough] a Mac, of all things, was a mind-bending experience.
Long story short, I waited until 10.2 came out and pulled the trigger on a shiny new iBook. A week and a half into it, I couldn't be happier. Jeez, they even include a developer tools disc. Cool!
Spoken like someone with no experience in this area.
There will never be a major cross-platform GUI application that uses Cocoa. Taking advatange of Cocoa makes your code non-portable. Any major software developer that has a large amount of cross-platform GUI code will have to use Carbon or face rearchitecting their code around Cocoa. Case in point: When Alias|wavefront ported Maya to Mac OS X, they had no need for a 9 version, they had no existing Mac code base to salvage, they were starting from scratch. Yet they ended up using Carbon, not Cocoa. Why don't you go "bitchslap" them, and they can smack you back and explain why using Cocoa for what they are doing is a stupid idea.
Cocoa is the Visual Basic of Mac OS X. It's great for little one-shot tools and utilities, but the big boys use Carbon.
Apple won't stop those widget sets coming to Mac OSX--they'll just get Quartz backends and otherwise behave just like they did under X11. Apple could actually make the situation better by taking control of X11 on OSX, improving it, and standardizing things, as well as by allowing KDE and Gnome to provide native-looking OSX themes.
What this is really about isn't usability, it's about Apple trying to tie developers to their proprietary APIs. But I predict that's a losing battle: Cocoa and Quartz are side shows today--faintly 1980's in their design and without any ground breaking advantage. Most non-Carbon Mac development is happening, and will continue to happen, with C++ wrappers and Java.
Can you name a single X11 app that comes even close to conforming to the Apple UI guidelines?
Gnome, KDE, and many other X11 desktops and toolkits are completely themable and reconfigurable. You can make them look and behave as close to OSX as Apple's lawyers will allow. KDE, for example, already has options to put the titlebar at the top of the screen and choose Macintosh style focus behavior and shortcuts.
The availability of X11 native on OS X would discourage developers from making their applications at all Mac-like in appearance or functionality, leading to less mindshare for Apple's way of doing the GUI.
Yeah, and the lack of availability of X11 just discourages developers, period.
I have heard the arguments before, and my prediction is: Apple is hurting themselves big time by trying to herd developers to Cocoa-based ports. The should celebrate the fact that they have gotten a lot of interest from scientists and engineers and support their (potential) new customers; they can then worry about how to help those new customers and developers to develop Macintosh-y applications using their chosen tools.
Some are just the sort of window dressing we've come to expect like making bash the default shell
/bin/sh because the dynamic modules mean that none of the interactive functionality would be loaded when running basic shell scripts.
I don't see that as particularly being an improvement. They would have been better off updating to a more recent version of zsh. It would make a more efficient
The only reason bash is the default shell on Linux is that it is official GNU shell and nothing todo with whether it is technically any good.
In a bid to win over MS Windows users who up until now have been worried about loosing the registry bloat of their OS, Apple has invented an equivalent that gradually fills up with cruft and needs purging once in a while. Hehe :-D
Try NetBSD... safe,straightforward,useful.
This is a bit offtopic, but is there any projects making use of the ipsec API in OSX to do VPN connectivity? The 'VPN' used in MacOS is PPTP by default, and I would like to integrate an OSX system into the VPN configuration here for free..
XML is like violence. If it doesn't solve the problem, use more.