Rants Tagged with “Windows”
<< < 1 2 3 4 > >> (Total Pages: 4/Total Results: 31)
Longhorn finally has a real name: Windows Vista. Huh? Can't we just go back and call it Windows 2006? XP was wierd enough, but now the marketing people have invaded the campus' core. They announced the new name with the marketing tagline:
"Clear, Confident, Connected: Bringing clarity to your world."
Get used to it. We got used to XP, we'll get used to it. But I am going to try and call it Windows 2006 until someone slaps me down.
I concur with this blogger. I don't get what will be in Longhorn. I really like Avalon and Indigo presents a great platform for SOA, but they are pre-Longhorn. And anyone who reads this blog knows how I feel about WinFS...
Speaking of Cairo, I hope WinFS was dumped because they needed more time to get the API right (the last few builds were horribly difficult to understand) and not just because SQL Server dropped key features (row-level security and FileStream datatypes).
This week is expected to be the OS X (Tiger) vs. Longhorn week. With Steve Jobs taking the covers off the newest incarnation of OS X, he'll be trying to besmirch Longhorn at every turn. This newsweek article is probably only the first of many on the subject.
I am still impressed that the Microsoft spin machine hasn't been able to get WinFS out of the press's minds. They still beat up on them for dropping WinFS. I am hoping that Microsoft sees fit to include WinFS in a future version. My opinion is that they can't ship WinFS until SQL Server (the underlying DB engine that had powered WinFS) has row-level security. Building something akin to NT File Permissions over SQL Server is just too much overhead.
Even though I'd love to poke Microsoft about how Tiger will have something akin to WinFS, it doesn't really. Tiger's new feature is to allow metadata on files to help out search. This is not WinFS. While WinFS was to have supported additional metadata, it went a lot further than that. It was going to be an object-based file system with full support for relationships between objects in the file system. That's a lot bigger than just metadata support.
My only hope is that the continued bad press about lack of WinFS will push Microsoft to accellerate WinFS to earlier than the rumored 2010. I have heard whispers that the WinFS team is still working on the product, but when it will see the public eye is anybody's guess.
I finally have my Media Center PC set up and does it rock. It blows away Tivo and ReplayTV. It's much easier to use than either of those and has all the features i'd ever want. The TV Recording is great...the music menu is awesome...and the green button makes it all easy!
+1
I am perhaps most disgruntled about Apple's new metadata/search functionality which mirrors some of the importance of WinFS. As Joe Wilcox stated:
"Apple also is in a position to exploit Microsoft missteps. Tiger will feature metadata search capabilities as part of the file system. Microsoft touted such capabilities with WinFS, but that file system now won't ship with Longhorn, if ever." (emphasis added, ed.)
I hope MSN Desktop search isn't Microsoft's answer to real metadata in the Post-Longhorn timeframe.
I've been dealing with this nasty ASP.NET Configuration Error that only happens on my dev machine for several weeks now. Inexplicably, it will think that some random DLL that is part of my project is locked while it is trying to do the aspx compilation. I finally found the solution in the MS Support Database; the solution? Disable the Indexing Service (or exclude the ASP.NET temporary files section). Arg! The problem seems to be when my build copies a copy of a .dll to the temporary files section, it would start to be indexed by the Indexing Service and was locked so that the aspx compilation couldn't overwrite it.
For those who might think they have this problem, these are the symtoms (and click on the link for the solution):
- Random “Configuration Errors“ in your ASP.NET that say “Access Denied to XXX.dll“
HTH
I've had the WinHEC build of Longhorn for a while now and I have to say I am very pleasantly surprised. It seems that Longhorn is really coming along. I am very focused on WinFS programming, so I have not had too much time to dig into other interesting topics like Avalon (though Chris Sells loves the data binding) and Indigo.
The biggest change that has effected me is the lack of VS.NET. Because of very different development schedules, there is not a version of VS.NET that works with this release of Longhorn. At first I was a bit daunted...I have become so dependent on the tools. I haven't compiled from the command-line in quite a while. Luckily, MSBuild came to the rescue. After having been using NAnt, I was unsure what the big deal with MSBuild was and why it mattered. I am now a big fan. Instead of having to learn their XML syntax, I was delighted to find out that it will build based on a csproj file. This helped me out a lot, because I know how to write those files like the back of my hand (mostly from hacking csproj's to fix annoying problems like licx files remaining after you remove a reference).
Once I could build, I started digging into WinFS, I am suprised by the sheer scope of change in this version. I do expect it to calm down in later builds and I know it is *really* early. What has surprised me is the pace of development by the WinFS team. Whole interfaces have changed drasticly and concepts (chielfly relationships) seem to be redesigned completely. Truth be known, I am not sure it is for the better yet; much of the interfaces for navigating relationships seem much more heavy handed and complicated...but I have faith they'll get it right before it is all over.
Lastly, though I would never expect it from an early OS, the startup/shutdown time in this version is vastly improved from the PDC bits. Since I am dual booting to Longhorn, this really helps me switch back and forth quickly.
Rumor has it that MS is going to ditch Media Center Edition. This comes on the heels of giving up on Smart Displays. Wonder if MS is cleaning house to allow it to focus on Longhorn/Yukon/Whidbey/Orcas.
After attending most of the Keynote this morning at the PDC I am convinced that Microsoft is headed in the right direction, but it is still a long way off. 2005 or 2006 is too long to plan towards. On other note, Yukon and Whidbey will be here soon. Its about time to start planning for these technologies now.
I'll blog in more detail later tonight about what these technologies mean to you.
Looks like
Microsoft has given up the ghost on expecting users to patch their systems. Wonder whether that means automatic patching or something more interesting. The article mentions working with Firewall vendors more closely, but not sure how that will help.
