Subject: General Tech | May 2, 2016 - 03:36 PM | Jeremy Hellstrom
Tagged: windows 10, microsoft, market share, linux
We've all seen the comments about how Windows 10 has finally convinced people to switch operating systems but today we have numbers which show that some may have been true to their word. According to Netmarketshare the marketshare of Windows on desktop machines has dropped below 90% for the first time. Mac OSX holds onto 3.96% of the market but the Other category is up to 8.59%, which is the category that represents the various flavours of Linux; it holds 1.56%, as well as other non-Microsoft OSes. It may not be the year of Linux but it certainly is not Microsoft's year. You can read the calm, rational discussion over at Slashdot on this topic, it is guaranteed to provide amusement.
"Windows 7 is still the king, but it no longer holds the majority. Nine months after Windows 10's release, Windows 7 has finally fallen below 50 percent market share and Windows XP has dropped into single digits. While this is good news for Microsoft, April was actually a poor month for Windows overall, which for the first time owned less than 90 percent of the market, according to the latest figures from Net Applications."
Here is some more Tech News from around the web:
- If the Internet of Things will be SOOO BIG why did Broadcom just quit the market? @ The Register
- Intel loses its ARM wrestling match, kicks out Atom mobe chips @ The Register
- Iron Man-Inspired ROG GT51 Gaming Desktop Revealed @ Tech ARP
- Linksys LGS116P 16-Port Business Desktop Gigabit PoE+ Switch Review @ NikKTech
- Has Mankind Gone Too Far With Drone Fishing? @ Hack a Day
- Must listen: We've found the real Bastard Operator From Hell @ The Register
Subject: General Tech | April 26, 2016 - 04:26 PM | Scott Michaud
Tagged: windows 10, microsoft
After the release of Windows 10 version 1511, Microsoft took a few months to refactor and otherwise update the deep-down chunks of their OS. After that was all settled, they started merging features from their many teams. For the last two builds, the amount of changes ramped way up, not all of which were announced at Build conference.
These features have been merged without much bug-crushing, though. Microsoft knows this, and then talk about a “Bug Bash” event happening sometime this week. To get a feel for the state of this build's quality, though, you can check out WinBeta attempting to show off the new features. Note that some of the issues they were experiencing were actually in the known issues list, namely the crash attempting to pin Settings options, but the list is quite long.
A couple of new changes are interesting and surprising. First, long-time, multi-monitor users will like that the clock is now on all taskbars, not just the primary monitor. They acknowledge that this was driven by the gaming community, although they don't explicitly state that it's because our applications run in fullscreen mode so frequently (covering the main monitor clock). I don't exactly know why this slipped past the user experience people for so long, at least since the multi-monitor enhancements in Windows 8, but it did. It should be publicly available in July.
They will also allow desktop icons to have mini symbols (badges) attached to them. This could tell you how many unseen emails you have, whether your alarm is active, and probably many other features when it's in a publicly-accessible API. It's concerning that it's UWP-only, though. It shows that Microsoft wants to deprecate Win32 for new features, without migrating them into UWP containers, which further suggests that Microsoft intends to deprecate Win32 altogether. This is very concerning for several reasons, but I'm not going to reiterate them in this post.
The other cool feature, though, is a new interface to select between multiple sound cards. In my scenario, I have two main sound devices. When I listen to my headphones, I plug them into a USB sound card (technically a Blue Yeti). When I want to use speakers, I flip over to motherboard audio and turn on my sound system. This means that I need to go deep into the Sound preferences in the Control Panel, and it also means that some applications don't cleanly switch over (even locking up entirely). With this a front-and-center input menu of Windows 10, it should pressure developers to test whether their software can accept a sound device change on the fly, and fix accordingly.
So yeah -- those are the three features that spoke most to me. Again, the lack of innovation in native Win32 APIs is concerning. It reminds me of when browser vendors declared that certain new APIs would be artificially held back from non-secure HTTP contexts. In some cases, it makes sense -- an unsecure Web app accessing your webcam is a sign that they don't care about your privacy -- but it also means that software developers need to give up some level of their anonymity to acquire a certificate to access those features (unless offline sites are classified as secure in the user's browser, which Google Chrome does and others might too). Tangent aside, it feels like Microsoft is trying to apply the same level of pressure to push people away from bare Win32. That makes sense, they want to promote new platforms, but it also usually comes before the old one gets the guillotine.
Subject: General Tech | April 26, 2016 - 12:58 PM | Jeremy Hellstrom
Tagged: microsoft, windows 10
If you are in the Windows Insider program you will have a chance to check out the new build 14328 of Windows 10, which reveals many of the new features which will arrive in the so called Anniversary edition. Once again they have chosen to change the Start menu, something which has always been well received by users, though perhaps this time it will not be so bad as the idea of a customizable Rail which always displays the power button and icons the user selects may be useful.
They have also added Ink Workspace, aka Inky, which will make using a stylus in Windows 10 much easier, for those with touchscreens or tablets and a desire to draw or write by hand. There are also quite a few things which sound less welcome, such as default save folders which vary from app to app and some odd behaviour from Cortana. Read more about the new features over at The Inquirer.
"Microsoft has released Windows 10 build 14328 to "Windows Insider" previewers. The build is available for both PC and mobile, and is described by VP Gabe Aul as a "MAJOR build, packed with lots of new features and improvements"."
Here is some more Tech News from around the web:
- Carbon nanotubes light up on photonic chips @ Nanotechweb
- Dogspectus: Android ransomware is silently installing bad apps @ The Inquirer
- BlackBerry is pivoting from phones to enterprise software @ The Register
- Gmail For Android Gets Microsoft Exchange Support @ Slashdot
- Do AMD Drivers Really Deserve Such a Hostile Reception @ eTeknix
Intro and Xbox One
Introduction to Remote Streaming
The ability to play console games on the PC is certainly nothing new. A wide range of emulators have long offered PC owners access to thousands of classic games. But the recent advent of personal game streaming gives users the ability to legally enjoy current generation console games on their PCs.
Both Microsoft and Sony now offer streaming from their respective current generation consoles to the PC, but via quite different approaches. For PC owners contemplating console streaming, we set out to discover how each platform works and compares, what level of quality discerning PC gamers can expect, and what limitations and caveats console streaming brings. Read on for our comparison of Xbox One Streaming in Windows 10 and PS4 Remote Play for the PC and Mac.
Xbox One Streaming in Windows 10
Xbox One Streaming was introduced alongside the launch of Windows 10 last summer, and the feature is limited to Microsoft's latest (and last?) operating system via its built-in Xbox app. To get started, you first need to enable the Game Streaming option in your Xbox One console's settings (Settings > Preferences > Game DVR & Streaming > Allow Game Streaming to Other Devices).
Once that's done, head to your Windows 10 PC, launch the Xbox app, and sign in with the same Microsoft account you use on your Xbox One. By default, the app will offer to sign you in with the same Microsoft account you're currently using for Windows 10. If your Xbox gamertag profile is associated with a different Microsoft account, just click Microsoft account instead of your current Windows 10 account name to sign in with the correct credentials.
Note, however, that as part of Microsoft's relentless efforts to get everyone in the Virgo Supercluster to join the online Microsoft family, the Xbox app will ask those using a local Windows 10 account if they want to "sign in to this device" using the account associated with their Xbox gamertag, thereby creating a new "online" account on your Windows 10 PC tied to your Xbox account.
If that's what you want, just type your current local account's password and click Next. If, like most users, you intentionally created your local Windows 10 account and have no plans to change it, click "Sign in to just this app instead," which will allow you to continue using your local account while still having access to the Xbox app via your gamertag-associated online Microsoft account.
Once you're logged in to the Xbox app, find and click on the "Connect" button in the sidebar on the left side of the window, which will let you add your Xbox One console as a device in your Windows 10 Xbox app.
Subject: Graphics Cards | April 14, 2016 - 06:17 PM | Scott Michaud
Tagged: microsoft, windows 10, uwp, DirectX 12, dx12
At the PC Gaming Conference from last year's E3 Expo, Microsoft announced that they were looking to bring more first-party titles to Windows. They used to be one of the better PC gaming publishers, back in the Mechwarrior 4 and earlier Flight Simulator days, but they got distracted as Xbox 360 rose and Windows Vista fell.
Again, part of that is because they attempted to push users to Windows Vista and Games for Windows Live, holding back troubled titles like Halo 2: Vista and technologies like DirectX 10 from Windows XP, which drove users to Valve's then-small Steam platform. Epic Games was also a canary in the coalmine at that time, warning users that Microsoft was considering certification for Games for Windows Live, which threatened mod support “because Microsoft's afraid of what you might put into it”.
It's sometimes easy to conform history to fit a specific viewpoint, but it does sound... familiar.
Anyway, we're glad that Microsoft is bringing first-party content to the PC, and they are perfectly within their rights to structure it however they please. We are also within our rights to point out its flaws and ask for them to be corrected. Turns out that Quantum Break, like Gears of War before it, has some severe performance issues. Let's be clear, these will likely be fixed, and I'm glad that Microsoft didn't artificially delay the PC version to give the console an exclusive window. Also, had they delayed the PC version until it was fixed, we wouldn't have known whether it needed the time.
Still, the game apparently has issues with a 50 FPS top-end cap, on top of pacing-based stutters. One concern that I have is, because DigitalFoundry is a European publication, perhaps the 50Hz issue might be caused by their port being based on a PAL version of the game??? Despite suggesting it, I would be shocked if that were the case, but I'm just trying to figure out why anyone would create a ceiling at that specific interval. They are also seeing NVIDIA's graphics drivers frequently crash, which probably means that some areas of their DirectX 12 support are not quite what the game expects. Again, that is solvable by drivers.
It's been a shaky start for both DirectX 12 and the Windows 10 UWP platform. We'll need to keep waiting and see what happens going forward. I hope this doesn't discourage Microsoft too much, but also that they robustly fix the problems we're discussing.
Subject: General Tech | April 8, 2016 - 01:21 PM | Jeremy Hellstrom
Tagged: flash, microsoft, edge, windows 10
The new insider build of Windows 10 includes a new feature on Edge, similar to the one already found on Chrome, it will pause Flash assets on webpages which are not the main content. This should mean far less annoying advertisements blaring from your speakers if you happen to visit an uncouth website which features that type of advertisement. It is also a step in the right direction for security, considering Adobe has posted yet another critical update for a gaping security hole in Flash. You can follow the links from Slashdot to grab the update if you wish, or delve into the morass of comments about this update.
"Microsoft Edge will "intelligently auto-pause" Flash content that is "not central to the webpage." If you want to try this out now, you can take the feature for a spin with Windows 10 build 14316, which was recently made available to Windows Insiders"
Here is some more Tech News from around the web:
- Adobe issues another Flash patch following Windows 10 ransomware threat @ The Inquirer
- Microsoft rethinks the Windows application platform one more time @ The Register
- What to Know before Using Windows 10’s New Linux System @ Linux.com
- Asustek reduces demand for Intel-developed smartphone platforms @ DigiTimes
- OPPO F1 Plus Smartphone First Look @ TechARP
- Mumblehard spam-spewing botnet floored @ The Register
- Managing infrastructure, a newbie's guide: Simple stuff you need to know @ The Register
Subject: General Tech | April 6, 2016 - 12:16 PM | Jeremy Hellstrom
Tagged: microsoft, surface phone
For those masochists who like to run Windows phones there is good news on the horizon, three Surface phones are due to arrive some time in 2017. The market segmentation is different from the competition, instead of offering curved screens or a different size they will sell consumer, business and enthusiast models. That is an interesting way to separate your products and with the amount that usual phone usage has changed an Enthusiast model actually makes sense for those who spend more time gaming and watching HD content on their phones than on their laptops.
The Inquirer has heard rumours that the phones will have a 5.5" QHD AMOLED screen, an Intel Atom CPU, 4GB of RAM and 64GB or 128GB of local storage, though one hopes the enthusiast model gets a little boost in specs.
"MICROSOFT'S RUMOURED Surface Phone reportedly won't see the light of day until next year, but will arrive in three versions when it does."
Here is some more Tech News from around the web:
- Seagate joins hands with Intel, adds tasty IEEL to its pie and mash @ The Register
- NVIDIA GTC 2016 Recap – Pascal GPUs, Iray VR, AI and Autonomous Racing @ Techgage
- Samsung kind of cracks the 10nm barrier with new 8GB DDR4 slabs @ The Register
- Quanta LTE Router May Be Most Unsecure Router Ever Made @ Slashdot
- Huawei P9 and P9 Plus arrive with dual Leica-certified cameras @ The Inquirer
- Windows 7's grip on the enterprise desktop is loosening @ The Register
Subject: General Tech | April 4, 2016 - 02:33 PM | Scott Michaud
Tagged: windows 10, microsoft
Microsoft has been slowly shifting Windows and the rest of their software toward a dark theme over the last couple of years. This is the case on Visual Studio, Edge, and... some of the operating system's user interface. You can see it in the taskbar, in a few context menus on the desktop, and so forth. If you then open the system settings, you are greeted with light grey and white.
According to Brad Sams at Thurrott.com, Windows 10 will receive an actual dark theme option in the upcoming Anniversary Update. It could have been unlocked in the registry since before Windows 10 initially launched last year, but it was very incomplete. I also don't exactly like enabling experimental things in the registry, because you never know if Microsoft will test all possible combinations of work-in-progress flags when said feature actually goes public.
Speaking of which, the Windows 10 Anniversary Update is expected at some point in July. You know, the one-year anniversary of Windows 10 reaching
RTM totally not RTM, because Windows 10 doesn't go RTM.
Subject: Mobile, Shows and Expos | March 31, 2016 - 01:52 PM | Scott Michaud
Tagged: BUILD, build 2016, microsoft, windows 10, windows phone
If you watched the opening keynote of Microsoft's Build conference, then you probably didn't see much Windows Phone (unless you were looking at your own). The Verge talked to Terry Myerson about this, and Microsoft confirmed that they are leading with non-Windows, 4-inch devices, and they want to “generate developer interest” on those platforms for this year.
PC World interpreted this conversation to say that Windows Phone is put on hold.
That might be a little hasty, though. Microsoft is still building Windows 10 for Mobile. In fact, since Microsoft updated “Windows OneCore” and jumped build to 14xxx-level build numbers with Windows 10 build 14251, Windows 10 Mobile and Windows 10 PC are kept in lockstep. As far as I know, that is still the plan, and Windows Insiders should continue to receive these on compatible devices.
That said, Microsoft has basically admitted that Windows Phone would just be a distraction for developers this year. At the very least, they don't believe that the platform will be ready for them until next year's Build conference, which means that consumers will probably be even further down than that because there would be no applications for them. Yes, Windows Phone could be slowly shimmying out of the spotlight, but it could also be delayed until they make a good impression, and have the PC, Xbox, Hololens, and other ecosystems secure to lift it up.
Subject: General Tech, Shows and Expos | March 30, 2016 - 01:14 PM | Scott Michaud
Tagged: windows 10, uwp, microsoft, build 2016, BUILD
When a platform vendor puts up restrictions, it can be scary, and with good cause. Microsoft's Universal Windows Platform (UWP) is the successor of WinRT, which, in the Windows 8 era, forced web browsers to be reskins of Internet Explorer, forced developers to get both their software and themselves certified before publishing, and so forth. They still allowed the traditional, more open, Win32 API, but locked them into “the Desktop App”.
Naturally, UWP carries similar concerns, which some developers (like Tim Sweeney of Epic Games) voiced publicly. It's more permissive, but in a brittle way. We don't want Microsoft, or someone like a government who has authority over them, to flip a switch and prevent individuals from developing software, ban content that some stakeholder finds offensive (like art with LGBT characters in Russia, the Middle East, or even North America), or ban entire categories of software like encryption suites or third-party web browsers.
This is where we get to today's announcement.
Microsoft's Phil Spencer, essentially responding to Tim Sweeney's concerns, and the PC gaming community at large, announced changes to UWP to make it more open. I haven't had too much time to think about it, and some necessary details don't translate well to a keynote segment, but we'll relay what we know. First, they plan to open up VSync off, FreeSync, and G-Sync in May. I find this kind-of odd, since Windows 10 will not receive its significant update (“Anniversary Update”) until July, I'm not sure how they would deliver this. It seems a little big for a simple Windows Update patch. I mean, they have yet to even push new versions of their Edge web browser outside of Windows 10 builds.
The second change is more interesting. Microsoft announced, albeit without dedicating a solid release date or window, to allow modding and overlays in UWP applications. This means that software will be able to, somehow, enter into UWP's process, and users will be encouraged to, somehow, access the file system of UWP applications. Currently, you need to jump through severe hoops to access the contents of Windows Store applications.
They still did not address the issue of side-loading and developing software without a certificate. Granted, you can do both of those things in Windows 10, but in a way that seems like it could be easily removed in a future build, if UWP has enough momentum and whoever runs Microsoft at the time decides to. Remember, this would not be an insidious choice by malicious people. UWP is alluring to Microsoft because it could change the “Windows gets viruses” stigma that is associated with PCs. The problem is that it can be abused, or even unintentionally harm creators and potential users.
On the other hand, they are correcting some major issues. I'm just voicing concerns.