That's nonsense. You're saying that everyone should just sell anything they own the first time they receive an offer without doing any due diligence, or verifying that the offer is even fair? If I walked up and offered you $10 for a painting you owned because I knew (but you didn't) that it was actually worth millions, would that be fair? But according to your claim, I should be perfectly justified to be insulted that you would even want to find out how much the painting is actually worth before selling it!
This article is just dumb. You can make custom Linux images with custom software also. If you download a random Vista ISO and install it, you deserve what you get, just like you would if you download a random Linux ISO.
According to basic economic theory, no matter who the tax is levied on, the end result will be the same, depending on the elasticity of demand. If demand is highly elastic, then the manufacturer ends up bearing the burdern of the tax, and if demand is flat, then the consumer ends up bearing the burden, with a whole spectrum in between.
California labor code limits what rights an employer can claim in confidentiality and non-complete agreements. See below:
CALIFORNIA CODES LABOR CODE SECTION 2870-2872
2870. (a) Any provision in an employment agreement which provides that an employee shall assign, or offer to assign, any of his or her rights in an invention to his or her employer shall not apply to an invention that the employee developed entirely on his or her own time without using the employer's equipment, supplies, facilities, or trade secret information except for those inventions that either:
1. Relate at the time of conception or reduction to practice of the invention to the employer's business, or actual or demonstrably anticipated research or development of the employer; or
2. Result from any work performed by the employee for the employer.
(b) To the extent a provision in an employment agreement purports to require an employee to assign an invention otherwise excluded from being required to be assigned under subdivision (a), the provision is against the public policy of this state and is unenforceable.
2871. No employer shall require a provision made void and unenforceable by Section 2870 as a condition of employment or continued employment. Nothing in this article shall be construed to forbid or restrict the right of an employer to provide in contracts of employment for disclosure, provided that any such disclosures be received in confidence, of all of the employee's inventions made solely or jointly with others during the term of his or her employment, a review process by the employer to determine such issues as may arise, and for full title to certain patents and inventions to be in the United States, as required by contracts between the employer and the United States or any of its agencies.
2872. If an employment agreement entered into after January 1, 1980, contains a provision requiring the employee to assign or offer to assign any of his or her rights in any invention to his or her employer, the employer must also, at the time the agreement is made provide a written notification to the employee that the agreement does not apply to an invention which qualifies fully under the provisions of Section 2870. In any suit or action arising thereunder, the burden of proof shall be on the employee claiming the benefits of its provisions.
Since I'm the developer directly quoted in both articles (I guess I had the best sound bite), I should probably offer a clarification. Stating that a feature will be implemented if and only if there is a developer who wants to implement it is merely a statement of reality.
However, to claim that this means that I personally or other GNOME devs don't care about users is an exaggeration. Users requesting a feature quite often is a way to get a developer to want to implement the feature, especially since free software developers want their projects to be good and widely used.
All we were saying in that thread is we already know what features are widely requested. Adding voting merely creates an illusion that the votes will, in the end, count for something meaningful. In reality the best the votes could provide is a biased sample of oft-requestedness, which we can already discern by comments on bugzilla bugs and duplicates. We do care about users and we do care about their concerns.
Actually cars DO contain a bomb. It's called the gas tank. Extensive steps have been taken to try to prevent explosions of the fuel tank in a wide range of circumstances.
The point is that all technology can fail, sometimes disastrously, but we can develop other technologies to make that less likely.
Century theaters do not show TV ads before their movies. AMC is absolutely intolerable because of their advertising practices. I absolutely refuse to go to AMC theaters because of this. Century has all the same movies with a much better experience.
A friend of mine suggested a reverse-polish notation caclulator. It's a pretty good project since you'll have a chance to use a common data structure (stack) along with all the basic features of the language.
On my system running GNOME built from CVS HEAD, with a number of foreground processes running, including galeon, evolution, and a build process for gnome, I'm using only 181 MB of RAM.
... is that the author of the article fails to state how NDAs harm the chances of the technology startup. Basically the argument is that the company will probably fail anyway, so why bother? The simple fact of the matter is that the secrecy is not hurting the company, and there are a number of circumstances where the secrecy can help the company.
Gconf is self-documenting. Every gnome application includes a schema file which describes every gconf key, and its functionality in excruciating detail. Clicking on a key will give you all the details in gconf editor. But, if you don't like using gconf-editor, you can always just edit the user-readable XML configuration files generated by gconf-editor by hand.
But you're right in one respect: metacity used to be a not-very-good window manager. This is why I decided to take action rather than complaining and wrote some code. Metacity is far better than it was a year ago now that I've put some work into it (of course, I'm not the only one...)
Well, since you've never used metacity, you obviously don't have any idea what you're talking about. The window manager is supposed to be unobtrusive. The window manager really needs to just work without requiring you to configure everything. That's what metacity does.
Why don't you go and look at the window manager in windows or in Mac OS X -- two desktops renowned for good user interfaces -- and ask yourself how configurable they are. They answer is they aren't. At all. Metacity is much more configurable out of the box than either system.
And the always on top keybinding is a compromise for advanced users only. gconf keys with no user interface are commonly used in the gnome desktop for advanced options that aren't really needed. And if you don't think that gconf-editor is sufficiently intuitive, why don't you stop whining and write some fucking code.
As a metacity maintainer, I feel I have to respond to this.
First, HP (Havoc Pennington) isn't on an anti-feature craze. The point is to develop a desktop that works well for everyone without requiring you to go through dozens of preference dialogs to get something that will work correctly. KDE actually has a preference, off by default, to be not horribly broken on a xinerama setup.
But, aside from that, metacity does support an always on top keybinding (I commited this about a month ago) It's just not bound by default; you can edit it using gconf-editor though.
Also, there has been talk of changing the put on workspace menu. Perhaps if idiots like you could stop whining for two seconds on slashdot and perhaps join in a useful discussion on bugzilla, you can have a say in how that gets done eventually: http://bugzilla.gnome.org/show_bug.cg i?id=110904
Also, there is no new GTK file save dialog yet; this is a feature that won't appear until gnome 2.6, since gnome 2.4 is based on gtk 2.2. The dialog you may have seen is a ximian patch to GTK, and is certainly not the final incarnation of the GTK file save dialog.
The reason you can see flicker on monitors running at 60Hz is because the phosphors on modern displays decay very quickly -- they are designed to decay in time for a high-refresh display running at 85Hz or higher. Use slower phosphors, and 60Hz is flicker-free as well, but you get a bit of a "motion blur" if objects move across the screen very quickly.
The maximum that the eye can see is considerably higher, but it isn't a constant fps. It depends on what part of the eye is being used, the intensity and color of the light, the ambient light in the room, how dilated the pupil is, which specific receptors you inherited from your parents, and many other factors.
Attacking communications infrastructure is already a primary target for military operations. When preparing for an assault, the first thing you destroy are radar installations. The second thing you destroy are power plants and communications, and then you destroy transportation -- bridges and highways. All this is to make the enemy response difficult to coordinate.
I spent my summer internship at HP helping to prepare for HP's migration to Exchange from OpenMail -- rewriting a messenging backend to use SMTP and LDAP rather than depend on OpenMail and a proprietary directory service.
HP's been preparing for this move since last summer, and made the final switch to Exchange on November 1. Why continue work on a project that the companies internal IT doesn't even think enough of to use?
Actually, any NP problem can be reduced in polynomial time to any NP-complete problem. Solving any NP-complete problem in polynomial time proves that every problem in NP is in P.
Multiply encrypting text does not improve the security -- in fact it actually makes it easier to break. And these are all trivially breakable algorithms.
This is not quite true. The way Napster works, anything you download is automatically made available for upload. I'd bet the vast majority of the people on the list were just downloading the music, without any express plan to offer it for download to the masses. It's still illegal, but not nearly as offensive.
Slashdot Mirror
That's nonsense. You're saying that everyone should just sell anything they own the first time they receive an offer without doing any due diligence, or verifying that the offer is even fair? If I walked up and offered you $10 for a painting you owned because I knew (but you didn't) that it was actually worth millions, would that be fair? But according to your claim, I should be perfectly justified to be insulted that you would even want to find out how much the painting is actually worth before selling it!
This article is just dumb. You can make custom Linux images with custom software also. If you download a random Vista ISO and install it, you deserve what you get, just like you would if you download a random Linux ISO.
Torrents for Root of All Evil:
5 20.torrent/Richard_Dawkins_-_The_Root_of_all_Evil_ Episode_1_-_The_God_Delus.3462520.TPB.torrent8 14.torrent/Richard_Dawkins_-_The_Root_of_all_Evil_ Episode_2_-_The_Virus_of_.3462814.TPB.torrent
http://torrents.thepiratebay.org/hashtorrent/3462
http://torrents.thepiratebay.org/hashtorrent/3462
Actually, you have to take into account the chance that the claiming that 1/3 of studies are wrong is wrong, so it's not really a one in three chance.
According to basic economic theory, no matter who the tax is levied on, the end result will be the same, depending on the elasticity of demand. If demand is highly elastic, then the manufacturer ends up bearing the burdern of the tax, and if demand is flat, then the consumer ends up bearing the burden, with a whole spectrum in between.
California labor code limits what rights an employer can claim in confidentiality and non-complete agreements. See below:
CALIFORNIA CODES
LABOR CODE
SECTION 2870-2872
2870. (a) Any provision in an employment agreement which provides that an employee shall assign, or offer to assign, any of his or her rights in an invention to his or her employer shall not apply to an invention that the employee developed entirely on his or her own time without using the employer's equipment, supplies, facilities, or trade secret information except for those inventions that either:
1. Relate at the time of conception or reduction to practice of the invention to the employer's business, or actual or demonstrably anticipated research or development of the employer; or
2. Result from any work performed by the employee for the employer.
(b) To the extent a provision in an employment agreement purports to require an employee to assign an invention otherwise excluded from being required to be assigned under subdivision (a), the provision is against the public policy of this state and is unenforceable.
2871. No employer shall require a provision made void and unenforceable by Section 2870 as a condition of employment or continued employment. Nothing in this article shall be construed to forbid or restrict the right of an employer to provide in contracts of employment for disclosure, provided that any such disclosures be received in confidence, of all of the employee's inventions made solely or jointly with others during the term of his or her employment, a review process by the employer to determine such issues as may arise, and for full title to certain patents and inventions to be in the United States, as required by contracts between the employer and the United States or any of its agencies.
2872. If an employment agreement entered into after January 1, 1980, contains a provision requiring the employee to assign or offer to assign any of his or her rights in any invention to his or her employer, the employer must also, at the time the agreement is made provide a written notification to the employee that the agreement does not apply to an invention which qualifies fully under the provisions of Section 2870. In any suit or action arising thereunder, the burden of proof shall be on the employee claiming the benefits of its provisions.
They took my original quote verbatim but changed "received" from the correct spelling to an incorrect one!
Since I'm the developer directly quoted in both articles (I guess I had the best sound bite), I should probably offer a clarification. Stating that a feature will be implemented if and only if there is a developer who wants to implement it is merely a statement of reality.
However, to claim that this means that I personally or other GNOME devs don't care about users is an exaggeration. Users requesting a feature quite often is a way to get a developer to want to implement the feature, especially since free software developers want their projects to be good and widely used.
All we were saying in that thread is we already know what features are widely requested. Adding voting merely creates an illusion that the votes will, in the end, count for something meaningful. In reality the best the votes could provide is a biased sample of oft-requestedness, which we can already discern by comments on bugzilla bugs and duplicates. We do care about users and we do care about their concerns.
Actually cars DO contain a bomb. It's called the gas tank. Extensive steps have been taken to try to prevent explosions of the fuel tank in a wide range of circumstances.
The point is that all technology can fail, sometimes disastrously, but we can develop other technologies to make that less likely.
Century theaters do not show TV ads before their movies. AMC is absolutely intolerable because of their advertising practices. I absolutely refuse to go to AMC theaters because of this. Century has all the same movies with a much better experience.
A friend of mine suggested a reverse-polish notation caclulator. It's a pretty good project since you'll have a chance to use a common data structure (stack) along with all the basic features of the language.
I don't know how obvious it is to do:
if (((year % 4) == 0) && ((year % 400) == 0 || (year % 100) != 0))) return true;
Since that's the correct way to compute leap years.
On my system running GNOME built from CVS HEAD, with a number of foreground processes running, including galeon, evolution, and a build process for gnome, I'm using only 181 MB of RAM.
... is that the author of the article fails to state how NDAs harm the chances of the technology startup. Basically the argument is that the company will probably fail anyway, so why bother? The simple fact of the matter is that the secrecy is not hurting the company, and there are a number of circumstances where the secrecy can help the company.
Gconf is self-documenting. Every gnome application includes a schema file which describes every gconf key, and its functionality in excruciating detail. Clicking on a key will give you all the details in gconf editor. But, if you don't like using gconf-editor, you can always just edit the user-readable XML configuration files generated by gconf-editor by hand.
But you're right in one respect: metacity used to be a not-very-good window manager. This is why I decided to take action rather than complaining and wrote some code. Metacity is far better than it was a year ago now that I've put some work into it (of course, I'm not the only one...)
Well, since you've never used metacity, you obviously don't have any idea what you're talking about. The window manager is supposed to be unobtrusive. The window manager really needs to just work without requiring you to configure everything. That's what metacity does.
Why don't you go and look at the window manager in windows or in Mac OS X -- two desktops renowned for good user interfaces -- and ask yourself how configurable they are. They answer is they aren't. At all. Metacity is much more configurable out of the box than either system.
And the always on top keybinding is a compromise for advanced users only. gconf keys with no user interface are commonly used in the gnome desktop for advanced options that aren't really needed. And if you don't think that gconf-editor is sufficiently intuitive, why don't you stop whining and write some fucking code.
Man you people just piss me off.
As a metacity maintainer, I feel I have to respond to this.
g i?id=110904
First, HP (Havoc Pennington) isn't on an anti-feature craze. The point is to develop a desktop that works well for everyone without requiring you to go through dozens of preference dialogs to get something that will work correctly. KDE actually has a preference, off by default, to be not horribly broken on a xinerama setup.
But, aside from that, metacity does support an always on top keybinding (I commited this about a month ago) It's just not bound by default; you can edit it using gconf-editor though.
Also, there has been talk of changing the put on workspace menu. Perhaps if idiots like you could stop whining for two seconds on slashdot and perhaps join in a useful discussion on bugzilla, you can have a say in how that gets done eventually:
http://bugzilla.gnome.org/show_bug.c
Also, there is no new GTK file save dialog yet; this is a feature that won't appear until gnome 2.6, since gnome 2.4 is based on gtk 2.2. The dialog you may have seen is a ximian patch to GTK, and is certainly not the final incarnation of the GTK file save dialog.
The reason you can see flicker on monitors running at 60Hz is because the phosphors on modern displays decay very quickly -- they are designed to decay in time for a high-refresh display running at 85Hz or higher. Use slower phosphors, and 60Hz is flicker-free as well, but you get a bit of a "motion blur" if objects move across the screen very quickly.
The maximum that the eye can see is considerably higher, but it isn't a constant fps. It depends on what part of the eye is being used, the intensity and color of the light, the ambient light in the room, how dilated the pupil is, which specific receptors you inherited from your parents, and many other factors.
Attacking communications infrastructure is already a primary target for military operations. When preparing for an assault, the first thing you destroy are radar installations. The second thing you destroy are power plants and communications, and then you destroy transportation -- bridges and highways. All this is to make the enemy response difficult to coordinate.
Hello Wor
Segmentation Fault
I spent my summer internship at HP helping to prepare for HP's migration to Exchange from OpenMail -- rewriting a messenging backend to use SMTP and LDAP rather than depend on OpenMail and a proprietary directory service.
HP's been preparing for this move since last summer, and made the final switch to Exchange on November 1. Why continue work on a project that the companies internal IT doesn't even think enough of to use?
Actually, any NP problem can be reduced in polynomial time to any NP-complete problem. Solving any NP-complete problem in polynomial time proves that every problem in NP is in P.
That's true, but you can only log in as the root user from localhost -- it won't accept a remote login unless you change some configuration options.
Multiply encrypting text does not improve the security -- in fact it actually makes it easier to break. And these are all trivially breakable algorithms.
This is not quite true. The way Napster works, anything you download is automatically made available for upload. I'd bet the vast majority of the people on the list were just downloading the music, without any express plan to offer it for download to the masses. It's still illegal, but not nearly as offensive.