Domain: aeroxp.org
Stories and comments across the archive that link to aeroxp.org.
Comments · 7
-
Re:And we should attack the FSF...
http://www.downloadsquad.com/2009/08/26/free-software-foundation-throwing-a-hissy-fit-over-windows-7/
http://news.cnet.com/8301-13505_3-10318343-16.html
http://www.aeroxp.org/2009/08/fsf-violates-creative-commons/
http://news.softpedia.com/news/Windows-7-Sins-Bad-Vista-6-1-120095.shtml
Yeah, there actually has. -
Re:You can already do this ...
Well, the parent articles covered this, which leads me to my point:
Why couldn't this slashdot post point to the two people who actually came up with this? CWMike provided no original insight whatsoever.
Original sites referenced by CW's article:
http://www.aeroxp.org/2009/03/ie8-functionally-removable/
http://chris123nt.com/2009/03/03/win7-build-7048-ie8-is-removable/ -
Re:Import calendar?
Well, that might explain why the same clock doesn't exist in the subsequent Zunes, but who knows.
I'm more disturbed by one of the comments and the subsequent reply. -
What about W2K, Windows Update & corporations?
Let's see, there are still millions of people using W2K yet there's no Silverlight for it. I guess those people won't be allowed to access Microsoft.com... (Read the system requirements--Silverlight 1.1 will supposedly support W2K, but that's months away...)
What about Windows Update? Will there be a special "Windows Update for W2K" until Silverlight 1.1 appears?
Why is M$ only supporting PowerPC Macs with Silverlight 1.0 and not 1.1?
How will corporations take to having Silverlight installed on their W2K, XP, & Vista PCs--in all likelihood against their wills by way of an automatic update--despite having automatic updates disabled? (Microsoft recently did this...)
Could all of this be due to a lack of trust in Microsoft??? -
Re:Not interesting... Yeah right.
"When Microsoft writes an application for Linux, I've Won." - Linus Torvalds
Well, seems that Linus can declare himself a winner and retire.
Front Page Extensions for Linux
Triple DES encryption algorithm (source code)
SQL JDBC driver (runs on Linux) .NET (Unix-like compatible source code)Not to mention the technical help Microsoft has provided to Mono (.NET clone for Linux) and Firefox.
Congratulations.
-
features that didn't make the keynoteFirst off, Jobs publically stated that there is a bunch of stuff that's still under wraps. This may very well be because it's not done, or because it's of no significance to developers, and doesn't need to be announced in advance. Imagine all the bad press Microsoft could have avoided by never announcing WinFS until they were *positive* that it would be done in time for Longhorn?
With that out of the way, a bunch of other "less exciting" features were announced, albeit not in the keynote.
A few highlights:- Leopard will be resolution-independent -- This is a HUGE feature that the world has needed for the past 10 or so years. We can finially move twoard HD displays without having to squint our eyes because the text on a 4000x3000 monitor would be microscopic.
- Carbon apps can now embed Cocoa components. Might breathe some more life into the old legacy apps, as well as making Photoshop and Office a little more tolerable, and a little more mac-like.
- Apache 2.0, Ruby on Rails and Subversion are included in the end-user version as well as the server, which I think speaks for itself. How cool is that?
- Complete support for 64-bit applications across the OS. Last time I used it, there were some (very noticiable) lingering 32-bit remnants in XP-64 that made it virtually unusable.
- All sorts of new APIs that should allow every application take advantage of the cool new features announced in the keynote, as well as extensions to some older APIs (iCal specifically) -- anyone who's used the
.Mac Backup application can attest to the wide range of software that builds in support for it.
-
Re:Microsoft is never silent before the storm.
They called it Longhorn back in 2000, then renamed it as vista.
When they decide for a code name doesn't matter.
What the target date is set to is what matters if we're still talking six year delays.
A delay is impossible without a target date to miss, or at least a change of plans.
Are you really saying Longhorn/Vista was supposed to be released in 2000 but delayed to 2006?
In that case, you have quite some burden of proof here. ;-)
The *first* internal Longhorn alpha build I've heard of was build 3646, built on 2002-06-12. That build was nowhere near complete, and even later builds that were made a bit more public showed up basically like touch-up work to the kernel it was built on.