A project I was on in 2000ish went as follows: Steppings A0, A1, A2, and A3 were halted in-fab because someone found a critical bug in simulations. A4-A7 did not work. B0-B4 did not work B6 did not work C0-C4 did not work B5, B7, C5 sorta worked. The company folded. That's what a software mentality working on hardware will get you.
Luckily Microsoft stepped in and bought the company, and now market the product as X-Box.
The vehicle can deliver 12 tonnes to a 300km equatorial orbit, 10.5 tonnes to a 460km equatorial spacestation or 9.5 tonnes to a 460km x 28.5 deg spacestation when operating from an equatorial site.
You do the per flight math.
I'm more worried about the fact that it can only go in two directions: to the equator, to to 28.5deg.
Yah, wealth is created by making stuff , and not by just pulling ideas out of one's arse. If the ideas can be used to make something, then they might be worth a bit, but an idea alone is worth exactly bupkus.
I would have agreed with you, except for the existence of, and rapid improvement of, Fabbers. Give it a decade or two, and kids/techies will be downloading designs to build what they need, and only ordering raw materials from amazon. Since some fabbers are self-replicating, not even making fabbers will be a safe job/revenue stream. Given that mining and other resource harvesting is becoming more and more automated too, ideas are soon going to be all that's left.
Essentially, we're moving towards the society the (fictional) Krell had. They were smarter than us, and their own tech wiped them out. Let's see how we do. One thing's for sure: if we stick to the RIAA model, we're all screwed.
said that 2.0 labeling is for high-speed only. But they had too much 2.0 low speed product in the channel that didn't want to be labeled 1.0
Yep, the problem is that some devices don't, and will never be able to utilise a high speed link. Standard keyboards, for instance. What they really need is some kind of label that means "Uses the a USB version that allows full throughput". Call it USB Unlimited, or something. That way, a keyboard can be USB Unlimited, and the best HD cams can be USB unlimited, but the cheap-ass model you get free with your netbook clearly won't be.
Exactly so. Making science funny isn't really an achievement, when the person doing the judging is into science. Geeks do tend to like geek jokes. Also, business people tend not to insult their hosts' entertainment too often. To their faces, at least.
I think the best SCM is that SCM which you known the best
Since SCMs are designed for collaboration, that's very unlikely to be true. Perhaps, if your use of an SCM is entirely as a private timeline tracking and branching tool.
You're quite right. It seems to me that Git isn't intended to provide access to the latest versions of individual files. Git, like all DVCS's I know of, is essentially a version-control plugin for your filesystem. The filesystem itself provides the current version you're working with, and so it's only a matter of providing an http server over the directory or something like that. Which is exactly what GitWeb and Trac-Git provide, only they're better.
Have you put together a clear, serious, constructive proposal for an alternative that spells out the pros and cons? If you haven't, its your own fault really. But if you have, and they don't listen, then yeah, "shit" about sums things up. At any other time, I'd say find better bosses and quit in that situation, but few have that option at the moment.
Just wait 'til you get a dumbass letter from the RIAA saying that the IP 127.0.0.1 has been identified as a computer uploading copyrighted material. Then the shit will really hit the fan;)
Of course scaling should scale the whole page, not just the text. It shouldn't be that hard.
Well, PDF had vector graphics from the start, so that was a no-brainer. With the web, people were holding out for scalable webpages to be done right. SVG was the solution to that, not scaling up bitmaps with disregard for their intended size, resolution, and fundamental function. But someone got bored and did it wrong, and now we'll all pay, just like, for years, we've been paying for blink tags being used for animation and emphasis, and tables being used for layout.
All true, and not something I'm trying to deny. Yet I still think we should encourage working together, and discourage diversity, except where necessary. The amount of wasted and duplicated effort in Free Software is staggering sometimes.
That much is true, but I'm mainly referring to the pretty desktop GUI elements that help you to manage your IDs and authorise sites to use them, not the underlying transport mechanism. Yes, openid has a transport mechanism. BUT, it also has a horrible user interface model.
a more general ancient mammalian characteristic that has been lost in most modern mammals, and is only retained in a couple of very ancient lineages.
How does this work, I wonder? Are the mammals in question actually immune to the poison, or are they just built not to bite themselves somehow? Seems the most likely explanation.
If the latter though, I wonder if this is related to mammalian affection at all? Lots of mammals seem to be affectionate enough to lick their young/mates, nuzzle, groom peers, playfight, etc...
Individual projects have their own unique challenges, engineering firms come up with improvements, etc. What's shared is the general design.
Yes, and the equivalent in software is a single software project, with branches trying out new features, then re-integrating the best of breed stuff back into trunk.
because different branches and government agencies use different software and different file formats, which impedes communication between other agencies and the people.
We seem to agree here.
What makes you think that switching from Red Hat to Canonical would be so easy?
Since we're talking about two distributions of the same applications, I think the burden of proof is on you. What makes you think they'd be incompatible, assuming competent admins who read any release notes or bug reports before upgrading? Note that I'm not talking about the standard sort of upgrade issues you get between windows 98 and windows 2000, or between OOo 2.x and OOo 3.x. That's simple stuff for any competent IT dept, and certainly any company with a multi-million dollar IT contract for government. I'm talking fundamental incompatibility, due to one company not having access to the specifications or patents that the previous company used.
We are not talking about a single machine here, we are talking about thousands (millions?) of computers at a time, with various regulations on data retention.
Deployment isn't easy, and never has been. I don't see anything relevant or special about it here though.
Actually, it's not. Most systems synchronize the two, so you don't get flicker (monitor refresh) during refreshes of the video buffer (FPS). Otherwise, the result can be a bit like driving past railings, looking at something behind them. I'm not sure it's an issue for LCDs, but on standard CRTs and TVs (mainly consoles these days), it's a definite issue, and only bad game designs don't use sync. It's quite strange that PC gamers have accepted increasing FPS beyond their monitor refresh as a good thing.
Slashdot Mirror
Luckily Microsoft stepped in and bought the company, and now market the product as X-Box.
I know, right? The Visitors would have given us their cancer cure ages ago, if it wasn't for that stupid Donovan guy.
Unfortunately Kodos and Kang were unavailable for comment.
I'm more worried about the fact that it can only go in two directions: to the equator, to to 28.5deg.
I would have agreed with you, except for the existence of, and rapid improvement of, Fabbers. Give it a decade or two, and kids/techies will be downloading designs to build what they need, and only ordering raw materials from amazon. Since some fabbers are self-replicating, not even making fabbers will be a safe job/revenue stream. Given that mining and other resource harvesting is becoming more and more automated too, ideas are soon going to be all that's left.
Essentially, we're moving towards the society the (fictional) Krell had. They were smarter than us, and their own tech wiped them out. Let's see how we do. One thing's for sure: if we stick to the RIAA model, we're all screwed.
Yep, the problem is that some devices don't, and will never be able to utilise a high speed link. Standard keyboards, for instance. What they really need is some kind of label that means "Uses the a USB version that allows full throughput". Call it USB Unlimited, or something. That way, a keyboard can be USB Unlimited, and the best HD cams can be USB unlimited, but the cheap-ass model you get free with your netbook clearly won't be.
Exactly so. Making science funny isn't really an achievement, when the person doing the judging is into science. Geeks do tend to like geek jokes. Also, business people tend not to insult their hosts' entertainment too often. To their faces, at least.
And only excluded those communities from two entire versions. I'm sure no one minded though.
CPU usage is fixed in all USB standards. It's 140%.
And a get-away vehicle.
Since SCMs are designed for collaboration, that's very unlikely to be true. Perhaps, if your use of an SCM is entirely as a private timeline tracking and branching tool.
You're quite right. It seems to me that Git isn't intended to provide access to the latest versions of individual files. Git, like all DVCS's I know of, is essentially a version-control plugin for your filesystem. The filesystem itself provides the current version you're working with, and so it's only a matter of providing an http server over the directory or something like that. Which is exactly what GitWeb and Trac-Git provide, only they're better.
Have you put together a clear, serious, constructive proposal for an alternative that spells out the pros and cons? If you haven't, its your own fault really. But if you have, and they don't listen, then yeah, "shit" about sums things up. At any other time, I'd say find better bosses and quit in that situation, but few have that option at the moment.
Just wait 'til you get a dumbass letter from the RIAA saying that the IP 127.0.0.1 has been identified as a computer uploading copyrighted material. Then the shit will really hit the fan ;)
Wrong. Updates in distro releases are usually security updates, which should be applied by everyone.
Sorry, Michelle, I'm not familiar with all these terms you HR babes use. What's it called again? The Sexualize Her Ass policy?
Well, PDF had vector graphics from the start, so that was a no-brainer. With the web, people were holding out for scalable webpages to be done right. SVG was the solution to that, not scaling up bitmaps with disregard for their intended size, resolution, and fundamental function. But someone got bored and did it wrong, and now we'll all pay, just like, for years, we've been paying for blink tags being used for animation and emphasis, and tables being used for layout.
All true, and not something I'm trying to deny. Yet I still think we should encourage working together, and discourage diversity, except where necessary. The amount of wasted and duplicated effort in Free Software is staggering sometimes.
That much is true, but I'm mainly referring to the pretty desktop GUI elements that help you to manage your IDs and authorise sites to use them, not the underlying transport mechanism. Yes, openid has a transport mechanism. BUT, it also has a horrible user interface model.
How does this work, I wonder? Are the mammals in question actually immune to the poison, or are they just built not to bite themselves somehow? Seems the most likely explanation.
If the latter though, I wonder if this is related to mammalian affection at all? Lots of mammals seem to be affectionate enough to lick their young/mates, nuzzle, groom peers, playfight, etc...
I heard it was Redmond.
Yes, and the equivalent in software is a single software project, with branches trying out new features, then re-integrating the best of breed stuff back into trunk.
Electricity is based on Linux.
We seem to agree here.
Since we're talking about two distributions of the same applications, I think the burden of proof is on you. What makes you think they'd be incompatible, assuming competent admins who read any release notes or bug reports before upgrading? Note that I'm not talking about the standard sort of upgrade issues you get between windows 98 and windows 2000, or between OOo 2.x and OOo 3.x. That's simple stuff for any competent IT dept, and certainly any company with a multi-million dollar IT contract for government. I'm talking fundamental incompatibility, due to one company not having access to the specifications or patents that the previous company used.
Deployment isn't easy, and never has been. I don't see anything relevant or special about it here though.
Actually, it's not. Most systems synchronize the two, so you don't get flicker (monitor refresh) during refreshes of the video buffer (FPS). Otherwise, the result can be a bit like driving past railings, looking at something behind them. I'm not sure it's an issue for LCDs, but on standard CRTs and TVs (mainly consoles these days), it's a definite issue, and only bad game designs don't use sync. It's quite strange that PC gamers have accepted increasing FPS beyond their monitor refresh as a good thing.