There is an article about "The Anatomy of a Trivial Patent" written by RMS. It may be a nice introduction to the topic if you want to read more complex patent texts.
... if a 16 year old kid has to go to prison for 180 days! In Germany the kid would have been judged to perform about 180 working _hours_ to amend his guilt.
I liked the old design better, but I guess it's just a question of time till I get used to it. And the new website doesn't use tables for the layout. Would like to see such modernization at slashdot, too.
BTW: I think the good documentation for PostgreSQL is reason enough to use it. This is a big plus for me. In contrary I don't like the MySQL documentation at all.
Portability between various UNIX variants is an important issue -- most "popular" server software runs on every UNIX anyhow (I don't mean to play this down, it's a great achievement). But I think the real difference are the special features of these Unices which are not standardized anyhow (think of things like FreeBSD Jails, Sun N1 Grid containers etc.).
I would be really happy if a big company as Google would establish a standardized IM. By "standardized" I mean that they should use an open and well documented protocol, such as XMPP (aka "Jabber", see RFC 3920-3923).
Once I wanted to try out AOL, just to use the "50 hours of free internet". Well, besides that it didn't work for some reason (can't recall exactly what it was), I made a bad mistake: I used some fake name, address etc. to activate the account. Problems began when I had to explain to a women on the hotline that there is a city called "Phobos Lab" in Germany (that was the name of the city I supplied, which really is the name of a Doom level).
I think the parent posters point was another one: PHP is a programming language for "web-things". MySQL is a relational database. These are two separate things. Even if you know how to access a database from a programming language, you do not necessarily know how to design a database. With a badly designed DB and a relatively small amount of data, the advantage of using a DB might mostly be vanished.
Strange. The chapter about installing the software is the one I always skip. With todays ["user friendly"] installing routines [for popular software] these advices seem to be obsolete for me. Additionaly, if you are installing from the sources, you probably have to read some up-to-date instructions anyhow. So I don't see any reason to print OS-specific, release-dependent details in a book about a software product [for developers].
One of the weaknesses is simply everything is subject to interptation.
[...] If you are using one of the "for profit" models, its easier to prioritorize bugs: you target the ones that are the most expensive first.
What are "expensive" bugs? This too, depends on interpretation. If you are a software company which develops firewall solutions, security flaws are most likely the "expensive" bugs. If - in contrast - you develop so-called "end-user" software, the most expensive "bug" may be a new icon theme for your app or a nifty new button for <insert any useless feature here>.
"I think it pretty much exemplifies how hard Linux gaming is [...]"
You should have tried out one of the titles released by Loki. I bought several games from them. Not that it was a criteria for me, but with the Loki installer it's pretty "easy" and straight forward to install a game. After the installation, you will find an entry in your GNOME/KDE program menu. What else would one want?
You are asking for a full featured IRC client. Why not use software that is developed for that specific purpose? If you are that much of an IRC guy, you should check out BitlBee and use instant messaging in your (favourite) IRC client, not the other way around.
Slashdot Mirror
Just FYI: these problems are mostly solved. An official(!) Debian package is underway.
There is an article about "The Anatomy of a Trivial Patent" written by RMS. It may be a nice introduction to the topic if you want to read more complex patent texts.
I didn't feel like being insulted. In fact I was surprised to read a reply written in such a polite language. After all, this is slashdot!
(-1 Offtopic)
Ooops... I guess the reason for my misunderstanding is that here in my timezone (CET) it's early in the morning and I've slept 2 hours at most... :-)
... if a 16 year old kid has to go to prison for 180 days! In Germany the kid would have been judged to perform about 180 working _hours_ to amend his guilt.
Please have a look at the bug. Several fixes exist but haven't been incorporated into the CVS branch.
feature for 2.0:
reconfigurable key bindings
I still would like to see bug #67127 "Newline in tooltips (title attribute) converted to black bars" fixed... this bug dates back almost 4 years now!
I read another roadmap about two weeks ago. IIRC some (small) changes in the extension interface were planned for 1.1, but that's all I can remember.
Hehe, this somehow reminds me on this cartoon...
1) Implement a darn menu bar and clean up the menus. The right-click system sucks.
This one is already done.
4) Rename the program. GIMP does not convey an image of a good, reliable program
I don't see any advantages in renaming the program.
I liked the old design better, but I guess it's just a question of time till I get used to it. And the new website doesn't use tables for the layout. Would like to see such modernization at slashdot, too.
BTW: I think the good documentation for PostgreSQL is reason enough to use it. This is a big plus for me. In contrary I don't like the MySQL documentation at all.
They told that GNOME 2.6 would not get it into sarge. The release date for sarge was pushed further. And GNOME 2.6 made it into sarge.
They told that GNOME 2.8 would not get it into sarge. The release date for sarge was pushed further. And GNOME 2.8 made it into sarge.
They told that KDE 3.4 would not get it into sarge...
Portability between various UNIX variants is an important issue -- most "popular" server software runs on every UNIX anyhow (I don't mean to play this down, it's a great achievement). But I think the real difference are the special features of these Unices which are not standardized anyhow (think of things like FreeBSD Jails, Sun N1 Grid containers etc.).
There's not much money in defining a proprietary protocol and letting people produce an ad-free version of what you offer either...
I would be really happy if a big company as Google would establish a standardized IM. By "standardized" I mean that they should use an open and well documented protocol, such as XMPP (aka "Jabber", see RFC 3920-3923).
LCD Display = Liquid Crystal Display Display
Once I wanted to try out AOL, just to use the "50 hours of free internet". Well, besides that it didn't work for some reason (can't recall exactly what it was), I made a bad mistake: I used some fake name, address etc. to activate the account.
Problems began when I had to explain to a women on the hotline that there is a city called "Phobos Lab" in Germany (that was the name of the city I supplied, which really is the name of a Doom level).
I think the parent posters point was another one:
PHP is a programming language for "web-things". MySQL is a relational database. These are two separate things. Even if you know how to access a database from a programming language, you do not necessarily know how to design a database. With a badly designed DB and a relatively small amount of data, the advantage of using a DB might mostly be vanished.
Strange. The chapter about installing the software is the one I always skip. With todays ["user friendly"] installing routines [for popular software] these advices seem to be obsolete for me. Additionaly, if you are installing from the sources, you probably have to read some up-to-date instructions anyhow. So I don't see any reason to print OS-specific, release-dependent details in a book about a software product [for developers].
[...]
If you are using one of the "for profit" models, its easier to prioritorize bugs: you target the ones that are the most expensive first.
What are "expensive" bugs? This too, depends on interpretation. If you are a software company which develops firewall solutions, security flaws are most likely the "expensive" bugs. If - in contrast - you develop so-called "end-user" software, the most expensive "bug" may be a new icon theme for your app or a nifty new button for <insert any useless feature here>.
"I think it pretty much exemplifies how hard Linux gaming is [...]"
You should have tried out one of the titles released by Loki. I bought several games from them. Not that it was a criteria for me, but with the Loki installer it's pretty "easy" and straight forward to install a game. After the installation, you will find an entry in your GNOME/KDE program menu. What else would one want?
"frequently see" could mean that they will see succes rates like that if they are using SpamAssassin... :-)
You mean you missed 22,786 mails...
You are asking for a full featured IRC client. Why not use software that is developed for that specific purpose? If you are that much of an IRC guy, you should check out BitlBee and use instant messaging in your (favourite) IRC client, not the other way around.