![]() |
|
|
Thread Tools | Display Modes |
#81
|
|||
|
|||
![]() "Dave Michelson" wrote in message news:%XK9c.37119$R27.31744@pd7tw2no... You know the reason that "millions of people" use Microsoft: They're forced to maintain compatibility with the MS Office file formats. Because these file formats are not Open Standards, no one can build applications that can compete with MS Office, handing MS a defacto monopoly. Since I have on my desktop three non-MS Office suites that easily read the Office files I produce, this is clearly demonstrable nonsense. My system, which runs Win98SE, came with StarOffice. I also have OpenOffice and EasyOffice (which I include on my real estate book's CD to use the MS Office files I've created). I have yet to have a problem, and I use Office 2000. I'm about to add another workstation to my office, and it will have EasyOffice. If businesses don't want to put forth the effort it would take to train their employees in new software, it's hardly *MicroSoft*'s responsibility. Apathy and inertia to change on the part of the free market simply means that MicroSoft has provided what the market wants. There are alternatives out there. It's clear that they *are not* better than what the public is using now, or else the public would be using them. In my case, my system came with StarOffice when I bought it in 2000. I was already using MS Office 97 and later bought Office 2000. I started using EasyOffice because it was free, and it was good enough for my third workstation. Office 2000 came with Publisher, which I still use. In other words, *the alternatives are available*, even at Wal-Mart, as is information about them. The public has spoken, and continues to speak every time they buy a system loaded with MS software. The alternatives aren't better enough for the general public to give a rat's ass about them. They aren't being *forced* to buy MS software, they choose to buy because it isn't important enough to them to put forth the effort to check out the alternatives. MS did not invent public apathy, it just talks advantage of it, *which is a good thing* economically, and MS would be failing its responsibilities to its shareholders not to encourage apathy. I tried Linux. At the time it wasn't worth the learning curve and it did not operate my most important software, Office 97. I'll try it again sometime this year, with different software. |
#82
|
|||
|
|||
![]() "Greg D. Moore (Strider)" wrote in message news ![]() My laptop is over 3 years old, only maintenance I do is apply patches as required and defrag the disk. I can't remember if it's crashed at all or not. I don't believe so. My computers crash at least once a week, but that isn't MicroSoft's fault- I keep screwing around with them. If I left them alone they'd run just fine. More power! |
#83
|
|||
|
|||
![]() "Scott Hedrick" wrote in message . .. "Greg D. Moore (Strider)" wrote in message news ![]() My laptop is over 3 years old, only maintenance I do is apply patches as required and defrag the disk. I can't remember if it's crashed at all or not. I don't believe so. My computers crash at least once a week, but that isn't MicroSoft's fault- I keep screwing around with them. If I left them alone they'd run just fine. I've had XP Pro on my new machine, it hasn't crashed once. Certainly some apps have, most notably Outlook Express 6, but not WinXP itself. It's much, much better in that regard than Win98SE, 98 or 95B. |
#84
|
|||
|
|||
![]()
rk wrote:
OK, so you can't show any lineage for the FBW systems from Airbus. Airbus introduced FBW to commercial aviation in 1987 on the A320. It wasn't only the "FBW" portion that was new, but also the sophisticated flight management software that automated much of aircraft/cockpit, and introduced many error checking software to prevent pilot errors. (this was source of much debate). But Airbus was fraught with problems (read: Bugs) in its software for the first couple of years. (with Air France bearing the brunt of the problems). And the FAA was caught with its pants down because it had given the A320 its certificate without properly testing the software (since it hadn't designed software testing methods. Another issue was that of pilot training. Initial training focused on the switches and blinking lights. But pilots ended up fighting the aircraft instead of understanding how it worked. So Pilot training was changed to make pilots better understand the aircraft philosophy. Now, add a few years, during which Boeing had a lot of fun at Airbus's expense, and when Boeing did get into the FBW fray, it had learned a lot from the Airbus experience. During this time the FAA also had setup better testing procedures to monitor software quality. So the 777 (and airbus's other planes) were introduced with far fewer problems, and by now, you don't hear much criticism of FBW because the technology has matured. And that has what to do with technology development for the A380? Airbus didn't have any government imposed deadlines to launch and deliver the A380. It was a "nice project in study" for many years until they got reasonably sure that they could do it. There was also questions of how it would be financed. NASA is in a different position now. It has been given a deadline of 2008 (and hard deadline of 2010) to get a new vehicle up and running, and retire shuttle by 2010. So it's got roughly 3.5 years to get that CEV/whatever on the pad for its first test flight. And it has no budget to do that, and there are expectations that it will magically and dramatically reduce flight costs. Even if they are given massive amounts of money, I doubt that NASA could get such a totally new vehicle up and running by the deadline. Unless, of course, it becomes a race at any cost and without much concern for long term operating costs (which was the case for the moon shots). |
#85
|
|||
|
|||
![]()
Scott Hedrick wrote:
"JazzMan" wrote in message ... Thus, the free market in action. Nobody is forced to buy MS products. They Sigh... Nevermind. The way you folded when confronted with the facts is telling. Sure, you can see it that way if you want. Me? I just see it as arguing with a stone, it accomplishes nothing. JazzMan -- ************************************************** ******** Please reply to jsavage"at"airmail.net. Curse those darned bulk e-mailers! ************************************************** ******** "Rats and roaches live by competition under the laws of supply and demand. It is the privilege of human beings to live under the laws of justice and mercy." - Wendell Berry ************************************************** ******** |
#86
|
|||
|
|||
![]()
Jorge R. Frank wrote:
And Thank GOD for that. The mere thought of Microsoft-generated code running something as expensive as the Shuttle gives me cold shivers. Hate to break it to ya, but MS code does run on the shuttles. Granted, it's on the crew's laptop PCs and not the main flight computers, and it's not trusted for anything critical, but it's there. Jorge, You might re-read his post. He was referring to code that "runs the shuttle", not code that just happens to be going along for the ride. -- Dave Michelson |
#87
|
|||
|
|||
![]()
Mary Shafer wrote:
You do know, don't you, that it's still got to prove itself as being certifiable, economic to build, economic to fly, and economic to maintain? All the predictions in the world won't help if the airplane misses any of those goals. Correct. But the big difference is that if the 380 sinks instead of flies, it is Airbus that will bear the wrath of bankers wanting their money back, and airlines will just go shop elsewhere. Airlines have negotiated a fixed price with certain performance garantees and certain garantees on cost of operation. But if it does meet its goals, Airbus will deliver at least 100 of the beasts before the end of this decade. (It has sold nearly 130 by now). Now, if NASA were to choose a disposable vehicle, perhaps it could sign deals with Boeing to buy 100 vehicles over a period of 10 years at a fixed price. Lets look at the ET for the shuttle. I realise they are a technical problem for Columbia. But from a business point of view, aren't those as close to "commodity product" as one can get ? As I recall, one of the A380 issues was manufacturing the skin. In order to be strong enough, it has to be quite thick, so thick that it's more like plate. This means that different methods have to be used to shape it, as the usual tooling doesn't work on plate. What I had heard was that they developped new manufacturing techniques to produce not thicker sheets, but rather much larger in order to reduce joints/riveting (where much fatique occurs). They also implemented cold welding techniques to bond sheets together. (Still possible that it will be thicker). I believe that surface of the main wings will be made of a single sheet of aluminium. (except for moving surfaces, of course). |
#88
|
|||
|
|||
![]()
On Mon, 29 Mar 2004 01:42:27 -0400, John Doe wrote:
Now, add a few years, during which Boeing had a lot of fun at Airbus's expense, and when Boeing did get into the FBW fray, it had learned a lot from the Airbus experience. During this time the FAA also had setup better testing procedures to monitor software quality. So the 777 (and airbus's other planes) were introduced with far fewer problems, and by now, you don't hear much criticism of FBW because the technology has matured. You know, you can say pretty much the same thing about the F/A-18 and the F-16. GD/Lockheed got to solve a lot of the operational FBW problems on the F-16 and McAir took advantage of that when they built the F/A-18. Of course, Dryden had solved the basic FBW problems with the F-8 DFBW. So much so, in fact, that GD only went with FBW because of our success. Now FBW is old hat but I can remember when it was a Big Deal and we were considered to be real risk takers for not having a mechanical or hydraulic backup on the F-8. And that has what to do with technology development for the A380? Airbus didn't have any government imposed deadlines to launch and deliver the A380. It was a "nice project in study" for many years until they got reasonably sure that they could do it. There was also questions of how it would be financed. You do know, don't you, that it's still got to prove itself as being certifiable, economic to build, economic to fly, and economic to maintain? All the predictions in the world won't help if the airplane misses any of those goals. Look at the A340 on the Asian routes and all the problems it has for an example of a seemingly minor glitch in performance having a major effect in operation. As I recall, one of the A380 issues was manufacturing the skin. In order to be strong enough, it has to be quite thick, so thick that it's more like plate. This means that different methods have to be used to shape it, as the usual tooling doesn't work on plate. Mary -- Mary Shafer Retired aerospace research engineer |
#89
|
|||
|
|||
![]()
"Marvin" wrote ...
Windows is a very fancy system, its got more bells & whistles than anyone can discover in a lifetime. But what users actually need (despite contrary propaganda from microsoft), is a *stable* and *predictable* and *secure* system. That may be what users /need/ but what they /want/ is a stable, predictable and secure system with those *particular* bells and whistles that take their fancy. Not to mention that they want any applications they are interested in to be released for their OS. |
#90
|
|||
|
|||
![]() "Henry Spencer" wrote in message ... MOST, which weighs 53kg as launched and totalled maybe US$4M development cost, has a star tracker that holds it on target to within a few arcseconds. The software for it, while by no means trivial, is nothing supernatural (and I speak as the project's Software Architect). So your software is merely astronomical, then? ![]() |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Unofficial Space Shuttle Manifest | Steven S. Pietrobon | Space Shuttle | 2 | February 2nd 04 10:55 AM |
Unofficial Space Shuttle Launch Guide | Steven S. Pietrobon | Space Shuttle | 0 | February 2nd 04 03:33 AM |
Unofficial Space Shuttle Manifest | Steven S. Pietrobon | Space Shuttle | 0 | October 6th 03 02:59 AM |
Unofficial Space Shuttle Launch Guide | Steven S. Pietrobon | Space Shuttle | 0 | September 12th 03 01:37 AM |
Unofficial Space Shuttle Manifest | Steven S. Pietrobon | Space Shuttle | 0 | September 12th 03 01:37 AM |