I'm willing to accept many ways, but not every way.
For entertainment, wider is significantly better except for splitscreen multiplayer. There's almost always much more important things happening along the horizon line roughly
For work, I'd take a 16:9 display in which I could comfortably put two programs side-by-side over a 4:3 display in which I could not, and I'd do it without hesitation.
I would guess it's the controlled nature of a transplant.
From TFA: But Canaveroâ(TM)s proposal is different: By cutting spinal cords with an ultra-sharp knife, and then mechanically connecting the spinal cord from one personâ(TM)s head with another personâ(TM)s body, a more complete (and immediate) connection could be accomplished. As he notes in his paper:
âoeIt is this âoeclean cutâ [which is] the key to spinal cord fusion, in that it allows proximally severed axons to be âfusedâ(TM) with their distal counterparts. This fusion exploits so-called fusogens/sealantsâ¦.[which] are able to immediately reconstitute (fuse/repair) cell membranes damaged by mechanical injury, independent of any known endogenous sealing mechanism.â
What I don't know is why they couldn't do the same thing for spinal cord injury patients, just cutting out the injured part.
If you want to argue that boot viruses are likely to ever be much of a problem, that's fine. If you want to argue that secure boot is the wrong solution, that's also fine. Both would be an interesting discussion.
But saying "it's not currently a problem so MS shouldn't do anything about it"? That's dumb, and what I was trying to call out.
Then you can use the methods other people have said. I didn't say that it works in every case (someone else has complained about the requirement of having a Windows key), but it covers almost all cases.
Also, just in the off chance that you don't know this and be helpful, apparently you can set remote desktop so that it will always forward the Windows key to the remote host. (See the "alternatively,..." bit here.) Again, not saying this is better or worse; you may or may not like it.
I don't really care what you want to use to type, but I get irked when I see people (not you, just used your comment as a jumping off point) who scoff at the Windows key and (apparently) everything it stands for.
I know it's irrational, but me too. If anything, I find the windows key (mod4 or super if you prefer) more useful on Linux than I do on Windows, because window managers are so configurable. To me, it is great: window manager functions get the Windows key, which means (1) I only need one key to perform window manager functions* and (2) there's basically no chance I'll mess with a program's shortcuts, which isn't the case for ctrl-<whatever> or alt-<whatever> (or even ctrl-alt-<whatever> some of the time). I'm not sure, but I wouldn't be surprised if I use the windows key more than I use alt.
* I use a tiling WM, so I may do a lot more keyboard-based window manager actions than is typical.
A Model M-type keyboard isn't for me for a number of reasons, but I really really feel that people who stick with them are making a huge mistake. There are other mechanical keyboards with windows keys if you want one...
They have already been doing it for nearly 2 decades, there are no infrastructure or upkeep costs at this point that would be substantially diminished by removing XP support.
Says someone who hasn't even written software, apparently. Even if nothing else, dropping a configuration removes a bunch of testing costs.
However, it's even more. When Vista was released, Microsoft made a bunch of changes to the driver model -- basically the API that drivers are programmed against -- usually to move stuff from kernel mode to user mode. (This increases system stability.) Vista through 8 (I think) all use this driver model. Supporting XP as well means writing and maintaining XP-specific code for its driver model.
I don't know anywhere near enough about this to say that it costs 2% more or 20% more or 50% more. But to say that "it costs these companies zero dollars" means that you clearly have zero knowledge about what you're talking about.
I would say that a reasonable measure is (or you could argue is) the time at which it was superseded by a new version. But that's still Jan. 2007, so almost 6 1/2 years ago. Even Windows 7 is almost 4 years since release.
I would say that Python and Lisp at least are both reasonably strongly-typed (just because they're dynamic doesn't mean they can't be strong). PHP and Perl are both definitely weakly typed. The others I don't know well enough to evaluate.
But at this point I honestly don't know what people really mean when they complain that X language doesn't have pointers. Because basically everything out there offers something like Java references. Are people really missing pointer arithmetic? How often do you need that?
However, it sure would reduce cognitive load to not switch languages between browser and server ends.
I have heard one argument I find somewhat convincing, which is that using a single language means that if requirements change or people discover a better way to do something, it's possible to move or share code between client and server side without rewriting it. If you do something on the server side now and then say "hey, we'll get more responsiveness if we put it client-side", you can just move that function to the client side and call it.
Not being a web dev, I can't actually evaluate this claim with high confidence, but it sounds somewhat plausible at least.
But if you're in one of the instances where you're trying to access a program that you don't use very often, and don't remember the exact name of it, the hierarchical menu is light years beyond the start screen.
The Win8 start screen -- IMO that's essentially unusable. (You could make it usable if you put in a bunch of effort to arrange tiles the way you want, but it'd take a while.)
But: there's an "all apps" view or something in Windows 8 that basically gives you a flat presentation of the start menu, including grouping icons by what folder they're in (in the start menu) and showing the name of that folder.
I don't know which is better -- start menu or all apps -- as I basically never use either. In fact, I forget how to open the all apps screen. But I suspect that about the worst you could say about Win8 is that it's reasonably competitive there. I'm with vux984: the Windows Vista/7 start menu is really bad at just navigating through. It's too short, it's too narrow, if you open the wrong folder you have to click it again to re-collapse it, etc.
To be fair, the start menu was never that great. It was just better than what came before and went through a couple of improvements (and several worsenings) over its lifetime.
Actually I'm one of those people who think that it never went through a worsening, at least until now. There were certain aspects that I don't like about some of the changes (e.g. with Vista & 7 it's harder to browse because of the limited size), but I think each of the changes was a significant plus overall. There haven't even been all that many changes... The most controversial I would guess would be with XP, but I really liked even that because I loved the the automatically-maintaned frequently-used programs list; XP was when I started to back off on keeping my start menu organized sanely, and with Vista I stopped entirely.
What would you consider one of the worsenings? (Other than metro.)
"Increasingly", true, and I do try to support cross-platform games and will do so even more in the future, even if I primarily or only play on Windows. But it's still a looong way off from being the norm unless you're willing to restrict your game choices a lot.
Wine would open up a lot of options, but I don't really feel like messing around with it when I can just run Windows and be done with things, especially considering that some of the games I play aren't even rated all that highly on the appdb.
The biggest thing is the fact that you can search all sections (Apps, Settings, Files) with a single search bar now. No more having to type, mouse-move, click, and then find the option I want!
For a while that was actually my biggest complaint about metro actually, and then I learned about Win-W, which will open the search interface set to settings (like if you pressed Win then clicked settings). Presumably there's one for files too but I never use that anyway so don't know what it is.
It's still kinda annoying and I'm glad to see that they're going back, but it's a lot better than having to mouse.
A compute rate that varies with temperature would seem to be a bug, rather than a feature.
Read again: The inability to re-clock the GPU frequencies and voltages dynamically based upon load has been... The reclocking (or lack thereof) affects temperature, not is caused by it.
(Though the other responses are technically accurate, I think they miss the main point of the complaint.)
At least in my experience, Phillips heads are rather more common than flat heads, and screwdrivers are about equally common for both. Both are far, far more common than anything else.
(I'm not saying that it's hard to find others -- just that if you're at a friend's house or something and need to borrow a screwdriver, there's a decent chance they'll have several flat heads, several Phillips, and little or nothing else.)
This is really only useful as proof that you knew something that's resistant to guessing lots of times (Like some specific description of an event, a long private key, etc).
That's still really useful, you know. For example, suppose you take a photo of some damage when you move into an apartment or something, and want a third party to be able to attest that you took it when you moved in instead of moved out.
As they explain in the FAQ, they can't really attest to the truth of something for obvious reasons, but that doesn't mean that they're only slightly useful.
OK... so is what you're saying that there is a greater difference between the two runtimes than what TFA says, because.NET doesn't have the possibility of heap pollution? Something like that?
Slashdot Mirror
I'm willing to accept many ways, but not every way.
For entertainment, wider is significantly better except for splitscreen multiplayer. There's almost always much more important things happening along the horizon line roughly
For work, I'd take a 16:9 display in which I could comfortably put two programs side-by-side over a 4:3 display in which I could not, and I'd do it without hesitation.
Mmmmm, Slashcode. The pinnacle of Internet message board software.
I would guess it's the controlled nature of a transplant.
From TFA:
But Canaveroâ(TM)s proposal is different: By cutting spinal cords with an ultra-sharp knife, and then mechanically connecting the spinal cord from one personâ(TM)s head with another personâ(TM)s body, a more complete (and immediate) connection could be accomplished. As he notes in his paper:
âoeIt is this âoeclean cutâ [which is] the key to spinal cord fusion, in that it allows proximally severed axons to be âfusedâ(TM) with their distal counterparts. This fusion exploits so-called fusogens/sealantsâ¦.[which] are able to immediately reconstitute (fuse/repair) cell membranes damaged by mechanical injury, independent of any known endogenous sealing mechanism.â
What I don't know is why they couldn't do the same thing for spinal cord injury patients, just cutting out the injured part.
I'm not sure why this was modded troll.
If you want to argue that boot viruses are likely to ever be much of a problem, that's fine. If you want to argue that secure boot is the wrong solution, that's also fine. Both would be an interesting discussion.
But saying "it's not currently a problem so MS shouldn't do anything about it"? That's dumb, and what I was trying to call out.
Then you can use the methods other people have said. I didn't say that it works in every case (someone else has complained about the requirement of having a Windows key), but it covers almost all cases.
Also, just in the off chance that you don't know this and be helpful, apparently you can set remote desktop so that it will always forward the Windows key to the remote host. (See the "alternatively, ..." bit here.) Again, not saying this is better or worse; you may or may not like it.
What you should do is remap Caps Lock to act as the Windows key
Blasphemy! Caps lock is meant to be ctrl!
I suppose you could put mod4/super on the ctrl key, then ctrl on caps. Actually, that's probably what I'd do if I had to deal with a 101-key keyboard.
I know it's irrational, but me too. If anything, I find the windows key (mod4 or super if you prefer) more useful on Linux than I do on Windows, because window managers are so configurable. To me, it is great: window manager functions get the Windows key, which means (1) I only need one key to perform window manager functions* and (2) there's basically no chance I'll mess with a program's shortcuts, which isn't the case for ctrl-<whatever> or alt-<whatever> (or even ctrl-alt-<whatever> some of the time). I'm not sure, but I wouldn't be surprised if I use the windows key more than I use alt.
* I use a tiling WM, so I may do a lot more keyboard-based window manager actions than is typical.
A Model M-type keyboard isn't for me for a number of reasons, but I really really feel that people who stick with them are making a huge mistake. There are other mechanical keyboards with windows keys if you want one...
I can't believe that no one has mentioned that Win-R brings up the run dialog, like it always has.
But boot virii/malware are not very common anyway.
And of course the way to respond to a potential threat is to do nothing until it's common, then scramble to find a half-assed solution.
They have already been doing it for nearly 2 decades, there are no infrastructure or upkeep costs at this point that would be substantially diminished by removing XP support.
Says someone who hasn't even written software, apparently. Even if nothing else, dropping a configuration removes a bunch of testing costs.
However, it's even more. When Vista was released, Microsoft made a bunch of changes to the driver model -- basically the API that drivers are programmed against -- usually to move stuff from kernel mode to user mode. (This increases system stability.) Vista through 8 (I think) all use this driver model. Supporting XP as well means writing and maintaining XP-specific code for its driver model.
I don't know anywhere near enough about this to say that it costs 2% more or 20% more or 50% more. But to say that "it costs these companies zero dollars" means that you clearly have zero knowledge about what you're talking about.
That's ridiculous, in fact.
I would say that a reasonable measure is (or you could argue is) the time at which it was superseded by a new version. But that's still Jan. 2007, so almost 6 1/2 years ago. Even Windows 7 is almost 4 years since release.
...anything that doesn't have pointers fails the OP's test... which is a lot these days.
And my point is that it's a dumb test. (Granted, I did say it in response to you. :-))
I would say that Python and Lisp at least are both reasonably strongly-typed (just because they're dynamic doesn't mean they can't be strong). PHP and Perl are both definitely weakly typed. The others I don't know well enough to evaluate.
But at this point I honestly don't know what people really mean when they complain that X language doesn't have pointers. Because basically everything out there offers something like Java references. Are people really missing pointer arithmetic? How often do you need that?
However, it sure would reduce cognitive load to not switch languages between browser and server ends.
I have heard one argument I find somewhat convincing, which is that using a single language means that if requirements change or people discover a better way to do something, it's possible to move or share code between client and server side without rewriting it. If you do something on the server side now and then say "hey, we'll get more responsiveness if we put it client-side", you can just move that function to the client side and call it.
Not being a web dev, I can't actually evaluate this claim with high confidence, but it sounds somewhat plausible at least.
The Win8 start screen -- IMO that's essentially unusable. (You could make it usable if you put in a bunch of effort to arrange tiles the way you want, but it'd take a while.)
But: there's an "all apps" view or something in Windows 8 that basically gives you a flat presentation of the start menu, including grouping icons by what folder they're in (in the start menu) and showing the name of that folder.
I don't know which is better -- start menu or all apps -- as I basically never use either. In fact, I forget how to open the all apps screen. But I suspect that about the worst you could say about Win8 is that it's reasonably competitive there. I'm with vux984: the Windows Vista/7 start menu is really bad at just navigating through. It's too short, it's too narrow, if you open the wrong folder you have to click it again to re-collapse it, etc.
Actually I'm one of those people who think that it never went through a worsening, at least until now. There were certain aspects that I don't like about some of the changes (e.g. with Vista & 7 it's harder to browse because of the limited size), but I think each of the changes was a significant plus overall. There haven't even been all that many changes... The most controversial I would guess would be with XP, but I really liked even that because I loved the the automatically-maintaned frequently-used programs list; XP was when I started to back off on keeping my start menu organized sanely, and with Vista I stopped entirely.
What would you consider one of the worsenings? (Other than metro.)
"Increasingly", true, and I do try to support cross-platform games and will do so even more in the future, even if I primarily or only play on Windows. But it's still a looong way off from being the norm unless you're willing to restrict your game choices a lot.
Wine would open up a lot of options, but I don't really feel like messing around with it when I can just run Windows and be done with things, especially considering that some of the games I play aren't even rated all that highly on the appdb.
As someone who uses Windows at home, there are two main reasons:
1.) Games
2.) I use Linux at work, and it's nice to have my OS piss me off in different ways depending on where I am
The biggest thing is the fact that you can search all sections (Apps, Settings, Files) with a single search bar now. No more having to type, mouse-move, click, and then find the option I want!
For a while that was actually my biggest complaint about metro actually, and then I learned about Win-W, which will open the search interface set to settings (like if you pressed Win then clicked settings). Presumably there's one for files too but I never use that anyway so don't know what it is.
It's still kinda annoying and I'm glad to see that they're going back, but it's a lot better than having to mouse.
Read again: The inability to re-clock the GPU frequencies and voltages dynamically based upon load has been... The reclocking (or lack thereof) affects temperature, not is caused by it.
(Though the other responses are technically accurate, I think they miss the main point of the complaint.)
At least in my experience, Phillips heads are rather more common than flat heads, and screwdrivers are about equally common for both. Both are far, far more common than anything else.
(I'm not saying that it's hard to find others -- just that if you're at a friend's house or something and need to borrow a screwdriver, there's a decent chance they'll have several flat heads, several Phillips, and little or nothing else.)
The domain existed, but Twitter didn't. Not really. Twitter wasn't created until 2006, and they bought the domain twitter.com for $7500 in that year.
That's still really useful, you know. For example, suppose you take a photo of some damage when you move into an apartment or something, and want a third party to be able to attest that you took it when you moved in instead of moved out.
As they explain in the FAQ, they can't really attest to the truth of something for obvious reasons, but that doesn't mean that they're only slightly useful.
Why would you get a useless fact notarized?
No, here's is being used as "a small fact", which doesn't even meet the alternative definition you cite.
OK... so is what you're saying that there is a greater difference between the two runtimes than what TFA says, because .NET doesn't have the possibility of heap pollution? Something like that?