|Google is actively breaking my Android workflow|
|By Thom Holwerda on 2016-06-28 21:53:48|
Way back when Android Lollipop was released, Google introduced a feature called "merge tabs and apps" and enabled it by default for all Lollipop users. Basically, what it did was turn individual Chrome tabs into application windows in Android's application switcher. If you have an understanding of how Android works, this makes perfect sense; this turns tabs into full citizens of the Android application and intents workflow.
Starting with - I think? - Android Marshmallow, Google turned the feature off, but kept it as an option in Google Chrome, so that those of us that liked it could turn it back on. Obviously, this was the first thing I always turned on when setting up any new Android device; it just makes sense from an Android perspective. It smooths out the workflow, and makes sure that tab management becomes a thing of the past; they are discarded just like other Android applications.
Sadly, starting with Chrome 51, released a few weeks ago, the Android or Chrome or whatever team decided to remove the option altogether. The release notes stated:
When Android Lollipop was released last year, we moved Chrome tabs to live alongside apps in Android’s Overview app switcher. Our goal was to make it easier for you to switch between your open apps and websites. However, we heard from many of you that you could not find the tabs you created. This was especially difficult on phones that do not have a dedicated Overview button. While considering how to make Chrome work better for everyone, we brought the tab switcher back into Chrome so you can find your Chrome tabs in a single place. Look for a new way to manage your open tabs in coming releases.
This single change has thoroughly ruined the way I use my phone. I now have upwards of 60 - and growing - "open" tabs, because the Chrome team wants me to manually keep track of and close every individual tab that gets opened while using Twitter, Facebook, WhatsApp, and other applications. I now have to keep track of not only running applications in the switcher, but also open tabs in the tab switcher, the latter of which can only be opened with a button in Chrome all the way at the top of my ginormous Nexus 6P display. The tab switcher itself, meanwhile, is a finicky clusterfuck of imprecise swipes and physics nonsense, making it all incredibly frustrating to use.
Update: this paragraph was added later as clarification. In addition, if you tapped on a link in, say, Fenix (Twitter) and read the website in the tab and then pressed back, said tab was automatically closed. This automatic closing of tabs with the back button does not happen with the inferior new method, hence the asinine clutter build-up.
Trying to switch to a specific tab I may have opened earlier in the day is an exercise in frustration now, since instead of just opening the application switcher and finding it a few swipes up (I don't use many applications), I now have to first find Chrome or launch it from my homescreen, find the tab switcher button all the way at the top, count to ten as I try to use the asinine tab switcher, and then hope I can find it somewhere among the more than 60 - and growing - "open" tabs and UI input lag caused by having to render all these tabs in that weird 3D space.
As someone who keeps track of world news, things like UEFA Euro 2016, technology news, and so on, all throughout the day, I end up with countless interesting tabs that get opened on Twitter, other social media, instant messenger, and so on. The Chrome team has actively decided to break my workflow, and there's no way for me to get it back - probably just because instead of looking at the how or why, they just looked at their precious, precious user data, and called it a day.
Looking to the future, with (freeform) windowing coming to Android, the change makes even less sense. Having tabs as part of the regular application switcher surely makes sense from a multitasking and multiwindow perspective, automatically giving Android users the ability to have multiple tabs side-by-side, in a way that is consistent with using other applications side-by-side. How are they going to implement this now? Will Android users have to deal with multiple Chrome windows, each with their own tab switcher? Where do tabs of closed windows go? What madness is this?
I find solace in that I'm not alone. Countless friends have expressed their hatred for the removal of merge tabs and apps (I've seen some of my programmer friends with well north of 100 "open" tabs), and the Chrome for Android reviews in the Play Store are riddled with angry one-star reviews. Google's forums, too, are filled with angry users. I'm hoping the angry comments and one-star reviews will make the Chrome team reconsider and bring back the option to merge tabs and apps, the Only True Android Way™ to manage tabs.
I'm sure tons of people here will consider this whining, but imagine if you're a programmer, and someone randomly took away your ability to insert tabs, forcing you to use spaces instead (or vice versa). That twitch you feel? That's us right now, every time we use Android.
For the first time in my life, I actually rated an application on an application store. Guess how many "stars" (why is it always stars?) I gave to Chrome for Android.
|Microsoft restores function of 'X' button on window|
|By Thom Holwerda on 2016-06-28 21:53:18|
Microsoft officials said late on June 27 that the new update experience -- with clearer "upgrade now, schedule a time, or decline the free offer" - will start rolling out this week. Microsoft will also revert to making clicking on the red X at the corner of the Windows 10 update box dismiss the update, rather than initiate it, as it has done for the past several weeks.
If you had told me only a few months ago that Microsoft would be putting out a press statement extolling how it made sure that the close button on a window frame actually closed the window instead of initiating something crappy people don't want, I'd have called you crazy.
Why do we let software makers get away with producing crap? Why does software suck so much?
|Microsoft draws flak for pushing Windows 10 on PC users|
|By Thom Holwerda on 2016-06-27 22:56:26|
A few days after Microsoft released Windows 10 to the public last year, Teri Goldstein's computer started trying to download and install the new operating system.
The update, which she says she didn't authorize, failed. Instead, the computer she uses to run her Sausalito, Calif., travel-agency business slowed to a crawl. It would crash, she says, and be unusable for days at a time.
"I had never heard of Windows 10," Goldstein said. "Nobody ever asked me if I wanted to update."
When outreach to Microsoft's customer support didn’t fix the issue, Goldstein took the software giant to court, seeking compensation for lost wages and the cost of a new computer.
She won. Last month, Microsoft dropped an appeal and Goldstein collected a $10,000 judgment from the company.
We accept so much crap from software makers, so it feels good if someone manages to get back at them for the terrible quality of software in general.
|Announcing .NET Core 1.0|
|By Thom Holwerda on 2016-06-27 18:49:14|
We are excited to announce the release of .NET Core 1.0, ASP.NET Core 1.0 and Entity Framework 1.0, available on Windows, OS X and Linux! .NET Core is a cross-platform, open source, and modular .NET platform for creating modern web apps, microservices, libraries and console applications.
This release includes the .NET Core runtime, libraries and tools and the ASP.NET Core libraries. We are also releasing Visual Studio and Visual Studio Code extensions that enable you to create .NET Core projects. You can get started at https://dot.net/core. Read the release notes for detailed release information.
|Dolphin 5.0 released|
|By Thom Holwerda on 2016-06-24 22:10:03|
The long awaited Dolphin 5.0 release is finally here! After nearly a year of bug-hunting and handling the release process, everything has come together for our biggest release yet! The three previous releases followed a very distinct pattern: sacrifice performance, hacks, and features in exchange for higher accuracy. As such, Dolphin 3.0, 3.5, and 4.0 progressively grew slower. But thanks to the cleanups put forward throughout those releases, Dolphin 5.0 is the fastest Dolphin has ever been! By removing all of those hacks and outdated features while cleaning up the codebase, Dolphin has reached a new level of efficiency, powered by a revitalized dynamic recompiler. On the GPU side, OpenGL and D3D11 have seen tons of optimizations and accuracy improvements, and have been joined by a brand new D3D12 backend for huge performance gains. If there's a CPU or GPU extension that can make Dolphin faster, we take advantage of it.
Dolphin is an incredibly impressive project - not just from a technological standpoint, but also from an organisation one. They post regular, detailed development updates, have in-depth release notes that are still entirely readable for laypersons such as myself, and you always learn a ton of new stuff following the project's progress.
A great example of how to run a project like this. Don't forget to check out the release video with tons of side-by-side examples of the long list of improvements.
|PowerNex: kernel written in D|
|By Thom Holwerda on 2016-06-24 22:02:38|
PowerNex is a kernel written in the D Programming Language. The goal is to have a whole OS written in D, where PowerNex powers the core.
Exactly what it is.
|macOS Sierra developer preview: different name, same ol' Mac|
|By Thom Holwerda on 2016-06-24 01:11:11|
It's tempting to read the "macOS" rebranding as some grand statement about the Mac, but, truth be told, "Sierra" is more indicative of what we're getting. The name comes from a mountain range that encompasses Yosemite and El Capitan rather than moving away from them. It's another year of building on Yosemite's foundation, another year of incremental change, and another year of over-saturated mountain wallpapers.
Like El Capitan before it, Sierra focuses on a few marquee features, a couple of under-the-hood changes, a smattering of smaller tweaks, and one or two signposts pointing toward future development. It's the next release of OS X, new name or not. And we've spent a week with the first developer beta to dig into some of the new features ahead of the public beta in July and the public release in the fall.
Insights into the developer preview.
|Huawei is working on its own mobile OS|
|By Thom Holwerda, submitted by Adurbe on 2016-06-24 01:04:51|
Huawei, the world's third-largest smartphone manufacturer, is reportedly developing its own mobile OS. Phones made by the Chinese manufacturer currently run on the company's Android skin, EMUI, but according to a report from The Information Huawei is building an alternative OS in case its relationship with Google sours.
The company reportedly has a team working on the mobile OS in Scandinavia, with the engineers including ex-Nokia employees. But although Huawei isn't the only Android phone maker exploring alternatives (Samsung has its own Linux-based Tizen OS, although that's mainly been deployed in IoT devices so far), sources speaking to The Information say the company's operating system "isn't far along."
That ship has sailed. It's probably in Fiji by now.
|'Gruber misses the point completely about Lightning headphones'|
|By Thom Holwerda on 2016-06-22 20:00:26|
John can argue all he wants that this is all somehow in the best interest of customers by virtue of it being great business for Apple, but it simply isn’t true. It also won’t be a hill that many customers will die on at the point of sale. People will not buy into Lightning headphones, they will put up with it. This transition will be painful and difficult because of just how thoroughly entrenched the current solution is, how little the new solution offers, and how many complications it adds for customers. Nilay is correct, it is user-hostile, and it is stupid.
But hey, it’s great for Apple.
I have very little to add here, other than dongle, and a plea: can somebody finally give me a valid reason for removing the 3.5mm jack? I've heard nonsense about waterproofing (can be done just fine with 3.5mm jack), battery life (negligible, unlikely because of the location of the assembly, entirely and utterly eclipsed by making the battery like 0.5mm thicker), cost (...seriously? That's the best you can do?), or thinness (oh come on, the iPhone 6S is 7.1mm thick - it will take a miracle for the iPhone 7 or even 8 or 9 to be thinner than 3.5mm).
As far as I can tell, there are only downsides.
|Taking the headphone jack off phones is user-hostile and stupid|
|By Thom Holwerda on 2016-06-21 21:20:08|
Another day, another rumor that Apple is going to ditch the headphone jack on the next iPhone in favor of sending out audio over Lightning. Or another phone beats Apple to the punch by ditching the headphone jack in favor of passing out audio over USB-C. What exciting times for phones! We're so out of ideas that actively making them shittier and more user-hostile is the only innovation left.
Tell us how you really feel, Nilay.
Needless to say - fully agreed. Removing the headphone jack is dumb.
|Read some older news|