Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


itsnotabug itsnotabug
  • Seems like metro on the desktop is a done deal

    well, no doubt pro-audio is a big niche, but it probably pales in comparison to the vast majority of boring lob apps where 100ms latency is fine. james dailey seems to be optimistic, but for some reason, it's not a priority. "As a musician myself I have been pushing to see the platform support round trip latencies in the 15 - 20 ms range. I think that this is totally possible with the current architecture. Unfortunately at this time this really isn't on the roadmap. I will keep pushing and we will have to see how the platform evolves."

    personally, i would love to be able to fool around with interface ideas to trigger and sequence sounds in realtime. there should be a petition or something.


  • Seems like metro on the desktop is a done deal

    @bitflipper yep. i'm a big fan of nanostudio on ios and its developer (matt) has this thread running on msdn. i think it goes into some detail on the limitations you allude to.


  • Seems like metro on the desktop is a done deal

    i didn't say it was a good plan :D

  • surface pro 3 as dev machine?

    90% of the time, i will be in desktop mode with 2nd monitor. i hope the dock comes out soon though. i don't like touchpads so will be bringing a mouse everywhere. i think the tablet aspect will just be icing on the cake when i'm traveling for work. i hate having to lug around a laptop + ipad with incompatible power supplies/chargers.

  • Seems like metro on the desktop is a done deal

    i feel like a sku-morphic windows 9 with the windowed rt apps + start menu with live tiles was the end goal all along. by releasing windows 8 they were able to:

    1) buy more time

    2) get real feedback/testing for the rt/tablet side of things. despite being forced, it exposed a lot of people to the idea of a usable windows tablet

    3) use a throwaway os to get past the 'every other major version of windows is crap' belief (i don't believe this, but the perception is out there)

    i suspect windows 9 will be released alongside a more complete rt api that will allow easy porting from win32, at least for the apis used heavily in enterprise.

  • surface pro 3 as dev machine?

    i'm shopping around for a new laptop and while i know that it can technically run visual studio without a problem, i'm interested in hearing real world anecdotal experiences or gotchas with the form factor. can you do serious work with it? is the display sufficient for your needs? is it easily 'dockable' with a mouse and external keyboard, 2nd monitor setup? the reviews seem to say that it's not quite a laptop and not quite a tablet. how do YOU like it?

  • History

    cringeworthy, although i do have an appreciation for mathew perry's geekiness. i just learned he was a voice actor in fallout 3 new vegas and genuinely loves the series. http://youtu.be/yAbRzjRRLds

  • read-​thru/write-​thru cached generic list?

    yes this gets even trickier with multi-threading. maybe the newer ConcurrentDictionary would be better used for this. i'm essentially going for a 'live' cached generic List<T> that automatically syncs to it's corresponding db table on touches. i can eliminate a lot of the complexity if i just assume that the entire table will fit in memory.

  • read-​thru/write-​thru cached generic list?

    yeah i suppose so, but i'm thinking that it shouldn't be aware of the implementation of the backing store and generalized for any List<T>. most repository patterns i've seen have a distinct repository per entity/table. i could use a micro-orm like sqllite, dapper or petapoco to get the typed entity experience and convenient crud stuff within my concrete implementation. the more i think about it, it becomes trickier, especially if i'm working with a large table that wouldn't necessarily fit in memory, so there would have to be rules about invalidating/removing from cache the rarely used items.

  • read-​thru/write-​thru cached generic list?

    i've been thinking about an abstract data structure that seamlessly caches a list of Something and exposes overrides like OnSomethingAdded, OnSomethingDeleted, OnSomethingUpdated for you to handle the persistence to a backing datastore. GetSomethingById(), GetAllSomethings(), AddOrUpdateSomething(), etc... methods on the list would do the standard caching patterns like checking whether the Something was in the list by key and acting on it, if not, then it would try to find it in the database by key, if it's found then it would add it to the list and return the Something or null. has someone already built something like this? time to expire and linq support against the list would be nice too. i'm sure the full-fledged orms have already figured this out, but i'm looking for something light-weight.