Entries:
Comments:
Posts:

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

Discussions

androidi androidi
  • What are desirable ​'foundation​al' operating ​system/engi​ne features?

    Maybe support for automatic patch backporting? - this project claims to do more complex things but not as much what I suggested earlier which was ability to not only do backporting but also combine that with automatic translation from one language to another, allowing to have a source project in C/C++ and keep a C# or some other language project up to date with changes in the source while also keeping new features in added in C#. In spirit of classic embrace and extend. 

    http://crest.cs.ucl.ac.uk/autotransplantation/downloads/autotransplantation.pdf (credit to wired for picking it up)

    http://crest.cs.ucl.ac.uk/autotransplantation/MuScalpel.html

     

  • What are desirable ​'foundation​al' operating ​system/engi​ne features?

    There's probably a lot of such, taken for granted in most modern OS, however here's some that I like to mention here often, I just now compiled some of those that I remember into one place.

    - ability to use common good UI-design tools on top of any custom engine (= low level overlaying/composition where layers can be running at various frame rates / freesync/ g-sync)

    - low latency I/O for audio and user inputs across the OS - eg. suitable for realtime data acquisition and triggering external hardware on realtime schedule and minimal drift/jitter hardware osc/clock in the motherboard

    - easy to implement jitter free smooth scrolling (one possible benchmark is, how much invidual pixels you can get updated smoothly at fixed low enough interval, eg. 20 ms, while doing useful work in other cores)

    - security/tamper proof

    - moddability

    - code transparency/readability after compilation instead of 'read the source'

    - dynamic software updating - like JRebel ("Edit optimized code while running" - schedule updates to happen such that audio/gfx will run without audible/visible glitch)

    - for virtual machines the ability to optionally patch old snapshots with new updates so that the patches don't need to be applied to each snapshot separately after each snapshot recall - essentially a snapshottable virtual desktop or snapshottable process

    The last is no different from being able to save a game state, patch the game engine, then resume the saved game without things getting corrupt.. Yeah "mission impossible" if the game/engine/OS ships so buggy that it needs major patching. So this would need user visible patch classification so that user can decide whether they want to lose their state or not and be ideally be able to patch all security issues without losing state.

  • Faulty update time! (And again, W10..)

    @bondsbw: W10 "Never finished" Okay now I really regret selling my spare unopened W7 box too early. It was only going for 2x what I paid, maybe 3x would have been possible in a year.

     

     

     

     

  • WTF WIN10 auto update restart.

    I think that auto-updates and reliance on automated testing has enabled going to a point where "obvious 'edge'-case fault-finding" is being/has been outsourced to customers with the belief that it has zero negative impact. If product is so full of obvious edge case flaws that it's plain frustrating to use during first public releases the impression is not good. Like with VS2013 I think it was only by RTM update 3 when it was actually usable for very basic C# console app coding that I do. I simply didn't bother to report any bugs until RC/RTM as there was too much show stopping bugs, this is the RTM becoming the old beta. Currently with games I'll wait atleast 1 year after "RTM" before installing them... Soon perhaps I'll only install new software after 1 year of no new patches and then it probably turns out there's still thousand annoying bugs since no one either didn't bother testing it as too much manual testing had been outsourced to customers. (or worse, potential customers saw too much issues and went to look at if there was any better competition around ... well probably not if everyone has same standards lol)

     

  • Low voltage & frequency background task offloading?

    (Maybe all this has already been solved in WP in the way explained or otherwise, I haven't really looked)

    I read some press piece about saving iphone battery life by turning off the fitness background tracking thingy. Then I figured, well why would such thingy consume any noticeable battery amount if the amount of resources that needed amounted to some 80's home computer or less - isn't the problem really that if your ability to write sloppy code to a cpu that can boost to high frequencies is not limited, then the result is going to be higher battery use.

    I'm not sure if having some custom offloading processor is actually necessary, maybe the solution for background usage of the various sensors is simply having ability to run the background tasks with the primary cpu running at very low frequency so that the background tasks can collect data practically continuously without consuming much battery. I use similar approach on my old Pentium M laptop to run near-realtime data collection without setting off the noisy fans - I simply used the advanced power settings to force the cpu to never go above certain % of the max frequency.

    The way I see it, if there are multiple different background tasks of various natures, such as polling and realtime data capture (maybe you want to covertly record audio while not consuming any more battery than it really needs), then the battery saving problem boils down to making sure that expensive polling type behaviour is forcibly scheduled to not occur too often and various near-realtime/continuous types of data acquisition background activities should be each running the cpu only at frequency they really need - a further improvement would be to have low level/hardware based solution for capturing all the inputs and then have the app just specify a frequency at which they want to read the captured data/buffer.

     

    The benefit here is that this sort of possibly cpu intensive task would not be left to the average programmer but still enabled average programmer to create battery efficient realtime data acquisition solutions (essentially a gui for the low level capture functionality). Such low level functionality would probably have to use some sort of power efficient storage by itself if the capture produced lots of data, without needing to invoke the user written application to actually perform the saving of the data to disk. So when the user calls read data and save to disk API it would actually only copy or move the already saved pages to another location in the disk. (move would be similar to taking the captured data blocks in the 'page file' of the raw audio/video data and then assigning a filename to those blocks and putting some headers around them for later processing)

     

     

  • What bird noise was that in latest Mythbusters (breaking bad myth)

    Here's the exactly same sound from Strike Commander game intro:

    Yeah it's some hawk screech, any of them sound just like this or did they add some echo?

    (bummer no one has recorded the floppy ver intro etc with real mt32, sounds a lot better, none of the youtube mt32 recordings are infact sounding correct)

  • Did MS just save 6.6 billion in taxes?

    Well I'm sure big four/goldman can arrange some sort of scheme for turning those haven moneys into capital gains, for % fee.

     

     

     

  • Did MS just save 6.6 billion in taxes?

    Very clever. Buy Nokia for only $1 bil, then do some accounting to say it was 6.6 billion loss (I mean, 1 bil was a low ball bargain, not what it was really worth obviously - but since the phones didn't do well, it really is now a 7.6 bil "loss") , and now they can bring back the tax haven money and deduct the repatriation tax using that "loss" without needing to wait for repatriation tax break.

    https://news.microsoft.com/2015/07/08/satya-nadella-email-to-employees-on-sharpening-business-focus/

    Or perhaps I just don't understand how accounting works?

  • Anyone used WinPh10???

    http://www.phonearena.com/news/At-the-snap-of-a-finger-which-flagship-takes-photos-the-fastest_id57165

    Iphone 6 still took 1.9 seconds to shoot. *way too long* If you have the device in hand it needs to shoot in <300 ms from standby - pressing camera button fully down - shot at infinite focus, you can digital zoom/crop in later.

     

    Anyone know why these take so long time to shoot from standby? Is there something involved that makes it impossible to go faster? (lets say there's preset focus and 10 or 20 MP, I don't really need over 20 MP or 4-5 MP when need to just get quick shot). Lots of studying of 1020 shots shows that unless you have it mounted, there's no real use for having it save in more than 20 MP.

  • Anyone used WinPh10???

    Looking at some wp10 preview, it seems MS has taken exactly opposite approach? or maybe it's the user who has configured it like that. There's EVEN MORE TILES.

    People I talk want their windows desktop to be empty with new computer. So same goes for phone too. Have all the stuff in "all programs" like I explained above and then user adds stuff to desktop. This is how things were in Android 2.x and that was big success. I can't stand the 4.x Samsung Androids as they don't start with a "clean slate" with only the basic stuff if any. It's a big uncategorized mess of things. eg. I should not need a "camera" icon.. there should be dedicated camera button on every model - but if I don't use camera then I should be able to change that button to launch the phone or whatever app I want (skype?).