Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #29743
| Date | 2012-09-22 07:44 -0400 |
|---|---|
| From | Dave Angel <d@davea.name> |
| Subject | Re: Blue Screen Python |
| References | <7c8701cc-1bc5-46ee-a83a-3e9a038ceada@googlegroups.com> <k3i09d$in$2@reader1.panix.com> <gb07s.566859$LO.119209@fx26.am4> <mailman.1048.1348267711.27098.python-list@python.org> <gMg7s.19626$bQ3.17648@fx01.am4> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1075.1348314294.27098.python-list@python.org> (permalink) |
On 09/22/2012 06:53 AM, Alister wrote: > On Fri, 21 Sep 2012 18:47:57 -0400, Dave Angel wrote: > >> <SNIP> >> >> That's not true at all. You'd re thinking of Windows 3, Windows 95, 98, >> and ME, which were hacked on top of MSDOS. But Windows NT3.5, 4, 2000, >> XP, Vista and Windows 7 have an entirely different bloodline. >> >> NT 3.51 was actually very robust, but in 4.0 to gain better performance, >> they apparently did some compromising in the video driver's isolation. >> And who knows what's happened since then. > Although NT upwards has tried to introduce Your wording seems to imply that you still think NT was built on some earlier MS product. It was written from scratch by a team recruited mostly from outside MS, including the leader, a guy who was I think experienced in VMS development. The names escape me right now. But there were a couple of books, by Helen someone, I think, which helped us outsiders understand some of the philosophies of the development. > user-space requirements the > need to maintain backwards compatibility has compromised these efforts. > it is not helped by the end user's (just look at what happened to Vista's > attempt to make users authorise any changes to the system) > > I don't see any connection between memory address space user models and user security models. -- DaveA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Blue Screen Python mikcec82 <michele.cecere@gmail.com> - 2012-09-21 07:04 -0700
Re: Blue Screen Python Chris Angelico <rosuav@gmail.com> - 2012-09-22 00:29 +1000
Re: Blue Screen Python Grant Edwards <invalid@invalid.invalid> - 2012-09-21 15:14 +0000
Re: Blue Screen Python Alister <alister.ware@ntlworld.com> - 2012-09-21 16:01 +0000
Re: Blue Screen Python Alister <alister.ware@ntlworld.com> - 2012-09-21 16:02 +0000
Re: Blue Screen Python Dave Angel <d@davea.name> - 2012-09-21 18:47 -0400
Re: Blue Screen Python Alister <alister.ware@ntlworld.com> - 2012-09-22 10:53 +0000
Re: Blue Screen Python Dave Angel <d@davea.name> - 2012-09-22 07:44 -0400
Re: Blue Screen Python 88888 Dihedral <dihedral88888@googlemail.com> - 2012-09-22 05:19 -0700
Re: Blue Screen Python 88888 Dihedral <dihedral88888@googlemail.com> - 2012-09-22 05:19 -0700
Re: Blue Screen Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-09-22 13:07 +0000
Re: Blue Screen Python Chris Angelico <rosuav@gmail.com> - 2012-09-23 00:10 +1000
Re: Blue Screen Python 88888 Dihedral <dihedral88888@googlemail.com> - 2012-09-23 04:17 -0700
Re: Blue Screen Python 88888 Dihedral <dihedral88888@googlemail.com> - 2012-09-23 04:17 -0700
Re: Blue Screen Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2012-09-22 13:53 +0100
Re: Blue Screen Python mikcec82 <michele.cecere@gmail.com> - 2012-10-09 00:37 -0700
Re: Blue Screen Python Philipp Hagemeister <phihag@phihag.de> - 2012-10-09 12:32 +0200
Re: Blue Screen Python mikcec82 <michele.cecere@gmail.com> - 2012-10-09 05:10 -0700
Re: Blue Screen Python mikcec82 <michele.cecere@gmail.com> - 2012-10-22 06:15 -0700
csiph-web