Re: Concurrent reply alert
by castaway (Parson) on Aug 19, 2004 at 09:08 UTC
|
Some points on this just expounded (by me) in the CB:
1) Not everything everyone else has is good for us (cos we aren't them).
2) We like to see everyones opinion on things, so multiple posts with the same answer and in a short time frame arent a bad thing at all.
3) Technical problems also, this mysql on bsd we're running is really bad at concurrency, also because its running on two separate web servers.
4) Theres also the keep it simple theory, which prefers not to add complexity for little gain (and this wouldnt be much gain)..
5) Lastly, nobody is/should be 'competing for points' here
C. | [reply] |
|
We like to see everyones opinion on things, so multiple posts with the same answer and in a short time frame arent a bad thing at all.
From my point-of-view, it's actually a good thing when that happens. When I see several posters offering the same solution, then I *really* pay attention to it, as there must be *some* reason that so many of these enlightened folks choose to do it the same way.
Especially if they're all saints :)
We, of the lower ranks, aren't just looking for solutions to current problems, we're looking to *learn how and why* the solution works, so we can do it in the future on our own, and grow as developers. So, there is benefit in seeing that the solution being offered is a pretty standard one.
Lastly, nobody is/should be 'competing for points' here
Ah... points will come... even I occasionally luck into them :)
Trek
| [reply] |
|
here here!!
Given that there is more than one way to do it for nearly every problem, I think it would be counterproductive to implement something like this.
castaway summed this up nicely.
| [reply] |
|
| [reply] |
Re: Concurrent reply alert
by Aristotle (Chancellor) on Aug 19, 2004 at 11:37 UTC
|
| [reply] |
|
| [reply] |
|
Careful. One might find that the fact that you feel defensive about it speaks volumes by itself. :-) I hope you're not overlooking the fact that the node in question was written nearly two years ago.
And though far as it be from me to suggest I know who ignatz was thinking of, I feel pretty sure I can hazard a guess as to whom he was thinking of, which would not be you.
Let's just appreciate that node for what it is, namely, a great piece of humour on the (Perl programmer's) human nature, okay? :-)
Makeshifts last the longest.
| [reply] |
Re: Concurrent reply alert
by dfaure (Chaplain) on Aug 19, 2004 at 15:53 UTC
|
We should at least be able to delete a post within a couple of minutes of posting it without needing special permission.
<humour>
As you were surely told to do in your childhood, you should turn your tongue seven times and only speak after that... This is the place to practice here ;)
Also, don't forget you're here in a monastery, not in a campus yard. Things written here are to be laid by hand on parchments by copist monks for next generations of devoted to Perl. You're welcome to apply for the job...
</humour>
More seriously, it would be nice to be able to subscribe to choosen threads and being /msged when new replies are posted.
____
HTH, Dominique
My two favorites:
If the only tool you have is a hammer, you will see every problem as a nail. --Abraham Maslow
Bien faire, et le faire savoir...
| [reply] |
Re: Concurrent reply alert
by graff (Chancellor) on Aug 19, 2004 at 23:22 UTC
|
If you use a browser that allows you to open a link in a new window or new tab, use that to open the "Comment on..." link. Then, after you have composed/previewed/revised your reply and are ready to hit that "create" button, flick back to the OP window/tab and hit "reload" to see if others have replied during your labors, and if so, what they have said. Make further revisions to your epistle, or ditch it, as appropriate.
(If you don't use such a browser, it should be easy enough for you to fix that yourself... ;) | [reply] |
A reply falls below the community's threshold of quality. You may see it by logging in. |
A reply falls below the community's threshold of quality. You may see it by logging in. |