The electromotive force (e.m.f.) predicted by Faraday's law reflects the forces acting on the charge, â"e, of an electron moving through a device or circuit, and is proportional to the time derivative of the magnetic field. This conventional e.m.f. is usually absent for stationary circuits and static magnetic fields. There are also forces that act on the spin of an electron; it has been recently predicted that, for circuits that are in part composed of ferromagnetic materials, there arises an e.m.f. of spin origin even for a static magnetic field. This e.m.f. can be attributed to a time-varying magnetization of the host material, such as the motion of magnetic domains in a static magnetic field, and reflects the conversion of magnetic to electrical energy. Here we show that such an e.m.f. can indeed be induced by a static magnetic field in magnetic tunnel junctions containing zinc-blende-structured MnAs quantum nanomagnets. The observed e.m.f. operates on a timescale of approximately 10^2-10^3 seconds and results from the conversion of the magnetic energy of the superparamagnetic MnAs nanomagnets into electrical energy when these magnets undergo magnetic quantum tunnelling. As a consequence, a huge magnetoresistance of up to 100,000 per cent is observed for certain bias voltages. Our results strongly support the contention that, in magnetic nanostructures, Faraday's law of induction must be generalized to account for forces of purely spin origin. The huge magnetoresistance and e.m.f. may find potential applications in high sensitivity magnetic sensors, as well as in new active devices such as 'spin batteries'.
Readers with subscriptions can see the whole paper.
Do you think Comcast gave a shit when my internet connection wasn't working?
Funny you mention that, because Comcast was almost certainly granted a state monopoly on cable service in your area. The decision to use or not use Comcast was never yours to make; it's ultimately up to the municipality you live in, and the cable companies have done a pretty good job of making themselves immovable once in place.
Bugzilla: still the best, as far as I'm concerned, because it quantifies communication (you know who bug changes will go to), has good search features, and is free. The big downsides are mostly from a management perspective: no time tracking, too chatty (i.e. if you only care about state transition on bug completion, you get to listen on all the other crap, too), and no integration with management tracking tools.
The nits I have from a worker-bee perspective are that Bugzilla can't eliminate a project once it's been created (hiding would really be a better word); this has been a feature request that's been ignored for years now. This makes deciding where to put a bug much more difficult than it otherwise needs to be.
Fogbugz: Mostly fixes the managerial problems with Bugzilla but at the expense of horrific communication problems elsewhere.
It wants to use e-mail as its primary means of communication, yet an absence of integration with LDAP (or any means of establishing a list of authorized users) means it doesn't support auto-fill-in for e-mail fields as it does for, say, bug assignment.
It doesn't automatically let the author of the bug -- or anyone else! -- know if something has changed on the bug; you have to explicitly request this, and there is no preference to automatically change this for auto-subscribe to bugs you write or are assigned to.
Similarly, there is no way to know who is subscribed to a bug. This is simply inexcusable for a bug tracking system; the whole point is communication.
The filter interface doesn't include all options. One of the most irritating misfeatures of this package is the fact that many crucial search options are available as text-only operators, and do not appear on the user interface.
E-mail always appears to come from the Fogbugz administrative user no matter who originated it. The package appears to be made by people who had no desire to communicate with each other...
... as evidenced by their built-in preference for TOFU quoting.
Formatting is a nightmare. Bugzilla, at least, guarantees fixed-width fonts, so tables and code examples are readable; Fogbugz insists on using variable-width fonts, which wreaks havoc with code. And there's no way to use HTML, either (though this is an equally valid criticism of Bugzilla).
That's just the start.
trac: Mercifully, I didn't have to use this much, but the learning curve appeared to be rather steep, and it was a completely alien experience from Bugzilla.
And the people get one opportunity every election to toss out malingerers, incompetents, and hacks. Good luck if your pet issue isn't the one that happens to be hot that year.
Businesses have to answer to the customer EVERY DAMN DAY. People who fail to notice this difference are arguing about strawmen.
MLB Gameday under Fedora 9 is still broken. I switched recently to the above release (which has Firefox 3.0.2) and it typically breaks after not very long. If this is "equal", give me back Flash 9.
You know, sometimes I get the feelin'
That, that uh, accountants and lawyers
are in cahoots with the Devil Yeah, they're in cahoots with the Devil!
To cover the Earth
Cover the Earth with this wretched swill
of gutless, mediocre, middle-of-the-road,
sleep-inducing, homogenized pabulum programming languages for the slavery of daily drudgery
Sometimes I get that feeling man, but I know it's a lie I know it's not true I know it's not true
And I'm talkin' to Larry Wall now
Larry Wall, I'm talkin' to ya
Larry Wall, where are ya?
Gotta have more Perl!
Gotta have more Perl!
Microsoft, for one. As of three years ago, 60% of supercomputers were running Linux and I can only imagine that figure has gotten higher subsequently. Nobody trusts Microsoft for high-end applications, and what's more, it's expensive, too. Microsoft needs a reference application to show its customers that they aren't being left in the penguin's dust.
before it is useful. "Cloud computing" is like myriad other technology shorthands ("Web 2.0" being my favorite bête noir, but there are dozens of others) too immature to be trusted in production.
tells me they don't have a lot of faith in this movie. February and March are typically dumping grounds for films that got made but nobody has confidence in.
Calculated Risk believes this is a case where S&P decided not to believe their own models and tweaked them to match the results derived by Moody's, which spit out the wrong results in the first place. Call it bug-compatibility, but it's also clear that there were plenty of financial incentives at the time for the rating agencies to deliver results in step with their peers lest they lose out on lucrative "second opinion" business.
Umm, says who? Thanks exactly what we do. We have/trunk and/branches/devel. When one of us gets a particularly stable version of/branches/devel ready, we merge it to/trunk.
"We" != "build manager." I'm assuming by your language that anyone at your shop, not one build manager, has the ability to make code go live.
But since branches are basically free, why would you want to avoid them?
Because they are a pain in the ass to keep merging. It's not that "branches... are free", it's that you have to keep making the damn things every time you want to merge mods from the newly modified trunk.
The build manager can't merge the changes without those changes taking on his identity, that is, all identifying information about the originator of the changes is lost.
Since I'm sure you're not talking about what svn blame gives you, what do you mean exactly?
The problem stems from the fact that we want to lock down the trunk and have one user responsible for managing that trunk. This is impossible in the current version of SVN without erasing the history of the true author on the code. See the Sub version Roadmap for details, especially the section labeled "Commutative Author and Revision Reporting for Merged Changesets".
Why can't wind power make it without huge subsidies? Why can't the free market solve the problem? Because it is not a free market.
Rubbish twice over is still rubbish. Subsidies have to come from somewhere, and if the rest of the economy is powered by fossil fuels, that means your subsidies have to come from the thing your windmills claim to be saving you from. Furthermore, whatever "subsidies" (more like not taxing them in some way or another, something most critics can't discern between) there are for oil and such generally are more than made up for by fuel taxes and the like.
Eliminate subsidies for everyone.
I have a feeling this is just nameplate generation, something the story doesn't tell you. Figure actual capacity is about a third of this because of wind variability.
Without saying too much about distributed version control schemes like Git (which I have never used), I have two major beefs with SVN:
Merges in a typical environment become effectively anonymous. Let's say you have a build manager and individual developers working on different changes in parallel. The build manager can't merge the changes without those changes taking on his identity, that is, all identifying information about the originator of the changes is lost.
So-called "best practice" for SVN branching means building new branches with every new release. That is, it's not recommended to build one branch and merge changes from the trunk into it as you're incrementally changing things on that branch, noooo. You have to keep polluting the repository with needless hair by making new branches every week, and sometimes, multiple ones per day.
These are just two I'm aware of that bite us in the ass on a regular basis. The first issue is supposed to be fixed in one of the near-term mods to SVN, but the fact that the second even exists tells me that the guys developing SVN don't really work in the same world as a lot of the bigger commercial development environments do.
Slashdot Mirror
Readers with subscriptions can see the whole paper.
Funny you mention that, because Comcast was almost certainly granted a state monopoly on cable service in your area. The decision to use or not use Comcast was never yours to make; it's ultimately up to the municipality you live in, and the cable companies have done a pretty good job of making themselves immovable once in place.
That's just the start.
And the people get one opportunity every election to toss out malingerers, incompetents, and hacks. Good luck if your pet issue isn't the one that happens to be hot that year. Businesses have to answer to the customer EVERY DAMN DAY. People who fail to notice this difference are arguing about strawmen.
What, how does this go? Infidel! Terrorist! Am not. Are so! Twitter: insanely useless or just a huge waste of time?
... but there are plenty of times I do feel that way. It seems like Gameday and Gameday Audio break every damn year; this sometimes includes the Mac platform as well. MLBAM has almost no concern for minority platforms.
That's no "character smear", it goes straight to the heart of the kind of person he is.
See also. Lore Sjoberg rips Twitter a new one, but it's only common sense; who frankly gives a damn?
MLB Gameday under Fedora 9 is still broken. I switched recently to the above release (which has Firefox 3.0.2) and it typically breaks after not very long. If this is "equal", give me back Flash 9.
That, that uh, accountants and lawyers
are in cahoots with the Devil
Yeah, they're in cahoots with the Devil!
To cover the Earth
Cover the Earth with this wretched swill
of gutless, mediocre, middle-of-the-road,
sleep-inducing, homogenized pabulum programming languages for the slavery of daily drudgery
Sometimes I get that feeling man, but I know it's a lie
I know it's not true
I know it's not true
And I'm talkin' to Larry Wall now
Larry Wall, I'm talkin' to ya
Larry Wall, where are ya?
Gotta have more Perl!
Gotta have more Perl!
(with respects to Mojo Nixon)
Microsoft, for one. As of three years ago, 60% of supercomputers were running Linux and I can only imagine that figure has gotten higher subsequently. Nobody trusts Microsoft for high-end applications, and what's more, it's expensive, too. Microsoft needs a reference application to show its customers that they aren't being left in the penguin's dust.
he just happens to be right. Google doesn't have to pick up that stuff.
Did you bother to actually look at sourcetool.com? Multiple keywords, all unrelated to each other, each with the same anchor tag. He's a whiner.
before it is useful. "Cloud computing" is like myriad other technology shorthands ("Web 2.0" being my favorite bête noir, but there are dozens of others) too immature to be trusted in production.
tells me they don't have a lot of faith in this movie. February and March are typically dumping grounds for films that got made but nobody has confidence in.
buzzword-compliant computing. I hate stories like this, which are really just cover for somebody's marketing.
Fargin' hilarious. Twitter seems to me to be absolutely February 2001, just milliseconds before the crash stupid.
No kidding, and no surprise: the Bush Administration seems to think it's playing a game of Risk.
Calculated Risk believes this is a case where S&P decided not to believe their own models and tweaked them to match the results derived by Moody's, which spit out the wrong results in the first place. Call it bug-compatibility, but it's also clear that there were plenty of financial incentives at the time for the rating agencies to deliver results in step with their peers lest they lose out on lucrative "second opinion" business.
I have a feeling this is just nameplate generation, something the story doesn't tell you. Figure actual capacity is about a third of this because of wind variability.
- Merges in a typical environment become effectively anonymous. Let's say you have a build manager and individual developers working on different changes in parallel. The build manager can't merge the changes without those changes taking on his identity, that is, all identifying information about the originator of the changes is lost.
- So-called "best practice" for SVN branching means building new branches with every new release. That is, it's not recommended to build one branch and merge changes from the trunk into it as you're incrementally changing things on that branch, noooo. You have to keep polluting the repository with needless hair by making new branches every week, and sometimes, multiple ones per day.
These are just two I'm aware of that bite us in the ass on a regular basis. The first issue is supposed to be fixed in one of the near-term mods to SVN, but the fact that the second even exists tells me that the guys developing SVN don't really work in the same world as a lot of the bigger commercial development environments do.If I had mod points, I would give this post +1 Informative. Seriously, Pidgin's UI has gotten worse with every recent iteration.