I think you can upgrade to get the key converted to Windows 10, then downgrade if you want to stay on the older version.
I haven't done this myself, so I don't know if it still works.
Loading user information from Channel 9
Something went wrong getting user information from Channel 9
Loading user information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Of course, you could also just hack the assembly of your process in-memory as it's running. No programming language required.
This guy exploited a copy of Super Mario World on a standard, unaltered SNES and wrote and then executed an implementation of Flappy Birds. All live while playing the game, by hand using standard controllers.
UWP is definitely the newest of the group, and its history suffers most from the past prioritization of building a good universal platform over being a feature complete replacement of Win32. It's only this year that we have started to hear that Microsoft really aims to push as many Win32 API equivalents into UWP as is practical (they'll still shy away from the misused and abused APIs).
The acquisition of Xamarin is hopefully just the first step. There is still a disconnect between what Xamarin has created and what was created in-house by Microsoft. That needs to be reconciled in my opinion, things like implementing XAML2009 in UWP and WPF.
@androidi: Programming brainwaves? I'm not even going to speculate.
The music fading thing I can speak to. Let's create a scenario: you have 2 processes, the first process holds an audio buffer in memory which pushes that audio data to the sound card, and the second process reads your audio file from disk, processes the audio in a tight loop, and pushes the data into the memory buffer that is used by the first process. (Assume the buffer is sufficient to account for hitting the debug breakpoint, pasting the new code, and continuing.) The change we want to make is to simply raise all volume by 10 db.
Continuity depends on how you program your change. Simply changing the code to multiply the value by 10 would be abrupt. To make it smooth you would need to make your change account for raising the volume slowly, say by incrementing the multiplier from 1 to 10 over the timeframe you want.
You would break the second process, apply your code change, and hit Continue. It would start feeding the buffer with the remaining audio data that is now processed to be louder.
So the work is on you to smooth out any changes that are applied, because the exact details are dependent on what you are doing. This is how it has to be, at least at a "general programming language" level. Different scenarios and different tasks have specific needs. Someone could write a library to help generalize audio changes in this fashion, but its needs would be very different from working with video, robotics, or brainwaves. There's no way a general purpose language and environment would handle those cases naturally.
@RealBboy360: An Xbox 1.5 would be great if and only if it were 100% backwards and forwards compatible with games and apps. New games should run on the old one, but the new one has better graphics/etc.
I think it would be acceptable if the OR only works on the 1.5. It would still cost less than buying a new PC for gaming.
Is there a technical reason why the OR cannot be driven from Xbox One, even at some reduction in quality (say, comparable to PS4 VR)? I mean aside from the connector, unless there is no external bus on the Xbox One that has the bandwidth for it.
@magicalclick: That may be a possibility.
Another is that the Photoshop tile doesn't appear on the phone Start screen, but only on the docked desktop Start menu. But that is speculative, and Microsoft may discourage having separate Start menu environments.
The third possibility is that Photoshop's UI is rebuilt for UWP, but some of the backend is provided by the desktop app. That way you can get reduced functionality in phone mode, and when docked the whole app lights up and can take advantage of all the capability of the desktop.
Yep, it's all about running the language in a REPL.
C# has this capability now, as of Visual Studio 2015 Update 1. It's called C# Interactive.
@elmer: That's an interesting idea, I suppose the ARM chip would be the master and perhaps a combination of Continuum and Hyper-V could allow the x86 CPU to operate as a native-speed VM? And come to think of it Microsoft may already have some relevant experience. The Surface Book has a hot-pluggable GPU in its keyboard case.
I suspect that getting multiple architectures to play nicely on the same bus is a bit more of a challenge, but AMD appears to have already started paving that path by building a multi-architecture CPU: http://www.extremetech.com/computing/182790-amds-next-big-gamble-arm-and-x86-cores-working-side-by-side-on-the-same-chip
But I'm thinking all storage/apps/settings would be on the phone itself, and the dock would just provide the x86 CPU and the RAM for use in that CPU.