4thjuly

35 ms·

1. 1.▲
   by 4thjuly 12y ago

   Just to nitpick the first point, ARC apps run inside the NaCl sandbox so there's no potential for harming the strong security model in ChromeOS
2. 2.▲
   by 4thjuly 12y ago

   Although it makes it much more comfortable to wear.
3. 3.▲
   by 4thjuly 12y ago

   As others have said this is really a source control problem but still there's a workaround. Just copy the production dll and use .Net Reflector (or similar) to decompile it back in to C#. Make your edits, recompile and upload.
4. 4.▲
   by 4thjuly 13y ago

   I wasn't involved so don't know first hand but suspect the gory details were discussed by everyone in the working group. http://lists.w3.org/Archives/Public/www-style/ . Or were you being sarcastic?
5. 5.▲
   by 4thjuly 13y ago

   That's why I put 'private' in quotes. Given a decent debugger, nothing is strictly private but then it's a meaningless distinction. Perhaps there's a better term for APIs you can technically call but will get your a
6. 6.▲
   by 4thjuly 13y ago

   For recent examples I was thinking specifically about the Windows.Networking.NetworkOperators APIs and such. These APIs are 'private' to network operators. If you try to use them from a regular app then you'll be kicked out o
7. 7.▲
   by 4thjuly 13y ago

   Exactly, Microsoft already does something similar by reserving some of their APIs for their own use. There are others that are available to some (eg the carriers) but nobody else. It's nothing new, they have had so-called 'private