where are all these starving open source programmers?
I'm not starving (yet), but I'm not too far from it. I've been out of work since early October, and I've begun selling off computer gear to pay bills. I write free software mostly because I'm bored and it's more entertaining than watching TV. Also, it looks better on a resume than an empty space.
If you're reading this and you need a Cocoa programmer - hire me!. I'm in Boston right now, but I'll move anywhere I need to. At this point I'd even work for Microsoft - principles don't pay the rent.
Ever since the term "open source" was first used. The term was invented for the specific purpose of making the idea of open, collaborative development more appealing to businesses who may be put off by the idealogical aspects of the Free Software Foundation.
The "Open Source" and "Free Software" communities may use the same development methodology, but they do so for entirely different reasons.
The problem isn't that a few brain dead applications can screw up the security policy. The problem is that a few brain dead applications are written with the assumption that there is no security policy, and thus are prevented from running when one is in effect.
The word "unsupported" does not necessarily mean it doesn't work. It's likely that it works perfectly well under Win2K, but they haven't yet trained their phone drones to handle questions about using it with Win2K.
You mean like/usr/bin or any other unix system folder?
Now that you mention it - yes. The traditional arrangement made sense twenty years ago, when/usr/bin may have had a couple hundred files in it at most. But these days, we have *nix distros that throw everything *including* the kitchen sink in there, simply because that's the way it's always been done. Tradition can be a good thing - but sometimes people take it to absurd lengths.
python apparently has excellent macos X gui support.
I haven't actually *created* anything using PyObjC, but I did learn quite a bit about the inner workings of the Objective-C runtime by studying the code. I'd go so far as to say that I couldn't have written CamelBones without first studying the PyObjC bridge - there's some stuff in there that I still haven't seen documented anywhere. So, as far as my own limited exposure to it goes, I'd say that yes, Python's support for Cocoa is very good.
I agree with the other part of your post, too - the more options that OS X programmers have, the better. Language bigots need to grow up.
If so, then why even bother with the computer generation, then? At this point it's just being done to please the stats-hungary DM.
For the same reason that Tolkien bothered with creating an entire Elvish language, even though most readers don't care about that kind of thing. The background material, even though it's not something that players directly interact with, helps round out the environment and make it more believable. It provides the foundation for the parts that they do interact with.
Yes, but they only work well with Foundation classes, because they're implemented as a module that gets loaded into a traditional Perl script. AppKit depends pretty heavily on being surrounded by an application bundle, I'm afraid.
CamelBones is implemented as a framework that gets linked into an application, and lets you build your GUI with Interface Builder. On the other paw, it can't be loaded into a standalone script as a module; like AppKit, it requires an application bundle.
The two products are addressing different problems, really; which one will be more useful to you depends on what you want to accomplish.
the documentation is nearly non-existant, unfortunately.
Guilty as charged. All I can say is, I didn't think very many people were interested in it; I can count the daily hits on the project page with one hand. Seems like the interest level is higher than I thought, though, so I'll get off my lazy ass and write more docs, pronto.
You can put a masterlock on the machine to prevent it from being opened.
The padlock itself may be able to laugh at bullets, but the little tab of lightweight metal it's attached to is about two seconds work with a Dremel.
Locking a computer case that way is about as effective as putting a bulletproof window into a cardboard wall. It's the illusion of security, nothing more.
Steve is a smart businessman (especially since NeXT taught him a thing or two)
I once saw an interview with a venture capitalist who said he wouldn't invest a dime in a company unless the founder had had at least two failures prior to starting it. Failing, and learning from the experience, is part of the path to success.
To bring this back at least somewhat on topic, the inclusion of better Rage Pro support in the 10.1.5 release, and the release of the eMac to the general public, is evidence that Jobs has learned from his failures, and is a better CEO for having been through them. The "old Steve" would have stuck to his guns and defended his decisions in these areas to the last. The "new Steve" better understands the price of stubbornness.
Aside from a few vocal, attention-starved whiners who have nothing better to do than move files around and scroll Finder windows back and forth all day, most of the people who have made an honest attempt at using it, have found OS/X's performance to be acceptable for getting Real Work done. It's not perfect, of course - nothing is. But the amount of whining that some people do over trivial issues is pathetic and annoying - thus, flamebait.
Instead of blaming it on the user, why don't you lobby Apple to fix it?
Honestly? I haven't seen the problem. I've heard other people complain about it, but I simply haven't seen it. This is not Steve's, my neighbor's, or my cat's opinion, it's my own, based on my own personal experience, using my Mac daily to make a living.
For one thing, I organize my files, instead of dumping them all into a single folder. Having inherited the maintenance task on web sites where there were literally tens of thousands of files dumped into a single folder, I recognize the value of organization. If your MP3 player requires you to keep all your Jazz files in a folder in order to display them that way, I'd suggest getting a better MP3 player.
For another thing, very, very little of the time I spend using my Mac is spent in the Finder. Like most people who use a computer, I spend my time getting work done, not shuffling files around. If all you do all day is dump a few thousand files into a folder, scroll the window back and forth and move the files around, what are you complaining about? Are you angry because you can't waste your time more efficiently?
If you want to complain, please, complain about real issues that really matter. Ask Apple why the eMac can't be ordered with a DVD-ROM. Ask them why the Finder no longer has labels. Ask them why DVD-RAM disks are read-only in OS/X. Ask them why their RAM is so damned expensive. Ask them why the the iMac only supports mirroring, when the video card it uses is capable of driving two monitors. Ask them why, even though FireWire works great to transfer video from my camcorder in iMovie, I can't use it to download photos from the same device in iPhoto.
I'm no fan boy - far from it. I'll be the first to admit that there are serious issues that need to be addressed. But by constantly whining about trivial non-issues that are easily avoided with the barest minimum of thought and rarely cause problems in the real world, you're helping to divert people's attention from the problems that actually matter.
In other words, it's fast - until you try to use it?
Um... no. In other words, it's fast - unless you're organizationally challenged, and keep every file you've ever worked on in a single folder. If you're going to be dumb, you have to be patient.
Okay, here's another example: id. A well-run company by most accounts, with a solid business plan, a huge fan base, and a history of excellent products. Do they make money from their Linux versions? No, they don't - they've admitted as much. They make Linux versions of their games available as a gift to the community, because John Carmack is a fan of Linux and free software in general.
Instead of just laughing, how about providing a counter example? Can you name a single company that makes money selling packaged software for Linux?
Slashdot Mirror
where are all these starving open source programmers?
I'm not starving (yet), but I'm not too far from it. I've been out of work since early October, and I've begun selling off computer gear to pay bills. I write free software mostly because I'm bored and it's more entertaining than watching TV. Also, it looks better on a resume than an empty space.
If you're reading this and you need a Cocoa programmer - hire me!. I'm in Boston right now, but I'll move anywhere I need to. At this point I'd even work for Microsoft - principles don't pay the rent.
Really? Since when?
Ever since the term "open source" was first used. The term was invented for the specific purpose of making the idea of open, collaborative development more appealing to businesses who may be put off by the idealogical aspects of the Free Software Foundation.
The "Open Source" and "Free Software" communities may use the same development methodology, but they do so for entirely different reasons.
The problem isn't that a few brain dead applications can screw up the security policy. The problem is that a few brain dead applications are written with the assumption that there is no security policy, and thus are prevented from running when one is in effect.
The word "unsupported" does not necessarily mean it doesn't work. It's likely that it works perfectly well under Win2K, but they haven't yet trained their phone drones to handle questions about using it with Win2K.
I want my PHONE to do ONE THING and ONE THING ONLY.
:-(
Make calls.
Heh - me too. Unfortunately the damn thing has a habit of also receiving calls.
You mean like /usr/bin or any other unix system folder?
/usr/bin may have had a couple hundred files in it at most. But these days, we have *nix distros that throw everything *including* the kitchen sink in there, simply because that's the way it's always been done. Tradition can be a good thing - but sometimes people take it to absurd lengths.
Now that you mention it - yes. The traditional arrangement made sense twenty years ago, when
Forget the coffee - at $347, the damn thing better have a blowjob attachment.
python apparently has excellent macos X gui support.
I haven't actually *created* anything using PyObjC, but I did learn quite a bit about the inner workings of the Objective-C runtime by studying the code. I'd go so far as to say that I couldn't have written CamelBones without first studying the PyObjC bridge - there's some stuff in there that I still haven't seen documented anywhere. So, as far as my own limited exposure to it goes, I'd say that yes, Python's support for Cocoa is very good.
I agree with the other part of your post, too - the more options that OS X programmers have, the better. Language bigots need to grow up.
If so, then why even bother with the computer generation, then? At this point it's just being done to please the stats-hungary DM.
For the same reason that Tolkien bothered with creating an entire Elvish language, even though most readers don't care about that kind of thing. The background material, even though it's not something that players directly interact with, helps round out the environment and make it more believable. It provides the foundation for the parts that they do interact with.
Perl-Objc bindings are included in jaguar.
Yes, but they only work well with Foundation classes, because they're implemented as a module that gets loaded into a traditional Perl script. AppKit depends pretty heavily on being surrounded by an application bundle, I'm afraid.
CamelBones is implemented as a framework that gets linked into an application, and lets you build your GUI with Interface Builder. On the other paw, it can't be loaded into a standalone script as a module; like AppKit, it requires an application bundle.
The two products are addressing different problems, really; which one will be more useful to you depends on what you want to accomplish.
Camelbones works pretty well
Thanks, I'm glad you like it.
the documentation is nearly non-existant, unfortunately.
Guilty as charged. All I can say is, I didn't think very many people were interested in it; I can count the daily hits on the project page with one hand. Seems like the interest level is higher than I thought, though, so I'll get off my lazy ass and write more docs, pronto.
using Project Builder and Interface Builder, is, I dare say, easier than writing Perl scripts that call Cocoa functions would be.
Yes indeed it is! That's why I included support for PB+IB in CamelBones from the start - because I hate writing GUI code.
You can put a masterlock on the machine to prevent it from being opened.
The padlock itself may be able to laugh at bullets, but the little tab of lightweight metal it's attached to is about two seconds work with a Dremel.
Locking a computer case that way is about as effective as putting a bulletproof window into a cardboard wall. It's the illusion of security, nothing more.
going to take a coffe and leaving my iBook on my desc...
I'd be far more worried about that iBook getting stolen than getting cracked...
None of the players or their characters will have access to census data, nor will they be particularly interested in them.
Exactly! Why should the DM have to worry about a bunch of boring details that none of the players care about? That's what computer are for.
there is just no way to send a 50MB file once a day in a cost effective manor.
Have you tried burning it to CD and FedExing it?
Steve is a smart businessman (especially since NeXT taught him a thing or two)
I once saw an interview with a venture capitalist who said he wouldn't invest a dime in a company unless the founder had had at least two failures prior to starting it. Failing, and learning from the experience, is part of the path to success.
To bring this back at least somewhat on topic, the inclusion of better Rage Pro support in the 10.1.5 release, and the release of the eMac to the general public, is evidence that Jobs has learned from his failures, and is a better CEO for having been through them. The "old Steve" would have stuck to his guns and defended his decisions in these areas to the last. The "new Steve" better understands the price of stubbornness.
I'd like to know how, exactly, this is flamebait.
Aside from a few vocal, attention-starved whiners who have nothing better to do than move files around and scroll Finder windows back and forth all day, most of the people who have made an honest attempt at using it, have found OS/X's performance to be acceptable for getting Real Work done. It's not perfect, of course - nothing is. But the amount of whining that some people do over trivial issues is pathetic and annoying - thus, flamebait.
Instead of blaming it on the user, why don't you lobby Apple to fix it?
Honestly? I haven't seen the problem. I've heard other people complain about it, but I simply haven't seen it. This is not Steve's, my neighbor's, or my cat's opinion, it's my own, based on my own personal experience, using my Mac daily to make a living.
For one thing, I organize my files, instead of dumping them all into a single folder. Having inherited the maintenance task on web sites where there were literally tens of thousands of files dumped into a single folder, I recognize the value of organization. If your MP3 player requires you to keep all your Jazz files in a folder in order to display them that way, I'd suggest getting a better MP3 player.
For another thing, very, very little of the time I spend using my Mac is spent in the Finder. Like most people who use a computer, I spend my time getting work done, not shuffling files around. If all you do all day is dump a few thousand files into a folder, scroll the window back and forth and move the files around, what are you complaining about? Are you angry because you can't waste your time more efficiently?
If you want to complain, please, complain about real issues that really matter. Ask Apple why the eMac can't be ordered with a DVD-ROM. Ask them why the Finder no longer has labels. Ask them why DVD-RAM disks are read-only in OS/X. Ask them why their RAM is so damned expensive. Ask them why the the iMac only supports mirroring, when the video card it uses is capable of driving two monitors. Ask them why, even though FireWire works great to transfer video from my camcorder in iMovie, I can't use it to download photos from the same device in iPhoto.
I'm no fan boy - far from it. I'll be the first to admit that there are serious issues that need to be addressed. But by constantly whining about trivial non-issues that are easily avoided with the barest minimum of thought and rarely cause problems in the real world, you're helping to divert people's attention from the problems that actually matter.
No mention of updates to the slow-ass finder.
That doesn't bother me any - I have the fast version. Apple keeps the slow-ass Finder in reserve, so they can sell it to idiots.
In other words, it's fast - until you try to use it?
Um... no. In other words, it's fast - unless you're organizationally challenged, and keep every file you've ever worked on in a single folder. If you're going to be dumb, you have to be patient.
No, it hasn't slowed it down any. It's still too fast to keep up with for many tasks.
Or, were you referring to some other "speed problem?"
erm... office v.X is cocoa isnt it?
No, it isn't. What gave you that silly idea?
Okay, here's another example: id. A well-run company by most accounts, with a solid business plan, a huge fan base, and a history of excellent products. Do they make money from their Linux versions? No, they don't - they've admitted as much. They make Linux versions of their games available as a gift to the community, because John Carmack is a fan of Linux and free software in general.
Instead of just laughing, how about providing a counter example? Can you name a single company that makes money selling packaged software for Linux?
I am looking forward to a metal-less iTunes!
Not me! If iTunes won't play my Machine Head rips, I'm gonna be mighty pissed!