This build is incredibly old now. The interface of today doesn't even look remotely like it. I don't understand why PCWorld is previewing this now, especially a build intended for hardware developers. The majority of Longhorn's features weren't even merged in for this build.
It seems like a lot of people here are blaming patents for the slowing of innovation. To me that sounds rather silly. Patents have been around for a very long time. And it can certainly be argued that they encourage innovation through incentive, which is what they were ment for in the first place. Research and development is much more institutionalized now adays, beyond Universities. Corporations like IBM pump tons of money into R&D to create new inventions and the government conducts a lot of research also. If anything we should see more innovation today, but if we're not, here's like the likely reason why, IMO...
Pretty much all technological inventions of the past 150 or so years have revolved around the manipulation of electromagnetic fields. Quite simply, use of electricity is what was the behind all the inventions of the past. Now we're running out of things to do it with it. We're just tweaking existing designs, making them better and more reliable but it's going to take a major scientific discovery to spur the creation of new inventions once again. After all, how many times can you reinvent an electric motor?
The AJAX framework is built on ASP.NET 2.0 callbacks which Microsoft went out of their way to make sure works on non-IE browsers. In fact, all ASP.NET 2.0 controls generate XHTML 1.0 strict compliant code and work on all browsers identically. Even the advanced heavy-javascript controls it ships with. On top of that, everything gracefully scales back on older browsers or when javascript is disabled.
XmlHttpRequest started with IE but Netscape came out with their own version which most non-IE browsers also use. It WAS later added to the standard.
This is certainly much better than the Kyoto protocol where you spend trillions of dollars and achieve barely anything at all besides screwing over your industry. A project like this would quiet all the liberals whining about the environment and please the right-wingers by being a boost to industry and creating jobs. With a project like this you can have your cake and eat it too.
One of the main goals behind Longhorn is have equivalent system requirements to Windows XP with limited exceptions. Although, Longhorn will drive support for new types of hardware like hybrid hard drives, microphone arrays, ambient light sensors and auxilary displays in laptops, etc.
IE7 has full support for PNGs because it was a very popular request. Again, Microsoft won't support any of the new CSS (2.1 and 3.0) recommendations because they're not finalized. CSS 2.0 is, but its full of errata, thus CSS 2.1. If the W3C would get their act together you'd see more support in Internet Explorer.
You don't write extra code for handling piped output or writing to the console. I don't understand what you're on about. MSH will figure out how to format your command's output by running reflection on its properties.
The only advantage to objects is certainly not speed. Working with objects as opposed to text output has many advantages. It's much more elegant and intuitive. The command you pipe your output to doesn't even need to know what kind of object you're sending it. It can use.NET's reflection to discover what the Object's members are. The objects piped can expose methods which you can execute without using another command. The whole object-oriented concept in a shell opens up many possibilities.
Also, the only way that MSH can avoid making the developer do any extra steps is if it gives piped programs direct access to its classes which would be nuts.
I'm sorry but I have no idea what you're talking about. MSH has many unique features besides object piping. You can find out about them by reading the DOCUMENTATION.
Wow I think you totally missed every single one of my points.
So is Search, Instant Messaging, and Satellite Mapping. Yet MS is all over these areas (mapping is under dev.) Why? Because it's all about providing one complete, pervasive experience.
My point is Microsoft's entrance into the security software market is completely different from Internet browsers, search, instant messaging, and mapping.
I think you mean that security threats are something we want less of, and that's true. But security is something we want more of, and MS realizes that vast numbers of people are using 3rd party software products to get that security.
No, they're tired of their customers having to rely on 3rd parties to secure their software. Parties who would not be in business if their software made security non-issue.
A narrow view is that MS's primary business is Windows and Office. I think that a broader view is MS's primary business is acheiving dominant share and providing as much of the above-mentioned 'experience' as the DOJ will allow.
This isn't a narrow view, Windows and Information Worker (Office) are Microsoft's core businesses by a longshot. Most of Microsoft's other business units don't even make a profit at all. The MSN business unit just started to break even this year. They're all investments.
MS share is shrinking in some markets, notably browser use.
Haha, yeah right. IE still has nearly 90% share and they got a much improved version on the horizon. I'm sure they're scared shitless about that. If you throw a fairly good new browser into the mix, you can't expect the market share not to change.
Do you think they will ship/integrate/support their AV solution in Longhorn?
Their AV solution already ships every second Tuesday of the month. It's called the Windows Malware Remover, it runs silently when you perform a Windows Update. It's not a complete AV solution but it gets all the big worms and its updated each month.
Yes in the big scheme of things they would like to make back the millions spend to put together this security software. But in the short-time they're willing to spend a lot of money to fix this whole "security thing".
Internet browsing is a totally different issue. People want the market for internet browsers to stay alive and grow. Internet browsing is a good thing. But security is something that we want less of. Companies like Microsoft see security as something that needs to be fixed, not as a market for growth. Security issues hurt their core businesses like Windows and they want it to stop. So, they're willing to spend all this money making their own security products.
Consider the motives for security companies like Symantec. These guys rely on the market for security products for profit. Microsoft's primary business is not in virus scanners or anti-spyware products. They're more interested in quickly fixing security because it hurts profits from Windows.
I've been using my university's site-licensed version of Norton Antivirus. It's the corporate version which is actually called Symantec Antivirus. It's amazing how much better the enterprise versions of virus scanners are compared to the consumer versions. There's no flashy interfaces, but that's the point. They're quiet and don't hog resources. There's no subscription that runs out. If you can get your hands on a corporate version of a virus scanner, definetly go for it.
Obviously one of the reasons Microsoft is creating security software is that the existing 3rd party stuff sucks. Their anti-spyware software will be free even out of beta. There's no profit motive there.
When Microsoft turned on the automated bug reporting in XP the biggest reported cause of crashes was video drivers. But second to that was security software. Virus scanners and the like. Security software has a tendency to dig deep into the system and then crash. Virus scanners will install low-level file system filters to intercept activity, and then have a buffer overflow, bringing the whole system down with it.
Of course since this was found out. Microsoft has been holding security software conferences and getting vendors to fix their shit. And Longhorn tries to more actively fix the problem by sandboxing kernel file system filters amoung other things.
I was waiting for someone to do this. Piping to awk is a HACK. You're parsing text and assuming the memory consumption is always the 8th column. Which it isn't always. Not having to parse text is one of the reasons MSH is so great.
When you run get-process you're getting an array of Process objects. Each containing properties about the object. PID, image name, working set size, etc. The objects also have methods, so I can easily call the Kill() method on my list of objects.
Since this is.NET you get reflection of course. So I can pipe some arbitrary object to a command. And that command can learn what properties and methods are exposed by the object. And convert them to some different format like XML or something.
The entire.NET class library is exposed to MSH. And the class library almost entirely wraps all Win32's functionality. So yes, you can do anything. The design philosophy behind Longhorn is that any UI configuration must be exposed in the CLI. On and by the way, you get lossless JPEG rotation in Longhorn.
Slashdot Mirror
If you don't know what InfoPath is and have any shred of decency. Please do not comment on this article.
This build is incredibly old now. The interface of today doesn't even look remotely like it. I don't understand why PCWorld is previewing this now, especially a build intended for hardware developers. The majority of Longhorn's features weren't even merged in for this build.
It seems like a lot of people here are blaming patents for the slowing of innovation. To me that sounds rather silly. Patents have been around for a very long time. And it can certainly be argued that they encourage innovation through incentive, which is what they were ment for in the first place. Research and development is much more institutionalized now adays, beyond Universities. Corporations like IBM pump tons of money into R&D to create new inventions and the government conducts a lot of research also. If anything we should see more innovation today, but if we're not, here's like the likely reason why, IMO...
Pretty much all technological inventions of the past 150 or so years have revolved around the manipulation of electromagnetic fields. Quite simply, use of electricity is what was the behind all the inventions of the past. Now we're running out of things to do it with it. We're just tweaking existing designs, making them better and more reliable but it's going to take a major scientific discovery to spur the creation of new inventions once again. After all, how many times can you reinvent an electric motor?
The AJAX framework is built on ASP.NET 2.0 callbacks which Microsoft went out of their way to make sure works on non-IE browsers. In fact, all ASP.NET 2.0 controls generate XHTML 1.0 strict compliant code and work on all browsers identically. Even the advanced heavy-javascript controls it ships with. On top of that, everything gracefully scales back on older browsers or when javascript is disabled.
XmlHttpRequest started with IE but Netscape came out with their own version which most non-IE browsers also use. It WAS later added to the standard.
This is certainly much better than the Kyoto protocol where you spend trillions of dollars and achieve barely anything at all besides screwing over your industry. A project like this would quiet all the liberals whining about the environment and please the right-wingers by being a boost to industry and creating jobs. With a project like this you can have your cake and eat it too.
That's an old screenshot. It doesn't look anything like that anymore. That's all I can say.
Please see: http://www.w3.org/Style/css2-updates/REC-CSS2-1998 0512-errata.html
IE7 fixes rendering bugs in CSS styles. It also supports some additional features of CSS2.1. I won't talk about specifics.
Says you. Usability tests say otherwise.
One of the main goals behind Longhorn is have equivalent system requirements to Windows XP with limited exceptions. Although, Longhorn will drive support for new types of hardware like hybrid hard drives, microphone arrays, ambient light sensors and auxilary displays in laptops, etc.
You're seeing double. There's only one menubar.
They combined the toolbar to prevent the tab bar from taking up more vertical space.
As I've said a billion times, Microsoft program managers don't do anything without usability testing.
IE7 has full support for PNGs because it was a very popular request. Again, Microsoft won't support any of the new CSS (2.1 and 3.0) recommendations because they're not finalized. CSS 2.0 is, but its full of errata, thus CSS 2.1. If the W3C would get their act together you'd see more support in Internet Explorer.
The menubar is probably the least used element of the browser interface. It doesn't belong at the top.
Microsoft program managers never make interface changes without usability testing. Obviously, menubars at the bottom won out over menus at the top.
I guess you don't like Macs very much.
Microsoft announced today a plan to 'extend the RSS standard to better support the publishing of ordered lists of information...'
Microsoft didn't announce anything. This was leaked by some totally random guy on his blog.
You don't write extra code for handling piped output or writing to the console. I don't understand what you're on about. MSH will figure out how to format your command's output by running reflection on its properties.
.NET's reflection to discover what the Object's members are. The objects piped can expose methods which you can execute without using another command. The whole object-oriented concept in a shell opens up many possibilities.
The only advantage to objects is certainly not speed. Working with objects as opposed to text output has many advantages. It's much more elegant and intuitive. The command you pipe your output to doesn't even need to know what kind of object you're sending it. It can use
Also, the only way that MSH can avoid making the developer do any extra steps is if it gives piped programs direct access to its classes which would be nuts.
I'm sorry but I have no idea what you're talking about. MSH has many unique features besides object piping. You can find out about them by reading the DOCUMENTATION.
Wow I think you totally missed every single one of my points.
So is Search, Instant Messaging, and Satellite Mapping. Yet MS is all over these areas (mapping is under dev.) Why? Because it's all about providing one complete, pervasive experience.
My point is Microsoft's entrance into the security software market is completely different from Internet browsers, search, instant messaging, and mapping.
I think you mean that security threats are something we want less of, and that's true. But security is something we want more of, and MS realizes that vast numbers of people are using 3rd party software products to get that security.
No, they're tired of their customers having to rely on 3rd parties to secure their software. Parties who would not be in business if their software made security non-issue.
A narrow view is that MS's primary business is Windows and Office. I think that a broader view is MS's primary business is acheiving dominant share and providing as much of the above-mentioned 'experience' as the DOJ will allow.
This isn't a narrow view, Windows and Information Worker (Office) are Microsoft's core businesses by a longshot. Most of Microsoft's other business units don't even make a profit at all. The MSN business unit just started to break even this year. They're all investments.
MS share is shrinking in some markets, notably browser use.
Haha, yeah right. IE still has nearly 90% share and they got a much improved version on the horizon. I'm sure they're scared shitless about that. If you throw a fairly good new browser into the mix, you can't expect the market share not to change.
Do you think they will ship/integrate/support their AV solution in Longhorn?
Their AV solution already ships every second Tuesday of the month. It's called the Windows Malware Remover, it runs silently when you perform a Windows Update. It's not a complete AV solution but it gets all the big worms and its updated each month.
Yes in the big scheme of things they would like to make back the millions spend to put together this security software. But in the short-time they're willing to spend a lot of money to fix this whole "security thing".
Internet browsing is a totally different issue. People want the market for internet browsers to stay alive and grow. Internet browsing is a good thing. But security is something that we want less of. Companies like Microsoft see security as something that needs to be fixed, not as a market for growth. Security issues hurt their core businesses like Windows and they want it to stop. So, they're willing to spend all this money making their own security products.
Consider the motives for security companies like Symantec. These guys rely on the market for security products for profit. Microsoft's primary business is not in virus scanners or anti-spyware products. They're more interested in quickly fixing security because it hurts profits from Windows.
I've been using my university's site-licensed version of Norton Antivirus. It's the corporate version which is actually called Symantec Antivirus. It's amazing how much better the enterprise versions of virus scanners are compared to the consumer versions. There's no flashy interfaces, but that's the point. They're quiet and don't hog resources. There's no subscription that runs out. If you can get your hands on a corporate version of a virus scanner, definetly go for it.
Obviously one of the reasons Microsoft is creating security software is that the existing 3rd party stuff sucks. Their anti-spyware software will be free even out of beta. There's no profit motive there.
When Microsoft turned on the automated bug reporting in XP the biggest reported cause of crashes was video drivers. But second to that was security software. Virus scanners and the like. Security software has a tendency to dig deep into the system and then crash. Virus scanners will install low-level file system filters to intercept activity, and then have a buffer overflow, bringing the whole system down with it.
Of course since this was found out. Microsoft has been holding security software conferences and getting vendors to fix their shit. And Longhorn tries to more actively fix the problem by sandboxing kernel file system filters amoung other things.
I was waiting for someone to do this. Piping to awk is a HACK. You're parsing text and assuming the memory consumption is always the 8th column. Which it isn't always. Not having to parse text is one of the reasons MSH is so great.
When you run get-process you're getting an array of Process objects. Each containing properties about the object. PID, image name, working set size, etc. The objects also have methods, so I can easily call the Kill() method on my list of objects.
.NET you get reflection of course. So I can pipe some arbitrary object to a command. And that command can learn what properties and methods are exposed by the object. And convert them to some different format like XML or something.
Since this is
The entire .NET class library is exposed to MSH. And the class library almost entirely wraps all Win32's functionality. So yes, you can do anything. The design philosophy behind Longhorn is that any UI configuration must be exposed in the CLI. On and by the way, you get lossless JPEG rotation in Longhorn.
You never used the thing did you?