“In this continuing series of Longhorn articles, I will talk about the APIs that developers will use to write the next generation of Windows applications. In this article I will focus on WinFX and discuss briefly the rest of the technologies. I will give you a high-level introduction to WinFX and what it means to developers.” Read the article by Wei-Meng Lee at WindowsDevCenter.
Understanding WinFX in Longhorn
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
This all sounds interesting, but in the shorter term I wonder which of these new APIs will be integrated into future versions of the general .NET Framework, the one that runs on existing Windows versions now.
(sorry, forgot my name)
Is it just me or is anyone else afraid of the new paradigms and protocols and frameworks and blibbydoodahs? I feel like since I only really like assembly, C, and C++ that there will be no place for me in the future. First Java, then .Net, and Linux guys with Mono, where is it all leading!? Will the next generation of OS’es start out with a framework similar to .Net or Java and force developers to use that? If that ever happens, you’ll see me doing embedded stuff. Just a paranoid college CS major kid
Maybe you’ll have to do your embedded programming in Java/.Net, you don’t really know, don’t bank on technology in even 10 years.
One has to be flexible in regard to technologie. Apple uses Objectiv-C to as an API interface to the application programers. So if .NET and Java are the Evolution then they are.
If you want to do low level programming, learn MSIL and you can program in assembly for .NET.
..write and call classic unmanaged C++/Assembly. Do you seriously think that codecs and sound mixers will be programmed in managed languages?
It’s astounding when a senior writer like Wei-Meng Lee thinks that “the [Win32] programmer has to explicitly take care of memory de-allocation, or else when the program exits it will result in memory leaks”: since he’s talking about after the program exits, he’s talking about operating system leaks.. nonsense.
I’m also a bit surprised no one else noticed that.
I don’t know. If you know C++ reasonably well, you can adapt to most languages used fairly quickly. Obviously not one that’s a totally different ideology like prolog or something.
I have a feeling development companies would rather have someone who has good software design experience. Once you’ve got that, you can pretty much to any project. Spend a few weeks ‘learning’ the features/lackof as compared to C++, and you’re good to go.
Is it journaled or will it still fragment all over the hard drive?
If you’re still in college with future shock imagine being in your 30’s or 50’s.
paraphrasing First C, then C++, where is it all leading!? 🙂
You have to move forward and maintain at least a proficiency with the newer mainstream technologies in your field. Otherwise, your Plan B is to sit around creating overblown disaster scenarios like Y2K or Y2026 to maintain relevance.
first of all, WinFX is the new Managed APIs that MS will be using for their OS to protect against memory leaks and buffer overflows, etc.
second of all, a journalized FS does not prevent Fragmenting.
Third of all, WinFS is not a file system but a system that stores index information and metadata for files in the file system which is NTFS and will probably be NTFS 6 in longhorn just to add necessary features to it for WinFS.
A journaled filing system does in fact prevent fragmentation. Second of all, sorry to offend you. Third off, I was under the impression that FS stood for FILING SYSTEM, like 99% of all other FS’s
I wonder which of these new APIs will be integrated into future versions of the general .NET Framework, the one that runs on existing Windows versions now.
None of them. The goal of these APIs is to expose the new funcionality that Microsoft is gonna include in Longhorn. So it’s probably not going to happen.
first off, I was simply bulleting the points I was making, I was not offended.
second off, Journalized file systems do not help prevent fragmentation.
http://en.wikipedia.org/wiki/Journaling_file_system
Thrid off, welcome to marketese.
I wonder how this will affect older applications and games ie starcraft which uses 32 bit networking proticals.