Entries:
Comments:
Discussions:

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

Bass Bass Knows the way the wind is flowing.
  • Free car with Microsoft band 2!

    This is actually a good area for open standards. Cars are suppose to last decade or longer, I should be able to be confident that my smart car can interact with my smartwatch or smart brain implant 10 years from now.

    The problem is standards is not in the car manufacturers vocabulary. It's amazing they all standardized on a single cigarette lighter design but it is going to be hard to ask for more then that.

  • What? No mention of Ian Murdock?

    Founder of Debian. One of the most popular Linux-based operating systems, and the one that Ubuntu is based off of. Committed suicide under strange circumstances.

  • Universal Windows App Programming -- not all it's cracked up to be.

    , Dr Herbie wrote

    I'm resurrecting this thread as I now find I have some time to write a wrapper to hide the (IMHO) appalling API design that is ApiInformation.IsApiContractPresent. If the wrapper is good enough, I'll open source it.

     

    So, opinions on how to design the library, taking the 'VibrationDevice' as the starting point. Which seems like the better API:

    1. A static class where you just call

    1
    VibrationDevice.Vibrate(TimeSpan.FromSeconds(2));

    And if there is a vibration device it will be used, but if there isn't nothing will happen (optional return value indicating whether it happened or not).

    2. The same format as the MS VibrationDevice class where you call

    1
    2
    var device = VibrationDevice.GetDefault();
    device.Vibrate(TimeSpan.FromSeconds(2));

    But without the nasty exception throwing, using a NullObject replacement to perform the empty implementation.

     

    I'm currently leaning to option 1 as it seems cleaner to call (being just a hardware interface) rather than having to create an instance using a static factory method.

    Other opinions are sought.

    Personally I think something like this looks best:

    Device.Vibrate(2);

    But maybe years being away from overabstract/verbose Java (and I guess C# too) corrupted my opinion on APIs.

  • SpaceX successfully lands stage 1 rocket

    , spivonious wrote

    *snip*

    Exactly! Rockets are old tech. Let's get something into space without burning tons of rocket fuel.

     

    Warp drives and nuclear engines (if you <3 fallout) are all cool and all, but realistically chemical rockets are all we have.

    Reusable rockets can drop the cost of sending things to space dramatically. I mean launch costs of millions instead of tens or hundreds of millions. The cost of fuel is extremely overrated, rockets are the expensive part of sending things to space. This won't get us to interstellar travel but it will open low Earth orbit to a lot more businesses.

  • SpaceX successfully lands stage 1 rocket

    Reusable spacecraft.

  • Dear Microsoft

    Mainstream users already have access to great services like Google Drive/Apple iCloud that manage all their stuff already, without requiring them to buy hardware or understand what a server is and how to maintain it. They aren't gonna maintain a server in their house. It's not gonna happen.

  • Windows Phone, may ye rest in peace... the clone wars are over and the droids are winning.

    , elmer wrote

    I don't understand what the issue is.

    All that I'm saying is that while running W32 apps would be a nice feature to have, they don't need to compromise the phone to achieve it, just create an accessory... sort of like an Intel compute-stick or small NUC, but with the option to create a system/boot volume on the phone, if you prefer to have your W32 apps installed in the one place.

    I don't see how what you are describing isn't a desktop PC. You are just calling a desktop PC a dock. So you use your phone as a expensive flash drive. The whole using your phone to store files is crazy, what if your phone gets stolen or lost? Phones are all hooked up to the 'cloud' anyway. Oh wait, so are PCs. Basically what are we talking about again? You have Internet access right? 

    Maybe it makes a little sense if the smartphone is running an Intel CPU and the dock is a glorified USB cable. But problem is for a CPU to fit into a phone and still implement all the crazy x86 microcode/control overhead it's gonna be weak as fock or have crap battery life. I wouldn't want to run Visual Studio or Photoshop on something like that. Seriously look up all the dizzying amount of crap Intel crams into a CPU just to get x86 to work. It is just a poorly designed ISA, it originates from a time when computer engineers had no * clue what they were doing. Shame that W32 was built on a garbage foundation. It had a great run, maybe it's time to let it die already.

  • Windows Phone, may ye rest in peace... the clone wars are over and the droids are winning.

    So if I have a desk why wouldn't I have a desktop? Desktops are pretty cheap. You are not really buying much efficiency using the smartphone's power to power a dock. You still have to pay for the keyboard and mouse and monitor. And the dock, which using proprietary tech is often expensive. Your experience will be like a super low end desktop at best. You aren't going to compete with your desktop at work or high end laptop in a smartphone form factor. Might as well just buy a Raspberry Pi and call that a desktop. New Raspberry Pi is essentially a low/mid range smartphone guts.

    Worst thing though is I can't take my dock to Starbucks. A laptop will still be a superior option because you can use it anywhere and get a pretty good 'desktop' experience in a portable form factor. It can also obviously be docked. Apple has been making really portable laptops, more portable then small Chromebooks even. Have you seen the new Macbook? Macbook is not a hassle to carry around even on a bad commute. And you can use it anywhere. That's key.

  • OpenAI founded

    , Ian2 wrote

    *snip*

     

    It's the next frontier imo (but still a little scary?)

    The AI field has a tendency to discover something revolutionary which causes a rapid acceleration in advancement until all obvious possibilities are exhausted and a brick wall is hit (or if you rather, the field ran into a local minima). This leads to a kind of AI winter, were little progress is made overall. And that can last decade(s).

    Given the current research pace I think we will see AGI/tech singularity in the next few years or we'll head into another AI winter, which may last until 2030 or longer. So I think there is a small chance we won't see 2020 as humans, but most likely we are heading to an AI winter and you have nothing to worry about.

    Regardless it's notorious difficult to predict. AI is not like a typical engineering project where we even know or have a good theory on what to do to develop it. I suspect it's more like a discovery someone will stumble on, as opposed to a directed engineering project. Because if intelligence is like what humans have, the information content in the genetic code that provides us this capability is rather tiny. So it can not be something very complicated to reproduce - in the algorithmic sense at least.

  • Windows Phone, may ye rest in peace... the clone wars are over and the droids are winning.

    , TexasToast wrote

    @figuerres:I think they will walk back that decision on dropping android emulation. 

    If you are going to do Android emulation you might as well just do Android. Microsoft experimented with selling Android phones, and tbh they looked pretty good:

    http://www.microsoft.com/en/mobile/phones/nokia-x/?order_by=Latest 

    These phones have Microsoft's Android apps (which are superior anyway, right?) and the tile UI. So it doesn't have WinNT, and doesn't support a dev framework nobody really cares about. That's the big difference. But lets be honest, Linux is a much more advanced and battle tested mobile kernel anyway. The point is, WinPho is a bit redundant. It is better to be a notable Android or iOS developer than a vendor of an OS nobody uses. They can even acquire Xamarian and port .NET stuff to other OSes, you know that's what everyone really wants anyway.