@Jaime Y'all'n should have seen the build process for NT 3.5, 3.5.1, and 4.0. (I worked for one of the very first and very few holders of a source license; they bet the farm on NT ~1991. They lost the farm, but that was only one of three major reasons.) It was based on an early incarnation of MSBuild (which was also the build tool bundled with the DDK for some number of further years). 6000 directories; I forget how many targets. A full build took 20 hours on a dual Pentium 90 and consumed every square micron of a 9Gb drive.
Frank Wilhoit
@Frank Wilhoit
Best posts made by Frank Wilhoit
-
RE: The MS release toolchain is :trwtf:
-
RE: Shallow eyeballs make many bugs
@izzion The last graf of the linked article contains this excellent advice: "...As a temporary measure to neutralize the flaws, Nichols recommends blacklisting the kernel if its’s not being used...."
Yes, we know what he means; but...
-
RE: The MS release toolchain is :trwtf:
@topspin Don't know where they got it. It was 5.25" full-height and it ran hot enough to burn your finger. It was a grim sort of fun working inside 32-bit Windows, implementing PSExec before it existed, discovering that some of the DDK documentation was sheer bluff (cough spinlocks cough cough), that parts of the MP kernel weren't actually multiprocessor-safe, that some of the DCE RPC APIs were stubbed out (that one cost them one billion dollars, with a 'b'), finding the header comments in assembly-language files saying "This is 32-bit OS/2, Author: David Cutler", analyzing crash dumps due to bad memory, ...
-
RE: Which Firefox?
@dcon There are (at least) two financial-industry sites that have recently begun to refuse Firefox unless it is started with extensions disabled. One of them has the grace to explain this; the other just goes into a loop. Doubtless someone read an article that put the wind up them.
-
RE: MOVs all the way down
Note the sponsor -- a deeply weird organization with a very long, and occasionally startling, history.
-
RE: Amazon out to kill every WISP in existence
@izzion I'm out to kill every wasp (NB. Hymenoptera, not acronymic) in existence. This goal is of course purely aspirational.
-
RE: The most idiotic idea about types ever
@sh_code Not the most idiotic idea ever, no. There have been at least two worse: "duck typing" and "there is only one type, and it is this here particular processor's native word". But you do raise two good questions: (A) how should reflection be implemented for "low level" types? (B) what price bits? -- in other words, how much computing resource (memory space, memory bandwidth, processor overhead) are we, or should we be, willing to pay for semantic integrity? Everyone who has attempted to answer these questions (typically without fully and rigorously understanding them) has come up with a different answer: and some of the answers have been quite silly.
Latest posts made by Frank Wilhoit
-
RE: The most idiotic idea about types ever
@sh_code Not the most idiotic idea ever, no. There have been at least two worse: "duck typing" and "there is only one type, and it is this here particular processor's native word". But you do raise two good questions: (A) how should reflection be implemented for "low level" types? (B) what price bits? -- in other words, how much computing resource (memory space, memory bandwidth, processor overhead) are we, or should we be, willing to pay for semantic integrity? Everyone who has attempted to answer these questions (typically without fully and rigorously understanding them) has come up with a different answer: and some of the answers have been quite silly.
-
RE: MOVs all the way down
Note the sponsor -- a deeply weird organization with a very long, and occasionally startling, history.
-
RE: Amazon out to kill every WISP in existence
@izzion I'm out to kill every wasp (NB. Hymenoptera, not acronymic) in existence. This goal is of course purely aspirational.
-
RE: The MS release toolchain is :trwtf:
@topspin Don't know where they got it. It was 5.25" full-height and it ran hot enough to burn your finger. It was a grim sort of fun working inside 32-bit Windows, implementing PSExec before it existed, discovering that some of the DDK documentation was sheer bluff (cough spinlocks cough cough), that parts of the MP kernel weren't actually multiprocessor-safe, that some of the DCE RPC APIs were stubbed out (that one cost them one billion dollars, with a 'b'), finding the header comments in assembly-language files saying "This is 32-bit OS/2, Author: David Cutler", analyzing crash dumps due to bad memory, ...
-
RE: The MS release toolchain is :trwtf:
@Jaime Y'all'n should have seen the build process for NT 3.5, 3.5.1, and 4.0. (I worked for one of the very first and very few holders of a source license; they bet the farm on NT ~1991. They lost the farm, but that was only one of three major reasons.) It was based on an early incarnation of MSBuild (which was also the build tool bundled with the DDK for some number of further years). 6000 directories; I forget how many targets. A full build took 20 hours on a dual Pentium 90 and consumed every square micron of a 9Gb drive.
-
RE: Intel is the jealous ex
@Atazhaia said in Intel is the jealous ex:
driving more and more people away from Intel
Not possible. Every user is locked into a platform and the platform chooses the vendors. Plenty of people wanted to stay with the 680x0 family. They had no choice. Some people probably wanted to stay with PowerPC (Stockholm Syndrome is a very powerful thing); they had no choice either. The only thing driving people away from Intel is Apple. It may be a good thing, especially in the light of grievances such as this; but no one is in a position to choose a processor vendor, except maybe as between Intel and AMD, and not even that in the Apple ecosystem. -
RE: Which Firefox?
@dcon There are (at least) two financial-industry sites that have recently begun to refuse Firefox unless it is started with extensions disabled. One of them has the grace to explain this; the other just goes into a loop. Doubtless someone read an article that put the wind up them.
-
RE: Shallow eyeballs make many bugs
@izzion The last graf of the linked article contains this excellent advice: "...As a temporary measure to neutralize the flaws, Nichols recommends blacklisting the kernel if its’s not being used...."
Yes, we know what he means; but...