Personally I liked Gnome 1.x a good deal better than I like the 2.x series.
Except for gnome-terminal. The newer versions of gnome-terminal are better.
I tend to agree -- gnome 1.x was much cooler in some ways. Gnome-terminal still sucks compared to rxvt or konsole sadly. One thing I was REALLY glad to see in 2.x was the pervasive unicode support from pango, and the decent anti-aliased font support. That stuff, at least, deserves some serious credit.
Oh, and thank god GNOME was easily installable when enlightenment never moved on, and KDE 3.x basically imploded in the name of 4.x "improvement".
If 14 years is optimal, than 7 years would be unreasonable.
I don't think unreasonable means what you think it means. The concept you were looking for is "suboptimal". In many cases, a suboptimal solution is a very reasonable one. In fact, this is the case much more often than the most optimal solution is a reasonable one.
But personally, I think (and have said before) that copyright in the internet age should be no more than about 3 years, and probably even less. Back when the it took 20 years for society to distribute, appreciate, and adopt a new composition into the collective pysche, it made a lot of sense for the copyright term to be 20 years. Now that we can distribute a new song around the world in a day, comment on it, assess it, collaboratively remix it, and distribute the improved version, it makes much less sense to hold creativity back for so long.
It's not really about the money right now, it's about finding something that works. Reprap and similar projects are mostly just trying to find materials that can be put down at high res, and will hold form even when "painting" curves etc. that have little support underneath. This would let people essentially build any object they can model in a 3d program. Otherwise, you're limited to fairly basic solid blocks and things you print, but then cut or work into smaller shapes.
Packt Publishing (and probably other publishing houses) already do this by asking reviewers on famous product-related sites to review in exchange for a free copy.
On BSD, perhaps. On Linux, learning that manpages aren't always current, trustworthy, or even related** to the specified topic is at least as important.
Considering that there's a saggitarius starstream colliding with the milky way right now, and that, if it went horribly wrong instead, I'd probably die, I'd give you pretty good insurance on that too.
My only worry is that... with 4.4 out, are we going to be subjected to KDE5.0 soon?
It would fit the pattern. 3.x only started becoming usable around 3.3/3.4, and when it was really good (around 3.6/3.7), 4.0 was committed (in the criminal sense, not the version control sense).
I read these warnings and knew not to take 4.0 seriously. Why didn't other people?
Because it was never about the number. When people release a.0, other developers want to release their new.0's of related software. For that, they need APIs to be in place, the groundwork to be laid, etc. None of that was done. So not only did you get a horrible release, undoing the good reputation gradually won with 3.x releases, but the whole community around the platform was fractured and unable to work. That was only aggravated by the KDE core developers being unwilling to listen to their community, taking down sites that had design documents, etc.
Why can't YOU walk over here, you prick? I knew this job wouldn't go well. Fucking asshats. ;)
I suspect it worked because the government considered it important enough to pay for.
My mixed metaphor sensor just took the head-staggers.
I tend to agree -- gnome 1.x was much cooler in some ways. Gnome-terminal still sucks compared to rxvt or konsole sadly. One thing I was REALLY glad to see in 2.x was the pervasive unicode support from pango, and the decent anti-aliased font support. That stuff, at least, deserves some serious credit.
Oh, and thank god GNOME was easily installable when enlightenment never moved on, and KDE 3.x basically imploded in the name of 4.x "improvement".
I don't think unreasonable means what you think it means. The concept you were looking for is "suboptimal". In many cases, a suboptimal solution is a very reasonable one. In fact, this is the case much more often than the most optimal solution is a reasonable one.
But personally, I think (and have said before) that copyright in the internet age should be no more than about 3 years, and probably even less. Back when the it took 20 years for society to distribute, appreciate, and adopt a new composition into the collective pysche, it made a lot of sense for the copyright term to be 20 years. Now that we can distribute a new song around the world in a day, comment on it, assess it, collaboratively remix it, and distribute the improved version, it makes much less sense to hold creativity back for so long.
Some sort of gypsy curse?
It's not really about the money right now, it's about finding something that works. Reprap and similar projects are mostly just trying to find materials that can be put down at high res, and will hold form even when "painting" curves etc. that have little support underneath. This would let people essentially build any object they can model in a 3d program. Otherwise, you're limited to fairly basic solid blocks and things you print, but then cut or work into smaller shapes.
Next you'll be coming up with some crazy, way-out theory that people get depressed by habitual negative thinking ;)
That's interesting, when I read "brain-computer interface", I was thinking more along the lines of a stake.
Actually, most desktop people who are just after ease of use end up using Excel :)
With a spear, or on horseback?
Packt Publishing (and probably other publishing houses) already do this by asking reviewers on famous product-related sites to review in exchange for a free copy.
That will happen automatically, due to time dilation, once we accelerate to lewdicrous speed.
On BSD, perhaps. On Linux, learning that manpages aren't always current, trustworthy, or even related** to the specified topic is at least as important.
I'm sure you must mean ironic#, unladen ironic, or ironic swallow.
You should check out this new thing called Windows ;)
Actually, your mom loves that game ;)
Considering that there's a saggitarius starstream colliding with the milky way right now, and that, if it went horribly wrong instead, I'd probably die, I'd give you pretty good insurance on that too.
Regular expressions are not appropriate on a galactic scale.
And if it's a wikipedia, digg, slashdot, or other popular server, then you need to multiply.
Careful now. He said an Intel SSD.
It would fit the pattern. 3.x only started becoming usable around 3.3/3.4, and when it was really good (around 3.6/3.7), 4.0 was committed (in the criminal sense, not the version control sense).
No, the API wasn't NEW. For Python developers, and probably others, it was NON-EXISTENT for a long time.
Because it was never about the number. When people release a .0, other developers want to release their new .0's of related software. For that, they need APIs to be in place, the groundwork to be laid, etc. None of that was done. So not only did you get a horrible release, undoing the good reputation gradually won with 3.x releases, but the whole community around the platform was fractured and unable to work. That was only aggravated by the KDE core developers being unwilling to listen to their community, taking down sites that had design documents, etc.