Slashdot Mirror
Developer Tools For MacOS X
Vizer writes: "Apple is shipping CDs with the development tools for MacOS X to its developers. Not only that, but the tools will be downloadable in mid-October. Details are on the Apple Developer Connection site. This jives well with what we've been told in the past by Apple, about how MacOS X will eventually ship as two CDs, one of which is just the basic user installation and the other CD full of developer tools.
And yes, developing for MacOS X is very familiar to anyone who has done some BSD programming, except that the paths are all different and HFS+ volumes are case-insensitive. Having the terminal window with access to various unix utilities is great, and nearly all of my un-ported apps run in the compatability environment without complaint. No OS crashes, no problems other than finding out where Apple hid all the preferences and utilities.
No, I don't want to go back."
I was just at an Apple recruiting event yesterday, and they obviously had a demo of OS X. The presenter was also a recent graduate from my college (Carnegie Mellon). Of course, he knew that most of the people in the room were used to Linux and command line interfaces.
:)
To prove that OS X was not just a nifty a GUI, but an honest-to-god POSIX-compliant BSD-based distribution, he opened up a terminal window and proceeded to type in the following:
emacs foo.c
Then, in emacs:
#include
int main(int argc, char **argv)
{
printf("Hello world!\n");
}
^X^C
Then back in the terminal:
make foo
./foo
I think when he did that, the amount of applause that filled the room was the most applause a terminal window has ever gotten
You should never take life too seriously - You'll never get out of it alive.
I still haven't managed to figure out what the differences are between: /usr/bin, /usr/local/bin
/usr/sbin, /usr/local/sbin
/usr because /usr might be on a different partition/disc
/bin,
/sbin,
/bin: stuff essential for system booting (can't be on
/usr/bin: normal binaries
/usr/local/bin: non-distribution binaries (aka non-RPM, non-DEB, etc etc)
/sbin: system binaries (not supposed to be on the average users path), needed for booting
/usr/sbin: system binaries (not supposed to be on the average users path)
/usr/local/sbin: system binaries, not installed via the package manager
--
Ian Peters
We got a copy of the public beta today and installed it. There's an installation option to choose between HFS+ and a "unix filesystem". (I believe it is UFS.) We tested it, and it is properly case-sensitive. So, for those who care to install MacOS X with a sane filesystem, the option is there.
The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...
I am sorry that you got moderated down.
Perhaps a more precise way to phrase your question would be: can anbody present an example of legitimate use of two files in the same directory named identically save for case? I indeed would be extremely interested in such an example, and have never seen one in my life.
There is perhaps nothing more frustrating in using computers than typing "vi makefile" and being presented with a screenfile of tildes instead of the contents of "Makefile". It is unfortunate that the computer is not smart enough to understand what I meant.
Being a VMS user, I like file names which are in all-caps, with one dot, and a version number. The all-caps look makes it look dry and technical (which I much prefer over Unix's cutesy, friendly use of lower case and mixed case)
Windows NT's filesystem with preservation is perhaps the best compromise for most users (and Windows 98's almost-but-not-quite case preservation is not).
Unfortunately, due to the pervasiveness of Unix (e.g. for web servers), most computer users, even extreme newbies, have been conditioned to believe that everything should be case sensitive. There is a myth that it is faster, but it is not: it would be if Unix used a sensible string format, but nul-terminated strings have to go a byte at a time anyways.
With Unicode the mapping of upper to lowercase can be extremely complex, and potentially two file systems or programs would use different algorithims, resulting in very difficult to understand errors and potential security problems.
And there is nothing "user friendly" about case insensitivity. The average user picks a file by clicking on them!
The main reason to use a case sensitive file system is that C is case sensitive, so every thing should be too, god damnit!!
Scuttlemonkey is a troll
OS X natively supports running off HFS+ and UFS drives, and reads and writes HFS and FAT(16, possibly 32) drives. HFS+ is case insensitive, but of course case preserving. You deal with case insensitive file systems just like Mac and Windows people have been doing for the last decade and a half. UFS is case sensitive, like most unix style file systems. It's got advantages for servers, but Classic can't run off it. Carbon Apps can, though. So, use it for servers you don't need to run Classic Apps on, and use HFS+ for desktops for compatibility.
... and someone who may yet go back, I can speak with a little experience here. Apple has a flaky history when it comes to pleasing its developers. I remember back when all it took was a small annual fee, and you had full access to all alpha/beta releases from their ADC site, plus steep hardware discounts. These days, Apple's implemented a tiered system whereby the more you pay, the more benefits you receive, but the more you pay, the lower the benefit/return ratio is.
When I first got in with ADC, I was a starving college student who could barely pay the interest on his student loans, much less pay for the latest and greatest Apple hardware to test the software I was writing (some pretty sophisticated finance software, back before I started consulting in an unrelated field -- if anyone's interested, give me a holler). Here I was, struggling to develop software that Apple's platform desperately needed, and Apple recognized this and subsidized my hardware through ADC. If they hadn't, I can assure you I would've had to give up the ghost and quit my dream.
But what are young developers today to do? Unless you're Adobe or Intuit, Apple doesn't want to hear from you. If you have several thousands of dollars to throw at an upgraded ADC membership, then you're lucky. We're not all so fortunate.
Cheers,
Froid
There is an online petition for Apple to port OSX to x86 here. I think this is something they need to do. Their ability to compete using proprietary hardware which is more expensive than commodity PC's is only going to worsen as time goes by.
They should leverage the PC and gain a portion of its massive market instead of trying to hold on to their own separate market, which is tiny in comparison and progressively getting smaller.
A new OS isn't going to be enough to convince very many to replace their hardware. But offer that new OS for the hardware they already own and you'll have yourself some customers. Customers equal money and market share and Apple needs all it can get of both.
Lee
Muslim community leaders warn of backlash from tomorrow morning's terrorist attack.
I've never understood why so many UNIXheads think case-sensitivity is a GOOD thing. Yes, I'd like the files to have upper and lower case in them for the sake of appearance, but I'd rather NOT have it case-sensitive for matching, etc.
Does anyone have a GOOD reason to have a case-sensitive file system? If so, please enlighten me...
Everything I hear from people is how much they love OS X. Where is everyone else?
/Applications, /System and /Users. Application configuration files and resources all get bundled into one place for each App.
I installed it on a G3 PowerBook with 128M of RAM. I liked it at first. But the more I used it and the more I got into the details, the less I like it.
GUI:
The thing is not fast by any means.
Just minimizing a window into the Dock would use 75% of my CPU.
They got rid of 'window shading'.
The menus - formerly one of the most consistent aspects of the MacOS - lose much of their consistency.
I think the whole Aqua thing is too 'bubbly and sweet' - of course that's just aesthetic, so I won't hold that against them.
Underneath:
It defaults to running inetd, nfsiod, portmap, and a couple of other things. To exacerbate this problem there is no GUI method of turning off these services, and the only command line method is 'kill'. To get these services to not start at boot required hacking config files (after 30 minutes of searching to find them).
They have discarded way to many Unix conventions for my liking. They have come up with their own method of 'controlling' services. They discarded the standard rc format.
They have added all kinds of odd directories like
I could go on, but I think I made my point. I use Unix and Macs and like them both for different reasonse. OS X is not Mac enough nor Unix enough for me to like it at all.
I just don't think Apple get's it . . . hopefully they'll get a clue.
If anyone has a MacOS (7-X) system up and running already and wants some tools right now, they can follow the instructions from MacAddict on how to copy the Darwin versions of g++ and company over to MacOS. For those interested in other BSD apps on OS X, keep an eye on MacAddict's Ports page.
Recursion (n): See recursion
Apple is not a company I can morally approve of... I cannot use without feeling dirty.
...and goes back to his Debian GNU/Linux machine
what a terribly small world you must live in when your morality depends on giving away 100% of your property. Out here in reality I can give a meal to a homeless person and not be decried evil because I didn't give him my refrigerator, and I can give a hundred buck to the MDA and not be accused of immorality for not handing them my bank account. Does the homeless person feel dirty because I only gave him a sandwich? Does the MDA feel dirty because I haven't quit my job and volunteered full time? Of course not!
Apple giving back to the FreeBSD community isn't good enough for you types. Opening up (also known as freeing) other of their own code isn't good enough. It seems you want all or nothing. Well that's not how the world works. If you don't like it, then don't use it. But don't call them immoral or their users dirty. The real immorality is your self-righteousness. Listen, there is a lot more to morality then your petty licensing issues.
It's not the ownership of their software that concerns you, because every software except public domain is owned. Even the FSF copyrights their own software. It's not that, it's just that you haven't been given the number of permissions to use the code that you would like. There's nothing wrong with that, it's just a price that you (and I) don't want to pay. But don't call it a case of morality. That's just bogus.
How did I know that was coming?
A Government Is a Body of People, Usually Notably Ungoverned