Domain: microsoft.com
Stories and comments across the archive that link to microsoft.com.
Comments · 34,132
-
Re:Hang on
I think he is referring to the use of PsTools. I've personally dissected viruses which have used that set of utilities as part of their payload but this was years ago before SysInternals even belonged to Microsoft and the viruses I saw which used them were very unsophisticated. Either way, I don't see how it's relevant to Cisco having unsafe-defaults.
-
Re:what is malware?
That's why now days I just run this.
http://www.microsoft.com/en-us/security_essentials/default.aspx
From reading all of your posts on this topic, I swear you must work for Microsoft, or for an advertising/marketing company they pay, or for benefits given to you by them.
Of all the infected machines I see, that are running, FULLY up to date anti-malware software on FULLY up to date versions of Windows, the top two culprits for missing things are (in this order) McAfee and MSE.
Again, I am only counting machines where the software is up to date and where Windows is up to date (and verifying the malware infected the machine AFTER the anti-malware software was installed).
-
TL:DR FUD
Article makes it sound like Win7 is getting inundated with viruses, but when you look at the counts it paints a different story.
Windows 7: Increase of 33%
1Q2010: 3/1000
2Q2010: 4/1000 - 64 Bit: 2.5/1000Windows XP: Decrease of 22%
1Q2010: 18/1000
2Q2010:14/1000Basically, You're still safer using windows 7 vs other Windows versions.
Current Numbers from MS are Here. Not exactly sure how computerworld got those numbers since MS numbers are higher and lower than others but there you go.
-
Re:what is malware?
That's why now days I just run this.
http://www.microsoft.com/en-us/security_essentials/default.aspx
-
Huge sample size
According to the Microsoft Report this is based on a sample size of 600 million computers. That is plenty large enough for the results to be statistically significant.
It was trollish for the summary to omit that Windows 7 still has 1/5 of the infection rate of Windows XP, though.
-
Re:It's just sales
By your definition, everyone is then a "bad user". Clueless individual users like my father-in-law are "bad users" and have no business using a Windows computer. And technology companies larded with full-on technology professionals are "bad users".
I think that, if Windows auto updates were a real solution, everyone would be using it, all the time. Yet slashdot is rife with stories about security vulnerabilities Windows (and their handmaiden of chaos, Adobe) have left uncorrected for all kinds of reasons (obsolescing some older piece of software, its part of the business model, etc.) And the IT at pretty much everywhere I've worked simply has not trusted it. Oh, look what just popped up on my calendar here, just while I was typing this;
.
AUDIENCE:
All Enterprise Managed Windows desktop and laptop system usersSUMMARY:
As part of routine maintenance of Windows computers, patches to the Windows operating system and select Windows applications will be installed on Friday, 5/13/2011 starting at 2:00 am.ACTION:
These updates might require one or more reboot(s). If required, the reboot(s) will occur starting at 3:00 am on Friday, 5/13/2011. It is possible that additional reboots may still be required following 3:00 am; if so, a pop-up will appear asking you to reboot now or later. Please reboot at your earliest convenience.DETAILS:
If your computer is not on at 2:00 am on Friday, 5/13/2011, the updates will install as soon as possible after 9:00 am on 5/13/2011, but will not force a reboot. If you have a laptop that is not attached to the network, in a loaner pool, or out in the field and would like to have it updated prior to the scheduled time, you may activate the patches via the [Some third party not Windows auto updates] Patch Management system as early as Thursday morning. If you need to install the patches prior to their availability in [that third party software], feel free to install the patches using Microsoft's Windows Update website. Please install all Critical and Important patches.For more detailed information regarding the Microsoft patches, please visit the following website:
http://www.microsoft.com/technet/security/bulletin/ms11-May.mspxPlease note: In some cases Microsoft makes changes to the patches that are distributed on the Windows Update web site. If the version of the patch installed on your system is not the most current version, the [third party] patch distribution software will reapply the patch and reboot your system if needed. If you would like to update your system prior to the schedule time, you can follow the directions posted here:
http://someplace/services/desktop/security/PatchManagementSystemFAQs.htm
.That's fine, it's not like I'm doing any work on this PC that could be interrupted by multiple (and an apparently unpredicable number of) reboots. It's not inconvenient at all.
YET, even still, with a ginormous IT department, huge budget for IT, ruthless discipline, multiple networking choke points, and some skin in the game WRT national security and cyber warfare, my employer was hacked, thoroughly and repeatedly, by real adversaries, ah, but only through the Windows machines. Must be we are all "bad users". It couldn't be Windows.
-
Re:Windows tortures users... what's new?
Of course third-party applications can use the logging facility! Wow. You are a Windows admin and you didn't know this?
Scripts can use it too:
http://technet.microsoft.com/en-us/library/ee176682.aspx -
Re:Windows tortures users... what's new?
if it's a system error, you can always look in the system log.
Because 'the fubar service failed to start' is so useful when you're trying to figure out why your system isn't working. Particularly when the service control panel claims that it's running.
BTW, the new Slashdot interface is definitely 'torturing users'. How can they keep screwing it up more and more with every update?
-
Re:Windows tortures users... what's new?
Windows are terrible to troubleshoot: the norm is "in case of any error, silently terminate program, never ever log anything, don't even have an option to do so." It wasn't until I've been using various Linux workstations for a few years and then had to troubleshoot a Win7 box that I realized this. ("[warn] cannot open
/foo/bar/baz.xyzzy" is not massively helpful, but it's much better than the "" you'll get from Windows and most programs for Windows.)Isn't that actually a problem with the mindset of the people who write the applications.
If it's a system error, you can always look in the system log.
-
Re:Wrong Question
This is tired old FUD that you Microsoft shills trot out all the time.
Can you name one technology that Microsoft innovated? And by the way, it doesn't count if they bought it from someone else.
Ok, now to your original question:
1. Alchemy
2. Bespin
3. Bitcoin
4. eyeOS
5. KDE Social Desktop
6. Ksplice
7. Unity
8. HTTP, the Web, TCP/IP, and ARPAnet
9. X Windows
10. Perl
11. Slashdot
12. Google keeps playing with open source, but can't make up their minds. Here are some
13. Microsoft plays with open source, here are some. This must just eat you up. Too bad, Open Source is everywhere.
14. Here are some more innovative open source projects.
Now, I expect you to provide at least 5 innovative projects Microsoft created within the last 10 years. (Sorry, you can't count Windows or Office, since those ideas are much older, and are no longer considered innovative.)
Failing that, at least read what I wrote. -
Re:Bait and switch off
Apple and MS built on the entry cost of computing or the lack of low cost options in many areas.
Google offered a vision of been more open to set itself apart and draw in mindshare.
Now the code stops in one area. What will be closed next and why...
http://www.microsoft.com/opensource/directory.aspx http://www.codeplex.com/ MS is trying ;) -
Re:Failed?
I think the submitter needs to understand what "failed" means.
He's mostly using "failed" in the conventional marketdroid sense - they didn't fly off the shelves making the corporation manufacturing them and those investing in them buckets of cash.
A lot of that stuff were far from failures. they were designed for a specific task. the 3d mousing devices are STILL used to this day in high end 3d CAD.
That's true of many of the items in the collection.
He labels the overblown Swiss Army Knife as a bad design - while failing to consider the purpose of the design. (As a collectible/art piece, which he tacitly admits it was a success at.) The next knife down he's equally dismissive of. But he fails to consider that a) there are other methods of carrying (a belt pouch for example), or b) that there *are* people who constantly have something it will fit into handy (a photographer and his camera bag, a fisherman and his tackle box, etc..). The lowest knife, which he praises, has so little functionality it's only real use is to be impressive to the guy in the next cubicle over because you're the Guy Who Always Has A Knife.
The same with the Nikon Coolpix 100. He seems utterly unaware that there are a huge number of cameras out there... My little Canon A1200 has no extra chargers or cables either.
He praises the Olympic Memory Stick Thumb Drive - but take away the 'cool' packaging, and it's just another thumb drive. Maybe he keeps the 'cool' packaging as an art piece on his desk, but I suspect he's one of the few.
Overall Mr Buxton is really, really bad at evaluating the success or failure and the usefulness or not of many of the items he has in his collection. -
Re:Failed?
I think the submitter needs to understand what "failed" means.
He's mostly using "failed" in the conventional marketdroid sense - they didn't fly off the shelves making the corporation manufacturing them and those investing in them buckets of cash.
A lot of that stuff were far from failures. they were designed for a specific task. the 3d mousing devices are STILL used to this day in high end 3d CAD.
That's true of many of the items in the collection.
He labels the overblown Swiss Army Knife as a bad design - while failing to consider the purpose of the design. (As a collectible/art piece, which he tacitly admits it was a success at.) The next knife down he's equally dismissive of. But he fails to consider that a) there are other methods of carrying (a belt pouch for example), or b) that there *are* people who constantly have something it will fit into handy (a photographer and his camera bag, a fisherman and his tackle box, etc..). The lowest knife, which he praises, has so little functionality it's only real use is to be impressive to the guy in the next cubicle over because you're the Guy Who Always Has A Knife.
The same with the Nikon Coolpix 100. He seems utterly unaware that there are a huge number of cameras out there... My little Canon A1200 has no extra chargers or cables either.
He praises the Olympic Memory Stick Thumb Drive - but take away the 'cool' packaging, and it's just another thumb drive. Maybe he keeps the 'cool' packaging as an art piece on his desk, but I suspect he's one of the few.
Overall Mr Buxton is really, really bad at evaluating the success or failure and the usefulness or not of many of the items he has in his collection. -
Re:Failed?
I think the submitter needs to understand what "failed" means.
He's mostly using "failed" in the conventional marketdroid sense - they didn't fly off the shelves making the corporation manufacturing them and those investing in them buckets of cash.
A lot of that stuff were far from failures. they were designed for a specific task. the 3d mousing devices are STILL used to this day in high end 3d CAD.
That's true of many of the items in the collection.
He labels the overblown Swiss Army Knife as a bad design - while failing to consider the purpose of the design. (As a collectible/art piece, which he tacitly admits it was a success at.) The next knife down he's equally dismissive of. But he fails to consider that a) there are other methods of carrying (a belt pouch for example), or b) that there *are* people who constantly have something it will fit into handy (a photographer and his camera bag, a fisherman and his tackle box, etc..). The lowest knife, which he praises, has so little functionality it's only real use is to be impressive to the guy in the next cubicle over because you're the Guy Who Always Has A Knife.
The same with the Nikon Coolpix 100. He seems utterly unaware that there are a huge number of cameras out there... My little Canon A1200 has no extra chargers or cables either.
He praises the Olympic Memory Stick Thumb Drive - but take away the 'cool' packaging, and it's just another thumb drive. Maybe he keeps the 'cool' packaging as an art piece on his desk, but I suspect he's one of the few.
Overall Mr Buxton is really, really bad at evaluating the success or failure and the usefulness or not of many of the items he has in his collection. -
Re:Failed?
I think the submitter needs to understand what "failed" means.
He's mostly using "failed" in the conventional marketdroid sense - they didn't fly off the shelves making the corporation manufacturing them and those investing in them buckets of cash.
A lot of that stuff were far from failures. they were designed for a specific task. the 3d mousing devices are STILL used to this day in high end 3d CAD.
That's true of many of the items in the collection.
He labels the overblown Swiss Army Knife as a bad design - while failing to consider the purpose of the design. (As a collectible/art piece, which he tacitly admits it was a success at.) The next knife down he's equally dismissive of. But he fails to consider that a) there are other methods of carrying (a belt pouch for example), or b) that there *are* people who constantly have something it will fit into handy (a photographer and his camera bag, a fisherman and his tackle box, etc..). The lowest knife, which he praises, has so little functionality it's only real use is to be impressive to the guy in the next cubicle over because you're the Guy Who Always Has A Knife.
The same with the Nikon Coolpix 100. He seems utterly unaware that there are a huge number of cameras out there... My little Canon A1200 has no extra chargers or cables either.
He praises the Olympic Memory Stick Thumb Drive - but take away the 'cool' packaging, and it's just another thumb drive. Maybe he keeps the 'cool' packaging as an art piece on his desk, but I suspect he's one of the few.
Overall Mr Buxton is really, really bad at evaluating the success or failure and the usefulness or not of many of the items he has in his collection. -
Re:Failed?
I think the submitter needs to understand what "failed" means.
He's mostly using "failed" in the conventional marketdroid sense - they didn't fly off the shelves making the corporation manufacturing them and those investing in them buckets of cash.
A lot of that stuff were far from failures. they were designed for a specific task. the 3d mousing devices are STILL used to this day in high end 3d CAD.
That's true of many of the items in the collection.
He labels the overblown Swiss Army Knife as a bad design - while failing to consider the purpose of the design. (As a collectible/art piece, which he tacitly admits it was a success at.) The next knife down he's equally dismissive of. But he fails to consider that a) there are other methods of carrying (a belt pouch for example), or b) that there *are* people who constantly have something it will fit into handy (a photographer and his camera bag, a fisherman and his tackle box, etc..). The lowest knife, which he praises, has so little functionality it's only real use is to be impressive to the guy in the next cubicle over because you're the Guy Who Always Has A Knife.
The same with the Nikon Coolpix 100. He seems utterly unaware that there are a huge number of cameras out there... My little Canon A1200 has no extra chargers or cables either.
He praises the Olympic Memory Stick Thumb Drive - but take away the 'cool' packaging, and it's just another thumb drive. Maybe he keeps the 'cool' packaging as an art piece on his desk, but I suspect he's one of the few.
Overall Mr Buxton is really, really bad at evaluating the success or failure and the usefulness or not of many of the items he has in his collection. -
I actually moved away...
...to Windows 7. No troll.
I've been using Linux desktop for years now, and when I discovered Ubuntu I was immediately sold. Started using Ubuntu itself and manually setup KDE because I figured it would be better to use the original product. As soon as I learned about the LTS version I immediately started using that one.
I'm the kind of guy who used to tinker a lot with his system but now my main concern is stability and continuity. I don't want to be confronted with having to upgrade or re-configure stuff within very short periods, also because I don't always care about the "latest and greatest" any longer; my main concern is getting my work done and considering that I'm self-employed means I need to have a system which continues doing what I want.
SO the latest LTS came out and as can be expected I took my time to perform the upgrade. Even "took a day off" so to speak so that I had all the time required to upgrade.
That was sheer hell. First from LTS 8.04 to 10; I ended up with many inconsistencies. From accidently installed 64bit libraries thus chocking my 32bit system after a reboot right to the upgrade procedure hanging itself along the way. I wasn't going to give up that easy; no way. I then decided to simply go between versions; I edited
/etc/sources.list to reflect the changes, and dist upgraded. No go; while I did manage to upgrade one version I then ended up with hardware issues.One of my Samsung printers couldn't be properly addressed anymore (even though it supports LPR besides your regular protocols), my screen resolution was a mess again (I knew this up front; I had to hack X.conf manually last time as well) and it only got worse.
SO eventually restored a backup and started to look for other people's experiences. The outcome? "You're probably better of re-installing from scratch".
Well, that is not why I started to use Linux, especially a Debian (-based) distro in the first place! I know my hardware is dated, but surely it can't be that hard to keep stuff somewhat backwards compatible ?
Alas; I had been using Vista for some time by then (but disliked it) and came into contact with Windows 7. The eventual outcome was that I removed Linux entirely and replaced it with Windows 7. It was even a breeze to move my GPG keys over (which kinda worried me at first) thanks to stuff like GPG4Win and Enigmail which works on both Linux and Windows.
No offense here but now I can finally get some work done again while still keeping a relative modern (patched) system around. And the best part here for me is that I will have at least 9 years of support without the need or urgent requirement to upgrade.
When looking at the latest Firefox and Thunderbird as well as Ubuntu I think more programmers should realize that not everyone wants to change the way they work every product cycle. At the very least give people some option to continue working as they were used to.
Microsoft isn't a saint on this subject either (just look at the difference between XP and Vista/Win7) but in the overall the changes usually aren't that drastic (not to mention that you can easily change the way Windows looks; right down to a 98 look and feel).
So.... Millions of people using Ubuntu? On a server, absolutely. But on the desktop; I don't see this happening. Not after the first upgrade requirement.
-
Re:Disclosure policy
Browsers such as Chrome contain memory allocations that avoid DEP by using VirtualProtectEx() as it is pretty much a requirement of JIT compilation.
Blaming Microsoft in this case is extremely premature, since we know that Chrome does in fact disable some protections intentionally. -
Re:Hungarian Notation
For an example of object-oriented language that supports "units of measure" see F#.
-
Re:Don't do it...
I'm a programmer-slash-sysadmin, and I've taken a stab at writing both command-line tools using C/C++,
.NET, and these days with PowerShell, so I might be able to answer your question.When I write complex software, I usually provide some command-line tools for the admins to do things like import data, export logs, or whatever. This is a royal pain in the ass, but I do it because it's useful. I always end up spending something like 80% of the time on annoying stuff like handling command-line parameters, input validation, and error messages. Of course, because whatever I come up with is new and different, I have to write doco for it, train staff, and so on.
Now, with PowerShell, instead of having to write a whole new program to implement a command, I can simply extend a class from a framework library. The PS framework does almost everything automagically: handle the pipeline, input parameters, parameter validation, parameter sets, optional parameters, help, tab-complete, wildcard matching, output formatting, etc...
To give you an idea, it is possible to write a PowerShell command in C# (.NET) with several parameters and complex output that does a useful task in about 50 lines of rather trivial code. The equivalent C program would be thousands of lines.
More importantly, the resulting PowerShell command will be orthogonal, consistent, discoverable, and embeddable
By orthogonal, I mean things like: every PS command that handles wildcards does it with the same shared library, which is trivial to use. Hence, I can do things like: Get-VM "prod_win_[a-k]*" which is a VMware snapin, and the behavior will be exactly the same as if I had called a Citrix XenApp snapin to lists farm servers with: Get-XAServer "prod_win_[a-k]*". Similarly, the output of commands is structured data. You can say: Get-VM | Export-CSV or Get-XAServer | Export-Csv and get similar results. Compare with legacy command line tools, which often implement such formatting internally, and badly. I just had to work on some Novell systems, for example, which export invalid XML files because the utility doesn't escape ampersands! Of course, our example 50 line command will get all of that. Export to CSV? You have it! Export to XML? Done! Quickly, tell me how to export CSV formatted data from the following 3 Linux command-line tools: 'ls', 'apt-get', and 'ps'.
By consistent, I mean that parameters are always specified with "-param", never "/param", or "--param", or "-abcdgh" where each letter does something that you can only determine by reading a five page document. Similarly, Microsoft has established a strict naming system for developers, so that instead of "retrieve-foo", "ask-foo", "query-foo", "request-foo", "list-foo", "foo-list", "fooenum", or god knows what else, the only acceptable standard is "get-foo". VMware has "Get-VM", Citrix has "Get-XAServer", Microsoft has "Get-Process", etc... no guessing! There are standards for command names, parameter names, and coding conventions. E.g.: Verb Naming Rules, and Cmdlet Development Guidelines.
By discoverable, I mean that if I write a little 50-line utility with a bunch of parameters, an administrator at the command line can simply press 'tab' and have both the command and the parameter names automatically completed. The help is automatically generated from my 50 lines of code. GUI script wizards can load a bunch of metadata about each parameter to enable drag & drop script development.
By embeddable, I mean that even a 50-line utility can be called not just from the shell, but from within a hosting application in the same process. Instead of having to handle text-based streams, PS commands take
.NET objects, and return .NET objects. There's no guessw -
Re:Don't do it...
I'm a programmer-slash-sysadmin, and I've taken a stab at writing both command-line tools using C/C++,
.NET, and these days with PowerShell, so I might be able to answer your question.When I write complex software, I usually provide some command-line tools for the admins to do things like import data, export logs, or whatever. This is a royal pain in the ass, but I do it because it's useful. I always end up spending something like 80% of the time on annoying stuff like handling command-line parameters, input validation, and error messages. Of course, because whatever I come up with is new and different, I have to write doco for it, train staff, and so on.
Now, with PowerShell, instead of having to write a whole new program to implement a command, I can simply extend a class from a framework library. The PS framework does almost everything automagically: handle the pipeline, input parameters, parameter validation, parameter sets, optional parameters, help, tab-complete, wildcard matching, output formatting, etc...
To give you an idea, it is possible to write a PowerShell command in C# (.NET) with several parameters and complex output that does a useful task in about 50 lines of rather trivial code. The equivalent C program would be thousands of lines.
More importantly, the resulting PowerShell command will be orthogonal, consistent, discoverable, and embeddable
By orthogonal, I mean things like: every PS command that handles wildcards does it with the same shared library, which is trivial to use. Hence, I can do things like: Get-VM "prod_win_[a-k]*" which is a VMware snapin, and the behavior will be exactly the same as if I had called a Citrix XenApp snapin to lists farm servers with: Get-XAServer "prod_win_[a-k]*". Similarly, the output of commands is structured data. You can say: Get-VM | Export-CSV or Get-XAServer | Export-Csv and get similar results. Compare with legacy command line tools, which often implement such formatting internally, and badly. I just had to work on some Novell systems, for example, which export invalid XML files because the utility doesn't escape ampersands! Of course, our example 50 line command will get all of that. Export to CSV? You have it! Export to XML? Done! Quickly, tell me how to export CSV formatted data from the following 3 Linux command-line tools: 'ls', 'apt-get', and 'ps'.
By consistent, I mean that parameters are always specified with "-param", never "/param", or "--param", or "-abcdgh" where each letter does something that you can only determine by reading a five page document. Similarly, Microsoft has established a strict naming system for developers, so that instead of "retrieve-foo", "ask-foo", "query-foo", "request-foo", "list-foo", "foo-list", "fooenum", or god knows what else, the only acceptable standard is "get-foo". VMware has "Get-VM", Citrix has "Get-XAServer", Microsoft has "Get-Process", etc... no guessing! There are standards for command names, parameter names, and coding conventions. E.g.: Verb Naming Rules, and Cmdlet Development Guidelines.
By discoverable, I mean that if I write a little 50-line utility with a bunch of parameters, an administrator at the command line can simply press 'tab' and have both the command and the parameter names automatically completed. The help is automatically generated from my 50 lines of code. GUI script wizards can load a bunch of metadata about each parameter to enable drag & drop script development.
By embeddable, I mean that even a 50-line utility can be called not just from the shell, but from within a hosting application in the same process. Instead of having to handle text-based streams, PS commands take
.NET objects, and return .NET objects. There's no guessw -
Re:Don't do it...
Might not have much of a choice.
**gripes**
Here are my gripes about windows from an admin POV:
1) Unlike unix/unixlike OSes with Windows quite often you cannot rename/move/delete files/dirs that are in use. You might be able to do it in some cases, but not others, it's quite annoying if you are trying to atomically change/upgrade/update stuff without rebooting/restarting too much crap. You may think this is a small thing, but it has a major effect/limit on how you do stuff on windows (even Microsoft has to force reboots to change files).
So you may have to resort to stuff like this: http://technet.microsoft.com/en-us/sysinternals/bb897556Might not be as big an issue once you're large enough to use load balancers
:).2) The fine grained ACLs are good, but they often don't seem to work properly. On Win2k8 I've encountered cases where an account belongs to the Administrator's group but it somehow does not have enough permissions to rewrite/save a file that "full access" permissions to those in the Administrator's group. Why can't I open the file, change it and save it back? When I use that account to copy a file onto that file I get a "privilege escalation" prompt and if I "OK" it it overwrites the file. So the account is definitely in the Administrators group already...
3) I don't know why but lots of Windows stuff tends to have crappy logging by default. You often have unhelpful error messages that say "it hurts", but not tell you where it hurts, or what was being attempted, or what the target was. Some are even more useless! e.g. "UVD Information".
In theory this shouldn't be OS related but somehow I've had a lot less trouble figuring out what's going on from logs in linux/*bsd machines than from windows machines -e.g. it's faster/easier to figure out why email is not being received/sent with the former than the latter.
Searching for stuff in windows event logs is also a pain and a lot slower than using tail and grep on the unix/linux text logs.
4) Too often nobody seems to know what things actually do or how things actually work, not even people working for Microsoft - (e.g. this is not the full story: http://blogs.msdn.com/b/oldnewthing/archive/2007/10/08/5351207.aspx
Apparently there's stuff like a not very documented ITaskList_Deleted property which also affects how windows are handled...
Then there's the ServerXMLHTTP vs XMLHTTP - my colleague found out the hard way that there are cases where ServerXMLHTTP works and XMLHTTP doesn't - he still doesn't know why. I've not seen documentation on the real technical differences - this is light on the details: http://support.microsoft.com/kb/290761 ).As a result there are messageboards, blogs and docs filled with incorrect information.
And there's often no practical way to find out (unless you're an uberhacker who can disassemble megabytes of code in your sleep). With OSS stuff, at least you can look at the source and have a better idea (but sometimes you just go wow it's amazing that stuff even works, maybe I should use something else
;) ).**tips**
OK end of grumbling, here's what I use for when the automation breaks down ;).1) Add notepad, texteditor and hexeditor shortcuts to your SendTo folder. If you are unclear on where your SendTo folder is (because of roaming profiles or other weirdness), go to start, and run shell:sendto
Once you've done that you can right click on any file and open it with your editor/program of choice (add media player classic or VLC if you want
;) ).2) create a folder for utilities. e.g. c:\util or c:\bin and add it to your path (WinXP: winkey+pause, advanced, environment variables, system variables, path. Win2K8:start,right click computer, manage, advanced or something
-
Re:Don't do it...
Might not have much of a choice.
**gripes**
Here are my gripes about windows from an admin POV:
1) Unlike unix/unixlike OSes with Windows quite often you cannot rename/move/delete files/dirs that are in use. You might be able to do it in some cases, but not others, it's quite annoying if you are trying to atomically change/upgrade/update stuff without rebooting/restarting too much crap. You may think this is a small thing, but it has a major effect/limit on how you do stuff on windows (even Microsoft has to force reboots to change files).
So you may have to resort to stuff like this: http://technet.microsoft.com/en-us/sysinternals/bb897556Might not be as big an issue once you're large enough to use load balancers
:).2) The fine grained ACLs are good, but they often don't seem to work properly. On Win2k8 I've encountered cases where an account belongs to the Administrator's group but it somehow does not have enough permissions to rewrite/save a file that "full access" permissions to those in the Administrator's group. Why can't I open the file, change it and save it back? When I use that account to copy a file onto that file I get a "privilege escalation" prompt and if I "OK" it it overwrites the file. So the account is definitely in the Administrators group already...
3) I don't know why but lots of Windows stuff tends to have crappy logging by default. You often have unhelpful error messages that say "it hurts", but not tell you where it hurts, or what was being attempted, or what the target was. Some are even more useless! e.g. "UVD Information".
In theory this shouldn't be OS related but somehow I've had a lot less trouble figuring out what's going on from logs in linux/*bsd machines than from windows machines -e.g. it's faster/easier to figure out why email is not being received/sent with the former than the latter.
Searching for stuff in windows event logs is also a pain and a lot slower than using tail and grep on the unix/linux text logs.
4) Too often nobody seems to know what things actually do or how things actually work, not even people working for Microsoft - (e.g. this is not the full story: http://blogs.msdn.com/b/oldnewthing/archive/2007/10/08/5351207.aspx
Apparently there's stuff like a not very documented ITaskList_Deleted property which also affects how windows are handled...
Then there's the ServerXMLHTTP vs XMLHTTP - my colleague found out the hard way that there are cases where ServerXMLHTTP works and XMLHTTP doesn't - he still doesn't know why. I've not seen documentation on the real technical differences - this is light on the details: http://support.microsoft.com/kb/290761 ).As a result there are messageboards, blogs and docs filled with incorrect information.
And there's often no practical way to find out (unless you're an uberhacker who can disassemble megabytes of code in your sleep). With OSS stuff, at least you can look at the source and have a better idea (but sometimes you just go wow it's amazing that stuff even works, maybe I should use something else
;) ).**tips**
OK end of grumbling, here's what I use for when the automation breaks down ;).1) Add notepad, texteditor and hexeditor shortcuts to your SendTo folder. If you are unclear on where your SendTo folder is (because of roaming profiles or other weirdness), go to start, and run shell:sendto
Once you've done that you can right click on any file and open it with your editor/program of choice (add media player classic or VLC if you want
;) ).2) create a folder for utilities. e.g. c:\util or c:\bin and add it to your path (WinXP: winkey+pause, advanced, environment variables, system variables, path. Win2K8:start,right click computer, manage, advanced or something
-
Re:A Fundamental Problem with This Suggestion!
Oh, right. Well, I'm sure if they truly wanted my help making their browser better and more secure, they'd be okay with letting me take a peek at the source code
It's called Microsoft Shared Source Initiative
You just have to meet certain pre-requisites: you need to be an enterprise with 1500 licensed windows seats, sign a big fat NDA, and intend to use the source code for an eligible reason.
-
Re:Don't do it...
Otherwise, you're looking at VBScript or batch scripts.
Powershell handles WMI - http://technet.microsoft.com/en-us/library/dd315295.aspx
-
For COM, use COM tools
VBScript and "jscript", along with the Windows Script Host, are designed for COM automation. Most of what you need in that case can be found in the script56.chm file.
http://www.microsoft.com/downloads/details.aspx?FamilyId=01592C48-207D-4BE1-8A76-1C4099D7BBB9
Perl is not COM-oriented, of course, but can be adapted if you prefer.
.Net is not primarily COM, so it doesn't make much sense unless you already know .Net and like it. Some have suggested WMI. WMI is not script. It's a set of classes that can be used through script -- typically used with VBScript. For most things other than hardware information, WMI is just a clunky, slow wrapper, while the syntax is ugly and unintuitive. -
Powershell and other tools
Powershell. The only tool that knows how to talk to all the different frameworks in Windows is Powershell. No other tool can talk to
.NET, COM, WMI, native APIs (via P/Invoke), and external stdio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool.Since the test guy usually has to be a part time sysadmin too, you should be aware of these tools:
System update readiness tool: http://support.microsoft.com/kb/947821/en-us
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20
ollydbg: http://www.ollydbg.de/
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062
Windows Management Framework: http://support.microsoft.com/kb/968929
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5DIf XP is involved, check out Windows SteadyState. It's like deepfreeze, if you've ever used that. qemu is also a great way to boot test machines and capture output at scale; using CoW disks you can have fresh machines every time you boot regardless if the test machines are XP or not.
-
Powershell and other tools
Powershell. The only tool that knows how to talk to all the different frameworks in Windows is Powershell. No other tool can talk to
.NET, COM, WMI, native APIs (via P/Invoke), and external stdio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool.Since the test guy usually has to be a part time sysadmin too, you should be aware of these tools:
System update readiness tool: http://support.microsoft.com/kb/947821/en-us
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20
ollydbg: http://www.ollydbg.de/
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062
Windows Management Framework: http://support.microsoft.com/kb/968929
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5DIf XP is involved, check out Windows SteadyState. It's like deepfreeze, if you've ever used that. qemu is also a great way to boot test machines and capture output at scale; using CoW disks you can have fresh machines every time you boot regardless if the test machines are XP or not.
-
Powershell and other tools
Powershell. The only tool that knows how to talk to all the different frameworks in Windows is Powershell. No other tool can talk to
.NET, COM, WMI, native APIs (via P/Invoke), and external stdio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool.Since the test guy usually has to be a part time sysadmin too, you should be aware of these tools:
System update readiness tool: http://support.microsoft.com/kb/947821/en-us
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20
ollydbg: http://www.ollydbg.de/
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062
Windows Management Framework: http://support.microsoft.com/kb/968929
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5DIf XP is involved, check out Windows SteadyState. It's like deepfreeze, if you've ever used that. qemu is also a great way to boot test machines and capture output at scale; using CoW disks you can have fresh machines every time you boot regardless if the test machines are XP or not.
-
Powershell and other tools
Powershell. The only tool that knows how to talk to all the different frameworks in Windows is Powershell. No other tool can talk to
.NET, COM, WMI, native APIs (via P/Invoke), and external stdio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool.Since the test guy usually has to be a part time sysadmin too, you should be aware of these tools:
System update readiness tool: http://support.microsoft.com/kb/947821/en-us
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20
ollydbg: http://www.ollydbg.de/
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062
Windows Management Framework: http://support.microsoft.com/kb/968929
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5DIf XP is involved, check out Windows SteadyState. It's like deepfreeze, if you've ever used that. qemu is also a great way to boot test machines and capture output at scale; using CoW disks you can have fresh machines every time you boot regardless if the test machines are XP or not.
-
Powershell and other tools
Powershell. The only tool that knows how to talk to all the different frameworks in Windows is Powershell. No other tool can talk to
.NET, COM, WMI, native APIs (via P/Invoke), and external stdio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool.Since the test guy usually has to be a part time sysadmin too, you should be aware of these tools:
System update readiness tool: http://support.microsoft.com/kb/947821/en-us
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20
ollydbg: http://www.ollydbg.de/
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062
Windows Management Framework: http://support.microsoft.com/kb/968929
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5DIf XP is involved, check out Windows SteadyState. It's like deepfreeze, if you've ever used that. qemu is also a great way to boot test machines and capture output at scale; using CoW disks you can have fresh machines every time you boot regardless if the test machines are XP or not.
-
Powershell and other tools
Powershell. The only tool that knows how to talk to all the different frameworks in Windows is Powershell. No other tool can talk to
.NET, COM, WMI, native APIs (via P/Invoke), and external stdio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool.Since the test guy usually has to be a part time sysadmin too, you should be aware of these tools:
System update readiness tool: http://support.microsoft.com/kb/947821/en-us
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20
ollydbg: http://www.ollydbg.de/
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062
Windows Management Framework: http://support.microsoft.com/kb/968929
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5DIf XP is involved, check out Windows SteadyState. It's like deepfreeze, if you've ever used that. qemu is also a great way to boot test machines and capture output at scale; using CoW disks you can have fresh machines every time you boot regardless if the test machines are XP or not.
-
Powershell and other tools
Powershell. The only tool that knows how to talk to all the different frameworks in Windows is Powershell. No other tool can talk to
.NET, COM, WMI, native APIs (via P/Invoke), and external stdio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool.Since the test guy usually has to be a part time sysadmin too, you should be aware of these tools:
System update readiness tool: http://support.microsoft.com/kb/947821/en-us
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20
ollydbg: http://www.ollydbg.de/
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062
Windows Management Framework: http://support.microsoft.com/kb/968929
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5DIf XP is involved, check out Windows SteadyState. It's like deepfreeze, if you've ever used that. qemu is also a great way to boot test machines and capture output at scale; using CoW disks you can have fresh machines every time you boot regardless if the test machines are XP or not.
-
Powershell and other tools
Powershell. The only tool that knows how to talk to all the different frameworks in Windows is Powershell. No other tool can talk to
.NET, COM, WMI, native APIs (via P/Invoke), and external stdio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool.Since the test guy usually has to be a part time sysadmin too, you should be aware of these tools:
System update readiness tool: http://support.microsoft.com/kb/947821/en-us
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20
ollydbg: http://www.ollydbg.de/
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062
Windows Management Framework: http://support.microsoft.com/kb/968929
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5DIf XP is involved, check out Windows SteadyState. It's like deepfreeze, if you've ever used that. qemu is also a great way to boot test machines and capture output at scale; using CoW disks you can have fresh machines every time you boot regardless if the test machines are XP or not.
-
Powershell and other tools
Powershell. The only tool that knows how to talk to all the different frameworks in Windows is Powershell. No other tool can talk to
.NET, COM, WMI, native APIs (via P/Invoke), and external stdio based tools. If you can't do the automation you want using something in one of the above frameworks, you've got bigger problems than finding a good automation tool.Since the test guy usually has to be a part time sysadmin too, you should be aware of these tools:
System update readiness tool: http://support.microsoft.com/kb/947821/en-us
WMI diagnostic utility: http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
gplogview: http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=BCFB1955-CA1D-4F00-9CFF-6F541BAD4563
Windows SDK (including debugging tools for windows): http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35AEDA01-421D-4BA5-B44B-543DC8C33A20
ollydbg: http://www.ollydbg.de/
sysinternals suite: http://technet.microsoft.com/en-us/sysinternals/bb842062
Windows Management Framework: http://support.microsoft.com/kb/968929
WDK: http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff
WAIK: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en
Windows 7 SP1 WAIK supplement: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0AEE2B4B-494B-4ADC-B174-33BC62F02C5DIf XP is involved, check out Windows SteadyState. It's like deepfreeze, if you've ever used that. qemu is also a great way to boot test machines and capture output at scale; using CoW disks you can have fresh machines every time you boot regardless if the test machines are XP or not.
-
Re:Don't do it...
And why not? Powershell is perfect for the job.
-
Re:A Fundamental Problem with This Suggestion!
This reminds me of a funny quote from Undocumented Dos on getting access to the complete Dos source code. You couldn't but you could get a mix of source, binaries (.obj) and debugging information (symbol values) for the binaries if you paid a few thousand dollars for the OEM Adaptation Kit or something like that. The authors of Undocumented Dos opined "That's almost as good as source code - the only thing it is missing is the comments which are probably misleading anyway"
With that in mind here's how to get symbols for Microsoft binaries
http://support.microsoft.com/kb/311503
It's worth pointing out that people don't debug non trivial things by staring at source code - they debug the binary using a debugger. If you have symbols, you can do that.
-
Re:Hard to even submit MS bugs.
Microsoft's consumer products are difficult to submit bugs for, for obvious reasons (MS users are total idiots). But their developer tools (.NET, VS (compilers&IDE), DX, etc) all have standard reporting processes. https://connect.microsoft.com/directory/
-
Re:Why not Safari as well as Chrome?
It's the same base engine, isn't it? What about the non-google Chromium? Will it work with Adobe to erase cookies?
This isn't a "base engine" issue -- it's a browser UI issue. Each browser needs to offer an API hook to plugins that allow them to say, "hey, call this function when the user has requested their browsing history be deleted!" So, the way you phrased your last question is backwards -- Adobe must work with browser capabilities, not the other way around.
In the case of IE8 and later, this is a one-function COM interface that gets passed a single flags parameter indicating what types of objects should be deleted. Pretty simple stuff..... why it took Adobe more than two years to implement this obvious little capability is beyond me.
I haven't been able to find an equivalent in Firefox 4's NPAPI documentation, but it may exist. If it doesn't now, it will soon -- it's a really obvious feature to have.
Also, for what it's worth, the Flash local storage is global to your user profile, not local to the browser.... so asking Chrome to delete your browser history will mean Flash cookies are deleted in all other browsers.
-
Re:What use for a BD-ROM or BD-R drive?
Sorry, I was thinking of HD-DVD, which is the camp Microsoft was in. And for that, they added all the stuff I wrote about. Check out http://en.wikipedia.org/wiki/Windows_Vista
As for BD support, I found http://answers.microsoft.com/en-us/windows/forum/windows_7-pictures/windows-7-media-player-will-not-play-back-bluray/36f826cd-db66-45e7-bfad-1ad7f37f42af which seems to indicate Win7 doesn't support playing BD discs (except through 3rd party software). So maybe the super-parent should complain to 3rd party software developers?
And what would happen if you had ANY non-signed driver installed, is that HD playback would automatically be disabled. You either would get no output or SD output. And you would have to manually unplug devices and unload drivers until only signed ones were loaded, as well as having a secure path to your display for you to see HD output (so, you need HDCP over DVI to your 1920x1080 display as well). A lot of crap had to be balanced just right for you to be able to actually get HD audio and video to display.
-
Re:Good.
Well, you could read the legally binding community promise... Or the projects MS has released under OSS licences (MVC, DLR, etc). I'm guessing you've stripped out the FAT32 support, and Samba from your linux builds too then?
-
Re:Not many tearsI admit it has been a few years since I developed in Java, but I wouldn't mind reading what your specific concerns are about collections and concurrency in
.Net. Here is astarting point for concurrency and one for collections.I would also be interested in hearing what you think is missing from the
.Net ecosystem. -
Re:Not many tearsI admit it has been a few years since I developed in Java, but I wouldn't mind reading what your specific concerns are about collections and concurrency in
.Net. Here is astarting point for concurrency and one for collections.I would also be interested in hearing what you think is missing from the
.Net ecosystem. -
Re:Not many tears
I'm not sure what you mean about parallelism being better in C# - can you elaborate?
I suspect he means Parallel LINQ, which is, of course, not a language-specific feature.
there's no equivalent that I'm aware of to something like java.util.concurrent (see previous comment about parallelism)
I'm not saying that it's as rich, but System.Threading.Tasks and System.Collections.Concurrent namespaces provide similar high-level building blocks in
.NET 4.By the way, this is about more than just parallelism - asynchrony is also neatly expressed via tasks/futures, and C# 5 will add some nice syntactic sugar for that.
As a platform though,
.NET has a way to go before it's really mature IMHO.It largely depends on the field of application. You have to remember that
.NET was originally marketed primarily for line-of-business desktop and web apps; in that role, you don't need e.g. a fancy collection framework, but solid database access and a fast UI framework is a must - and so those were prioritized. Consequently, there are areas where .NET is relatively underdeveloped compared to Java, and then there are other areas where it's on par or ahead.structs can burn in hell
Don't diss structs, they're immensely useful for direct, efficient interop with native (read: C/C++) code. With some care, you can even map them to C++ classes, hand-crafting vtables, if your compiler documents their layout.
I do wish we didn't have to use them outside of that area, though. Unfortunately,
.NET JIT is not (yet) good enough to do escape analysis and optimize reference type allocations to occur on the stack rather than heap where possible, like HotSpot does. -
Re:Not many tears
I'm not sure what you mean about parallelism being better in C# - can you elaborate?
I suspect he means Parallel LINQ, which is, of course, not a language-specific feature.
there's no equivalent that I'm aware of to something like java.util.concurrent (see previous comment about parallelism)
I'm not saying that it's as rich, but System.Threading.Tasks and System.Collections.Concurrent namespaces provide similar high-level building blocks in
.NET 4.By the way, this is about more than just parallelism - asynchrony is also neatly expressed via tasks/futures, and C# 5 will add some nice syntactic sugar for that.
As a platform though,
.NET has a way to go before it's really mature IMHO.It largely depends on the field of application. You have to remember that
.NET was originally marketed primarily for line-of-business desktop and web apps; in that role, you don't need e.g. a fancy collection framework, but solid database access and a fast UI framework is a must - and so those were prioritized. Consequently, there are areas where .NET is relatively underdeveloped compared to Java, and then there are other areas where it's on par or ahead.structs can burn in hell
Don't diss structs, they're immensely useful for direct, efficient interop with native (read: C/C++) code. With some care, you can even map them to C++ classes, hand-crafting vtables, if your compiler documents their layout.
I do wish we didn't have to use them outside of that area, though. Unfortunately,
.NET JIT is not (yet) good enough to do escape analysis and optimize reference type allocations to occur on the stack rather than heap where possible, like HotSpot does. -
Re:Good.
1) Do your research:
http://www.microsoft.com/interop/principles/osspatentpledge.mspx
http://www.microsoft.com/about/legal/en/us/IntellectualProperty/IPLicensing/customercovenant/msnovellcollab/patent_agreement.aspx2) Stop plagarizing Richard Stallman's quotes without attribution:
-
Re:Good.
1) Do your research:
http://www.microsoft.com/interop/principles/osspatentpledge.mspx
http://www.microsoft.com/about/legal/en/us/IntellectualProperty/IPLicensing/customercovenant/msnovellcollab/patent_agreement.aspx2) Stop plagarizing Richard Stallman's quotes without attribution:
-
You can't
http://technet.microsoft.com/en-us/library/cc512587.aspx
>>You can't clean a compromised system by patching it.
>>You can't clean a compromised system by removing the back doors.
>>You can't clean a compromised system by using some "vulnerability remover."
>>You can't clean a compromised system by using a virus scanner.
>>You can't clean a compromised system by reinstalling the operating system over the existing installation.
>>You can't trust any data copied from a compromised system.
>>You can't trust the event logs on a compromised system.
>>You may not be able to trust your latest backup.
>>>>>The only way to clean a compromised system is to flatten and rebuild.
Jesper M. Johansson, Ph.D. [YES, HE'S A DOCTOR], CISSP, MCSE, MCP+I
Security Program Manager
Microsoft Corporation -
First Trout
It has come to my attention that the entire Linux community is a hotbed of so called 'alternative sexuality', which includes anything from hedonistic orgies to homosexuality to paedophilia.
What better way of demonstrating this than by looking at the hidden messages contained within the names of some of Linux's most outspoken advocates:
- Linus Torvalds is an anagram of slit anus or VD 'L,' clearly referring to himself by the first initial.
- Richard M. Stallman, spokespervert for the Gaysex's Not Unusual 'movement' is an anagram of mans cram thrill ad.
- Alan Cox is barely an anagram of anal cox which is just so filthy and unchristian it unnerves me.
I'm sure that Eric S. Raymond, composer of the satanic homosexual propaganda diatribe The Cathedral and the Bizarre, is probably an anagram of something queer, but we don't need to look that far as we know he's always shoving a gun up some poor little boy's rectum. Update: Eric S. Raymond is actually an anagram for secondary rim and cord in my arse. It just goes to show you that he is indeed queer.
Update the Second: It is also documented that Evil Sicko Gaymond is responsible for a nauseating piece of code called Fetchmail, which is obviously sinister sodomite slang for 'Felch Male' -- a disgusting practise. For those not in the know, 'felching' is the act performed by two perverts wherein one sucks their own post-coital ejaculate out of the other's rectum. In fact, it appears that the dirty Linux faggots set out to undermine the good Republican institution of e-mail, turning it into 'e-male.'
As far as Richard 'Master' Stallman goes, that filthy fudge-packer was actually quoted on leftist commie propaganda site Salon.com as saying the following: 'I've been resistant to the pressure to conform in any circumstance,' he says. 'It's about being able to question conventional wisdom,' he asserts. 'I believe in love, but not monogamy,' he says plainly.
And this isn't a made up troll bullshit either! He actually stated this tripe, which makes it obvious that he is trying to politely say that he's a flaming homo slut!
Speaking about 'flaming,' who better to point out as a filthy chutney ferret than Slashdot's very own self-confessed pederast Jon Katz. Although an obvious deviant anagram cannot be found from his name, he has already confessed, nay boasted of the homosexual perversion of corrupting the innocence of young children. To quote from the article linked:
'I've got a rare kidney disease,' I told her. 'I have to go to the bathroom a lot. You can come with me if you want, but it takes a while. Is that okay with you? Do you want a note from my doctor?'
Is this why you were touching your penis in the cinema, Jon? And letting the other boys touch it too?
We should also point out that Jon Katz refers to himself as 'Slashdot's resident Gasbag.' Is there any more doubt? For those fortunate few who aren't aware of the list of homosexual terminology found inside the Linux 'Sauce Code,' a 'Gasbag' is a pervert who gains sexual gratification from having a thin straw inserted into his urethra (or to use the common parlance, 'piss-pipe'), then his homosexual lover blows firmly down the straw to inflate his scrotum. This is, of course, when he's not busy violating the dignity and co
-
First Trout
It has come to my attention that the entire Linux community is a hotbed of so called 'alternative sexuality', which includes anything from hedonistic orgies to homosexuality to paedophilia.
What better way of demonstrating this than by looking at the hidden messages contained within the names of some of Linux's most outspoken advocates:
- Linus Torvalds is an anagram of slit anus or VD 'L,' clearly referring to himself by the first initial.
- Richard M. Stallman, spokespervert for the Gaysex's Not Unusual 'movement' is an anagram of mans cram thrill ad.
- Alan Cox is barely an anagram of anal cox which is just so filthy and unchristian it unnerves me.
I'm sure that Eric S. Raymond, composer of the satanic homosexual propaganda diatribe The Cathedral and the Bizarre, is probably an anagram of something queer, but we don't need to look that far as we know he's always shoving a gun up some poor little boy's rectum. Update: Eric S. Raymond is actually an anagram for secondary rim and cord in my arse. It just goes to show you that he is indeed queer.
Update the Second: It is also documented that Evil Sicko Gaymond is responsible for a nauseating piece of code called Fetchmail, which is obviously sinister sodomite slang for 'Felch Male' -- a disgusting practise. For those not in the know, 'felching' is the act performed by two perverts wherein one sucks their own post-coital ejaculate out of the other's rectum. In fact, it appears that the dirty Linux faggots set out to undermine the good Republican institution of e-mail, turning it into 'e-male.'
As far as Richard 'Master' Stallman goes, that filthy fudge-packer was actually quoted on leftist commie propaganda site Salon.com as saying the following: 'I've been resistant to the pressure to conform in any circumstance,' he says. 'It's about being able to question conventional wisdom,' he asserts. 'I believe in love, but not monogamy,' he says plainly.
And this isn't a made up troll bullshit either! He actually stated this tripe, which makes it obvious that he is trying to politely say that he's a flaming homo slut!
Speaking about 'flaming,' who better to point out as a filthy chutney ferret than Slashdot's very own self-confessed pederast Jon Katz. Although an obvious deviant anagram cannot be found from his name, he has already confessed, nay boasted of the homosexual perversion of corrupting the innocence of young children. To quote from the article linked:
'I've got a rare kidney disease,' I told her. 'I have to go to the bathroom a lot. You can come with me if you want, but it takes a while. Is that okay with you? Do you want a note from my doctor?'
Is this why you were touching your penis in the cinema, Jon? And letting the other boys touch it too?
We should also point out that Jon Katz refers to himself as 'Slashdot's resident Gasbag.' Is there any more doubt? For those fortunate few who aren't aware of the list of homosexual terminology found inside the Linux 'Sauce Code,' a 'Gasbag' is a pervert who gains sexual gratification from having a thin straw inserted into his urethra (or to use the common parlance, 'piss-pipe'), then his homosexual lover blows firmly down the straw to inflate his scrotum. This is, of course, when he's not busy violating the dignity and co