Skunkworks At Apple -- The Graphing Calculator Story 642
avitzur writes with a link to the story behind the Macintosh Graphing Calculator. An excerpt from this strange account: "It's midnight. I've been working sixteen hours a day, seven days a week. I'm not being paid. In fact, my project was canceled six months ago, so I'm evading security, sneaking into Apple Computer's main offices in the heart of Silicon Valley, doing clandestine volunteer work for an eight-billion-dollar corporation."
EA? (Score:5, Funny)
Re:EA? (Score:5, Interesting)
I was dating a high school math teacher at the time, but, unsurprisingly, the relationship did not survive the events of the story.
Re:EA? (Score:5, Interesting)
At first, I was unimpressed. However, as soon as I saw it animate I was blown away. Of course, when I saw the plane intercept of a 3D function animated, I was visibly giddy.
I so wish I had this while in my vector calculus course. In fact, I think I might stop by former professor's office when school is back in session and show him.
As soon as your site recovers from this merciless slashdotting, I think I might pick up version 3.
And again, wow.
Re:EA? (Score:4, Insightful)
Re:EA? (Score:4, Insightful)
The 2 QA guys volunteered from September to October. Then they were assigned to the project officially in October, as were usability folks (who have a usability lab at their disposal). The story doesn't specify how many QA people were assigned, so maybe it was more than 2.
They also got free prototype hardware to develop on that made their app run 50 times as fast as it did on regular, publicly available hardware.
They shipped in January, so that's 1 month of 2 QA guys' free time, versus 4 months of full time QA, and an unknown amount of usability assistance.
This could certainly be made available to an open source project as well, of course. But don't overlook the big increase in resources that the project got when Apple managers decided to officially support it.
This is the leap that companies need to start making with open source, both in visualizing how it was made, and in investing in it. It isn't always a nights-and-weekends hobby project; sometimes it's a full time project with lots of people being paid to work on it. The fly-by-night image is one that Microsoft really, really wants people to believe, so they can say stuff like "there's no QA" or "there are no real releases" and make people scared to buy anything but Microsoft's incredibly high-quality, bug-free code. *cough*
And this is the kind of zealous insanity (Score:4, Interesting)
There will always be an Apple Computer.
Re:And this is the kind of zealous insanity (Score:5, Funny)
Re:Sadly, his company now distributes nagware (Score:5, Informative)
Re:EA? (Score:4, Funny)
Somehow, I don't think that will be a problem around here.
Article Text without silly next buttons (Score:3, Informative)
I used to be a contractor for Apple, working on a secret project. Unfortunately, the computer we were building never saw the light of day. The project was so plagued by politics and ego that when the engineers requested technical oversight, our manager hired a psychologist instead. In August 1993, the project was canceled. A year of my work evaporated, my contract ended, and I was unemployed.
I was frustrated by all the wasted effort, so I decided to uncancel my small part of the project. I had been paid to do a job, and I wanted to finish it. My electronic badge still opened Apple's doors, so I just kept showing up.
I had many sympathizers. Apple's engineers thought what I was doing was cool. Whenever I gave demos, my colleagues said, "I wish I'd had that when I was in school." Those working on Apple's project to change the microprocessor in its computers to the IBM PowerPC were especially supportive. They thought my software would show off the speed of their new machine. None of them was able to hire me, however, so I worked unofficially, in classic "skunkworks" fashion.
I knew nothing about the PowerPC and had no idea how to modify my software to run on it. One August night, after dinner, two guys showed up to announce that they would camp out in my office until the modification was done. The three of us spent the next six hours editing fifty thousand lines of code. The work was delicate surgery requiring arcane knowledge of the MacOS, the PowerPC, and my own software. It would have taken weeks for any one of us working alone.
At 1:00 a.m., we trekked to an office that had a PowerPC prototype. We looked at each other, took a deep breath, and launched the application. The monitor burst into flames. We calmly carried it outside to avoid setting off smoke detectors, plugged in another monitor, and tried again. The software hadn't caused the fire; the monitor had just chosen that moment to malfunction. The software ran over fifty times faster than it had run on the old microprocessor. We played with it for a while and agreed, "This doesn't suck" (high praise in Apple lingo). We had an impressive demo, but it would take months of hard work to turn it into a product.
I asked my friend Greg Robbins to help me. His contract in another division at Apple had just ended, so he told his manager that he would start reporting to me. She didn't ask who I was and let him keep his office and badge. In turn, I told people that I was reporting to him. Since that left no managers in the loop, we had no meetings and could be extremely productive. We worked twelve hours a day, seven days a week. Greg had unlimited energy and a perfectionist's attention to detail. He usually stayed behind closed doors programming all day, while I spent much of my time talking with other engineers. Since I had asked him to help as a personal favor, I had to keep pace with him. Thanks to an uncurtained east-facing window in my bedroom, I woke with the dawn and usually arrived ten minutes before Greg did. He would think I had been working for hours and feel obliged to work late to stay on par. I in turn felt obliged to stay as late as he did. This feedback loop created an ever-increasing spiral of productivity.
People around the Apple campus saw us all the time and assumed we belonged. Few asked who we were or what we were doing.When someone did ask me, I never lied, but relied on the power of corporate apathy. The conversations usually went like this:
Q: Do you work here?
A: No.
Q: You mean you're a contractor?
A: Actually, no.
Q: But then who's paying you?
A: No one.
Q: How do you live?
A: I live simply.
Q: (Incredulously) What are you doing
Re:Article Text without silly next buttons (Score:5, Insightful)
Or did they do it because they could? One of the things that so many Free Software users overlook as they use the software they didn't pay anything for is that OSS is more than about just getting stuff without paying, it represents the right for someone to write that code. Imagine a world where if you didn't legally work for Apple, you couldn't write a program for their computer. If you weren't a licensed and regulated programmer, you wouldn't be able to develop your own software or develop software for other people.
With signed code initiatives like TCPA/Palladium, that world could be coming to a planet near you soon.
Re:Article Text without silly next buttons (Score:4, Funny)
then it's just the pits for mars, isn't it... we should recall the rover as soon as possible.
Re:Article Text without silly next buttons (Score:5, Informative)
The 'extension' of which you speak is equivalent to the file extensions under dos, like
The only reason you had to 'register' an extention with Apple was so other applications could know, for sure, what kind of file an extention represented. There is nothing to stop anyone from using any code they desired, just as there is nothing to stop me from naming a file with an ending like '.dll' under dos/windows... it just isn't a prudent thing to do.
Re:Hehe (Score:4, Interesting)
That's where I have an issue with how copyright is enforced. Copyright was written in such a way so that after a given period of time, the work passes into the public domain. DRM effectively prevents that. In my opinion, if you want to require a licence/contract to view your work, then your work should no longer be protected by copyright law. In effect, you should have to choose between contract and copyright protection for your product.
Sheesh.. (Score:5, Funny)
Wouldn't you just know it.. the one place Microsoft has effective security is the place that keeps people from doing something useful.
Dedication (Score:5, Interesting)
- dshaw
Re:Dedication (Score:5, Insightful)
It is one thing to for a person or three finish a project out of love without expecting a reward. Key words "a project".
It is FAR different for a company to expect that level of work in a non-ceasing manner from their entire dev staff, knowing full well that it destroys mental and social health.
Not to mention the difference in stress level when you're volunteering that level of effort versus being chided in the hopes of squeezing out even more.
I've worked in both situations. One is a suite kind of pain, the other is an intense kind of anguish.
Well, two big reasons for that (Score:3, Insightful)
2) Many of them like to trumpet their software as better than closed source. K, great, but it'd better be good then and part of that is fixes and updates. Firefox is a good browser, however if they decide they don't need to patch it, and it gets secur
Re:Well, two big reasons for that (Score:3, Insightful)
Yes you can. OSS is a better model that usually puts out better software in the end. But part of that approach is a stage where the software is not yet done and still needs testing, bug fixes, and features. And sometimes it is not clear where in the process a given projec
Re:Well, two big reasons for that (Score:3, Insightful)
How recently have you read the EULA on most commercial software products?
What bugs are fixed, and under what kind of time frame? Who decides? You? No way. You are subject to THEIR priorities, which means that some bugs may be overlooked entirely, merely because the ROI isn't high enough.
You may not have the expertise to fix the bugs yourself, but I know from my own experience, we had a problem with a commercial software package whose recent upgrade not o
Re:Dedication (Score:5, Insightful)
Although there are people that do expect fame/ power from open source, a lot of them do the work because they like to do it. But do not blame EA employees, I would never do such work any any For profit company in my life unless they paid me more.
The first one is giving, the second one is being moronic....
Re:Dedication (Score:5, Funny)
Microsoft Security? (Score:5, Funny)
I hear you can use Internet Explorer and ActiveX to get around any Microsoft security...
Re:Microsoft Security? (Score:5, Funny)
In order to get into the building, I had to use the phone outside the door to call upstairs to my friend who then came down and let me in. (Five-digit extensions starting with 2.) Or you could just follow somebody in, but watch out, the building I went into has double sets of doors, and you have to swipe your card at both sets. And there's a receptionist inside who had to be distracted...
Once you're in, you're in. If you look vaguely like you belong there, nobody's going to raise a stink. It helps a LOT to wear an old T-shirt and jeans, the standard MS business suit. Wander in and out of offices nobody's in, load up your backpack with cool stuff lying around. Stop by the kitchen and pick up some free soda. (Well they don't have that anymore, I guess...) Play a game of pool or Donkey Kong.
If someone does challenge you, tell them the connector you're writing is driving you insane, and do they want to pop out for Chinese?
And definitely swipe 50 of those "Microsoft Confidential" CD-R's.
Sometime that evening, I notice the building seems a lot dimmer than it was before. When I got outside I noticed Microsoft Security driving around, stopping in front of a building, and pointing some sort of remote control at it. He pushed something, and most of the lights in the building shut off. I STILL want one of those remotes.
I got in my car, drove back across the lake, and hightailed it up I-5 to Canada...
Re:Microsoft Security? (Score:5, Interesting)
Just setting straight some of your inaccuracies
Internal numbers are accessible via the last 5 digits on an internal phone, but not all (or even most?) start with 2. Or maybe you're trying to get your friend in trouble?
If you tailgated in years ago, that may be true. These days, good luck tailgating if you're not known by the person you're following, even if you have a valid badge. Also, while all buildings have a double set of doors (access to the lobby from outside, and access to the inside from the lobby), the outside doors (into the lobby only) are unlocked during business hours. Good luck distracting the secretary (or more likely, secretaries). You'll need more than one accomplice to do that for you (they're really not busy enough for you to bank on random traffic, and even when they are busy they have a clear view of the doors and will stop you from tailgating), at which point you could just get a valid visitor's pass instead.
Cool stuff generally is not just "lying around", unless you want posters and such off of the wall. Everything else is in a locked lab or occupied offices, and in the latter case anything you could easily get away with is personal property. Do you feel good about stealing from people? (ignoring that you're suggesting stealing from a company)
The free sodas are still there.
If that's your goal, you need to have good inside sources. Entertainment items vary from building to building and floor to floor. If your heart is set on Donkey Kong, you'll be disappointed to find only Street Fighter 2 if you didn't do your research (and that's not publicly available, or even easily internally available aside from visiting every building).
Which are not sitting out in plain view, if available at all in that building. If it's software available to all internal employees (for example, connection manager software to connect to the VPN from home), you have to get it from the receptionist. If it's for a product group, it's either locked up in the lab or in the group admin's office (or more likely, not available in CD form, but on an internal share you'll not have access to). Either way, don't expect to find piles of booty just laying around.
I've never seen that, but most buildings are on a timer to shut off lights (not power) after a certain time of night. There are internal overrides if you're still working.
There's a good chance your car would've been towed if you weren't showing a valid parking pass or visitor's parking pass. And if you drove back across the lake to get to I5, you wasted a whole lot of time sitting in traffic on the floating bridges (I90, SR520). If Canada is the goal, better to take I405 up around the lake and meet I5 there.
Re:Microsoft Security? (Score:5, Interesting)
Re:Microsoft Security? (Score:5, Funny)
He's probably on the ActiveX team and not really used to the concepts of "security" and "secrets".
Re:Microsoft Security? (Score:4, Insightful)
Re:Microsoft Security? (Score:3, Interesting)
There's also an I-405 in Oregon, running through downtown Portland.
But this is all off-topic, so I'll take my karma hits now.
Re:Microsoft Security? (Score:3, Funny)
Working for no pay... (Score:4, Funny)
I like this line (Score:3, Insightful)
Re:I like this line (Score:5, Insightful)
I have to agree with that. I've solved many of my problems by IMing a friend. I might not know how to do X, but PersonA does, and he can shave a few days off of my learning curve by sending me in the right direction when I get stuck.
Sadly, some of my employers have had "no instant messaging" policies.
Re:I like this line (Score:3, Insightful)
Opensource plays this card a lot. One of the best ways to earn favors is by giving favors. If you write some cool code and give it away then people who use it will often be willing to return favors of one kind or another back to you. The fact that copying is easy in the digital age, the horror of
Heh (Score:5, Funny)
We wanted to release a Windows version as part of Windows 98, but sadly, Microsoft has effective building security.
Too bad that security didn't translate to other areas...
Re:Heh (Score:5, Funny)
I heard that if you issue any sentence longer than 1024 characters to the first guard, he'll obey any command you give after that.
For the second guard, keep shift pressed before he sees you and he won't notice you.
what do EA employees think of this? (Score:3, Interesting)
Recently there have been a number of slashdot postings related to the conditions of working for EA (can't recall the exact URL, but summary best described as "slave-labour like"). I wonder what those folks think of this level of dedication?
On another note, it was a nice holiday feel-good read for the techno-geek developer. Also inspires me to finish the damn project that I am on right now so that I can "be home for Christmas".
Happy Holidays!
Re:what do EA employees think of this? (Score:4, Insightful)
Now if I was forced to do that to get some rod mill in PA up and running on short notice because management screwed up and set a poor schedule, I'd be pretty pissed about it, and those hours would get mighty long mighty fast.
These guys wer working out of love (or insanity, you decide). That makes the long hours a lot more palatable...
Re:what do EA employees think of this? (Score:3, Insightful)
Re:what do EA employees think of this? (Score:3, Insightful)
I submit that all free men can make their own choices. That includes working on an educational tool because you want to see it shipped, fully recognizing the possibility of failure (and indeed with trespassing charges, jail time).
He did this of his own will. If you don't understand that, you will never understand greatness; most great men and women have pushed like this in their fields of art, science, industry and technology.
--
Evan
An engineer's dream (Score:5, Insightful)
The only downside was not getting paid, but even that seemed to work out.
But Apple was flailing at the time (Score:3, Interesting)
Re:An engineer's nightmare (Score:3, Insightful)
So typical company cancels the product while it is selling, and at the same time invests 100m+ into take overs t
Re:An engineer's dream (Score:4, Insightful)
Re:An engineer's dream (Score:3, Insightful)
If you have debt/family/etc to pay down then free work doesn't make sense. But if you've saved up enough to live a year or two without working I don't see the harm.
Tom
Re:An engineer's dream (Score:5, Informative)
No. There was a line in the story that got dropped on the editing room floor. I was offered a job as an employee on a new project when the old project was cancelled. I just wasn't interested in the new project. I prefered to be working on educational software.
Re:An engineer's dream (Score:4, Funny)
Good job, you will probably get security fired (Score:3, Funny)
Good job, Steve will probably hear about this tomorrow and start firing people working security.
Re:Good job, you will probably get security fired (Score:5, Informative)
Re:Good job, you will probably get security fired (Score:5, Funny)
Do you really think that little details like that can stop Steve's rage?
Re:Good job, you will probably get security fired (Score:3, Funny)
Well as Steve wasn't actually working there, he would probably be more annoyed that those guys weren't sneaking into his corporate headquarters and writing code for NeXTStep. It probably would have doubled the number of computers he sold, which really wouldn't have been all that hard.
Re:Good job, you will probably get security fired (Score:5, Interesting)
Re:Good job, you will probably get security fired (Score:3, Interesting)
Programmers: Please note. (Score:5, Insightful)
Sitting behind a two-way mirror, watching first-time users struggle with our software, reminded me that programmers are the least qualified people to design software for novices.
Re:Programmers: Please note. (Score:5, Interesting)
It makes some decisions about how to do things a whole lot easier...
Re:Programmers: Please note. (Score:5, Interesting)
Years ago when we developed a replacement CRM application for a large telco ISP, we did something unheard of - we integrated the customer service reps into the development process. At first we shadowed them for days to get a feel for how they use the existing application, and interviewed them to see what they liked and disliked. Then we invited at least one rep to every design meeting. During development they were constantly reviewing the work, making sure it was perfect. They almost cried they were so happy.
As an aside: their number one complaint was when they were doing data entry on the very long web form, they constantly had to take their hand off the keyboard, find the cursor, position it over the scroll bar, scroll the page down, then position the cursor over the text field, and resume typing. Tabbing took care of some text field focusing, but wasn't intuitive and predictable enough even when combined with javascript. We broke the data entry into multiple pages with simple navigation. I really miss the old days of character-based terminal applications (so do a lot of end users).
Re:Programmers: Please note. (Score:4, Insightful)
Smart companies do custom development by involving the end users in all steps of the process.
Stupid companies off-shore development to somewhere as far away from the end users as possible and think they are saving money by doing so. All they end up doing is shifting the cost from the development group to the end users, often multiplying those costs by an order of magnitude.
Re:Programmers: Please note. (Score:3)
I was the person that the maestro sent the problem people to - the shy ones, the ones with agression problems on both ends (too much and too little), etc. This was largely because of my background, teaching style, the fact that he'd known me be
Filled with Gems (Score:5, Informative)
classic...
I liked this line the best (Score:5, Funny)
Someone should write a novel about this.
Obligatory (Score:5, Funny)
Wow (Score:3, Interesting)
I don't own a copy of OS X, but is this application still on there?
Re:Wow (Score:3, Informative)
Re:Wow (Score:5, Informative)
It is available for OS X now. You can download the free release from http://www.PacificT.com/FreeStuff.html [pacifict.com] (Well, at least you will be able to after the server recovers from the Slashdot Effect.
Re:Wow (Score:3, Funny)
Can't legally volunteer (Score:4, Interesting)
-russ
p.s. R0ML says that this is why he couldn't get a carrier-grade accounting system turned into open source.
Re:Can't legally volunteer (Score:3, Interesting)
The trouble with enforcement is that it is the "intern" who must file the complaint with the Department of Labor. Only the person exploited can do it, nobody else can. And when you are working for nothing, what you are really working for is a good reference, so you will not do anything that will remotely piss off your "employer".
A while back I tried to report
All too true... (Score:4, Insightful)
I really wish more programmers, engineers, and managers understood this.
Re:All too true... (Score:5, Funny)
And I wish first time users weren't so flipping clueless
Re:All too true... (Score:3, Interesting)
It does makes sense though. A regular mirror only reflects light on one side.
Is this the explanation behind OSX graphing calc? (Score:3, Informative)
This would explain it nicely, or at least, provide more romantic one than a plain old easter egg.
Re:Is this the explanation behind OSX graphing cal (Score:5, Informative)
Find the Calculator icon in the Finder, and select "Get Info" (or press Command-I after clicking on the calculator). In the plug-ins section, select the "Add" button, and in the resulting file dialog, browser your way to the Calculator -> Contents -> Resources. Select any/all of the *.calcview directories, and press "Choose". Presto -- open the Calculator and select the "View" menu item, and your new plug-in views will be available.
Now for the caveat. Ever since one of the 10.3 updates (10.3.3 maybe?), none of the plug-ins work anymore. But in the event they ever fix this, you now know how to activate different view modes.
I doubt that the graphing capability built into the calculator has anything to do with the Graphing Calculator application, as the one built into the regular Calculator is supposedly 2D only, whereas the Graphing Calculator supports 3D graphs as well.
Yaz.
Ron Avitzur's Demo @ WWDC (Score:5, Interesting)
Anyway, I remember it was supposed to be a lecture about pen computing, and Apple had Ron come out and show the equation solving interface of the proto-graphing calculator. He threw a bunch o' X and Ys on the screen with some sins and coss for good measure. "Now if you want to solve for X"... and he tapped an X, dragged it to one side of the equals sign, and the equation solved itself.
We were floored. There was this deep silence for a couple of millisenconds and then everyone broke out in thunderous applause. He did more tricks with the equation interface and people hooted and hollered. It was a geek wet dream. After he finished he got a standing ovation and there was a long line of people who wanted to shake his hand.
Good times.
Re:Ron Avitzur's Demo @ WWDC (Score:5, Interesting)
Kinda like the beginning of Quartz at a meeting of engineers when "Engineer X" speaks up and says "you know, instead of using the CPU to render all of this 2-D stuff, we could use the GPU............." This statement was followed by a long pause while the implications of this statement sunk into everybody's wetware (brain) only to be followed by a quiet "sunofa....." by the senior project manager.
Of course Microsoft is busy co-opting this idea which has been shipping now with OS X for a few years but, what else is new?
Re:Ron Avitzur's Demo @ WWDC (Score:5, Informative)
Either way, I'm not so sure the UI acceleration thing was a blinding flash of the obvious, I think it was more hardware needing to get to a certian point. It wasn't until about mid 1999 that a card (TNT2) existed that even had the basic 3d capibility to do what would be needed for a user interface. Even so, at that level, all you could really do was make a window a big texture stretched on a polygon. Neat, but faily useless.
Real useful UI acceleration didn't become feasable until cards became Graphics Processing Units in fact, which means some programability. The GeForce 3, which came about in 2001, was the first consumer level card that could be really considered for that.
So I don't think it was an idea that really had to think in. I remember hearing people musing about using the Voodoos for UI acceleration (and having those more knowledgable tell them why that wouldn't work), I think it was just a matter of the hardware advancing to a point where it was sufficiently useful for things other than playing games.
Re:Ron Avitzur's Demo @ WWDC (Score:3, Informative)
2D is just 3D with some constants in the matrix. No, really.
Bravo! Bravo! (Score:3, Interesting)
I've worked in a big company like Apple in the past and with the right people this just shows how far someone can really go in the most ideal situation. (not really needing a job in the short term)
Good Job Ron!
Red stapler, anyone? (Score:5, Funny)
"They fired him, but he doesn't know it. He just comes in every day and works."
(And despite Milton's, ah, interesting character traits, I find him the coolest character in the show; or perhaps it's because of them. So, I mean this in the most praiseworthy manner possible. Rock on!)
Testament to Apple's luster (Score:5, Insightful)
Re:Testament to Apple's luster (Score:3, Informative)
Re:Testament to Apple's luster (Score:3, Interesting)
Golly... (Score:3, Funny)
Hire the guy (Score:5, Insightful)
I love the last line (Score:5, Funny)
My Best Project was a Skunkworks Job (Score:5, Interesting)
Back in the 80s I was part of an IT group in a manufacturing dept at Tektronix. Our software involved inventory control, tracking batches of work through assembly steps, that sort of thing. One of the computer operators asked if I could help him solve a problem for the stockroom people. Their job was to hand out parts to assembly workers, receive and store the finished subassemblies and hand them out for additional steps until they left the area as finished goods.
All movement of material was tracked by a giant MRP system on an IBM mainframe in another building. The IBM machine generated stacks of PUNCH CARDS which were delivered to our computer room and loaded into our VAX 11/750. As the stockroom people handed out and received material, they had to manually keep track of what they did, noting shortages and errors. Then they entered the information into the 750, which wrote it nightly to a tape that was hand-carried back to the building where the IBM system was.
The stockroom data entry program was very cumbersome to use. It simply did a one-way scroll through the entire inventory -- thousands and thousands of parts and subassemblies -- and allowed the user enter a code on the few items that mattered. To get to an item near the bottom, the clerks had to hit the Page key dozens of times and wait for the slow page refresh in between. Sometimes they would hold the Page key down for a while and go away until it caught up. If they overshot they had to start over because there was no Back function. The stockroom people spent most of their time doing data entry and were consistently several weeks behind, which forced them to come up with various manual ways of keeping track of things. This affected their ability to hand out parts and was starting to have an impact on manufacturing deadlines, and ultimately profits.
In spite of the importance of the situation, the stockroom was low on the IT priority list. So we had a couple clandestine meetings in which the staff told me how the business end of the system worked and the computer operator explained the behind the scenes parts. Working a couple hours a day on the sly for about 2 weeks, I came up with a new data structure and an editor that let the users search for what they wanted and produced various on-screen reports. I also changed the loading procedures to use a tape instead of the stupid cards, and my operator friend persuaded an IBM sysop to bypass the change control process and generate a tape for us instead of cards.
When the users were satisfied with the way everything worked, we put it into production one afternoon as the swing shift person came on duty. In that one shift she cleaned up their entire 3-week backlog of data entry. When the morning people arrived they were speechless. With the extra time they now had, they set about reorganizing their operation and making improvements that they had wanted to do for months.
It was amazing to see what this change did for the morale of these people. Their jobs had been absolutely miserable when they had to work with the old system. They were so happy they brought me a great big apple pie, and were almost in tears giving it to me. Best award I ever got.
Graphing calculator was an insanely great app (Score:4, Interesting)
Apple squandered a great opportunity in the 90's. Macs were much faster than many Sun workstations with the kind of work we did (computational fluid dynamics), much cheaper and ran a broader selection of applications. Despite this Apple knew nothing about the scientific market. I remember going to a seminar at MacWorld Boston in 1996 on scientific uses of the Macintosh. None of the presenters talked about how a PowerMac 7500 with a 3rd party 604 accelerator smoked a Sparc 20 for about 33 percent of the price. Instead they talked about how they could use a Mac to model the behavior of a lobster. I felt as if I was in crazy world, here was Apple with this insanely great line of CPUs and they basically ignored a market that would have gone for it lock stock and barrel.
Things have gotten better since then and I have been pleased to see that Apple is targeting bioinformatics applications with the Xserve, but they're going to have a lot of work ahead of them to keep up with Linux's inroads into the market.
This Program Changed My Life (Score:5, Interesting)
For me, at least, seeing things in motion (that nifty little value slider) made the concepts just click. Once they were there, the actual mathematical manipulation was much easier, because I was able to visualize "they way this should work out". My teachers were trying to show it on a static chalkboard, and it just wasn't getting through.
I just got my BS in Physics, and without Graphing Calculator, I doubt I'd be where I am today. To the author, if he reads this:
Thank You.
Re:This Program Changed My Life (Score:5, Interesting)
Re:This Program Changed My Life (Score:4, Interesting)
PowerCalc (Score:4, Interesting)
You can download Powercalc.exe [microsoft.com] from Microsoft's XP PowerToy page [microsoft.com].
Re:High Praise For Mediocrity (Score:5, Interesting)
Actually there is only one person preventing a multibutton mouse, unfortunately no one outranks him. He won't even allow a build-to-order option when you are ordering online.
Re:High Praise For Mediocrity (Score:5, Insightful)
And I'm still suffering from the torture he inflicted when I dared to use the scrollwheel.
I can't imagine what he did to the Mac OS X engineers when he found they'd built full support for multiple buttons and into the OS, or the fact that all their iApps - iTunes, iPhoto - support full functional scrollwheel movements.
Hmm...
Or maybe's it's because Apple's QA people know that best way to have software designed to be easy to use is to not encourage them to use right-click kludges. It is impossible to use a Windows machine without a two button mouse and learning context menus. That is not true of Mac OS X.
Re:Score Chart (Score:5, Insightful)
So what, its not like lots of people or hours translates to quality. Look at shareware in general, look at MS. There is only a very small core of people that have made Linux useful. Few people can read source code, fewer still can write working code at all, fewer still are able to write good code.
Re:Slashdotted already (Score:3, Funny)
Re:motivation same as OSS (Score:3, Insightful)
You think there is something new about writing code for free and sharing it with others? It predates "open source", it predates Linux, it predates GNU,
In
Re:PovRay. (Score:5, Interesting)
Re:The real story (Score:3, Insightful)
Re:formatting (Score:3, Interesting)
Re:This sounds like a Wired story (Score:5, Informative)
Now, should you see anything similar in some upcoming release of some unspecified operating system, check to see whether it's the real deal (Graphing Calculator from PacificT http://www.pacifict.com/Gallery.html [pacifict.com]), or something else.
Re:RMS on Hacking and the Graphing Calculator (Score:4, Interesting)
Remember that my software's users are primarily high school students or younger.
An open source release would cause the existing revenue stream to vanish, making it impossible to continue to support existing customers or maintain and develop the code base. Pacific Tech has provided free support for its customers and would like to continue to do so, and continue to maintain the product on Mac OS and on Windows. The reason GC is useful is the ease-of-learning and ease-of-use of its user interface. I do not know of a product which demonstrates the open source community's ability to produce excellent user interfaces.
In a high school classroom where any time spent on software is time taken away from teaching, usability is the most important feature of our product. In these respects, open sourcing the code could prove to be a large disservice to our customers.
This is educational software for high school users. There are remarkably few people in high schools, either students or teachers, with both the skills and the time to contribute to open source development. This removes one of the major motivations for open source development - the "I need this tool for myself" reason for working on something.
Furthermore, the reason this software is so useful to schools is not how powerful it is or how many features it has - it is completely unlike the classical monolithic mathematical applications of yore. It is useful due to the restraint in choosing a minimalist feature set and interface to address teachers' and students' needs with elegance. I fear that as an open source project, the incentive structures would lead down the slippery slope of creeping featuritis, which, while it might create something cool for hackers, will do little to help children learn math and like math.
I would like to find a way to have the best of both worlds. Genuinely open and free software, for all that that implies, and the ability to continue to create great software for people that are not programmers, for people that hate math, and know nothing about computers, and to have it installed at the factory, so that it actually reaches the people that need it where it can do some good.