Forum Home
PC World Chat
Thread ID: 71857	2006-08-19 15:48:00	Vista Joins MS Patch Treadmill	SurferJoe46 (51)	PC World Chat

Post ID	Timestamp	Content	User
479532	2006-08-20 14:53:00	. microsoft . com/os/singularity/" target="_blank">research . microsoft . com Let's see if I have this part (from your link) correct: "A key starting point is Singularity processes, which start empty and add features only as required . (Sounds like stacks and dumps to me!) Modern language runtimes come with huge libraries and expressive, dynamic language features such as reflection . This richness comes at a price . Features such as code access security or reflection incur massive overhead, even when never used . A Singularity application specifies which libraries it needs, and the Bartok compiler brings together the code and eliminates unneeded functionality through a process called "tree shaking," which deletes unused classes, methods, and even fields . As a result, a simple C# "Hello World" process in Singularity requires less memory than the equivalent C/C++ program running on most UNIX or Windows® systems . Moreover, Bartok translates from Microsoft® intermediate language (MSIL) into highly optimized x86 code . It performs interprocedural optimization to eliminate redundant run-time safety tests, reducing the cost of language safety . " This appears to keep the calls to a library unused until an absolute need for the call (process or loop . . . a "do" loop?) or pointer . . . right? Cutting the preload (prefetch) to a minimum is a good idea, if you have the time to make a library call start from scratch every time you need it . If so, then what device is used to decide which call to make? There must be a large library somewhere that is running all the time . At least, there has to be a language decoder and directory or identifier running to know what's accessable or not, and which has it's files open and running verses those that are awaiting being called . This is an attempt to keep the "board" (as just one focal point) free of operations . . . another trick we used in FORTH to keep clutter to a minimum . . . like putting one toy away to play with another one . The purpose I see here is to just minimize the exposure of the call, keeping it easier to protect from malcode and hacks . . . right? Again, transition time from opening and then closing a file for the next call/process is very time consuming . However, just who or what is watching over the store and deciding what is needed and what isn't? Seems the overhead there is large and open to malcode too not to mention abuse of resourses and memory .	SurferJoe46 (51)
479533	2006-08-20 21:57:00	. like putting one toy away to play with another one . I leave you all to draw your own conclusions . . . .	pctek (84)
1 2