Now you just have to tell the Xbox One team about this feature...
Jun 06, 2013 at 8:12 AM
Wouldn't the correct fix for most issues be a change in how the .NET framework works? Concating strings with chars shouldn't auto-box, for example. Is anyone fixing these things?
Jun 05, 2013 at 7:37 AM
If DirectAccess was available for Win8 Pro I'd totally use it. Right now, I can't. Heard about BYOD?
Feb 18, 2013 at 8:21 AM
Hello Surface Pro. Hello! Hello? Anybody there?
Oh. Surface Pro is not yet available in Europe... When will it? Nodobody knows. When will we get more information? Nobody knows. But it could be oh so simple, just take my money.
Bruce is an excellent presenter. I would love to see more data (numbers). Is there a Windows power blog?
The implementation of the feature is pretty odd. I would've implemented it a bit differently. Some alternatives:
- Collect startup profiles automatically for each and every application.
- Run NGEN in the background when you launch a non-ngened app.
I see the benefits of the API but if you did it this way every single app would benefit from the Multicore JIT. Now only a few apps will benefit since most developers will never learn about all this cool technology. At least you could've managed the profile directory automatically...
In the video you talked about command line arguments. Most apps probably won't use command line arguments. And the developers caring about that scenario could still add calls to the current API.
It'd be great if you could elaborate more why you implemented the way it is.
I'm interested (just a partial list, in no particular order) in the following topics:
- How does the filesystem perform in your bechmarks. What are it's strengths/weaknesses? I'll take that with numbers & charts please .)
- How does it solve the wandering tree problem? With Object-IDs?
- How is cleanup performed? On-demand? What policies are in place? How does this affect performance? What about defragmentation? Are segments used?
- How is allocation done? I'm interested in the policies. How does that affect locality?
- How are transactions supported?
- Are there any special provisions in place for flash media?
- Is there a single B+ tree on the disk? One per table?
- How are snapshots recorded? Is old metadata kept separate? Or is everything in a single big structure?
- What are the future plans for the FS, except the obvious support for some missing NTFS-features.
- Where are the weaknesses compared to NTFS?
- How are explicit flushes (user requested) handled?
- How will you handle future changes? Any provisions for on-disk layout changes?