So because you can't figure out wtf is wrong it must be a faulty network stack, right. I'm calling user error. My network stack is working so you must be wrong.
Which is why there are ready to play distributions such as ubuntu for the masses. I've installed countless ubuntu systems on people with little technical expertise that don't understand why they have 10 browser tool bars in their IE install and wonder why their computers run like shit. In every case I give them little information, and they are fine finding the "start" menu at the top of the screen and running a web broswer to waste hours on youtube, or finding a suitable mail client equivalent. At what point did they have to use the CLI and compile something by hand to get a working GUI? As far as I know, this was all built in ready to run.
I saw this as the intention and was referring to developers in the sense of microsoft's own.
On a related but side note, the navigation of a long list of unrelated, albietly grouped, tweaks doesn't make it very easy to navigate.
Developers are not end users and Microsoft's probable line of thinking is that the current implementation is appropriate for the masses as being easier to use.
Is any of that DNA in use or are those parts dormant? What effect do these modifications have on us beyond the initial use of replication and further propagation of viruses?
I would indeed count it among the other shuttles in the program, it seems that some at NASA found it meaningful as well. Others though find it as only an incremental footnote of history.
To quote wikipedia
"The Space Shuttle Enterprise (NASA Orbiter Vehicle Designation: OV-101) was the first Space Shuttle orbiter. It was built for NASA as part of the Space Shuttle program to perform test flights in the atmosphere.[2] It was constructed without engines or a functional heat shield, and was therefore not capable of spaceflight.
Originally, Enterprise had been intended to be refitted for orbital flight, which would have made it the second space shuttle to fly after Columbia.[2] However, during the construction of Columbia, details of the final design changed, particularly with regard to the weight of the fuselage and wings. Refitting Enterprise for flight would have involved dismantling the orbiter and returning the sections to subcontractors across the country. As this was an expensive proposition, it was determined to be less costly to build Challenger around a body frame (STA-099) that had been created as a test article.[2] Similarly, Enterprise was considered for refit to replace Challenger after the latter was destroyed, but Endeavour was built from structural spares instead.[2][3]"
Why not give em the cables and monitor everything coming down them?
Oh I remember why, surely our government would never do such a thing./tinfoil hat time
Well, no, wrong, you can brick MANY things by the definition of bricking. I can brick my processor by overheating it etc. How exactly are you going to salvage an overheated processor?
So no, my definition is generally what people used when the word first came into computing/hardware use. When you can revive a device by simply downloading a software fix from apple, that is NO WHERE NEAR a brick.
Brick means the only thing the device is good for, is being a brick. It means the device is irrevocably damaged, ie can NEVER be fixed. I bet a quick software update can fix this issue.
Slashdot Mirror
So because you can't figure out wtf is wrong it must be a faulty network stack, right. I'm calling user error. My network stack is working so you must be wrong.
Which is why there are ready to play distributions such as ubuntu for the masses. I've installed countless ubuntu systems on people with little technical expertise that don't understand why they have 10 browser tool bars in their IE install and wonder why their computers run like shit. In every case I give them little information, and they are fine finding the "start" menu at the top of the screen and running a web broswer to waste hours on youtube, or finding a suitable mail client equivalent. At what point did they have to use the CLI and compile something by hand to get a working GUI? As far as I know, this was all built in ready to run.
http://free.editdns.net/ ?
I can tolerate SW 4-5-6..
Fixed that for you.
Are the cserve id's not octal and thus wouldn't contain 8 or 9's?
Fwoosh.
I would consider these "modifiers and triggers" not dormant if they played a role.
Maybe they force him to use 128-bit RSA. He didn't really specify.
Before we receive some epic amateur porn.
I saw this as the intention and was referring to developers in the sense of microsoft's own. On a related but side note, the navigation of a long list of unrelated, albietly grouped, tweaks doesn't make it very easy to navigate.
Developers are not end users and Microsoft's probable line of thinking is that the current implementation is appropriate for the masses as being easier to use.
it is a good day to die
Is any of that DNA in use or are those parts dormant? What effect do these modifications have on us beyond the initial use of replication and further propagation of viruses?
I would indeed count it among the other shuttles in the program, it seems that some at NASA found it meaningful as well. Others though find it as only an incremental footnote of history.
To quote wikipedia "The Space Shuttle Enterprise (NASA Orbiter Vehicle Designation: OV-101) was the first Space Shuttle orbiter. It was built for NASA as part of the Space Shuttle program to perform test flights in the atmosphere.[2] It was constructed without engines or a functional heat shield, and was therefore not capable of spaceflight. Originally, Enterprise had been intended to be refitted for orbital flight, which would have made it the second space shuttle to fly after Columbia.[2] However, during the construction of Columbia, details of the final design changed, particularly with regard to the weight of the fuselage and wings. Refitting Enterprise for flight would have involved dismantling the orbiter and returning the sections to subcontractors across the country. As this was an expensive proposition, it was determined to be less costly to build Challenger around a body frame (STA-099) that had been created as a test article.[2] Similarly, Enterprise was considered for refit to replace Challenger after the latter was destroyed, but Endeavour was built from structural spares instead.[2][3]"
Evidence of the unas?
The second picture of the chair totally looks like a goatse. Amirite? http://www.sankakucomplex.com/wp-content/gallery/cache/33373__448x_exploded-chair-gas-cylinder.jpg
I totally just did a double take when it said only 6 comments,then I realized its not news, its idle.
Subby has it wrong. These are not 16 megapixel. You went through all that trouble to mention it's a Mark II. ( They are in the 21 megapixel range. )
I can watch.
is Principle Skinner. "I dont have any opinions anymore. All I know is that no one is better than anyone else and everyone is the best at everything."
Why not give em the cables and monitor everything coming down them? Oh I remember why, surely our government would never do such a thing. /tinfoil hat time
Yes, I'm sorry the BETA did not behave as expected. Be sure to skip out on the release.
Well, no, wrong, you can brick MANY things by the definition of bricking. I can brick my processor by overheating it etc. How exactly are you going to salvage an overheated processor? So no, my definition is generally what people used when the word first came into computing/hardware use. When you can revive a device by simply downloading a software fix from apple, that is NO WHERE NEAR a brick.
Brick means the only thing the device is good for, is being a brick. It means the device is irrevocably damaged, ie can NEVER be fixed. I bet a quick software update can fix this issue.