Open source is about sharing work to prevent reinventing of the wheel
of course everyone here thinks picking code out of the split is a good idea. but... let's consider the flip side for a moment:
why did the code base split in the first place? obviously, because a group of developers in the team felt they had a better vision or method or whatever than the team leads. a code split is only a last resort, so we can probably assume that the developers who went on to form the split put a lot of effort into trying to get their ideas into the original source tree and were unsuccessful.
so, now that the split team has got a project up and running and is writing new code that embodies their vision of the project, they find that the original team who probably rejected at least some of the split team's ideas before the split is now suitably impressed with the results to roll them into the original source tree.
the question the split team may be asking themselves right now is this: if our ideas and code are so hot, why didn't you pay attention to them originally? and, furthermore, if the original team is so impressed with the features of the split project, why don't they put their effort into working on the split instead of the first source tree?
not meant to be flamebait: just trying to consider the motivations and rationales of the split team since no member of that team was given the opportunity to present their opinions or views in the original post.
you want to reorganise the entire western hemispheres calendering system because the new one is easier to code?
well, let's face it: if the current time keeping system were software we'd seriously be considering a rewrite.
my personal favourite for easier time systems is the swatch "internet time" beats. basically, the day is divided into 1000 "beats" (about 90 seconds each) and the current beat count is global. by being global the annoyance of time zones is eliminated. you just have to remember that you go to work 350 in switerzerland and 600 in michigan and that hocky night in canada is on at 120, 145 in newfoundland.
nothing. unless, of course, you already have a major project that's been using cvs. then, if you want to switch to subversion you have to retrain your development team and switch over your repository with the cvs2svn.py tool which, according to the subversion site "is still under development... only use it on a copy of your CVS repository and double check your results"
if you're in a major production environment, that's a no go.
If they have a warrant, and access to your computer, what the fuck are they messing around keeping it running for anyway, why haven't they just arrested you?
because they're looking to get enough evidence to arrest you. all that is needed to get a warrant in most oecd countries is "probable cause". basically, the cops go to a judge and say "we have a guy who says a guy told him that person a might be a drug dealer. can we get a warrant?" and more often than not, the warrant is issued.
depending on the type of warrant, they can get a one time search and seizure, a wiretap on your phone or a passive listening device in your room. all this law in australia does is just add computer traffic to that list.
if you are concerned about your privacy and protecting it from the warrant system, you're about two hundred years late in complaining.
I work at an insurance office in Saskatchewan... We get all sorts of efforts to acquire fake ID, it's rather pathetic.
i live in alberta where we have a snazzy driver's license with an encoded pattern and such.
about a year ago i lost my license (along with just about every other card i have) so i headed down to one of the privatized "registry shops" to get a new one.
really, the process was embarassingly easy. when the woman asked me behind the counter for some i.d. i said "it's all been stolen". she shrugged, took my picture, and gave me a brand new license basically on faith alone that i was who i claimed to be.
now, she did look at the picture they had on file but, really, if you look like like your license photo you're in rough shape. bottom line: any 180 cm tall male with light hair and grey eyes who didn't look too dissimilar to me could have waltzed in there and picked up a license with my name on it, snazzy security stripe not withstanding.
I still say that reguardless of global warming it is better to continue on and deal with problems as they arise
so the solution is to deal with the symptoms rather than address the cause?
If we throw away our technology, as some would seem to prefer
slow down, there! it's a bit of a leap to conclude that those who advocate a meaningful reduction in greenhouse gasses are calling for us to "throw away our technology".
a hundred and twenty years ago, all the western world's major cities had a horse poop problem. lots of horses in the streets, lots of poop. how was this addressed? by "throwing away" the technology of horses? no. the solution was technological improvement rather than regression.
MS decides B.
MS distributes B across the globe, everyone repeats. End of story.
this reminds me of the whole "total cost of ownership" campaign ms ran a few months ago, whereby ms claimed that the tco of microsoft server solution was cheaper, overall, than the linux equivalent.
well, i downloaded the pdf of the study and read the whole damn thing. the bottom line: the ms solution was cheaper... if you factored in the "retraining costs" required to move your "existing i.t. staff" to use linux.
the devil, of course, was in the unspoken assumption that you are already running an ms shop. more correctly stated: the tco of your current system is cheaper than moving to a new system over the short or, potentially, medium term.
now, since ms still has the lion's share of the desktop and workstation installs and a healthy chunk of the server space they maybe could be forgiven for glossing over this crucial fact. but, still, it just boils down to making a simple unstated assumption that changes the whole outcome of the data.
What makes it worse still is that this was done on a PIII-667
i believe the minimum hardware requirements for gentoo are defined as "any machine capable of compiling the latest release in less time than the stated release period".
You learn so much more at college where you're taught and learn from others about alternatives, formal methodology, etc.
you're both wrong.
what the i.t. world really needs is an apprenticeship programme.
an apprenticeship system would create a common, impartial body to set standards of skill and competence and provide a structured yet flexible on the job learning path to get i.t. people from basement geek to enterprise administrator.
it's not like the industry doesn't already run on this type of system in an informal way already. you get your degree, and then spend a year working as a "night operator" changing tapes. only once you've proven diligent enough to not screw up the back ups do you move on deployment, then troubleshooting, then planning and, finally, administration.
we should formalize the process so that real experience translates directly to accredation.
If you just got some sort of an idea of how to beat the enemy, you've got a blank check.
apparently without putting any thought into the implications of the technology being developed!
imagine for a moment that teleportation is actually developed. if this technology falls into the "wrong hands" (ie anyone who doesn't subscribe to u.s. hegemony) the result is a total and complete disaster.
with true, receiverless teleportation, no geographic area is safe. period. governments and financial/industrial institutions would need to go into hiding to avoid attack. the only form of security would be obscurity.
true. so, now when the american government makes aggressive and belicose blunders in the middle east the rest of the world won't just despise and deride the president. they'll hate the american people too.
congratulations america! you've completely alienated yourselves from all of your former allies and friends and earned the distrust and emnity of the rest of the planet.
and the u.s. will always be that way because of the nature of the system. in a presidential election, second place (let alone third or fourth) counts for nothing.
in a parliamentary system, by contrast, parties with lower levels of support get to have input. either they form the opposition or join the opposition coalition or, more effectively, become part of a governing coalition and weild some degree of political power.
witness canada: the dominant liberals alienated both the conservative and liberal portions of the population (no mean feat). however, none of the other parties were generally considered experienced enough to rule... so the electorate handed the liberals a minority victory.
to govern, the minority government now has to form coalitions with other parties to acheive enough votes to pass bills. in this case, the party the liberals allied with was the left-of-centre new democratic party. the result is that the ndp now has a fair amount of "pivotal power" - and given that helth care and other social programme issues were a big deal during the election, this is probably a Good Thing.
in a minority government situation, the opposition parties also have increased power. since the the government can fall to a well-organized attack by the opposition, the liberals are less likely to antagonize stornaway.
the result is: less people are alienated in a parliamentary system. if you voted for gore in 2000, your vote was completely wasted. but no matter who you voted for in canada last april (unless you voted green, as i did) there's someone in the government representing you.
marry 3 people simultaneously, or whether one of these "people" can't be a horse or other arbitrary livestock?
er. the law, which is what we're discussing here, only applies to people. can a horse be charged with murder? does it need to submit income tax returns? no. and it can marry or be banned from marrying either. your point is moot.
if you're going to argue against gay marriage then i would request that you stay away from over-dramatic implementations of the slippery slope fallacy.
You'd think a company who's been making ATMs since their inception, would have a good understanding of cryptographic security and the "gotchas" inherent in such systems
understanding? sure. motivation to implement it? maybe not. consider:
if the bank machine borks my transaction i find out about it at month end in my statement. if the voting machine borks my ballot, i never know.
the atm is just a snazzy client for the bank's server. the banks approves the transaction and returns the balance, the atm just spits out the cash.
remember: in every first year computing science class assignment #2 is "bank machine".
so the military (Republican) vote will come through fine
but is the military vote really republican?
the christian science monitor today is running a story on anti-bush troops in iraq. give it a read -- and remember that the last time the u.s. was involved in a major land war a lot of the vetrans and enlisted men wound up developing strong anti-war stances... john kerry, for instance.
Slashdot Mirror
of course everyone here thinks picking code out of the split is a good idea. but... let's consider the flip side for a moment:
why did the code base split in the first place? obviously, because a group of developers in the team felt they had a better vision or method or whatever than the team leads. a code split is only a last resort, so we can probably assume that the developers who went on to form the split put a lot of effort into trying to get their ideas into the original source tree and were unsuccessful.
so, now that the split team has got a project up and running and is writing new code that embodies their vision of the project, they find that the original team who probably rejected at least some of the split team's ideas before the split is now suitably impressed with the results to roll them into the original source tree.
the question the split team may be asking themselves right now is this: if our ideas and code are so hot, why didn't you pay attention to them originally? and, furthermore, if the original team is so impressed with the features of the split project, why don't they put their effort into working on the split instead of the first source tree?
not meant to be flamebait: just trying to consider the motivations and rationales of the split team since no member of that team was given the opportunity to present their opinions or views in the original post.
yet another reason to make your passwords the names of your children!
well, let's face it: if the current time keeping system were software we'd seriously be considering a rewrite.
my personal favourite for easier time systems is the swatch "internet time" beats. basically, the day is divided into 1000 "beats" (about 90 seconds each) and the current beat count is global. by being global the annoyance of time zones is eliminated. you just have to remember that you go to work 350 in switerzerland and 600 in michigan and that hocky night in canada is on at 120, 145 in newfoundland.
simple.
nothing. unless, of course, you already have a major project that's been using cvs. then, if you want to switch to subversion you have to retrain your development team and switch over your repository with the cvs2svn.py tool which, according to the subversion site "is still under development... only use it on a copy of your CVS repository and double check your results"
if you're in a major production environment, that's a no go.
because they're looking to get enough evidence to arrest you. all that is needed to get a warrant in most oecd countries is "probable cause". basically, the cops go to a judge and say "we have a guy who says a guy told him that person a might be a drug dealer. can we get a warrant?" and more often than not, the warrant is issued.
depending on the type of warrant, they can get a one time search and seizure, a wiretap on your phone or a passive listening device in your room. all this law in australia does is just add computer traffic to that list.
if you are concerned about your privacy and protecting it from the warrant system, you're about two hundred years late in complaining.
i live in alberta where we have a snazzy driver's license with an encoded pattern and such.
about a year ago i lost my license (along with just about every other card i have) so i headed down to one of the privatized "registry shops" to get a new one.
really, the process was embarassingly easy. when the woman asked me behind the counter for some i.d. i said "it's all been stolen". she shrugged, took my picture, and gave me a brand new license basically on faith alone that i was who i claimed to be.
now, she did look at the picture they had on file but, really, if you look like like your license photo you're in rough shape. bottom line: any 180 cm tall male with light hair and grey eyes who didn't look too dissimilar to me could have waltzed in there and picked up a license with my name on it, snazzy security stripe not withstanding.
hm. makes me think there should be a study on the illiteracy of slashdot posts.
so the solution is to deal with the symptoms rather than address the cause?
If we throw away our technology, as some would seem to prefer
slow down, there! it's a bit of a leap to conclude that those who advocate a meaningful reduction in greenhouse gasses are calling for us to "throw away our technology".
a hundred and twenty years ago, all the western world's major cities had a horse poop problem. lots of horses in the streets, lots of poop. how was this addressed? by "throwing away" the technology of horses? no. the solution was technological improvement rather than regression.
now we just have to deal with the car poop.
really, what i want for christmas is:
estimated play time for all three, four and half minutes.
yes. but will they be able to implement when they have these guys running their servers?
MS distributes B across the globe, everyone repeats. End of story.
this reminds me of the whole "total cost of ownership" campaign ms ran a few months ago, whereby ms claimed that the tco of microsoft server solution was cheaper, overall, than the linux equivalent.
well, i downloaded the pdf of the study and read the whole damn thing. the bottom line: the ms solution was cheaper... if you factored in the "retraining costs" required to move your "existing i.t. staff" to use linux.
the devil, of course, was in the unspoken assumption that you are already running an ms shop. more correctly stated: the tco of your current system is cheaper than moving to a new system over the short or, potentially, medium term.
now, since ms still has the lion's share of the desktop and workstation installs and a healthy chunk of the server space they maybe could be forgiven for glossing over this crucial fact. but, still, it just boils down to making a simple unstated assumption that changes the whole outcome of the data.
i believe the minimum hardware requirements for gentoo are defined as "any machine capable of compiling the latest release in less time than the stated release period".
you may be out of luck.
you're both wrong.
what the i.t. world really needs is an apprenticeship programme.
an apprenticeship system would create a common, impartial body to set standards of skill and competence and provide a structured yet flexible on the job learning path to get i.t. people from basement geek to enterprise administrator.
it's not like the industry doesn't already run on this type of system in an informal way already. you get your degree, and then spend a year working as a "night operator" changing tapes. only once you've proven diligent enough to not screw up the back ups do you move on deployment, then troubleshooting, then planning and, finally, administration.
we should formalize the process so that real experience translates directly to accredation.
apparently without putting any thought into the implications of the technology being developed! imagine for a moment that teleportation is actually developed. if this technology falls into the "wrong hands" (ie anyone who doesn't subscribe to u.s. hegemony) the result is a total and complete disaster.
with true, receiverless teleportation, no geographic area is safe. period. governments and financial/industrial institutions would need to go into hiding to avoid attack. the only form of security would be obscurity.
and that's bad.
true. so, now when the american government makes aggressive and belicose blunders in the middle east the rest of the world won't just despise and deride the president. they'll hate the american people too.
congratulations america! you've completely alienated yourselves from all of your former allies and friends and earned the distrust and emnity of the rest of the planet.
Branigan uses commonly available Linux tools like grep for searching the suspect's hard drive...
by double-edged:
I wonder if the author left out some "secret methods" he used in the field
yes. fgrep
i think a lot of people are voting democratic because of bush's record. his three main goals this presidency were:
quite frankly if i screwed up two-thirds of my assigned tasks at work, i'd get canned. i think the american people have the same idea.
oh wait, you can.
- don't answer the phone
- stop eating your egg mcwhatsit
you have voice mail. your egg mcdoodad won't get any more gross for being a little colder. make the right decision.way more americans die in traffic accidents every year than because of international terrorism. you, sir, are threat to homeland security.
by extension this implies that sco is guilty of carrying a concealed source... perhaps in one of those fast tear-away source holsters.
and the u.s. will always be that way because of the nature of the system. in a presidential election, second place (let alone third or fourth) counts for nothing.
in a parliamentary system, by contrast, parties with lower levels of support get to have input. either they form the opposition or join the opposition coalition or, more effectively, become part of a governing coalition and weild some degree of political power.
witness canada: the dominant liberals alienated both the conservative and liberal portions of the population (no mean feat). however, none of the other parties were generally considered experienced enough to rule... so the electorate handed the liberals a minority victory.
to govern, the minority government now has to form coalitions with other parties to acheive enough votes to pass bills. in this case, the party the liberals allied with was the left-of-centre new democratic party. the result is that the ndp now has a fair amount of "pivotal power" - and given that helth care and other social programme issues were a big deal during the election, this is probably a Good Thing.
in a minority government situation, the opposition parties also have increased power. since the the government can fall to a well-organized attack by the opposition, the liberals are less likely to antagonize stornaway.
the result is: less people are alienated in a parliamentary system. if you voted for gore in 2000, your vote was completely wasted. but no matter who you voted for in canada last april (unless you voted green, as i did) there's someone in the government representing you.
er. the law, which is what we're discussing here, only applies to people. can a horse be charged with murder? does it need to submit income tax returns? no. and it can marry or be banned from marrying either. your point is moot.
if you're going to argue against gay marriage then i would request that you stay away from over-dramatic implementations of the slippery slope fallacy.
if you could create a machine that he didn't have skills to crack... why would you need to hire him in the first place?
understanding? sure. motivation to implement it? maybe not. consider:
remember: in every first year computing science class assignment #2 is "bank machine".
but is the military vote really republican?
the christian science monitor today is running a story on anti-bush troops in iraq. give it a read -- and remember that the last time the u.s. was involved in a major land war a lot of the vetrans and enlisted men wound up developing strong anti-war stances... john kerry, for instance.