I have VLC 0.83 installed on my Mac. If the.wmv is for WMP 10, I get an error message about the codec. I'm not going to waste my time trying find the magic combination of codecs just on the off-chance that I might be able to play that particular.wmv file. I've lived nearly 50 years without.wmv files in my life, I can survive quite well without them for another 50 if need be.
The Lagrange points are orbits, they just happen to be fixed in relation to the orbits of the other two bodies. L4 and L5 are also called "Trojan points" (Google is your friend). They are 60 degrees ahead and 60 degrees behind the Moon, in this case, and orbiting the earth at the same orbital radius and speed as the Moon. What effectively happens is, the gravitational pull of the Earth and the Moon are equal at that distance, so anything in orbit in either of those places never catches up to the Moon, nor does the Moon catch up to the other. If you were in orbit around the Earth at the same distance as the Moon, eventually either the Earth or the Moon's gravity would pull you out of the stable orbit towards one or the other, whichever was closer.
Well, anyway, go sober up, drink lots of water, and read this in the afternoon.
I'm 47 and just squeek under the wire! I find it fascinating that in every reply from those who diagrammed sentences, there are no grammatical mistakes.
And other TLAs. There should be a moratorium on any more acronyms being added to Java. No language should have more than two or three TLA or FLAs, at the most. When you have acronyms that are as long as the language you're acronyming, that's too much!
I mean, I've seen MILSPECs with fewer T/FLAs than Java has spawned! Hell, even the MILSPEC computer language doesn't have that many!
..we wait for people to actually understand amd implement the current C++ standard?
Unfortunately, because the spec is so convoluted, you can implement some aspects in completely incompatible ways, and still be "implementing the standard."
I've been in the profession for over 20 years, and I've seen the same thing happen to certain "standards". Something new and innovative will come along, and within a decade, features will be added that will make it unusable, and foster the demand for "something like X but easier/simpler/faster/cleaner". Most of the feature creep is driven by large corporate interests and the demands of their programming staffs to add features that they claim they can't develop without.
Not many people remember X Window 10R4, but the entire Xlib documentation took up a half-inch thick stack of single-sided pages, and described a basic networked window system that was useful enough to develop distributed systems with. The protocol was easy to implement, straightforward, and clean. But that wasn't good enough for the wonks at Apollo, DEC, HP, Sun, AT&T, and the researchers at MIT. So, once everyone added their "must have" requirements to X Window (we have to have font servers or we can't write good systems!) you ended up with a monstrosity of an Xlib spec that took up a thousand or so pages of documentation, added thousands of new points of failure, and spawned an entire bookshelf from O'Reilly just to try to explain how to use X.
I saw the same thing happen to C++. In the early days it was what it set out to be, a simple, easy to implement extension to C that let you do basic object oriented programming. Sure, it wasn't Smalltalk or Scheme, but it was good enough for 90% of the tasks that really needed simple lightweight objects. But, certain vested software interests demanded that the spec be extended to include things like templates and virtual this and that, all designed to save some corporate programming group some design time, at the expense of creating a spec that required Talmudic scholars to interpret.
I've been on the outside of Java, watching it since it was first described, and I've seen the changes and additions to the language spec over the years. The same thing is happening to Java that I saw happen to X and C++, and I predict that in 10 years or so someone will come out with a language "that does what Java does without all the overhead". I knew Java was doomed to follow the C++/X path when they announced namespace support in the language. Sorry, Javaheads, but that was the tipping point, and you're all on that long slide into obfuscation and bloat that many derided C++ for.
I know many who actually read this post won't believe it, will argue that "Java is different" somehow, but mark my words, Java will bloat into uselessness within 10 years, just like C++ did.
The parent poster should have said "mandatory UNPAID overtime", which is typical in software development shops. And "exempt" means that you are exempt from the wage/price laws which require payment for overtime. If you're a programmer and not self-employed, you are on salary which lets the employers exempt you from being paid for the time you work.
Plus, no one is saying that they shouldn't sell these complicated phone computers, it's just that it would be nice to have the option of simplicity.
The main problem with the "just don't use the features" response is that the complicated phones can break more easily, due to so many more things that can break. And if the functions are interrelated somehow, losing one "feature" could actually disable many others at the same time.
KISS is not just a rock band, but the phone companies don't seem to care.
Not to mention MSoft will be happy to sell anyone who is "switching" a copy of VirtualPC (which will no longer need to emulate an x86) along with a licence for Windows, so they will still make some money off of the switchers.
#6 presumes that the increased precipitation falls as snow. Nothing to prevent the precipitation from falling as rain, since the average air temperature will be higher for longer.
Global warming may well mean a new ice age for Europe.
I've asked this before, and I'll ask it again: How can Europe freeze with massive glacier growth, when Asia and North America at the same latitudes are experiencing melting of permafrost? How can it be globally so warm that glaciers are disappearing, yet it will be so cold that European glaciers will not only stop shrinking, but will start growing back?
And if it's all because of the Gulf Stream shutting down the warm air, how is it that major land masses far from the Gulf Stream are also warm enough to prevent glaciers from growing? How will Europe suddenly become colder than the Arctic, where pack ice is disappearing?
I expect to be modded down and ignored, but at least this post will be in the database somewhere...
Plus creating some kind of justification to keep a US military presence in South Korea, just like every time we've threatened to close down and pull out our troops. It's alright for the people to protest and demand that we leave, but not when we actually start planning to do so.
Slashdot Mirror
I have VLC 0.83 installed on my Mac. If the .wmv is for WMP 10, I get an error message about the codec. I'm not going to waste my time trying find the magic combination of codecs just on the off-chance that I might be able to play that particular .wmv file. I've lived nearly 50 years without .wmv files in my life, I can survive quite well without them for another 50 if need be.
Yeah. Finding that out saved me the waste of bandwidth downloading a file only to find out that nothing on my Mac would play it.
But since others in the world can play it, all must be right with the world...
There's room for a line here about "Open Source Conception," but I'm not touching it...
I just want a small island in the South Pacific: Australia!
PWI. Just say no, kids!
The Lagrange points are orbits, they just happen to be fixed in relation to the orbits of the other two bodies. L4 and L5 are also called "Trojan points" (Google is your friend). They are 60 degrees ahead and 60 degrees behind the Moon, in this case, and orbiting the earth at the same orbital radius and speed as the Moon. What effectively happens is, the gravitational pull of the Earth and the Moon are equal at that distance, so anything in orbit in either of those places never catches up to the Moon, nor does the Moon catch up to the other. If you were in orbit around the Earth at the same distance as the Moon, eventually either the Earth or the Moon's gravity would pull you out of the stable orbit towards one or the other, whichever was closer.
Well, anyway, go sober up, drink lots of water, and read this in the afternoon.
I'm 47 and just squeek under the wire! I find it fascinating that in every reply from those who diagrammed sentences, there are no grammatical mistakes.
:-)
Except perhaps in this one!
If they ever build a quantum grid computer, they should make it 300 qbits long, 50 qbits wide, and 30 qbits high...
"Howard Johnson is right!"
And other TLAs. There should be a moratorium on any more acronyms being added to Java. No language should have more than two or three TLA or FLAs, at the most. When you have acronyms that are as long as the language you're acronyming, that's too much!
I mean, I've seen MILSPECs with fewer T/FLAs than Java has spawned! Hell, even the MILSPEC computer language doesn't have that many!
un.org.anized.
I've been in the profession for over 20 years, and I've seen the same thing happen to certain "standards". Something new and innovative will come along, and within a decade, features will be added that will make it unusable, and foster the demand for "something like X but easier/simpler/faster/cleaner". Most of the feature creep is driven by large corporate interests and the demands of their programming staffs to add features that they claim they can't develop without.
Not many people remember X Window 10R4, but the entire Xlib documentation took up a half-inch thick stack of single-sided pages, and described a basic networked window system that was useful enough to develop distributed systems with. The protocol was easy to implement, straightforward, and clean. But that wasn't good enough for the wonks at Apollo, DEC, HP, Sun, AT&T, and the researchers at MIT. So, once everyone added their "must have" requirements to X Window (we have to have font servers or we can't write good systems!) you ended up with a monstrosity of an Xlib spec that took up a thousand or so pages of documentation, added thousands of new points of failure, and spawned an entire bookshelf from O'Reilly just to try to explain how to use X.
I saw the same thing happen to C++. In the early days it was what it set out to be, a simple, easy to implement extension to C that let you do basic object oriented programming. Sure, it wasn't Smalltalk or Scheme, but it was good enough for 90% of the tasks that really needed simple lightweight objects. But, certain vested software interests demanded that the spec be extended to include things like templates and virtual this and that, all designed to save some corporate programming group some design time, at the expense of creating a spec that required Talmudic scholars to interpret.
I've been on the outside of Java, watching it since it was first described, and I've seen the changes and additions to the language spec over the years. The same thing is happening to Java that I saw happen to X and C++, and I predict that in 10 years or so someone will come out with a language "that does what Java does without all the overhead". I knew Java was doomed to follow the C++/X path when they announced namespace support in the language. Sorry, Javaheads, but that was the tipping point, and you're all on that long slide into obfuscation and bloat that many derided C++ for.
I know many who actually read this post won't believe it, will argue that "Java is different" somehow, but mark my words, Java will bloat into uselessness within 10 years, just like C++ did.
All the systems I've seen seem to be the "sad big eyed kids" type...
The parent poster should have said "mandatory UNPAID overtime", which is typical in software development shops. And "exempt" means that you are exempt from the wage/price laws which require payment for overtime. If you're a programmer and not self-employed, you are on salary which lets the employers exempt you from being paid for the time you work.
Plus, no one is saying that they shouldn't sell these complicated phone computers, it's just that it would be nice to have the option of simplicity.
The main problem with the "just don't use the features" response is that the complicated phones can break more easily, due to so many more things that can break. And if the functions are interrelated somehow, losing one "feature" could actually disable many others at the same time.
KISS is not just a rock band, but the phone companies don't seem to care.
The horror...
Not to mention MSoft will be happy to sell anyone who is "switching" a copy of VirtualPC (which will no longer need to emulate an x86) along with a licence for Windows, so they will still make some money off of the switchers.
Not a big lose for them, either.
Although I have a large skull, most of it is nice thick bone, to protect my walnut-sized brain...
(I typed this using the small auxiliary nerve cluster near the base of my spine. As if there was any doubt...)
It would be really interesting if MS insisted that every OSX box ship with a copy of VirtualPC...
#6 presumes that the increased precipitation falls as snow. Nothing to prevent the precipitation from falling as rain, since the average air temperature will be higher for longer.
Maybe they should try selling him as a more efficient water heater...
Gao.
I've asked this before, and I'll ask it again: How can Europe freeze with massive glacier growth, when Asia and North America at the same latitudes are experiencing melting of permafrost? How can it be globally so warm that glaciers are disappearing, yet it will be so cold that European glaciers will not only stop shrinking, but will start growing back?
And if it's all because of the Gulf Stream shutting down the warm air, how is it that major land masses far from the Gulf Stream are also warm enough to prevent glaciers from growing? How will Europe suddenly become colder than the Arctic, where pack ice is disappearing?
I expect to be modded down and ignored, but at least this post will be in the database somewhere...
Plus creating some kind of justification to keep a US military presence in South Korea, just like every time we've threatened to close down and pull out our troops. It's alright for the people to protest and demand that we leave, but not when we actually start planning to do so.