>Yes, but after the patent period expires, the source would be public domain. I.e. during the period of the patent use of the source is restricted (and would be even if the source was not in the patent). Afterwards, use of that source would be unrestricted.
Patent period != Copyright period (Thus: requirement for FOSS license)
This would work quite well if software patents would be restricted in time, to say 5 years or something.
Re:I code C# for a living
on
Java 1.5 vs C#
·
· Score: 2, Informative
C# vs Java, mostly a tie (c# good: ref and out parameters, indexers, foreach; c# bad: properties, operator overloading)
c# library vs Java library: c# is much cleaner in some aspects.
VS.net vs Eclipse: no contest, VS.net is much worse.
One thing that has been recently broken on UNIX is character encodings.
With the switch to UTF-8, all the classic text file processing tools stop being useful on binary files (like grep,...). The 'old way' was that there is no difference between binary and text files, with the UTF-8 transition this is no longer true.
This also affects Perl (and other popular 'scripting' languages), because the lack of separation between strings and byte arrays.
On some days this makes me strongly prefer iso-8859-1.
One thing needs to be done is a cleaner separation between 'server' code that needs to know nothing at all about locales and 'client'/ui code that needs to do the UI the way locale is configured.
You really need to consider 60 half-frames per seconds (PAL) instead of 30FPS for better picture quality. I suspect doing deinterlacing on the usb device and sensing full 60fps frames to host would eat too much bandwidth, but maybe not.
I'd take a 50% perf from open source drivers hit any day (I'm just not going to buy the hardware of the day, but the next lower generation). I'm using R200 based cards until there it something better with open source drivers.
> But GNOME still uses extensions. It's just that if someone sends you a file like BritneySpears.jpg.exe, with a Trojan in it, GNOME will notice that the magic of the file matches a binary executable, not a JPG, and it will not treat it as a JPG. This is a good thing.
What I'd expect is the jpeg handling program reporting the JPEG as invalid. Or, ask/warn the user to rename the file. Obviously treating it as executable is wrong.
>The user is still free to use extensions! Good grief. But, for example, if you double-click on README it will open in a text editor (unlike Windows where it always asks you what program to use, every time you try to open a file with no extension).
This is one thing that OS/2 did right. If the file had no associated program it was treated as the text file. For unix this is also the only correct behavior.
>As far as breaking the predictability, there will never be a problem unless the extension is wrong. If you rename a JPG file to "file.txt", yes you will be surprised when it opens in GIMP instead of a text editor. But I don't think that's a bad thing; opening in the text editor, as gibberish, is not as good as just having the right thing happen automatically.
using magic files is an even worse idea because it breaks the predictability of the system.
Just look at how everyone is complaining about IE (and some other browsers) autodetecting HTML even on some files clearly marked as something else (text/plain).
Not using file extensions on today's file system is a bad idea. They are the easiest way for most people to identify a type of file. An icon is much worse most of the time and a separate column with file type is often less visible (and in some views not at all).
Most clueful windows people enable file extensions immediately. They are very useful between separating safe-to-click files and unsafe-to-click files. They are also a hint to the user about what will happen when they click on the file.
And if the above is not enough. I haven't seen anyone proposing elimination of.c and.h extensions yet.
Slashdot Mirror
>Yes, but after the patent period expires, the source would be public domain. I.e. during the period of the patent use of the source is restricted (and would be even if the source was not in the patent). Afterwards, use of that source would be unrestricted.
Patent period != Copyright period (Thus: requirement for FOSS license)
This would work quite well if software patents would be restricted in time, to say 5 years or something.
C# vs Java, mostly a tie (c# good: ref and out parameters, indexers, foreach; c# bad: properties, operator overloading)
c# library vs Java library: c# is much cleaner in some aspects.
VS.net vs Eclipse: no contest, VS.net is much worse.
Maybe not if source is a .doc or the like.
One thing that has been recently broken on UNIX is character encodings.
...). The 'old way' was that there is no difference between binary and text files, with the UTF-8 transition this is no longer true.
With the switch to UTF-8, all the classic text file processing tools stop being useful on binary files (like grep,
This also affects Perl (and other popular 'scripting' languages), because the lack of separation between strings and byte arrays.
On some days this makes me strongly prefer iso-8859-1.
One thing needs to be done is a cleaner separation between 'server' code that needs to know nothing at all about locales and 'client'/ui code that needs to do the UI the way locale is configured.
Mod parent up!
.tar.gz too.
Installers for each program are a terrible idea.
I wish mozilla/firefox folk would provide a direct link to
>The RealPlayer installer, for instance, should be picked up by Norton's and quarantined before you can even install it.
And the next step from this is Outlook and then IE.
I have the first 2 EE's, if they release anything after the 3rd, I'm getting it off the net.
Not in Prescott it is not.
I wouldn't know about best editor. But is is certainly the best newsreader and also has the best CVS frontend (pcl-cvs).
(too bad really that the editor is not the best part of emacs)
I'm looking for a new watch...
Where can I find a 24h analog watch?
Need to know if it's day or night without looking out the window.
In my observation, even on a GF4-Ti4200, the game looks really good when in motion. The screenshots really don't do it justice.
You really need to consider 60 half-frames per seconds (PAL) instead of 30FPS for better picture quality. I suspect doing deinterlacing on the usb device and sensing full 60fps frames to host would eat too much bandwidth, but maybe not.
It will only have "Jar" because both Jars will be said at the same time.
I agree with no-tabs.
I also prefer new windows. Now, how to lobby for desktop-global bookmarks sidebar....
(there is one thing where tabs are great: browsing pr0n... something like tab slideshow might be nice)
For me, one thing that is unusably slow in xorg composite is window resizing or maximization. It needs to be much faster to be usable.
Other than that, seems to work ok.
(not running latest version yet)
At least for the movies: Star Trek should have ended 5 minutes into ST7, right after Kirk's death.
The start of ST7 is one of my favorite parts of the movies but after Kirk death it all goes downhill.
It requires a very fast printer to run glxgears.
I was going to ask that.
Some of us non Americans have elections this year too.
Doom 3 only requires ~16ms, Quake3 requires 8ms.
To me, anything with "rounded" stuff is not just ugly, but also less usable.
Like rounded window borders for example. I want to be able to nudge the mouse to the top right corner and click on "X".
If the window has a hole there, I can't do that.
I'd take a 50% perf from open source drivers hit any day (I'm just not going to buy the hardware of the day, but the next lower generation). I'm using R200 based cards until there it something better with open source drivers.
The older cards with open source drivers are great.
Q3A works fine and no problems with binary drivers.
Of course, the new stuff is "do not touch with a 10-foot pole".
If there were open source drivers for R9800 PRO I'd buy one immediately.
>
But GNOME still uses extensions. It's just that if someone sends you a file like BritneySpears.jpg.exe, with a Trojan in it, GNOME will notice that the magic of the file matches a binary executable, not a JPG, and it will not treat it as a JPG. This is a good thing.
What I'd expect is the jpeg handling program reporting the JPEG as invalid. Or, ask/warn the user to rename the file. Obviously treating it as executable is wrong.
>The user is still free to use extensions! Good grief. But, for example, if you double-click on README it will open in a text editor (unlike Windows where it always asks you what program to use, every time you try to open a file with no extension).
This is one thing that OS/2 did right. If the file had no associated program it was treated as the text file. For unix this is also the only correct behavior.
>As far as breaking the predictability, there will never be a problem unless the extension is wrong. If you rename a JPG file to "file.txt", yes you will be surprised when it opens in GIMP instead of a text editor. But I don't think that's a bad thing; opening in the text editor, as gibberish, is not as good as just having the right thing happen automatically.
This is exactly the behavior I don't want.
In the above I forgot (edited out by mistake):
using magic files is an even worse idea because it breaks the predictability of the system.
Just look at how everyone is complaining about IE (and some other browsers) autodetecting HTML even on some files clearly marked as something else (text/plain).
Not using file extensions on today's file system is a bad idea. They are the easiest way for most people to identify a type of file. An icon is much worse most of the time and a separate column with file type is often less visible (and in some views not at all).
.c and .h extensions yet.
Most clueful windows people enable file extensions immediately. They are very useful between separating safe-to-click files and unsafe-to-click files. They are also a hint to the user about what will happen when they click on the file.
And if the above is not enough. I haven't seen anyone proposing elimination of