When I got my MBP my biggest concern was the trackpad. After years of using ThinkPads w/the nipple control I wasn't sure how the trackpad would work for me.
Turns out that the trackpad w/gestures is far more efficient. (at least for me)
You're worried about the lack of the second trackpad button? It is there as a two finger tap and it works great.
if you're fast enough and the timing is right you fix the build just as it is beginning to get liquid, then it cools with tendrills reaching to the surface.
if you fix it too fast if looks the same as if it took a long time to fix it.:)
"The most popular technique came by way of a story contributed by Alberto Savoia. He describes how his project uses red and green lava lamps to radiate the status of their scheduled build."
originally we only had one lava lamp that went on when the build broke. but because having the lava lamp going was a good thing we switched to having a red and green!
"Additionally, iTunes and the iTMS are presumeably staying in the Mac division. The FireWire sync of one's entire music library fom iTunes is the killer feature of the iPod. The iPod division will still have to work closely with the Mac division."
Just like they work closely with the Windows division for the same features...
OpenSource is supposed to be a place where this shouldnt happen, everyone should work together to make one single product better.
Uhmm, no, not according the OpenSource.org or any of the ESR documents or RMS documents that predate it.
There are lots of reasons people do open source. Working together so that you can have a single kick-ass product is generally not their motivation, though it may be a side-effect.
But don't take my word for it, go take a read: http://www.opensource.org/advocacy/case_for_hacker s.php
Optimal experience comes from "flow". See http://www.debateit.net/improvethought/flow1.htm In a company/team setting this means having shared challenges that are overcome by the working together. If an assignment isn't inherently challenging you can try to find ways to make it a game.
By contrast morale isn't developed by free food, foosball, ping pong, beer on Fridays, etc. Those things might make it more fun to be at work, they can reinforce the bonds in a team, but they don't make doing the work any more fun.
I spent a summer at the University of Missouri, Columbia working at the research reactor there. I remember my shock upon learning that all the code was in fortran, my only previous exposure to it have been from the jargon file. One of my jobs was to write code to control a sample changer (or rather to invoke the code for the sample changer and keep the samples w/the data), and they suggested that I write it in fortran.
That just felt so wrong.
So I talked to the staff programmer there and asked if I should take a fortran class. Lucky for me he pointed me at C instead...
I'm surprised you mention such a large difference in coding time between matlab and C/C++. I would think that if you have existing programs that do something similar it would be pretty fast to tweak them to do something slightly difference.
For green field stuff, however, I can certainly believe it.
If you're doing particularly involved matrix manipulations, it takes a lot of work to come up with C/C++ code that will work faster then well-written matlab code.
I'll admit to limited experience with matlab but I find this very hard to believe. My undergraduate computational physics was taught with matlab but since I was learning C I chose to write all my programs in C (ah, Turbo C 2.0 -- now _that_ was a good product).
I was no C wiz, and of course the other students weren't matlab experts, but there was orders of magnitude difference in execution speed.
Perhaps matlab has evovled a lot, or what you are doing has few enough iterations that you don't notice the difference, but I'd guess anything that had lots of iterations would quickly show a marked divergence in execution time.
Read The Innovator's Dilema
on
The Faded Sun
·
· Score: 2, Insightful
You're describing a classic retreat to the high end.
Sun may not go away, but their market share will continue to shrink and shrink and shrink as the lower end machines gain in capabilities.
No it isn't, but it is an issue when you're distilling, not brewing beer. (Other replies already explain the methanol issue.)
Fermentation is a natural process; distillation just speeds that process up.
Fermentation is the conversion of sugar to alcohol.
Distilation is the processes of concencentrating the alcohol. (Or more generally the process of separating volitile fractions based on differences in boiling point.)
Slashdot Mirror
When I got my MBP my biggest concern was the trackpad. After years of using ThinkPads w/the nipple control I wasn't sure how the trackpad would work for me.
Turns out that the trackpad w/gestures is far more efficient. (at least for me)
You're worried about the lack of the second trackpad button? It is there as a two finger tap and it works great.
actually in his case shouldn't it be the singular of anecdote is still not data?
what? no link?
"plugh"
that is the funniest damn thing I've in a long time. well done.
if you're fast enough and the timing is right you fix the build just as it is beginning to get liquid, then it cools with tendrills reaching to the surface.
if you fix it too fast if looks the same as if it took a long time to fix it.
originally we only had one lava lamp that went on when the build broke. but because having the lava lamp going was a good thing we switched to having a red and green!
we (Agitar) tried Ambient Orb but found the lava lamps a better solution.
discussion (and other "extreme feedback devices" here
>> my Dual G5 system does appear to run snappier
:)
prick.
"Additionally, iTunes and the iTMS are presumeably staying in the Mac division. The FireWire sync of one's entire music library fom iTunes is the killer feature of the iPod. The iPod division will still have to work closely with the Mac division."
Just like they work closely with the Windows division for the same features...
or for old-time SNL watchers, "Jane you ignorant slut!"
there's an argument that programming is a design activity:
. ht ml#N40008A
http://martinfowler.com/articles/newMethodology
...nope, can't do it.
As a software person I just can't manage to work up any ire that Apple wants to be paid for some of the work they do.
OpenSource is supposed to be a place where this shouldnt happen, everyone should work together to make one single product better.
r s.php
Uhmm, no, not according the OpenSource.org or any of the ESR documents or RMS documents that predate it.
There are lots of reasons people do open source. Working together so that you can have a single kick-ass product is generally not their motivation, though it may be a side-effect.
But don't take my word for it, go take a read: http://www.opensource.org/advocacy/case_for_hacke
on smallish projects I've seen huge increases in compile speed when using a ram disk, even if only for the compiled output.
with up to 8 gb of ram I wonder if this will be a more common technique on the G5s...
ahem... the Dell wasn't running Logic.
Optimal experience comes from "flow". See http://www.debateit.net/improvethought/flow1.htm
In a company/team setting this means having shared challenges that are overcome by the working together. If an assignment isn't inherently challenging you can try to find ways to make it a game.
By contrast morale isn't developed by free food, foosball, ping pong, beer on Fridays, etc. Those things might make it more fun to be at work, they can reinforce the bonds in a team, but they don't make doing the work any more fun.
Shouldn't that be "Come for the Java and stay for the Mocha"?
I spent a summer at the University of Missouri, Columbia working at the research reactor there. I remember my shock upon learning that all the code was in fortran, my only previous exposure to it have been from the jargon file. One of my jobs was to write code to control a sample changer (or rather to invoke the code for the sample changer and keep the samples w/the data), and they suggested that I write it in fortran.
That just felt so wrong.
So I talked to the staff programmer there and asked if I should take a fortran class. Lucky for me he pointed me at C instead...
I'm surprised you mention such a large difference in coding time between matlab and C/C++. I would think that if you have existing programs that do something similar it would be pretty fast to tweak them to do something slightly difference.
For green field stuff, however, I can certainly believe it.
If you're doing particularly involved matrix manipulations, it takes a lot of work to come up with C/C++ code that will work faster then well-written matlab code.
I'll admit to limited experience with matlab but I find this very hard to believe. My undergraduate computational physics was taught with matlab but since I was learning C I chose to write all my programs in C (ah, Turbo C 2.0 -- now _that_ was a good product).
I was no C wiz, and of course the other students weren't matlab experts, but there was orders of magnitude difference in execution speed.
Perhaps matlab has evovled a lot, or what you are doing has few enough iterations that you don't notice the difference, but I'd guess anything that had lots of iterations would quickly show a marked divergence in execution time.
You're describing a classic retreat to the high end.
Sun may not go away, but their market share will continue to shrink and shrink and shrink as the lower end machines gain in capabilities.
Unstoppable might be a bit much, but it IS nice to see some of their recent decisions paying off.
s /pr021203b.html
The StereoGraphics press release:
http://www.stereographics.com/news_about_us/03new
No it isn't, but it is an issue when you're distilling, not brewing beer. (Other replies already explain the methanol issue.)
Fermentation is a natural process; distillation just speeds that process up.
Fermentation is the conversion of sugar to alcohol.
Distilation is the processes of concencentrating the alcohol. (Or more generally the process of separating volitile fractions based on differences in boiling point.)