Up until 3.0 Ekiga did suck dick, I agree. And prior to Ekiga the previous GnomeMeeting worked fine. Ekiga has only been sucking between 2.0 up until 3.0. If you haven't tried it lately I recommend the later versions. Good news is that it's a thriving project with constant updates, just look at the changelogs for the 3.2.X series alone. Whatever it is it's completely free and while it has sucked dick at certain times at least it will never let its users to get it up the ass.
They have their own definition and standards of what constitutes "obviousness".
Wait wait wait, are you saying you don't? Are you saying you hold some sort of universal understanding of the word obvious? Of course it's a question of definition, but (un)fortunately their decision. Don't get me wrong though, I do agree with you that the patent system is fucking ridiculous and that patents, especially in the tech sector, seem to be given to anybody who writes it down on their wishlist for Santa.
You would want to release when it is ready, even if that is prior to the scheduled date.
Within most FOSS projects "ready" is a very relative term. Most of us have probably used a lot of good functioning software before it was ready. Take Firefox 3.5 BETA for example. It worked close to as good as 3.0 in terms of stability. The problem with your reasoning is that you treat the project as a whole, which is fine, but never forget that these packages often have independent devs whom don't really care about your cycle at all times. So even if application X will be ready in time, the devs for application X will instantly work on next version, unless you choose the less featured stable. Ubuntu solves this partially by releasing normal and LTS releases.
Wouldn't it be better just to release when things are "ready"?
Would you want to delay an entire OS due to the newest associated IM not being ready? In other words if you're hungry now, would you care for the larger part of the cookie now or would you rather stay hungry and wait for the whole cookie?
Second, limiting an OSS project to a time-based release cycle puts an artificial constraint on the development process. While it might be useful to encourage faster development in some cases, it is just as likely to force a new feature to be dropped at the last minute if it can't make it through the door in time.
At the same time a release can be delayed for the opposite reason and you end up delaying the entire project due to some packages.
The trick to avoiding your scenario and my scenario is by carefully picking the most appropriate intervals. Not too long between as this will drag out development leaving already stable and wanted features on hold for a longer time than necessary, and not too short leaving unstable features dropped or hurried out. The best way to do this would be to categorize your packages in different priorities, then gathering all the most important packages and calculating a suitable interval spectrum which is then used as the foundation for choosing the exact dates after having reviewed the less critical packages. Of course this won't please "everybody", but there is no solution for that. The only possibility is to please "as many as possible" in relation to their importance. To make it clear I'm personifying software packages when I refer to them as "everybody" and "as many as possible".
Exactly. The knife/murder example fits perfectly into the argument. Seriously, when is Apple going to fall over and die? Nothing good has ever come from this company and whatever good technology they made has been kept isolated and treated as the example above, benefiting nobody except Apple. We all know consumers are idiots, often siding with the party (company or brand) that they are purchasing. They don't understand the fundamental concept of trading where the byer (fucking) obviously is never supposed to side with the seller. Apple consumers on the other hand go one step further. I blame the sect like society which you seem to become a member of the second you make that Apple purchase. The brand becomes an obsession instead of an option, and it really is sickening. Still all you can do is rip off the suckers as much as possible, for they will never even care to understand what the fuck I'm talking about, due to the sect like Apple club of peers constantly padding on eachothers backs insisting on how great their iWhatthefuckever's are. You might think I'm overexaggerating but unfortunately, like many others which I'm sure of having observed the same behaviour, I have friends that feel this obsession. Incidently one of them also has OCD.
You mean you would expect them to wait 18 months and two weeks? That's absolutely ridiculous! The only reason to release now is that it's being exploited in the wild. Do you really think they would have fixed it on patch Tuesday if they hadn't done so in 18 months?
Nope, what's your point? I made it very clear. I'm only referring to the isolated action of patching something asap. I'm not defending nor attacking MSs methods. Please read the posts more thoroughly when you reply to them.
The finding could lend unique insights into how galaxies form stars in the early universe.
Yes we got that from all the other thousands of astronomy articles reporting new findings. This unifying goal of astronomers better be the question to 42.
It's not an issue exactly, but I can't off the top of my head recall a time that MS has released an out of schedule patch that wasn't to fix a problem already well known and being actively exploited.
Me neither, but it's still a good thing. Perhaps there should be Black Hat sessions every week?;-)
I have to agree. I don't see the reason why patching a security hole asap is an issue. Also to make it clear I'm only referring to this isolated action, nothing else.
The idiots don't understand that the largest portion covering this cost comes from those with high income. Those with high income controll all your corporates. Your insurance, medical, media, etc. The miserable people with low income are so stupid that they don't realise the simple fact that while everybody will chip in to make sure nobody gets untreated due to social status, in proportion the majority will still be paid by the wealthy. So they listen to CNN or Fox, run by the same people who are supposed to pay your healthcare with this bill. But please, by all means people, continue listening to them and when you die from treatable pneumonia make sure to say hi to Darwin from me.
Violence? That's a bit harsh. I'm not saying that there shouldn't be rules. I'm merely saying that I will follow those rules when everybody else does. I know what you're thinking, "if everybody thought that way then there would never be any progress." And of course you're right. The point is that if everybody thought that way then I guess everybody is OK with both scenarios, as long as everybody is on the same terms. Corporations systematically cheat the system, this is hardly any news. Why should I, or anyone for that matter, draw the shorter straw? The whole point of the rules are to make sure that nobody ends up drawing a shorter straw. Until that's fixed it's merely an illusion for the gullible.
Very interesting. Still I cannot say this shatters my love for Space Quest. It does however feel weird that you'd steal that concept. I mean it is funny, it's however not "oh my God why didn't I think of that!?"-funny. Thanks for the link thought.
I did. But only in order to keep the conversation related to the topic.
Up until 3.0 Ekiga did suck dick, I agree. And prior to Ekiga the previous GnomeMeeting worked fine. Ekiga has only been sucking between 2.0 up until 3.0. If you haven't tried it lately I recommend the later versions. Good news is that it's a thriving project with constant updates, just look at the changelogs for the 3.2.X series alone. Whatever it is it's completely free and while it has sucked dick at certain times at least it will never let its users to get it up the ass.
They have their own definition and standards of what constitutes "obviousness".
Wait wait wait, are you saying you don't? Are you saying you hold some sort of universal understanding of the word obvious? Of course it's a question of definition, but (un)fortunately their decision. Don't get me wrong though, I do agree with you that the patent system is fucking ridiculous and that patents, especially in the tech sector, seem to be given to anybody who writes it down on their wishlist for Santa.
Do not rely on this post for any reason.
You really are a lawyer!
;-)
Just kidding, thanks for the good information.
I had the same idea. A simple brute force approach should be able to outperform a human by atleast a factor of millions.
Or a much more preferred algorithm.
You would want to release when it is ready, even if that is prior to the scheduled date.
Within most FOSS projects "ready" is a very relative term. Most of us have probably used a lot of good functioning software before it was ready. Take Firefox 3.5 BETA for example. It worked close to as good as 3.0 in terms of stability. The problem with your reasoning is that you treat the project as a whole, which is fine, but never forget that these packages often have independent devs whom don't really care about your cycle at all times. So even if application X will be ready in time, the devs for application X will instantly work on next version, unless you choose the less featured stable. Ubuntu solves this partially by releasing normal and LTS releases.
Wouldn't it be better just to release when things are "ready"?
Would you want to delay an entire OS due to the newest associated IM not being ready? In other words if you're hungry now, would you care for the larger part of the cookie now or would you rather stay hungry and wait for the whole cookie?
Second, limiting an OSS project to a time-based release cycle puts an artificial constraint on the development process. While it might be useful to encourage faster development in some cases, it is just as likely to force a new feature to be dropped at the last minute if it can't make it through the door in time.
At the same time a release can be delayed for the opposite reason and you end up delaying the entire project due to some packages.
The trick to avoiding your scenario and my scenario is by carefully picking the most appropriate intervals. Not too long between as this will drag out development leaving already stable and wanted features on hold for a longer time than necessary, and not too short leaving unstable features dropped or hurried out. The best way to do this would be to categorize your packages in different priorities, then gathering all the most important packages and calculating a suitable interval spectrum which is then used as the foundation for choosing the exact dates after having reviewed the less critical packages. Of course this won't please "everybody", but there is no solution for that. The only possibility is to please "as many as possible" in relation to their importance. To make it clear I'm personifying software packages when I refer to them as "everybody" and "as many as possible".
Exactly. The knife/murder example fits perfectly into the argument. Seriously, when is Apple going to fall over and die? Nothing good has ever come from this company and whatever good technology they made has been kept isolated and treated as the example above, benefiting nobody except Apple. We all know consumers are idiots, often siding with the party (company or brand) that they are purchasing. They don't understand the fundamental concept of trading where the byer (fucking) obviously is never supposed to side with the seller. Apple consumers on the other hand go one step further. I blame the sect like society which you seem to become a member of the second you make that Apple purchase. The brand becomes an obsession instead of an option, and it really is sickening. Still all you can do is rip off the suckers as much as possible, for they will never even care to understand what the fuck I'm talking about, due to the sect like Apple club of peers constantly padding on eachothers backs insisting on how great their iWhatthefuckever's are. You might think I'm overexaggerating but unfortunately, like many others which I'm sure of having observed the same behaviour, I have friends that feel this obsession. Incidently one of them also has OCD.
Please read the posts more thoroughly when you reply to them.
Now that was embarassingly ironic. I apologise sincerely.
You mean you would expect them to wait 18 months and two weeks? That's absolutely ridiculous! The only reason to release now is that it's being exploited in the wild. Do you really think they would have fixed it on patch Tuesday if they hadn't done so in 18 months?
Nope, what's your point? I made it very clear. I'm only referring to the isolated action of patching something asap. I'm not defending nor attacking MSs methods. Please read the posts more thoroughly when you reply to them.
I don't know, I mean what would you expect Blizzard to say about this anyway?
Ching ching! More revenue for us!
That's what I'd expect Blizzard to say. I'm referring to the fact that therapists subscribe to their service in order to help the addicted.
The finding could lend unique insights into how galaxies form stars in the early universe.
Yes we got that from all the other thousands of astronomy articles reporting new findings. This unifying goal of astronomers better be the question to 42.
It's not an issue exactly, but I can't off the top of my head recall a time that MS has released an out of schedule patch that wasn't to fix a problem already well known and being actively exploited.
Me neither, but it's still a good thing. Perhaps there should be Black Hat sessions every week? ;-)
I have to agree. I don't see the reason why patching a security hole asap is an issue. Also to make it clear I'm only referring to this isolated action, nothing else.
The question is to what extent it is man-made and if it even is of significant magnitude.
Russia doesn't really import such energy but rather exports it. Russian natural gas alone heats big proportions of Europe.
The idiots don't understand that the largest portion covering this cost comes from those with high income. Those with high income controll all your corporates. Your insurance, medical, media, etc. The miserable people with low income are so stupid that they don't realise the simple fact that while everybody will chip in to make sure nobody gets untreated due to social status, in proportion the majority will still be paid by the wealthy. So they listen to CNN or Fox, run by the same people who are supposed to pay your healthcare with this bill. But please, by all means people, continue listening to them and when you die from treatable pneumonia make sure to say hi to Darwin from me.
Violence? That's a bit harsh. I'm not saying that there shouldn't be rules. I'm merely saying that I will follow those rules when everybody else does. I know what you're thinking, "if everybody thought that way then there would never be any progress." And of course you're right. The point is that if everybody thought that way then I guess everybody is OK with both scenarios, as long as everybody is on the same terms. Corporations systematically cheat the system, this is hardly any news. Why should I, or anyone for that matter, draw the shorter straw? The whole point of the rules are to make sure that nobody ends up drawing a shorter straw. Until that's fixed it's merely an illusion for the gullible.
You should get that lisp checked out.
For practical reasons (not owning any Windows machines) I'd have to ask. Does it run on Linux? ScummVM, or FreeDOS?
Very interesting. Still I cannot say this shatters my love for Space Quest. It does however feel weird that you'd steal that concept. I mean it is funny, it's however not "oh my God why didn't I think of that!?"-funny. Thanks for the link thought.
A humorous game series about a deep space janitor solving mysteries. There is no better plot.
The heating comes from inefficiency (transparency is never 100%) of the crystal, not from slowing down.
On the other hand 100% transparency would be completely useless as it wouldn't alter the wavelenght at all, right?
Do it yourself, it's open source.