Just a quick question. Why does copying a feature from another OS become a "ripoff" when said feature makes sense to incorporate into one of the Linux desktops? Why do the Linux desktops need to re-implement a solved GUI problem in a new, unique, and possibly unusable way?
If that blog posting by a KDE developer is a "rally to GNOME's cause" then I would hate to see outright criticism from said developer. That specific blog post should be more accurately thought of as damning with faint praise because the writer belittles GNOME and holds KDE as the epitome of the Linux Desktop. It's time to move away from such childishness (rants, flamewars) and start working on the respective pieces of software that people use. What is there to be gained from putting one another down?
Here are a few choice sentences from the link:
"Being the underdog puts a lot of presure on you, especially if you have fewer developers and therefore fewer resources. You just don't stand a chance catching up by following the leader, this has forced GNOME to go a different route than KDE."
"Sure I hate everything that GNOME does different from KDE; because KDE is doing things the Unix/Linux way of empowering the user and taking pragmatic decisions, but GNOME has taken chances that KDE could not take: They have risked alienated parts of their users in order to make a distinct interface, that may or may not attract users that might not otherwise use Linux."
"The only really bad thing about GNOME is that a few of their developers (hello, monkey-boys!) have never let go of the "There can be only one"-attitude, and continue to attack and attempt to eliminate KDE, however futile that may be."
The hangup for me with most, if not all, of the blogging software is that they have little to no support for alternate databases besides MySQL. As a consultant, I have deployed PostgreSQL in all aspects of my business from bookkeeping and web hosting to home-grown applications. As a result, it's difficult to pick either WordPress, TextPattern, or other blogging software because they rely solely on MySQL as a backend. I don't relish the thought of having to administer several different databases for different purposes...
I've gone with MovableType for the moment as it provides me with what I need now. If in the future WordPress (or any other solution) has solid database support for PostgreSQL I will be more than willing to switch to it.
NOTE: I know that some individuals have ported WordPress to PostgreSQL albeit with some stability issues and without help from the core developers.
Everytime somebody likes to say that about Debian, I like to remind them the NetBSD folks support an... impressive array of platforms, and at the same time hack userland, kernel and protocols. While Debian developers mostly package upstream stuff.
I would have to say that Debian developers, for the most part, are also involved in the userland, kernel, and protocols. Take a look at developers such as Colin Watson, Joey Hess, Branden Robinson, Ben Collins, and others are doing in and around the Free Software community. Debian developers should not be pigeonholed as being upstream packagers just because that's what the public sees as the end product.
P.S. Do a web search on those developers to see their current and past involvements.
If you want to install Debian on an SGI Indy, then you will need to create or buy a serial cable that connects from your PC (25 Pin DB25 Plug) to the SGI Indy (8 Pin Mini DIN).
The terminal should be connected to the Indy's first serial port and configured as 9600 8N1 with hardware flow control off. Use minicom to see the boot up messages.
There are a few sites committed to providing detailed and accurate representation of the Aramaic version of the Bible (often called the Peshitta). Peshitta.org is the most important since it provides not only an interlinear version of the New Testament (English and Aramaic) but also a forum that discusses the nuances of each and every chapter or verse and lessons in modern Aramaic (Syriac).
Beth Mardutho: The Syriac Institute is also working on collecting, indexing, and digitizing Aramaic (Syriac) manuscripts, books, and other invaluables from University libraries, personal libraries, monasteries, churches, and persons throughout the world.
Slashdot Mirror
Does it make you feel better to put someone else down? Moreso their religion when their loved one can die at any time?
You and those like you that have posted in this replies should be ashamed of themselves.
Pathetic.
Just a quick question. Why does copying a feature from another OS become a "ripoff" when said feature makes sense to incorporate into one of the Linux desktops? Why do the Linux desktops need to re-implement a solved GUI problem in a new, unique, and possibly unusable way?
If that blog posting by a KDE developer is a "rally to GNOME's cause" then I would hate to see outright criticism from said developer. That specific blog post should be more accurately thought of as damning with faint praise because the writer belittles GNOME and holds KDE as the epitome of the Linux Desktop. It's time to move away from such childishness (rants, flamewars) and start working on the respective pieces of software that people use. What is there to be gained from putting one another down?
Here are a few choice sentences from the link:
"Being the underdog puts a lot of presure on you, especially if you have fewer developers and therefore fewer resources. You just don't stand a chance catching up by following the leader, this has forced GNOME to go a different route than KDE."
"Sure I hate everything that GNOME does different from KDE; because KDE is doing things the Unix/Linux way of empowering the user and taking pragmatic decisions, but GNOME has taken chances that KDE could not take: They have risked alienated parts of their users in order to make a distinct interface, that may or may not attract users that might not otherwise use Linux."
"The only really bad thing about GNOME is that a few of their developers (hello, monkey-boys!) have never let go of the "There can be only one"-attitude, and continue to attack and attempt to eliminate KDE, however futile that may be."
The hangup for me with most, if not all, of the blogging software is that they have little to no support for alternate databases besides MySQL. As a consultant, I have deployed PostgreSQL in all aspects of my business from bookkeeping and web hosting to home-grown applications. As a result, it's difficult to pick either WordPress, TextPattern, or other blogging software because they rely solely on MySQL as a backend. I don't relish the thought of having to administer several different databases for different purposes ...
I've gone with MovableType for the moment as it provides me with what I need now. If in the future WordPress (or any other solution) has solid database support for PostgreSQL I will be more than willing to switch to it.
NOTE: I know that some individuals have ported WordPress to PostgreSQL albeit with some stability issues and without help from the core developers.
Everytime somebody likes to say that about Debian, I like to remind them the NetBSD folks support an ... impressive array of platforms, and at the same time hack userland, kernel and protocols. While Debian developers mostly package upstream stuff.
I would have to say that Debian developers, for the most part, are also involved in the userland, kernel, and protocols. Take a look at developers such as Colin Watson, Joey Hess, Branden Robinson, Ben Collins, and others are doing in and around the Free Software community. Debian developers should not be pigeonholed as being upstream packagers just because that's what the public sees as the end product.
P.S. Do a web search on those developers to see their current and past involvements.
If you want to install Debian on an SGI Indy, then you will need to create or buy a serial cable that connects from your PC (25 Pin DB25 Plug) to the SGI Indy (8 Pin Mini DIN).
The terminal should be connected to the Indy's first serial port and configured as 9600 8N1 with hardware flow control off. Use minicom to see the boot up messages.
This is the minimum you need to do btw. You can follow the entire procedure at http://www.zorg.org/linux/indy.shtml
There are a few sites committed to providing detailed and accurate representation of the Aramaic version of the Bible (often called the Peshitta). Peshitta.org is the most important since it provides not only an interlinear version of the New Testament (English and Aramaic) but also a forum that discusses the nuances of each and every chapter or verse and lessons in modern Aramaic (Syriac).
Beth Mardutho: The Syriac Institute is also working on collecting, indexing, and digitizing Aramaic (Syriac) manuscripts, books, and other invaluables from University libraries, personal libraries, monasteries, churches, and persons throughout the world.
All of the collected materials will be digitized according to the DjVu format as found at DjVulibre. You can take a look at some high quality samples of such digitized books, namely Liturgy of the Eastern Churches (Syriac) or The Syriac Orthodox Liturgy (English).