Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #29807
| Newsgroups | comp.lang.python |
|---|---|
| Date | 2012-09-23 04:17 -0700 |
| References | (3 earlier) <mailman.1048.1348267711.27098.python-list@python.org> <gMg7s.19626$bQ3.17648@fx01.am4> <mailman.1075.1348314294.27098.python-list@python.org> <505db7f5$0$29981$c3e8da3$5496439d@news.astraweb.com> <mailman.1079.1348323012.27098.python-list@python.org> |
| Subject | Re: Blue Screen Python |
| From | 88888 Dihedral <dihedral88888@googlemail.com> |
| Message-ID | <mailman.1115.1348399043.27098.python-list@python.org> (permalink) |
Chris Angelico於 2012年9月22日星期六UTC+8下午10時10分12秒寫道: > On Sat, Sep 22, 2012 at 11:07 PM, Steven D'Aprano > > <steve+comp.lang.python@pearwood.info> wrote: > > > As per their partnership agreement, IBM took over development of OS/2 > > > version 2 while Microsoft worked on developing version 3. OS/2 2.0 was > > > significantly improved over the 1.x series. > > > > > > Then Microsoft reneged on the agreement to release OS/2 version 3, and > > > instead re-badged it as Windows NT. One might say there was a little bit > > > of bad blood over this, especially as IBM had good reason to think that > > > Microsoft had been spending IBM's money on NT. > > > > And ever since then, Microsoft's been doing its best to kill OS/2 off. > > By the look of the database server sitting next to me, and the clients > > scattered throughout the building, it seems they have yet to > > succeed... > > > > OS/2 and Linux interoperate quite happily, too. Standards so . > > > > ChrisA This is off topic in this forum. But we are getting so far at the MMU part. A cpu with an L1 and an L2 caches of large sizes is better to be equipped with a VMS like OS in the thread and the heap managements. But if the situation is different, some other alternative approaches might be more appropriate.
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