Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re:Hooray for standardized hardware (Score 1) 75

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.

Comment Re:Oh great, Cogent is at it again (Score 4, Interesting) 111

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.

Comment Re:What are we trying to achieve? (Score 4, Insightful) 427

"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.

Comment Re:Mercurial vs. Git (Score 2, Interesting) 346

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?

Comment Re:My (short) experience with git so far (Score 1) 346

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.

Comment Re:strategy (Score 1) 346

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.

Slashdot Top Deals

Not only is UNIX dead, it's starting to smell really bad. -- Rob Pike