WTF is happening with Windows 10? And nothing else
-
if i get discourse loaded before i go sans wifi it's perfectly happy. but if i forget to load it first (as i often do) it will sit there on a white page, loading forever
That's bizarre, I haven't seen it on either of my phones.
-
WinRT is being orphaned:
After 2.5 years? Jesus fuck, Apple has a longer support policy than that.
-
I would say your cell provider sucks and you should get a better one, but… well, you're in the US.
i buy through a MNVO for a reason ;-)
but yeah the options still suck.
-
He's actually just mad that his specific device is only getting one more major update.
-
@rad131304 said:
That's not what Microsoft said was happening. No Windows RT device will receive Windows 10 Mobile.
Why are you telling me that I said that? I never did! I know you aren't getting Windows 10, and that no Windows RT device is. That doesn't mean that Windows RT is being orphaned, it means those devices are. Windows RT is just getting a new name.
I can post this 10 more times, but you'll probably just say, "But Windows RT devices don't get 10 so it's orphaned." once more, ignoring everything I post once more.
?
-
Random scrolling is far more likely on phones; I don't think I've ever seen it happen on a PC, laptop, or tablet
Well, it happens constantly to me, on every device I decide to torture by subjecting it to Dicsores.
-
Things that are being actively developed and are planned to be rolled out across millions of devices are not orphaned. Devices that don't get updates are. Conflating the two is tr .
-
He's actually just mad that his specific device is only getting one more major update.
I'm actually fine with it. I'm trying to figure out how you equate "device with specs that could run new OS not being given an upgrade path to new OS" to "New OS is the upgrade to Old OS, you just can't upgrade".
You keep saying Windows 10 Mobile is the upgrade to Windows RT, when, if it was, and a device could support the OS, Microsoft would build an upgrade path. Since it can't upgrade, it's obviously NOT an upgrade/rename. It may be taking the place of that OS in the product line, but calling it an upgrade means you don't understand what that word means.
-
Either way, MicroSoft fuck over existing Windows RT users, don't they?
-
Either way, MicroSoft fuck over existing Windows RT users, don't they?
Yes, all 8 of them.
Microsoft would build an upgrade path
What I'm saying is that they probably didn't build it in right. They didn't build in an upgrade path for windows phone 7, but windows 8 is pretty much just a new version. Once you've made that mistake, what are you going to do? Recall everyone's phones? Give them free hardware?
-
Explain. Is that supposed to reinforce or invalidate what I said?
-
@aliceif said:
Either way, MicroSoft fuck over existing Windows RT users, don't they?
Yes, all 8 of them.
Microsoft would build an upgrade path
What I'm saying is that they probably didn't build it in right. They didn't build in an upgrade path for windows phone 7, but windows 8 is pretty much just a new version. Once you've made that mistake, what are you going to do? Recall everyone's phones? Give them free hardware?
Except it wasn't - 7 was based on CE and 8 was based on NT.
-
They didn't build in an upgrade path for windows phone 7, but windows 8 is pretty much just a new version.
More than that: WP7 was effectively an updated WinCE6, whereas WP8 is a true WP OS; IIRC, it actually shares a lot of kernel-level code with the full Windows 8.Edit: d
-
If they'd put their system in the chip correctly, the upgrade would have been possible. But they didn't.
More than that: WP7 was effectively an updated WinCE6, whereas WP8 is a true WP OS; IIRC, it actually shares a lot of kernel-level code with the full Windows 8.
All I'm saying is that if they designed the system in such a way that the upgrade is not possible for the device, they can't magic it into being possible. They probably would have updated it properly if they could have. I don't think this situation is good, but I also wouldn't say that the Windows RT code base is orphaned.
-
I also wouldn't say that the Windows RT code base is orphaned
There was never a separate Windows RT codebase; it's just an edition of Windows 8 with limited desktop stuff running on ARM
-
Explain. Is that supposed to reinforce or invalidate what I said?
Win32s was a (partial implementation of) 32-bit Windows and it came out in the 90s, so, you decide.
-
-
@accalia said:
i buy through a MNVO for a reason
Because you like defective service?
Don't know what it's like in the US, but in the UK, using an MVNO network often works out cheaper than using a main network. And you get a lot less hassle.
-
Don't know what it's like in the US, but in the UK, using an MVNO network often works out cheaper than using a main network. And you get a lot less hassle.
Yes, it works like that here, too. And yet xe still can't get Discurse on zir phone.
-
This is what I've been saying. All I get in response is "BUT SURFACE RT CANT UPDATE TO 10 SO WINDOWS RT IS ORPHANED!!!"... no, it's just renamed. It's part of Windows 10. Devices being orphaned != an OS being orphaned.
-
Well, not having a MicroSoft account isn't a barrier to getting an upgrade notification on Windows 8.1
What I meant was that being logged into my MS-acct when I got the notification meant that I was only asked the question on one machine. Answering it (and skipping email) caused all my other machines to act the same way (when clicking the icon again) as the first one. I found that very odd (and am guessing the MS-acct is the common factor)
-
-
hmm... if you say so it must happen, but i for the life of me can't reproduce it on any of my devices....
Interesting... I actually am having trouble repro'ing it too. I am sure that it used to do it, so unless it works on Chrome on Linux but not for Chrome on Windows they must have fixed it! Spiffy! I figured I had just gotten used to the crappiness.
-
Recall everyone's phones?
Doesn't everyone upgrade their phones every year (or 2)?
Oh wait, my last one lasted at least 5. But then it wasn't a smart phone. Smart phones know they need replacing quickly. (ooo shiny!)
-
-
Devices being orphaned != an OS being orphaned.
The end-user doesn't care about the distinction.
Either way, MicroSoft fuck over existing Windows RT users, don't they?
-
I think "My Vagina Needs Onions", which is probably why I'm single.
-
I suspect other reasons, too.
-
Because you like defective service?
because i like spending only $30/mo for 3GB data on a month to month plan rather than a contract.
:-P
-
-
/me makes a note to move faster on that whole country swap thing
-
me makes a note to move faster on that whole country swap thing
But then you get crappy weather--oh, right, you live in
EastPortland. (I just remembered there's no need to disambiguate--they both have shitty weather.
-
portland OR has worse weather. :-P
also i don't live in portland, i just work there. ;-P
-
also i don't live in portland, i just work there.
You probably live close enough it doesn't matter for the purpose of this discussion, though.
-
true, but one must try for pedantry
-
Unfortunately, using kinda spoils the dickweedery side of it
-
i'm not good at being dickweedish.
i tend to get bitchy before that point.... of course that has been close enough before
-
Doesn't everyone upgrade their phones every year (or 2)?
So far, I upgrade every 4 - 5 years.
-
And to answer the Surface 2 RT thing, I just did all Windows updates and I don't have the Windows 10 notification. Too bad, because I was hoping for a WTF.
-
Based on my research, it is impossible; the scrollbar is controlled by the OS, and webpages cannot access anything to do with it except setting the scroll position through the DOM.
So set the scroll position instead.
We already know that Discourse reloads the entire thread (exc. the text) every 20 posts, so why not include the height of the post and fill blank posts that size?
Then the scrollbar works.I assume you can tell what part of the DOM is currently visible.
Of course, on a long thread the scrollbar becomes useless and eventually one scroll tick is too huge, but Discourse dies hideously on long threads already so this wouldn't be much worse.
-
Got the notification on my Win7 home machines here in Australia too. Haven't hooked the 8.1 laptop up to the network lately so it probably doesn't have it yet. (I also have an XP machine which doesn't get connected to the network. That one's too old to upgrade; there are no post-XP drivers available.)
I didn't mind the notification thing until I found out that it was such a special snowflake that it didn't feel it had to respect the "Hide icon and notifications" setting. Then I went looking for the update number and uninstalled it on all of my machines. (They're originally XP or, in one case, Vista machines that have been upgraded to 7; not a chance they'll manage to cope with 10.)
I do find it disappointing that Microsoft made no effort to distinguish this from a routine update, and furthermore that they marked it "important" rather than "optional". It smacks of dishonesty, though I expect in origin it's just more of the special snowflake thinking; if you're going to ignore the user's notification decisions you might as well ignore their patching preferences too. And if you don't have a technical way to do that, lie about yourself to get around it.
-
They're originally XP or, in one case, Vista machines that have been upgraded to 7; not a chance they'll manage to cope with 10
Anything that can cope with Vista can definitely manage 10. The XP ones should be about as sprightly as they are on 7, too. After Vista, MS have been making each major update be less of a system hog
-
There is a specific "important" Windows update you have to install to get it.
Don't have the KB number for that offhand, do you? I'd like to blacklist it for my site.
-
You can't just change pronouns and expect everyone to flip a switch in their heads instantaneously
Especially if their heads are ossified.
-
she's not even an actual hedgehog. Worst of the worst.
-
KB3035583.
Odd that even after 'reserving' the thing looks like it's going to hang around for the next two months.
-
[poll]
- I like the Cortana searchbar always visible on the taskbar with fixed size.
- I don't like it. It should be hidden under the Start menu.
- I like it on the taskbar, but it should collapse while not in focus.
- I don't mind either way.
[/poll]
-
Interesting. If one moves the taskbar to one of the sides of the screen, the searchbar becomes an icon (what choice does it have?) and clicking it opens the bar at the bottom of the popup.
Editing to add: resizing the taskbar doesn't turn the icon into a text field.
-
Isn't that the general direction the entire industry is moving in? Move fast and break things. Release unfinished buggy crap early and often. Redesign things every few years so it looks shiny. Make sure that using two of your products together is more seamless than using your product with a competitor's product. Move everything possible online. And so on.
-
ISTR, in earlier builds, the search didn't work at all with the taskbar anywhere but the bottom of the screen