You're thinking of Dominic Giampolo. Benoit wrote the App Kit and tons of good bits in the rest of BeOS but he didn't have much to do with the filesystem.
A socket adds a significant amount of parasitic capacitance and inductance. At high frequencies, this can cost quite a bit of power. You're right about it also contributing to space and cooling issues.
BGA has among the lowest parasitics of all IC packages so it's not surprising to see it everywhere nowadays. Except for how hard it is to desolder, it is an awesome way connect ICs to PCBs.
Contact area (wire size) doesn't really matter... Your connection needs to be big enough to handle the worst case power and no bigger -- any extra metal is just wasted (to a point, but let's not get pathological discussing running 1 GHz signals down 0 gauge wire). The path of the signal tends to be much more important than the wire size.
Back in the old days, whenever our peering ratio started getting wobbly, we'd just set up NNTP servers and have them hammer away (either downloading or uploading, depending on what direction we needed to move the balance).
I assume ISPs are still doing this but they're probably using BitTorrent now instead of NNTP.
"So again, what was Linux hoping to achieve by dropping old "obsolete" OSS in favor of increasingly complex solutions?"
Linux deprecated OSS2, which everyone agrees sucks hard. It was a no-brainer.
OSS3 is significantly better but it was only recently open sourced. Frankly, if the OSS devs hadn't spent most of the last decade with their heads firmly wedged, audio on Linux would probably be in a much better state. Ah well.
"Blue Rubicon attests that 'if you do them right you can make a material impact on people's behaviour.'"
That will certainly make a material impact on Blue Rubicon's net profits. But change people's behavior? That's pretty unlikely. History is not on their side.
True, you need to "git config --global core.autocrlf false". But that's only an issue if your files have embedded \rs. Most don't.
Git has no concept whatsoever of file permissions either except for the execute bit. To control it on Windows, use "git update-index --chmod=blah". No big deal.
Nope. Visual Source Safe is a horrible hack -- VCS extensions on top of a file sharing protocol. It's such a disaster to use that Microsoft won't even use it internally.
They'll sell it but they won't use it. Gotta love Microsoft.
Last I used Mercurial, I couldn't create a feature branch. I had to clone the whole damn repo. Well, either that or I could create a branch that lives forever, not a good idea if I'm doing a crazy experiment.
In Git, if I want to try something out, I create a feature branch (takes basically no time or disk space) and hack away. If it sucks, I just delete the branch. It's a very nice way to work once you get used to it.
Why stash / unstash before pulling master? Just commit your changes to a feature branch.
The only scary part of your workflow that I can see is the rebase. And, yes, rebase is a bit of an odd child. I hope that the Git team spends some time making it more more predictable and easier to use.
What an odd post. There are two VCSes that I've used that regularly suffer from corruption issues: cvs and svn. I have used Git since pre-1.0 and have not seen even a single corruption. In fact, git and hg's repo formats make it almost impossible for a corruption to go unnoticed -- not true of svn or cvs.
And, you say everybody should use svn for the wire protocol? Yeah, just because one VCS is crippled, let's force everybody to use wheelchairs! Horrible idea.
The world has moved way past svn dude. You might want to sign up for an account on one of the newer project hosting sites and catch up.
You're implying that you would be happy with HTML5 saying "widely recognized formats include Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format." Is that true? That sounds great to me.
What the hell is wrong with you schnell? The quote DOES appear in the story. Click the linked newsweek story, click on Page two, scroll down halfway. That's pretty much exactly what the GP told you to do. Do you need even more explicit instructions?
Too bad the GGGGP post actually is an example of the broken window fallacy. Here it is, side-by-side:
The baker should have been able to spend those six francs in the most efficient way to benefit his business. He might have chosen to buy new windows anyway (the better to allow customers to see his products). The child, however, *forced* him to spend it on a new window. The baker's loss of freedom is a net loss to the entire village.
Disk companies should be able to spend their R&D budgets in the most efficient way to benefit their business. They might even choose to research new ways of solving this specific problem. This lawsuit, however, *forces* them to spend it on this lawsuit. The disk company's loss of freedom is a net loss to the entire industry.
> Did you totally miss the part of the GPL that says it doesn't cover use?
Did you totally miss the part of the GPL that prevents tivoization? The FSF doesn't actually claim that anymore, do they? GPLv3's anti-tivoization clauses are all about use.
You're right, GPLv2 doesn't cover use. GPLv3 does. And that's why so many free software programmers have deep problems with v3.
Slashdot Mirror
I use a tiny script: https://github.com/bronson/sshkeys
Makes the easy even easier.
You're thinking of Dominic Giampolo. Benoit wrote the App Kit and tons of good bits in the rest of BeOS but he didn't have much to do with the filesystem.
A socket adds a significant amount of parasitic capacitance and inductance. At high frequencies, this can cost quite a bit of power. You're right about it also contributing to space and cooling issues.
BGA has among the lowest parasitics of all IC packages so it's not surprising to see it everywhere nowadays. Except for how hard it is to desolder, it is an awesome way connect ICs to PCBs.
Contact area (wire size) doesn't really matter... Your connection needs to be big enough to handle the worst case power and no bigger -- any extra metal is just wasted (to a point, but let's not get pathological discussing running 1 GHz signals down 0 gauge wire). The path of the signal tends to be much more important than the wire size.
Back in the old days, whenever our peering ratio started getting wobbly, we'd just set up NNTP servers and have them hammer away (either downloading or uploading, depending on what direction we needed to move the balance).
I assume ISPs are still doing this but they're probably using BitTorrent now instead of NNTP.
"So again, what was Linux hoping to achieve by dropping old "obsolete" OSS in favor of increasingly complex solutions?"
Linux deprecated OSS2, which everyone agrees sucks hard. It was a no-brainer.
OSS3 is significantly better but it was only recently open sourced. Frankly, if the OSS devs hadn't spent most of the last decade with their heads firmly wedged, audio on Linux would probably be in a much better state. Ah well.
"Blue Rubicon attests that 'if you do them right you can make a material impact on people's behaviour.'"
That will certainly make a material impact on Blue Rubicon's net profits. But change people's behavior? That's pretty unlikely. History is not on their side.
True, you need to "git config --global core.autocrlf false". But that's only an issue if your files have embedded \rs. Most don't.
Git has no concept whatsoever of file permissions either except for the execute bit. To control it on Windows, use "git update-index --chmod=blah". No big deal.
Nope. Visual Source Safe is a horrible hack -- VCS extensions on top of a file sharing protocol. It's such a disaster to use that Microsoft won't even use it internally.
They'll sell it but they won't use it. Gotta love Microsoft.
If someone else is in the same coffee shop as you, use gitjour: http://github.com/blog/75-git-over-bonjour
If not, just push your repo up to a machine that does have a static IP. Easy breezy.
Last I used Mercurial, I couldn't create a feature branch. I had to clone the whole damn repo. Well, either that or I could create a branch that lives forever, not a good idea if I'm doing a crazy experiment.
In Git, if I want to try something out, I create a feature branch (takes basically no time or disk space) and hack away. If it sucks, I just delete the branch. It's a very nice way to work once you get used to it.
Have they improved branching in hg?
Why stash / unstash before pulling master? Just commit your changes to a feature branch.
The only scary part of your workflow that I can see is the rebase. And, yes, rebase is a bit of an odd child. I hope that the Git team spends some time making it more more predictable and easier to use.
Not true anymore. msysgit works great on Win.
http://code.google.com/p/msysgit/
http://kylecordes.com/2008/04/30/git-windows-go/
What an odd post. There are two VCSes that I've used that regularly suffer from corruption issues: cvs and svn. I have used Git since pre-1.0 and have not seen even a single corruption. In fact, git and hg's repo formats make it almost impossible for a corruption to go unnoticed -- not true of svn or cvs.
And, you say everybody should use svn for the wire protocol? Yeah, just because one VCS is crippled, let's force everybody to use wheelchairs! Horrible idea.
The world has moved way past svn dude. You might want to sign up for an account on one of the newer project hosting sites and catch up.
https://www.dellbatteryprogram.com/
Not sure why Dell didn't just go with batteryprogram.dell.com or dell.com/batteryprogram.
Michael Stonebraker sure sounds like a moron: http://stuffthathappens.com/blog/2008/01/19/mapreduce-reading/
Does anybody have an example of something Stonebraker has said that isn't vapid, patently obvious, or flagrantly wrong?
yaossfsck?
You're implying that you would be happy with HTML5 saying "widely recognized formats include Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format." Is that true? That sounds great to me.
I've got an easier solution. Don't make the robot out of lead.
That's all you need to determine guilt? Motive? And a rather tenuous one at that?
We're not the leafiest tree in the park, are we?
What the hell is wrong with you schnell? The quote DOES appear in the story. Click the linked newsweek story, click on Page two, scroll down halfway. That's pretty much exactly what the GP told you to do. Do you need even more explicit instructions?
Who on earth modded this comment insightful?
Too bad the GGGGP post actually is an example of the broken window fallacy. Here it is, side-by-side:
The baker should have been able to spend those six francs in the most efficient way to benefit his business. He might have chosen to buy new windows anyway (the better to allow customers to see his products). The child, however, *forced* him to spend it on a new window. The baker's loss of freedom is a net loss to the entire village.
Disk companies should be able to spend their R&D budgets in the most efficient way to benefit their business. They might even choose to research new ways of solving this specific problem. This lawsuit, however, *forces* them to spend it on this lawsuit. The disk company's loss of freedom is a net loss to the entire industry.
"That's undetectable!"
You keep using that word... I do not think it means what you think it means.
> You're honestly giving Internet time servers too much credit if you think of depending for nanosecond resolution on them.
Not at all. Just repeat the operation 500 million times. Even a 15% slowdown is easily detectable.
It seems like you're only picturing one side of the board here. Try to think objectively about what both sides can do.
> Did you totally miss the part of the GPL that says it doesn't cover use?
Did you totally miss the part of the GPL that prevents tivoization? The FSF doesn't actually claim that anymore, do they? GPLv3's anti-tivoization clauses are all about use.
You're right, GPLv2 doesn't cover use. GPLv3 does. And that's why so many free software programmers have deep problems with v3.
It's a wiki! You can add it yourself.