Some reasonable points... now if your reply was
formatted, that would have been even better as I wouldn't have had to crawl through that horrible quoting;-)
Also, you're insane to put a system into production to "manage and control thousands of
servers" based on a platform that is still early
in its beta release cycle.
And I never stated, or implied, that Java invented the VM idea. However, it is probably the
best-known VM based development system in use at
this time. If you have a better example let me know.
.NET web services most certainly are RPC over
HTTPD using XML.
Sorry I didn't mention the multi-language facet. So you can create byte code
from multiple languages. The underlying VM concept
is still identical to Java (and there are compilers to translate from other languages to
Jave byte codes, but I digress). I code in C, C++, Java, Perl, and PHP and I use the one that is appropriate for the job. I don't see how giving all languages the weaknesses of a byte code based implementation accomplishes anything...
Those weeknesses make it unsuitable to build
large-scale high-performance applications. Period.
Ooops, I forgot, MS hasn't forced the need for
faster processors and more RAM for a while... and
Intel needs to sell the P4...
As for the class library, anyone who's used MFC knows how great MS is at designing and implementing class libraries. And if I recall the
CTS basically adds new types to all the languages
to achieve the compatibility you talk about... so
you're no longer writing Perl, you're writing.NET
perl that will not run outside of the.NET environment...
Note: I'm not knocking Java, most of my day job
code has been writing Java for the last 5 years...
I just think it's not what you want to build your
core applications/OS on =)
Yes, it's wonderful to see MS doing everything
possible to look good so they don't get slammed
when a remedy comes out of the anti-trust case.
Let's face it,.NET is not a very impressive
technology... RPC over HTTPD using XML running
what is basically Java (sorry, VM based platform-independent byte code is what Java IS)
is not a good foundation to build all of your
software on...
It allows some cool applications, but when people are giving examples (Corel's CEO) of using
it in a spreadsheet to perform calculations, it's
a bad idea...
But then they'd have to support a vast array of hardware. Hell, they don't even have full hardware support for the 7 Mac models it does support, much less being able to cover the thousands of possible PC configurations out there.
You know, I would be much more impressed and feel
he has a more valid point about ease of install/configuration IF OS X wasn't built to run on a closed hardware platform. Linux can be that easy to install and confgure as well... when you only have to support a handfull of machine configurations... and I do mean a handfull.. I count 7 supported machine types on Apple's website... and five of those are either laptops or iMacs, which means almost NO variation in hardware...
No, Microsoft got slapped for changing the core
Java APIs (java.awt packages specifically if I recall) which is not allowed if you're still calling it Java. This is an extension library that lets you use the QT/KDE APIs. Had Microsoft just
written an add-on lib that wrapped Win32 calls there would have never been a lawsuit.
Actually Sun sued Microsoft over them changing core APIs (in java.x packages) that made code built on their platform incompatible with other platforms. If Microsoft had written an extension (in other words a language binding to their libraries, which is what KDE did) there would have been no problems.
This basically just allows people that want to to write KDE apps in Java. There are no legal issues here.
Nope, but I'll give a brief explanation. Java
basically has 2 GUI toolkits, AWT and Swing. The
main difference is that every component in AWT
corresponds to a native system component while in
Swing the only system dependent components are very low-level, like a window. So in AWT if you
create a checkbox, it will ALWAYS look like whatever a checkbox looks like on the platform it's being run on because it actually calls a native component. Under Swing, checkboxes and such are rendered and controlled by
Java through Look And Feel classes. Metal is
an example of a Swing Look And Feel (there are a
bunch of them out there). So a Swing app will look
like whatever Look And Feel you tell it to use
(although some Look And Feels like Windows and Mac
will only run on those platforms because Sun doesn't want to risk a legal battle).
The KDE bindings don't use AWT or Swing. They
actually let you program using a Java variant of
the actual QT/KDE APIs. Another big difference is
that code written using these bindings can only be
run on platforms that have the QT/KDE libraries and a JVM, while AWT and Swing programs can be run wherever there is a JVM.
Hope that makes sense.
.technomancer
Re:Permanent compressed filesystem? WHY?!?!?!?!
on
Kernel 2.4.2 Released
·
· Score: 2
There are already file sysyems being
developed for embedded work (like cramfs), I was
assuming he was talking about something similar to
the compressed disk option in windows... basically my point was implementing this for a desktop system is a complete waste of time (or even for a laptop... my Vaio C1VN is about as small as they
come and it's got a 12 gig drive in it...)
Geeze, with 20 gig drives less than $100 what's
the point? Even when I was in college working
15 hours a week I could scrounge that much with
a little effort... and unless you're a major MP3
fiend, doing video editing, or mirroring large
ftp/web sites, 20 gigs is enough space for a Linux box (hell, I've got a network gateway box doing
email, http, ftp, and dns on a 1 gig drive
and it's fine)
GNU will only take in works if the author(s) assign the copyright for the work to the FSF. This doesn't matter to a lot of people, but some authors prefer to hold their own copyrights.
Actually, the main difference between the two
(from a features standpoint) is that Nautilus
includes SERVICES. Thus you can install and upgrade software from Eazel's library through
Nautilus, as well as online file storage.
I personally use KDE, but Eazel's services are
definitely a cool idea.
.NET has some interesting ideas... The general
mechanisms are similar to Java on some levels in
that everything is compiled down to byte code
(whatever Microsoft chooses to call it). The main
difference in the angle they take on this is that
they are specifically targeting a language-neutral
runtime, so you'll have perl.NET and python.NET
and VB.NET etc etc whereas (as far as Sun is concerned) the JVM is targeted at Java.
The other major difference is that everything in.NET is available as a distributed object by
default by SOAP. This is kind of cool and has some
interesting possibilities for building kick-ass
distributed applications.
However, IMHO the direction Microsoft wants to
go with this is horrible. Distributed pay-per-use
applications are just a bad idea. Basically if you
loose your network connection, you loose your apps
which just sucks.
So they have cool technology with a horrid targeted application of that technology.
As much as I hate to defend Helix errr Ximian they
didn't take anything... the founder of the Gnome
project is a cofounder of the company and most if
not all of the core Gnome developers work for Helix... in addition Helix is the official distributor or binary packages for Gnome...
On an unrelated note Ximian is a REALLY stupid
name while Helix Code was actually kind of cool...
Okay, I've seen a bunch of posts asking what this
is and what it would be used for, so here's my 2 cents:
The tech proposed (as I understand it) basically gives an ATA drive a key with which
it encrypts/decrypts data on writes/reads. Basically the end result is that if you burn a file (say an MP3) to a cd only the drive that burned it will have the keys to decrypt it. That's
my rough understanding... and this would apply to
HDs as well...
Now from what I deciphered from his answers the
revisions mean that 1) the encryption will only be
done for removable media and 2) it will be done by
software, not the drive controller
Basically if I interpreted the answers correctly, it means that those of us using Linux or other Open
Source OSs won't have to worry about it because our software won't be using the encryption so that CD of MP3s burned on a Linux box will be readable on any system... although disks created on OSs using the system will still not be readable by us...
And the decision has nothing to do with the fact
that they'd be in court in a heartbeat under the
terms of the DMCA if Capcom wanted to? While I do
think it was a responsible decision, I also think
that there was some enlightened self-interest at
work as well (even if the team denies it).
And to the team, congratulations, a great achievement.
This is the NASA Institute for Advanced Concepts... They're a research branch and are
supposed to do blue sky research. For short/near
term plans check NASA's other sites.
.technomancer
Re:Really? What would you have said in 1903?
on
Pushing The Envelope
·
· Score: 1
Or all the fiction about going to the moon (can you say Jules Verne?). If you had told somebody
at the turn of the century that man would be walking on the moon by 1969 they would have said
you were nuts.
Umm, how about a few mouse clicks and a password?
Click the updates icon conveniently located on your X desktop, enter the root password,
click OK (or hit enter), click Update List, click
Select All (or individually select the updates
you want/need), and click Do updates... The Update
tool in Mandrake 7.2 is really sweet...
DO NOT buy Java Servlet Programming from O'Reilly,
as the current version is terribly outdated. Certain concepts, such a servlet chaining, discussed in the book are no longer supported by
the current servlet APIs. A new edition is scheduled for release in March which covers the current APIs, so either wait for the new edition
or look elsewhere.
Amen. The pentium 4 is one of the worst CPUs released in a long time. The only people buying it
will be companies with pointy-haired bosses suffering from the "It's Intel and the numbers are bigger in the name and speed rating so it must be better than what we have now" syndrome. The only
way I'll go near a P4 is if someone gives me a
system containing one.
Slashdot Mirror
Also, you're insane to put a system into production to "manage and control thousands of servers" based on a platform that is still early in its beta release cycle.
And I never stated, or implied, that Java invented the VM idea. However, it is probably the best-known VM based development system in use at this time. If you have a better example let me know.
.technomancer
Sorry I didn't mention the multi-language facet. So you can create byte code from multiple languages. The underlying VM concept is still identical to Java (and there are compilers to translate from other languages to Jave byte codes, but I digress). I code in C, C++, Java, Perl, and PHP and I use the one that is appropriate for the job. I don't see how giving all languages the weaknesses of a byte code based implementation accomplishes anything... Those weeknesses make it unsuitable to build large-scale high-performance applications. Period.
Ooops, I forgot, MS hasn't forced the need for faster processors and more RAM for a while... and Intel needs to sell the P4...
As for the class library, anyone who's used MFC knows how great MS is at designing and implementing class libraries. And if I recall the CTS basically adds new types to all the languages to achieve the compatibility you talk about... so you're no longer writing Perl, you're writing .NET
perl that will not run outside of the .NET environment...
Note: I'm not knocking Java, most of my day job code has been writing Java for the last 5 years... I just think it's not what you want to build your core applications/OS on =)
.technomancer
Let's face it, .NET is not a very impressive
technology... RPC over HTTPD using XML running
what is basically Java (sorry, VM based platform-independent byte code is what Java IS)
is not a good foundation to build all of your
software on...
It allows some cool applications, but when people are giving examples (Corel's CEO) of using it in a spreadsheet to perform calculations, it's a bad idea...
.technomancer
.technomancer
OS X looks great, but spare me this guy's crap
.technomancer
I do agree with you that a Look and Feel that automatically pulls and uses your KDE theme would be nice, as would a set of Qt/KDE AWT peers.
.technomancer
.technomancer
This basically just allows people that want to to write KDE apps in Java. There are no legal issues here.
.technomancer
The KDE bindings don't use AWT or Swing. They actually let you program using a Java variant of the actual QT/KDE APIs. Another big difference is that code written using these bindings can only be run on platforms that have the QT/KDE libraries and a JVM, while AWT and Swing programs can be run wherever there is a JVM.
Hope that makes sense.
.technomancer
.technomancer
.technomancer
.technomancer
I personally use KDE, but Eazel's services are definitely a cool idea.
.technomancer
The other major difference is that everything in .NET is available as a distributed object by
default by SOAP. This is kind of cool and has some
interesting possibilities for building kick-ass
distributed applications.
However, IMHO the direction Microsoft wants to go with this is horrible. Distributed pay-per-use applications are just a bad idea. Basically if you loose your network connection, you loose your apps which just sucks.
So they have cool technology with a horrid targeted application of that technology.
Just my 2 cents.
.technomancer
Now where the hell are the SMP Athlon boards!!! =)
.technomancer
On an unrelated note Ximian is a REALLY stupid name while Helix Code was actually kind of cool...
.technomancer
The tech proposed (as I understand it) basically gives an ATA drive a key with which it encrypts/decrypts data on writes/reads. Basically the end result is that if you burn a file (say an MP3) to a cd only the drive that burned it will have the keys to decrypt it. That's my rough understanding... and this would apply to HDs as well...
Now from what I deciphered from his answers the revisions mean that 1) the encryption will only be done for removable media and 2) it will be done by software, not the drive controller
Basically if I interpreted the answers correctly, it means that those of us using Linux or other Open Source OSs won't have to worry about it because our software won't be using the encryption so that CD of MP3s burned on a Linux box will be readable on any system... although disks created on OSs using the system will still not be readable by us...
I think I deciphered that correctly =)
.technomancer
And to the team, congratulations, a great achievement.
.technomancer
.technomancer
.technomancer
.technomancer
.technomancer
.technomancer
I mean it's cool and all... but I really don't want a desktop that can kill me if it has a coolant leak? It'd be great for supercomputers tho' =)
.technomancer