I should note that my other source is taken from mainly home PC's, so adoption rate is typically quicker than the average. netmarketshare seems to favor large businesses, so their adoption rate is abysmal. And my own client's statistics is a blend of the two.
Or it could be that the statistics are being pulled from sources that have unusually slow adoption rate. I typically check the statistics that I see come from netmarketshare and the like from a couple other sources, and I've always noticed that they lag considerably from both another source, and my own statistics from visitors from my client's web sites.
For example, my statistics show 6.6% for Windows 8 , 7.88% for Vista, 30.28% for XP, and 54.69% for Windows 7. netmarketshare shows 5.1% for Windows 8, 4.62% for Vista, 37.17% for XP, and 44.37% for Windows 7. My other source shows 12.7% for Windows 8, 7.2% for Vista, 7.9% for XP, and 66% for Windows 7.
There is quite a bit of difference between the three, but ntmarketshare typically seems to poll from placed that hang on to their systems longer than most, I'm guessing some very large businesses as their primary source, which skews their numbers.
Sorry, I just double checked, it was rewritten for Windows NT 3.5, and then carried over to Windows 95. So the FreeBSD stack hasn't been in use for nearly 10 years. Some of the ancillary utilities however, were never rewritten for some time and might have used some FreeBSD code in them. They carried the "Some parts... blah blah...Berkely... blah blah" messages in them.
Windows doesn't use any of the FreeBSD TCP/IP stack anymore. It did at one time pre-Windows XP, but it was completely rewritten from the ground up prior to Windows XP, but many of the settings (registry settings) remained the same for compatibility.
The BIOS calls are intercepted by a little program that gets run off your media device (USB, Hard Disk, CD-ROM, whatever). Setting the BIOS to read only doesn't defeat that.
That's bullshit. I need UEFI. BIOS only allows a very limited set of space (384K) for hardware device BIOSes. I've hit that limit, as does most server admins because high performance devices use that space up very quickly. There is numerous other advantages to UEFI, but you'd need to take off your tin foil hat and actually learn about it for you to understand it. That or build a server. Then you'll be crying about why stuff doesn't work and how stupid BIOS really is and why there isn't something better out there.
So much for Americans that actually have read their constitution and the corresponding amendments.
Otherwise you would know that being able to say whatever you want without repercussions is not one of your rights, nor is it protected.
Actually, we do have the right to freely speak without repercussions from government entities. That is in fact protected by the First Amendment.
You aren't able to be free from repercussions from saying anything you want about government entities either. For example, you can not threaten the President of the United States. Nor does it protect you from being tried for treason by divulging information. Nor does it protect you from criminal prosecution. But mostly you are correct. The first amendment is about free speech of a citizen with respect to the government (not citizens about other citizens). A lot of people think it gives them the right to say anything they want about anything as a blanket statement and protects from from any and all repercussions.
I didn't mean they have no effect, just that they by themselves can't elect someone that is obviously completely wrong in the view of those older and wiser. If a candidate is obviously detrimental to the group, but because of the lack of wisdom and experience the 18-24 group can't see it, but the 25+ group can, then they won't be elected. But two candidates that are close otherwise, yes, then the 18-24 group can swing the vote, which is how it should be.
I'm sorry carp, you need to get with the program. Your views conflict with the interests of the people to have the government watching everyone, protecting everyone from everything and themselves. How can you expect that to happen if speak out with silly things like truth and logic. It'll be easier when they pass the bill next year that outlaws such things and reclassify "truth and logic" as a WMD.
So much for Americans that actually have read their constitution and the corresponding amendments. Otherwise you would know that being able to say whatever you want without repercussions is not one of your rights, nor is it protected.
And it may be declassified at some future point, but it currently isn't. Rules are put in place for a reason, and they are supposed to be followed. The average Army grunt isn't in charge of determining whether a document is sufficiently public knowledge to change a documents classification. That's for someone else to do, and until it's classification is changed, it is not allowed on non-secure computers, no matter the source.
There is no ambiguity, because ambiguity is the bane of a well secured network. It allows for social hacking and social hacking as time has proven is the easiest way to hack into secure systems. It's really not rocket science.
No, "Leaked" and "released" is not a matter of semantics. Released documents go through a formal process to have them declassified prior to being available to the public. Leaked documents are documents that bypass the formal process or aren't previously declassified before being available to the public. That's not a difference in semantics.
MS-SQL may use T-SQL for interrogating the data, programmers don't need to write it in most cases. Entity Framework will create all the T-SQL you need, including creating the actual database, tables, indexes, primary keys, and foreign keys. You can write entire applications without ever touching T-SQL.
I'll grant you that you do need to install the silverlight plug-in to get it to work on the client, but that isn't really harder than installing the browser in the first place. Millions of housewives have figured it out, just ask netflix.
I agree that TCP congestion control helps prevent hogging bandwidth, but TCP streams only using at most 33.33% of the network varies greatly on the latency, the amount of buffers in the routers between both connections, and window size. Properly tuned TCP stacks can achieve MUCH higher network utilization than that, including most current windows OS's.
Hmm.. You can write a silverlight app in C#, which then contacts an ASP.NET webservice that is written in C#, that calls the middle tier written in C# that calls the data access layer written in C#, that gets data from SQL Server that does a bunch of stuff that uses custom database functions written in C#.
Slashdot Mirror
I should note that my other source is taken from mainly home PC's, so adoption rate is typically quicker than the average.
netmarketshare seems to favor large businesses, so their adoption rate is abysmal.
And my own client's statistics is a blend of the two.
Or it could be that the statistics are being pulled from sources that have unusually slow adoption rate. I typically check the statistics that I see come from netmarketshare and the like from a couple other sources, and I've always noticed that they lag considerably from both another source, and my own statistics from visitors from my client's web sites.
For example, my statistics show 6.6% for Windows 8 , 7.88% for Vista, 30.28% for XP, and 54.69% for Windows 7.
netmarketshare shows 5.1% for Windows 8, 4.62% for Vista, 37.17% for XP, and 44.37% for Windows 7.
My other source shows 12.7% for Windows 8, 7.2% for Vista, 7.9% for XP, and 66% for Windows 7.
There is quite a bit of difference between the three, but ntmarketshare typically seems to poll from placed that hang on to their systems longer than most, I'm guessing some very large businesses as their primary source, which skews their numbers.
Sorry, I just double checked, it was rewritten for Windows NT 3.5, and then carried over to Windows 95. So the FreeBSD stack hasn't been in use for nearly 10 years. Some of the ancillary utilities however, were never rewritten for some time and might have used some FreeBSD code in them. They carried the "Some parts... blah blah...Berkely... blah blah" messages in them.
Windows doesn't use any of the FreeBSD TCP/IP stack anymore. It did at one time pre-Windows XP, but it was completely rewritten from the ground up prior to Windows XP, but many of the settings (registry settings) remained the same for compatibility.
The BIOS calls are intercepted by a little program that gets run off your media device (USB, Hard Disk, CD-ROM, whatever). Setting the BIOS to read only doesn't defeat that.
Nobody needs UEFI
That's bullshit. I need UEFI. BIOS only allows a very limited set of space (384K) for hardware device BIOSes. I've hit that limit, as does most server admins because high performance devices use that space up very quickly. There is numerous other advantages to UEFI, but you'd need to take off your tin foil hat and actually learn about it for you to understand it. That or build a server. Then you'll be crying about why stuff doesn't work and how stupid BIOS really is and why there isn't something better out there.
So much for Americans that actually have read their constitution and the corresponding amendments.
Otherwise you would know that being able to say whatever you want without repercussions is not one of your rights, nor is it protected.
Actually, we do have the right to freely speak without repercussions from government entities. That is in fact protected by the First Amendment.
You aren't able to be free from repercussions from saying anything you want about government entities either. For example, you can not threaten the President of the United States. Nor does it protect you from being tried for treason by divulging information. Nor does it protect you from criminal prosecution. But mostly you are correct. The first amendment is about free speech of a citizen with respect to the government (not citizens about other citizens). A lot of people think it gives them the right to say anything they want about anything as a blanket statement and protects from from any and all repercussions.
Would you say that the documents were leaked from the NSA?
I didn't mean they have no effect, just that they by themselves can't elect someone that is obviously completely wrong in the view of those older and wiser. If a candidate is obviously detrimental to the group, but because of the lack of wisdom and experience the 18-24 group can't see it, but the 25+ group can, then they won't be elected. But two candidates that are close otherwise, yes, then the 18-24 group can swing the vote, which is how it should be.
Would you say that the documents were released by the NSA?
Your memory is failing you. You read it back before you were transported back in time.
Well there are enough voters above 24 to offset any radical sillyness by the under-24 crowd.
Well after they get to the point that they've arrested everyone with 6 digit UID's, I'm making a new account.
I'm sorry carp, you need to get with the program. Your views conflict with the interests of the people to have the government watching everyone, protecting everyone from everything and themselves. How can you expect that to happen if speak out with silly things like truth and logic. It'll be easier when they pass the bill next year that outlaws such things and reclassify "truth and logic" as a WMD.
Thanks for your contributions to slashdot over the years. Please let me know how the food is.
I think you meant a pro tip, asshole. Because offering a pro tip asshole is something completely different. Maybe that is what you meant after all.
So much for Americans that actually have read their constitution and the corresponding amendments. Otherwise you would know that being able to say whatever you want without repercussions is not one of your rights, nor is it protected.
And it may be declassified at some future point, but it currently isn't. Rules are put in place for a reason, and they are supposed to be followed. The average Army grunt isn't in charge of determining whether a document is sufficiently public knowledge to change a documents classification. That's for someone else to do, and until it's classification is changed, it is not allowed on non-secure computers, no matter the source.
There is no ambiguity, because ambiguity is the bane of a well secured network. It allows for social hacking and social hacking as time has proven is the easiest way to hack into secure systems. It's really not rocket science.
No, "Leaked" and "released" is not a matter of semantics. Released documents go through a formal process to have them declassified prior to being available to the public. Leaked documents are documents that bypass the formal process or aren't previously declassified before being available to the public. That's not a difference in semantics.
Wiping a TV is a lot less labor intensive.
MS-SQL may use T-SQL for interrogating the data, programmers don't need to write it in most cases. Entity Framework will create all the T-SQL you need, including creating the actual database, tables, indexes, primary keys, and foreign keys. You can write entire applications without ever touching T-SQL.
I'll grant you that you do need to install the silverlight plug-in to get it to work on the client, but that isn't really harder than installing the browser in the first place. Millions of housewives have figured it out, just ask netflix.
I agree that TCP congestion control helps prevent hogging bandwidth, but TCP streams only using at most 33.33% of the network varies greatly on the latency, the amount of buffers in the routers between both connections, and window size. Properly tuned TCP stacks can achieve MUCH higher network utilization than that, including most current windows OS's.
The DRM integration doesn't necessarily have to be closed-standards. There is nothing that precludes the DRM from having open source implementations.
Hmm.. You can write a silverlight app in C#, which then contacts an ASP.NET webservice that is written in C#, that calls the middle tier written in C# that calls the data access layer written in C#, that gets data from SQL Server that does a bunch of stuff that uses custom database functions written in C#.
Is this part of Agile Programming or something? Write the most incomplete code you can get away with because it isn't in the spec?
Yes. It's part of TDD, where the coder is supposed to write the absolutely smallest set of code that passes said test.