In defense of the "be nice to girls" behavior, girls tended to be more mature, talk less on VoIP (tip to everyone: we dont care that your dog ralfed up a shoe, we just want you to pipe down), and generally act more like a human being than the teenage dudes.
Even though (anecdotally) they tended not to be as good, it may have something to do with tryharding less and worrying more about interacting like an adult with others-- and honestly I dont care if you're a leet 2300 rated rogue if you're obnoxious.. Dunno.
There is a lot of ugly misogyny in games. This is because such a large percentage of gamers are scumbags or young men who engage in the online equivalent of pulling a girl's pigtails because she makes them feel funny in the pants and they don't yet know why.
Thats not misogyny, its a behavior predicted by Penny Arcade's Gabe years ago and it transcends gender. When someone says theyre going to rape my mother because of my performance in a game, I can either interpret it as a misogynistic attack on the female gender, or I can realize that I got out of the third grade a long, long time ago and people who want to be foul cant actually hurt me with their words.
Seriously, just because someone calls your mother fat doesnt mean that theres a rape culture, it means some people act like children and should be ignored. Grow up.
Would you also prefer that TCP, UDP, ethernet, and IPSec used plaintext? What about TLS?
Sometimes it just doesnt make sense to use plaintext. Theres no time that plaintext would be useful that you couldnt simply use a tool (like wireshark or fiddler) to convert the binary into a readable form.
Exactly. But this is from the company who though zip-ing Excel files was a good idea (XLSX). You spend more time waiting for the file to decompress than actual loading into memory.
It was (decompression is way, way, way faster than IO to disk), but the two are completely unrelated.
Binary =/= compressed. They overlap, but they are not equivalent. Binary just generally means that its not specifically ASCII encoded, which generally means that it can skip the step of parsing and lexing the ASCII into binary-- which makes it run faster (not slower).
This is why I use windows 7. I find the OSX interface to be infuriating, along with its lack of decent multimon (did they fix that yet?) and window scaling shortcuts.
Surprise-- I actually dont like the dock at all, and actually think that the Win7 interface is the 2nd best interface out there (I think I would put CentOS 7s gnome implementation down as the best).
I guess it depends on how you define nice and what you do with the computer. My personal definition of "nicer" includes being reliable, not crashing often, and facilitating my work getting done quickly and without frustration
Then at this point I can only assume that the problem is the end user, because I've worked with Win7 since the technical preview and work in an office where everyone but one person uses it, and Im quite productive on it. Im not 100% sure the last time I've had a BSOD on a machine under my control, but it would probably have been at least 4 years ago.
For other examples, I have enough OS X keyboard shortcuts, gestures and preferences options burned into muscle memory at this point that even spending that same several hours on relearning those things would offset my productivity by $1000
Thats because you took the time to get familiar on a system that is marketed at a premium; if you need to pay more for muscle memory at this point its pretty much your fault. Win7 has plenty of shortcuts as well that I use too, and thats one of the reasons I wont be taking the time to get comfortable on a Mac: Lost productivity, and paying a premium for the privilege.
And while it sounds trivial, there are things like OS X being able to save any document from any application to PDF without using a plugin or other app where (for my personal workflow) the time saved easily outweighs the computer purchase price.
Not using Cute PDF is worth 1000 to you? Ok. I had thought people decried bloat and including unnecessary things in the OS, but guess I was wrong.
Everything you're saying confirms that its personal preference, and far be it for me to tell you that you shouldnt use the OS you like. I just think its an absurd waste of money when people spend ~2x as much for a Mac for some hypothetical boost in productivity or product life span-- because those depend far, far more on the person than the OS theyre using.
The kernel doesnt come up until after that "binary stuff", aka the boot record and MBR.
After the kernel is up, there is no distinction between "scripts" and "binaries" at all.
Being a pedant myself, you are correct that scripts are technically binary, but in the context a binary is referring to compiled bytecode, while a script is human-readable shell-interpreted code. There is a massive difference in that 1) binaries generally cannot be easily reverse engineered or altered 2) binaries are much, much faster (being compiled) 3) scripts rely on a lot of pre-existing infrastructure-- the kernel must be up, the userland must be up, the command interpreter must be up. Binaries can run straight off the disk (ie, the bootloader).
If you can manage to get a Linux/OS X or other *nix system to behave like windows,
Go grab an older version of pfSense 2.0 (would probably work with versions of FreeBSD 8.3), do a fresh install and plug a USB keyboard in. TA-DA, driver bug causing boot hangs. I think it occurred with certain combinations of keyboards and motherboards, but it was a bonafide documented driver bug.
Go grab a copy of Ubuntu 12.10 and install on a machine with certain Intel NICs. TA-DA, another driver bug bricking your NIC. Driver had to be blacklisted in a post-release update.
Go find and install SoftEther VPN or S5 proxy. Watch where they stick their binaries, log files, and user config-- and then tell me how it conforms to the magical Unix standard.
Hint: stop using a *nix system as root.
When I figure out how to run kernel-mode drivers without root privileges or install packages without root, I'll let you know.
I have a 2011 HP Probook with Win7 that I like quite well. As a bonus it lets me upgrade RAM without paying an arm and a leg, get the latest SSD for ~$180, and easily bridge NICs without a bunch of hoops (dont actually know how hard it is to bridge in OSX, but I havent seen that option).
Im not sure what yall are doing with your computers to create such problems when you use windows, but I can assure you that having done volunteer work on hundreds of laptops people manage to screw up Macbooks just as badly as Windows laptops, if not worse (because they think "indestructable" means you can use a macbook as a door wedge or some such).
I bought a brand new HP Probook in 2011 with a Sandy bridge CPU for $450; you paid 2/3 of that for a 5 year old computer with a crappy processor. In what world is that reasonably sane?
Whether its nicer is a matter of personal taste, but IMO you have to be loaded or have really poor financial decisionmaking to drop an extra grand on a piece of hardware just because the OS it comes with is "nicer".
Pretty sure I didnt say it was, but this hair-trigger reaction to anything thats not resounding support is exactly the sort of drama I was talking about. I didnt immediately come out and defend Zoe Quinn, so I must be "the enemy".
This "movement" sure has a way of turning people off before they even have heard the full story.
One is the registry. While a forgotten file in a forgotten directory doesn't take time, the registry is this huge blob that needs to be loaded.
The entire registry usually does not exceed 30MB, and the entire thing is not loaded at once. It is loaded piecemeal when used. You might as well argue that the fact that there are 80 zillion plist files on OSX causes it to get slower over time (maybe it does, but only if OSX were really badly engineered).
The other is that everybody gets to write their own installer.
Most dont, there are a handful of popular ones including the built in one. And lets face it, if you're running someone elses code on your box they could technically write their own installer no matter what OS you're on. Conventions may vary due to other factors, but the "Unixness" of an OS has no impact on your ability or lack thereof to write an installer.
And the combination of the two, even though a program is installed through MSI, it can still write all over the registry, and the system won't know about it.
MSI files describe what will be modified and when; thats their job, and how they can perform atomic installations. Any binary you run on any OS is generally going to be able to write anywhere, in the absence of a Mandatory Access Control system.
The solution would be that the software needs to inform the installer which folders and registry keys it needs,
I dont know that its safe to assume anything about other country's states simply because they use the same word. I dont know anything about AU's states, and would not assume that you have anything like the 10th amendment or that they look anything like the US's states. Different countries, different circumstances when the country was formed, different constitutions.
Irrelevant movement about how gaming news continues to make itself irrelevant by being unprofessional finds new ways to be unprofessional and irrelevant.
Since the last 2 articles, my level of caring about this issue hasnt budged beyond "its mildly interesting just how much drama a non-issue can generate".
And the US is a country of 350 million. You would do better to compare Ireland to perhaps Virginia or North Carolina, except that we have to contend with our federal government and the 10th amendment and relationships with other states.
Basically what Im saying is you're comparing apples and oranges; obviously Ireland can change faster because its smaller and has a lot less complex system. I might point you at a little word called "bureaucracy", and remind you that when organizational size increases linearly, complexity increases exponentially.
with windows an "installer" is just a binary program that you are trusting to write files all over the place but you have no real idea what its doing or if its working correctly.
This is not correct in the least.
Windows Installer programs (.msi), which are the backend for many programs, IS structured and is not "just a binary". Its not quite the same as a package manager like apt-get, but shares more in common with that than with "just a binary" able to "write files all over the place".
When the Installer service isnt used, there are a number of other options like InstallShield, which again are structured, not "just binaries". It is true that you can download a binary that doesnt use any installer and does just randomly write, but thats true of ANY non-walled garden OS. Notably, for the longest time (and probably still now) the best way to get good nVidia performance on Linux was to download a large binary blob driver from nVidia. It did not use a package manager, it simply executed via a shell script.
If you go outside of the package manager on unix and try to overwrite system packages by hand you can have serious problems too.
But it is sometimes necessary, and it isnt a feature of "unix". Windows has plenty of package managers, they just arent popular for a number of reasons that have nothing to do with its heritage as an NT-based OS and everything to do with the culture around the respective OSes and the common license model for software on those OSes. Most software people use on Windows is NOT OSS, and thus would be utterly unsuitable for a repository.
2, Transparency - Unix systems are much simpler and better understood, the boot process is usually just a series of scripts for instance,
Thats also not true. The "better understood" could perhaps apply to the FOSS *nixes, but not OSX. Series of scripts is just plain wrong; every OS follows a pretty standard progression of "boot record --> bootloader --> OS / drivers". Scripts dont kick in until after that; prior is a lot of "binary stuff". The filesystem structure you mention is also there on Windows, it just looks different; programs in Program Files, Window bits in the Windows folder, user data in the Users folder (and programdata, when a program is badly behaved and tries to stick userdata in program files). Im aware of the Unix heirarchy, but youre being deceptive if you claim that programs dont violate it all the time. Binaries and config stored in/usr/local,/usr/bin,/opt,/var (!), logs stored outside of/var, and so on-- I've seen it all.
3, Lack of third party drivers - on most unix systems, drivers typically ship with the OS, get updated when the OS does and get tested together
This is vaguely and sort of true. The kernel types are different; you might as well complain that a pencil isnt as well bristled as a paintbrush. And certainly there ARE driver problems on Linux, even when they're built in-- and as theyre built in theyre often far more of a PITA when they do break (like the old e1000 adapter bug that bricked the NICs).
Windows systems typically have a random collection of disparate drivers which sometimes don't play well together or with updates to other parts of the system.
This is very rare. If you got your system from an OEM, they provide the drivers (packaged from the hardware vendors) and generally there are no issues-- it works out of the box. If you build your own, you just grab the motherboard and video drivers and you're set. Actual conflicts are not common at all; the closest I've seen is buggy webcam drivers from logitech causing bluescreen, and that not for several years now. Since then I've heard of iOS bugs breaking wifi / mobile data, Linux bugs bricking e1000 NICs, FreeBSD USB driver bugs causing hang on boot (8.
While I generally disagree with you (and with the primacy of the bishop of Rome), I dont believe that there is a Catholic bishop out there who would contradict my statement.
The assumption is that I was boasting, but as it seems yall are occupied making snide remarks-- and as I had thought we were having a discussion-- I'll just let my self out.
Slashdot Mirror
In defense of the "be nice to girls" behavior, girls tended to be more mature, talk less on VoIP (tip to everyone: we dont care that your dog ralfed up a shoe, we just want you to pipe down), and generally act more like a human being than the teenage dudes.
Even though (anecdotally) they tended not to be as good, it may have something to do with tryharding less and worrying more about interacting like an adult with others-- and honestly I dont care if you're a leet 2300 rated rogue if you're obnoxious.. Dunno.
So, IMO, there is no solution in the larger context
Its called an ignore list and a lack of caring what a foul-mouthed player has to say.
Both of those have served me fairly well, and as a bonus you tend to play much better when your opponent is foaming at the mouth and you arent.
There is a lot of ugly misogyny in games. This is because such a large percentage of gamers are scumbags or young men who engage in the online equivalent of pulling a girl's pigtails because she makes them feel funny in the pants and they don't yet know why.
Thats not misogyny, its a behavior predicted by Penny Arcade's Gabe years ago and it transcends gender. When someone says theyre going to rape my mother because of my performance in a game, I can either interpret it as a misogynistic attack on the female gender, or I can realize that I got out of the third grade a long, long time ago and people who want to be foul cant actually hurt me with their words.
Seriously, just because someone calls your mother fat doesnt mean that theres a rape culture, it means some people act like children and should be ignored. Grow up.
This thread is filled with people who think that binary == compressed, plaintext == more efficient, and multiplexing == MITM.
I dont think anyone's really gonna notice.
Would you also prefer that TCP, UDP, ethernet, and IPSec used plaintext? What about TLS?
Sometimes it just doesnt make sense to use plaintext. Theres no time that plaintext would be useful that you couldnt simply use a tool (like wireshark or fiddler) to convert the binary into a readable form.
Exactly. But this is from the company who though zip-ing Excel files was a good idea (XLSX). You spend more time waiting for the file to decompress than actual loading into memory.
It was (decompression is way, way, way faster than IO to disk), but the two are completely unrelated.
Binary =/= compressed. They overlap, but they are not equivalent. Binary just generally means that its not specifically ASCII encoded, which generally means that it can skip the step of parsing and lexing the ASCII into binary-- which makes it run faster (not slower).
Being binary doesnt mean it needs decompression. It may actually mean that you skip the step of lexing ASCII into binary.
This is why I use windows 7. I find the OSX interface to be infuriating, along with its lack of decent multimon (did they fix that yet?) and window scaling shortcuts.
Surprise-- I actually dont like the dock at all, and actually think that the Win7 interface is the 2nd best interface out there (I think I would put CentOS 7s gnome implementation down as the best).
I guess it depends on how you define nice and what you do with the computer. My personal definition of "nicer" includes being reliable, not crashing often, and facilitating my work getting done quickly and without frustration
Then at this point I can only assume that the problem is the end user, because I've worked with Win7 since the technical preview and work in an office where everyone but one person uses it, and Im quite productive on it. Im not 100% sure the last time I've had a BSOD on a machine under my control, but it would probably have been at least 4 years ago.
For other examples, I have enough OS X keyboard shortcuts, gestures and preferences options burned into muscle memory at this point that even spending that same several hours on relearning those things would offset my productivity by $1000
Thats because you took the time to get familiar on a system that is marketed at a premium; if you need to pay more for muscle memory at this point its pretty much your fault. Win7 has plenty of shortcuts as well that I use too, and thats one of the reasons I wont be taking the time to get comfortable on a Mac: Lost productivity, and paying a premium for the privilege.
And while it sounds trivial, there are things like OS X being able to save any document from any application to PDF without using a plugin or other app where (for my personal workflow) the time saved easily outweighs the computer purchase price.
Not using Cute PDF is worth 1000 to you? Ok. I had thought people decried bloat and including unnecessary things in the OS, but guess I was wrong.
Everything you're saying confirms that its personal preference, and far be it for me to tell you that you shouldnt use the OS you like. I just think its an absurd waste of money when people spend ~2x as much for a Mac for some hypothetical boost in productivity or product life span-- because those depend far, far more on the person than the OS theyre using.
MBR in first line should be bootloader. Whoops
The kernel doesnt come up until after that "binary stuff", aka the boot record and MBR.
After the kernel is up, there is no distinction between "scripts" and "binaries" at all.
Being a pedant myself, you are correct that scripts are technically binary, but in the context a binary is referring to compiled bytecode, while a script is human-readable shell-interpreted code. There is a massive difference in that
1) binaries generally cannot be easily reverse engineered or altered
2) binaries are much, much faster (being compiled)
3) scripts rely on a lot of pre-existing infrastructure-- the kernel must be up, the userland must be up, the command interpreter must be up. Binaries can run straight off the disk (ie, the bootloader).
If you can manage to get a Linux/OS X or other *nix system to behave like windows,
Go grab an older version of pfSense 2.0 (would probably work with versions of FreeBSD 8.3), do a fresh install and plug a USB keyboard in. TA-DA, driver bug causing boot hangs. I think it occurred with certain combinations of keyboards and motherboards, but it was a bonafide documented driver bug.
Go grab a copy of Ubuntu 12.10 and install on a machine with certain Intel NICs. TA-DA, another driver bug bricking your NIC. Driver had to be blacklisted in a post-release update.
Go find and install SoftEther VPN or S5 proxy. Watch where they stick their binaries, log files, and user config-- and then tell me how it conforms to the magical Unix standard.
Hint: stop using a *nix system as root.
When I figure out how to run kernel-mode drivers without root privileges or install packages without root, I'll let you know.
I have a 2011 HP Probook with Win7 that I like quite well. As a bonus it lets me upgrade RAM without paying an arm and a leg, get the latest SSD for ~$180, and easily bridge NICs without a bunch of hoops (dont actually know how hard it is to bridge in OSX, but I havent seen that option).
Im not sure what yall are doing with your computers to create such problems when you use windows, but I can assure you that having done volunteer work on hundreds of laptops people manage to screw up Macbooks just as badly as Windows laptops, if not worse (because they think "indestructable" means you can use a macbook as a door wedge or some such).
I bought a brand new HP Probook in 2011 with a Sandy bridge CPU for $450; you paid 2/3 of that for a 5 year old computer with a crappy processor. In what world is that reasonably sane?
Why would the envelope be sweaty?
Whether its nicer is a matter of personal taste, but IMO you have to be loaded or have really poor financial decisionmaking to drop an extra grand on a piece of hardware just because the OS it comes with is "nicer".
Pretty sure I didnt say it was, but this hair-trigger reaction to anything thats not resounding support is exactly the sort of drama I was talking about. I didnt immediately come out and defend Zoe Quinn, so I must be "the enemy".
This "movement" sure has a way of turning people off before they even have heard the full story.
One is the registry. While a forgotten file in a forgotten directory doesn't take time, the registry is this huge blob that needs to be loaded.
The entire registry usually does not exceed 30MB, and the entire thing is not loaded at once. It is loaded piecemeal when used. You might as well argue that the fact that there are 80 zillion plist files on OSX causes it to get slower over time (maybe it does, but only if OSX were really badly engineered).
The other is that everybody gets to write their own installer.
Most dont, there are a handful of popular ones including the built in one. And lets face it, if you're running someone elses code on your box they could technically write their own installer no matter what OS you're on. Conventions may vary due to other factors, but the "Unixness" of an OS has no impact on your ability or lack thereof to write an installer.
And the combination of the two, even though a program is installed through MSI, it can still write all over the registry, and the system won't know about it.
MSI files describe what will be modified and when; thats their job, and how they can perform atomic installations. Any binary you run on any OS is generally going to be able to write anywhere, in the absence of a Mandatory Access Control system.
The solution would be that the software needs to inform the installer which folders and registry keys it needs,
It does.
I dont know that its safe to assume anything about other country's states simply because they use the same word. I dont know anything about AU's states, and would not assume that you have anything like the 10th amendment or that they look anything like the US's states. Different countries, different circumstances when the country was formed, different constitutions.
Alternate headline:
Irrelevant movement about how gaming news continues to make itself irrelevant by being unprofessional finds new ways to be unprofessional and irrelevant.
Since the last 2 articles, my level of caring about this issue hasnt budged beyond "its mildly interesting just how much drama a non-issue can generate".
And the US is a country of 350 million. You would do better to compare Ireland to perhaps Virginia or North Carolina, except that we have to contend with our federal government and the 10th amendment and relationships with other states.
Basically what Im saying is you're comparing apples and oranges; obviously Ireland can change faster because its smaller and has a lot less complex system. I might point you at a little word called "bureaucracy", and remind you that when organizational size increases linearly, complexity increases exponentially.
with windows an "installer" is just a binary program that you are trusting to write files all over the place but you have no real idea what its doing or if its working correctly.
This is not correct in the least.
Windows Installer programs (.msi), which are the backend for many programs, IS structured and is not "just a binary". Its not quite the same as a package manager like apt-get, but shares more in common with that than with "just a binary" able to "write files all over the place".
When the Installer service isnt used, there are a number of other options like InstallShield, which again are structured, not "just binaries". It is true that you can download a binary that doesnt use any installer and does just randomly write, but thats true of ANY non-walled garden OS. Notably, for the longest time (and probably still now) the best way to get good nVidia performance on Linux was to download a large binary blob driver from nVidia. It did not use a package manager, it simply executed via a shell script.
If you go outside of the package manager on unix and try to overwrite system packages by hand you can have serious problems too.
But it is sometimes necessary, and it isnt a feature of "unix". Windows has plenty of package managers, they just arent popular for a number of reasons that have nothing to do with its heritage as an NT-based OS and everything to do with the culture around the respective OSes and the common license model for software on those OSes. Most software people use on Windows is NOT OSS, and thus would be utterly unsuitable for a repository.
2, Transparency - Unix systems are much simpler and better understood, the boot process is usually just a series of scripts for instance,
Thats also not true. The "better understood" could perhaps apply to the FOSS *nixes, but not OSX. Series of scripts is just plain wrong; every OS follows a pretty standard progression of "boot record --> bootloader --> OS / drivers". Scripts dont kick in until after that; prior is a lot of "binary stuff". The filesystem structure you mention is also there on Windows, it just looks different; programs in Program Files, Window bits in the Windows folder, user data in the Users folder (and programdata, when a program is badly behaved and tries to stick userdata in program files). Im aware of the Unix heirarchy, but youre being deceptive if you claim that programs dont violate it all the time. Binaries and config stored in /usr/local, /usr/bin, /opt, /var (!), logs stored outside of /var, and so on-- I've seen it all.
3, Lack of third party drivers - on most unix systems, drivers typically ship with the OS, get updated when the OS does and get tested together
This is vaguely and sort of true. The kernel types are different; you might as well complain that a pencil isnt as well bristled as a paintbrush. And certainly there ARE driver problems on Linux, even when they're built in-- and as theyre built in theyre often far more of a PITA when they do break (like the old e1000 adapter bug that bricked the NICs).
Windows systems typically have a random collection of disparate drivers which sometimes don't play well together or with updates to other parts of the system.
This is very rare. If you got your system from an OEM, they provide the drivers (packaged from the hardware vendors) and generally there are no issues-- it works out of the box. If you build your own, you just grab the motherboard and video drivers and you're set. Actual conflicts are not common at all; the closest I've seen is buggy webcam drivers from logitech causing bluescreen, and that not for several years now. Since then I've heard of iOS bugs breaking wifi / mobile data, Linux bugs bricking e1000 NICs, FreeBSD USB driver bugs causing hang on boot (8.
Not sure what you mean about the US not getting it right. Registration in the US is state by state; its not a federal issue.
While I generally disagree with you (and with the primacy of the bishop of Rome), I dont believe that there is a Catholic bishop out there who would contradict my statement.
The assumption is that I was boasting, but as it seems yall are occupied making snide remarks-- and as I had thought we were having a discussion-- I'll just let my self out.
What does the size of the country have to do with it?
10 person company vs 10,000 person company. Which one can implement full-disk encryption across the board quicker? Why?