ulber

Just to clarify, not having Drag and Drop is not an API limitation (see [1]). Rather, they haven't implemented it yet in every place you'd expect to see it.

[1]: https://msdn.microsoft.com/en-us/library/windows/apps/mt2276...

The "energy current" when pumping gasoline into a tank is larger than what those achieved by Tesla's Superchargers (which take ~40 minutes to 80%). Thus gas stations can have much larger throughputs than comparably sized Supercharger stations.

Inking, sharing and reading mode are user facing features. Standards in web browsers have to do with the APIs and rendering and such conforming to standards.

My experience with concolic testing has been that single path satisfiability queries tend to be quite cheap and it's actually a bit challenging to write the tooling around the solver in such a way that the solver would actually become the bottleneck. This is not to say that combinations of concolic testing with other testing methods is not an interesting research topic :)

Not all theory fragments supported by Z3 are decidable: Z3 includes an incomplete decision procedure for non-linear real arithmetic [1].

[1] http://stackoverflow.com/a/13898524

The cost of the abstraction is language dependent though and the programmer might desire the abstraction to be worth it. For example, this particular abstraction is much cheaper in C++ which is a (admittedly small) point in C++'s favor.

>In this particular case, the fuzzer is going beyond just throwing random input, as it considers which changes to the input trigger new code paths in the target binary, and therefore should have a higher success rate in triggering bugs compared to just trying random stuff.

To expand on this, techniques like this are called whitebox fuzzing (or maybe graybox in afl's case). In their extreme whitebox fuzzers even incorporate constraint solvers to directly solve inputs that take the program to previously unexplored paths. One very impressive project is the SAGE whitebox fuzzer [1,2,3] that's in production use at Microsoft (an internal project sadly). I work in the related field of automated test generation, but all my tools are very much research-grade. However, in SAGE they've done all the work of figuring out how 24/7 whitebox fuzzing can be integrated into the development process. I am somewhat envious of the researchers getting to work in an environment where that is possible. If you're interested I very much recommend reading the papers on SAGE.

[1] Poster about SAGE: http://research.microsoft.com/en-us/um/people/pg/public_psfi...

[2] An approachable article on SAGE: http://research.microsoft.com/en-us/um/people/pg/public_psfi...

[3] The paper with all the details: http://research.microsoft.com/en-us/projects/atg/ndss2008.pd...

>Note: "One Drive" and "One Drive for Business" are totally different. The stuff connected to "Office 365" is the business stuff and it's really some friendlier front-ends on some kind of Cloud SharePoint thing...

From the link: "We’ve started rolling this out today to Office 365 Home, Personal, and University customers." I'm using Office 365 University and it definitely is the normal "One Drive" (just offers more space for it). The branding here seems a bit confused.

In Finnish it is also informally known as "miukumauku", which refers to the cat-like appearance of the symbol (long tail). This name isn't very common anymore.

If anyone wants this behavior in Firefox then here is an extension for that: https://addons.mozilla.org/en-US/firefox/addon/extra-padding...

>Google can't fulfill those obligations if those videos are showing up on WinMo without ads.

The mobile YouTube site that Google serves to Windows Phone devices does not display any ads. Therefore an ad-free app for WP does nothing to change the situation that WP users don't see ads on YouTube.

Now, it is possible that some of Google's content is licensed in such a way that only their mobile site is exempt from displaying ads while any native apps are not. However, a C&D hardly seems like the proper course of action here, given that Microsoft says they are willing to display Google's ads.

Bad name: Z3 is an SMT solver from Microsoft and a very good one at that. I'm assuming this LLVM OCaml thing is newer.

You can share significant amounts of code and design, but WP8 will necessarily require departures from the W8 app in UI design. For example WP8 uses panorama and pivot controls, which are not available in identical form in W8 (although analogs do exist).

On the "violating time and space" issue, I don't think the problem was on there being both blocking and non-blocking channel reads. Instead the problem for him was that in his mind the channel read "happens first" and how the result from that read is used (i.e. what it is assigned to) shouldn't have any effect on the read anymore. I must say that I agree and would prefer to have a more clearly separate syntax for blocking and non-blocking reads.