I wasn't aware that private businesses were required to adhere to the wishes of a third party.
Correct - they're not. However, that's a bit different than demanding rights which don't exist in the given context.
If Klayman wants to sue, he's more than welcome to, but he's going to have to prove damages first, in court - that's not "requiring" a business to do anything.
PS: The time zone thing was a holdover from the railroad days, and was created to address serious safety problems w/ timing and multiple trains on a given track.
Me, I wouldn't mind GMT. Just have to convince a billion or so others (at least) to use it as a single set time.
Just as French was once the international language of diplomacy 100 years or so ago, and Latin the universal scientific language before that, English is currently the international language of business.
My employer's corporate HQ is in the EU - yet the last time we held a quick (informal) meeting, in German, w/ a few counterparts at HQ, we'd get along just fine and get things done - then a VP gets wind of it. He promptly emails all involved, reminding us that corporate policy requires all cross-border phone/teleconferences be held in English (even if native English-speaking citizens weren't present- e.g. if it was a meeting between folks who were Germans and Spaniards).
It ain't just Europe, either. Do business with anyone in China, and even if you bring along Mandarin speaking co-workers, the meetings will be held in English more often than not these days. Anyone requiring a commercial aircraft pilot license, anywhere on the planet, is required to speak English.
sibling is right... most times, I don't even have to fill them out, instead feigning time pressures: "I have to be somewhere pretty soon - is it okay if I bring this back?" usually gets me the card with zero information to the store.
Not flaming or trolling, but that sounds pretty elitist to me.
If most profs refuse/hate Wikipedia, then maybe they should help make it worth using - the overarching goal of a prof is to educate and inform.
In the early days, I could understand why Wikipedia was actively avoided - it was inaccurate as hell most of the time (and back when I did the teaching thing, I also told students to stay the hell away from it - for exactly that reason). OTOH, quality has come up by quite a bit since 2004 or so, and while certainly not perfect, it is at least a great place to find references, and in the majority of cases provides a solid basic set of facts (esp. when properly cited).
Also, I don't think anyone is asking them to dumb it down any... just make sure it's correct, and correct a fact here and there when needed.
I understand the whole 'publish or perish' mentality, as well as the egos, the avoidance of the pedestrian/vulgar/whatever, but seriously? Maybe it's time for the professors as a whole to grow the hell up. The days of the Ivory Tower tenured professional metering information out to a fawning public? Those days have passed long ago - about when Phoenix University and similar schools began to gain some sort of recognition in the community at large.
Who knows? Wikipedia could even serve as a repository of sorts for the bleeding-edge research, where known facts on a subject could be stored after being agreed-upon, (so long as the edits were locked to only those professionals actively participating in studies of that subject).
IDC tries to justify it by throwing the word "Nokia" around a lot, but honestly, Nokia will (at least IMHO) be lucky to remain in the smartphone business by 2015.
There's something else that screams "bullshit!" at IDC's predictions: while next quarter's marketshare stats (e.g. Canalys, ComScore, etc) may say differently, Microsoft's share of the mobile market is still dropping like mad. Even though WinMo 6.5 still has some mass to blow off, one would think that nearly 6 months of WP 7 would have at least slowed down the fall a little bit.
The final elephant in an already heavily pachyderm-populated room is Microsoft's utter silence on sales numbers. They almost always trumpet and trot out numbers, even if it's just channel-related. We all heard the big, bad 'two millionz0rz since launch!!!111' figure back in January, even though those were only channel shipments. Now, Microsoft's marketing department has nothing but the sound of crickets when it comes to mobile licensing sales (or even shipments).
Taken all together, it spells a whole lot of potential fail, and IDC needs to do a hell of a lot more than shout Nokia's name, like it were some sort of talisman that defies all logic.
Really? I'd prefer a strict outcome, but an anything goes to get the solution approach.
May want to search the/. archives for "quack.exe" before you say that. Don't feel much like having a game's graphics pre-crippled by a vidcard desperate to tweak-up some FPS numbers again, err, thanks much...
Art really knew how to entertain - in a way that satisfied both the intellectual who enjoyed the funny-as-hell absurdity of it, and the typical trucker/double-wide type of person who took it all in as if it were gospel. It's a rare man who can do that simultaneously.
George is a nice guy and all, but he bored me clean out of listening to the show a very long time ago.
Still miss the opening bump tune occasionally, though:/
...they should be forced to retain online user data for exactly as long as the shortest amount of time they generally retain their own employees' emails.
If Microsoft is anything like Intel and the other big boys, that would be ~2 weeks for inboxes. Wanna keep the web-hoovered data for longer? They can then expose themselves to more legal liability by extending their corporate email retention policies similarly. I'm willing to wager that they really won't want to do that, but it's generally win-win - longer email retention times mean that anything stupid/illegal there has a better chance of recovery.
(Most big corps keep the time short to save disk space in general, to help auto-purge crap messages that most folks ignore, and of course to provide legal CYA. Individual employees are allowed to copy off mails to other folders which keeps the messages around for longer, but then liability shifts to the individual employee).
(disclosure: I have Radeons stashed in various machinery throughout the house - especially the Macs)
Anyrate, them are pretty big words, but I'd take them more seriously if they agreed on a neutral testing lab and benchmarks that aren't geared towards one over the other.
Oh, and for the love of all that is holy, please provide comic relief by including an Intel video chipset. Pretty please? (please insert evil grin here)
whoa, whoa... should've clarified. I meant using off-the-shelf frameworks (or worse, off-the-web ones) and trying to make it fit into a new project. Meant nada about someone writing common bits that the whole team can use.
...are zealots who will insist in coding in a certain language, even if your project would be better served by something else.
Having read TFA, I'm curious - which language would that be?
He didn't mention any specific language - he only listed what he didn't want his coders to use, and even then only as their primary skill.
Your posting history is more than a bit pro-Microsoft, so I can see why you may have gotten miffed at TFA, but seriously - why are you putting words in the guy's mouth?
So do you love writing code, or did you just do it for the paycheck?
TFA (yeah, I read it, my bad) says they're looking for people who love to write code, and know how to do it well. They want coders who have a passion for what they do. They want coders who are flexible, and who are able to adapt. They want coders who are able to not only write apps, but who understand what's really going on deep down.
Honestly? I agree with the guy. If you're running a startup, and looking for long-term growth, your initial coders need to be more than merely competent.
I remember when I did a stint working for a small company... these guys, to be exact. They had two full-on coders, one hell of a script whiz who knew 3D/CG like the back of his hand, and they had me. I had to learn Qt in very short order, figure out the fun nuances of helping port everything from x86 to PPC (this was pre-Intel Mac). Oh, and we did all of our own documentation, for both the SDK (both code and our own home-grown CG-oriented scripting language) *and* the users. I had to pick up bits and bobs that I thought I'd never have to use after leaving school (dusting off rusty trigonometry skills, blending in gaming, artistic, printing/color, and a whole pile of other concepts). Oh, and we'd just bought the codebase for Bryce during that time and had to clean that up (this is where I learned that Kai Krause can be a very evil man...)
Long story short, in that environment, you had to be agile, and given the insane hours, you had to be agile, and you had to really love doing it. OTOH, I wouldn't trade that for anything. We were outright cowboys by big-corp standards, and had a ball doing it.
In an environment like that? There's zero room for cookie-cutter technologies, or cookie-cutter programmers. (not accusing you, just sayin').
Slashdot Mirror
I wasn't aware that private businesses were required to adhere to the wishes of a third party.
Correct - they're not. However, that's a bit different than demanding rights which don't exist in the given context.
If Klayman wants to sue, he's more than welcome to, but he's going to have to prove damages first, in court - that's not "requiring" a business to do anything.
PS: The time zone thing was a holdover from the railroad days, and was created to address serious safety problems w/ timing and multiple trains on a given track.
Me, I wouldn't mind GMT. Just have to convince a billion or so others (at least) to use it as a single set time.
Just as French was once the international language of diplomacy 100 years or so ago, and Latin the universal scientific language before that, English is currently the international language of business.
My employer's corporate HQ is in the EU - yet the last time we held a quick (informal) meeting, in German, w/ a few counterparts at HQ, we'd get along just fine and get things done - then a VP gets wind of it. He promptly emails all involved, reminding us that corporate policy requires all cross-border phone/teleconferences be held in English (even if native English-speaking citizens weren't present- e.g. if it was a meeting between folks who were Germans and Spaniards).
It ain't just Europe, either. Do business with anyone in China, and even if you bring along Mandarin speaking co-workers, the meetings will be held in English more often than not these days. Anyone requiring a commercial aircraft pilot license, anywhere on the planet, is required to speak English.
Just the way it is at this time.
Larry Klayman is suing facebook for failing to violate another persons Freedom of Speech.
I wasn't aware that private businesses were required to adhere to the First Amendment.
The difference is this: if someone was born on some land, they have a better moral case than those who were not.
Israel was recognized in 1948 (or so)... I'm willing to wager that a healthy quorum (if not majority) of Israelis were born there by now.
...if only they found the decoder ring at the scene...
sibling is right... most times, I don't even have to fill them out, instead feigning time pressures: "I have to be somewhere pretty soon - is it okay if I bring this back?" usually gets me the card with zero information to the store.
Not flaming or trolling, but that sounds pretty elitist to me.
If most profs refuse/hate Wikipedia, then maybe they should help make it worth using - the overarching goal of a prof is to educate and inform.
In the early days, I could understand why Wikipedia was actively avoided - it was inaccurate as hell most of the time (and back when I did the teaching thing, I also told students to stay the hell away from it - for exactly that reason). OTOH, quality has come up by quite a bit since 2004 or so, and while certainly not perfect, it is at least a great place to find references, and in the majority of cases provides a solid basic set of facts (esp. when properly cited).
Also, I don't think anyone is asking them to dumb it down any... just make sure it's correct, and correct a fact here and there when needed.
I understand the whole 'publish or perish' mentality, as well as the egos, the avoidance of the pedestrian/vulgar/whatever, but seriously? Maybe it's time for the professors as a whole to grow the hell up. The days of the Ivory Tower tenured professional metering information out to a fawning public? Those days have passed long ago - about when Phoenix University and similar schools began to gain some sort of recognition in the community at large.
Who knows? Wikipedia could even serve as a repository of sorts for the bleeding-edge research, where known facts on a subject could be stored after being agreed-upon, (so long as the edits were locked to only those professionals actively participating in studies of that subject).
No kidding.
IDC tries to justify it by throwing the word "Nokia" around a lot, but honestly, Nokia will (at least IMHO) be lucky to remain in the smartphone business by 2015.
There's something else that screams "bullshit!" at IDC's predictions: while next quarter's marketshare stats (e.g. Canalys, ComScore, etc) may say differently, Microsoft's share of the mobile market is still dropping like mad. Even though WinMo 6.5 still has some mass to blow off, one would think that nearly 6 months of WP 7 would have at least slowed down the fall a little bit.
The final elephant in an already heavily pachyderm-populated room is Microsoft's utter silence on sales numbers. They almost always trumpet and trot out numbers, even if it's just channel-related. We all heard the big, bad 'two millionz0rz since launch!!!111' figure back in January, even though those were only channel shipments. Now, Microsoft's marketing department has nothing but the sound of crickets when it comes to mobile licensing sales (or even shipments).
Taken all together, it spells a whole lot of potential fail, and IDC needs to do a hell of a lot more than shout Nokia's name, like it were some sort of talisman that defies all logic.
You wuss... REAL coders use a REAL coder's keyboard!
Seriously... why all those excess keys, anyway?
That's not always true.
(FF4 came out rather well).
Really? I'd prefer a strict outcome, but an anything goes to get the solution approach.
May want to search the /. archives for "quack.exe" before you say that. Don't feel much like having a game's graphics pre-crippled by a vidcard desperate to tweak-up some FPS numbers again, err, thanks much...
No, seriously... Agreed perfectly.
Agreed w/ Sibling.
Art really knew how to entertain - in a way that satisfied both the intellectual who enjoyed the funny-as-hell absurdity of it, and the typical trucker/double-wide type of person who took it all in as if it were gospel. It's a rare man who can do that simultaneously.
George is a nice guy and all, but he bored me clean out of listening to the show a very long time ago.
Still miss the opening bump tune occasionally, though :/
...they should be forced to retain online user data for exactly as long as the shortest amount of time they generally retain their own employees' emails.
If Microsoft is anything like Intel and the other big boys, that would be ~2 weeks for inboxes. Wanna keep the web-hoovered data for longer? They can then expose themselves to more legal liability by extending their corporate email retention policies similarly. I'm willing to wager that they really won't want to do that, but it's generally win-win - longer email retention times mean that anything stupid/illegal there has a better chance of recovery.
(Most big corps keep the time short to save disk space in general, to help auto-purge crap messages that most folks ignore, and of course to provide legal CYA. Individual employees are allowed to copy off mails to other folders which keeps the messages around for longer, but then liability shifts to the individual employee).
(disclosure: I have Radeons stashed in various machinery throughout the house - especially the Macs)
Anyrate, them are pretty big words, but I'd take them more seriously if they agreed on a neutral testing lab and benchmarks that aren't geared towards one over the other.
Oh, and for the love of all that is holy, please provide comic relief by including an Intel video chipset. Pretty please?
(please insert evil grin here)
whoa, whoa... should've clarified. I meant using off-the-shelf frameworks (or worse, off-the-web ones) and trying to make it fit into a new project. Meant nada about someone writing common bits that the whole team can use.
Sorry 'bout any confusion.
Actually, he took a pretty hard slap at Java towards the bottom of the article.
The frameworks just save us from having to remake and reuse tons of code that somebody already did. Why do more work than you have to?
Well, there's this thing called "bloat" that you may want to avoid...
You expected folks to read TFA?
Heretic! Blasphemer!
Cardinal Biggles! Get the Pillow!
...are zealots who will insist in coding in a certain language, even if your project would be better served by something else.
Having read TFA, I'm curious - which language would that be?
He didn't mention any specific language - he only listed what he didn't want his coders to use, and even then only as their primary skill.
Your posting history is more than a bit pro-Microsoft, so I can see why you may have gotten miffed at TFA, but seriously - why are you putting words in the guy's mouth?
You must be new here. :p
According to TFA, he doesn't generally rule them out - it just raises a flag.
A developer who is versatile should have no problems getting past that.
I do .NET because that's where the money is.
So do you love writing code, or did you just do it for the paycheck?
TFA (yeah, I read it, my bad) says they're looking for people who love to write code, and know how to do it well. They want coders who have a passion for what they do. They want coders who are flexible, and who are able to adapt. They want coders who are able to not only write apps, but who understand what's really going on deep down.
Honestly? I agree with the guy. If you're running a startup, and looking for long-term growth, your initial coders need to be more than merely competent.
I remember when I did a stint working for a small company... these guys, to be exact. They had two full-on coders, one hell of a script whiz who knew 3D/CG like the back of his hand, and they had me. I had to learn Qt in very short order, figure out the fun nuances of helping port everything from x86 to PPC (this was pre-Intel Mac). Oh, and we did all of our own documentation, for both the SDK (both code and our own home-grown CG-oriented scripting language) *and* the users. I had to pick up bits and bobs that I thought I'd never have to use after leaving school (dusting off rusty trigonometry skills, blending in gaming, artistic, printing/color, and a whole pile of other concepts). Oh, and we'd just bought the codebase for Bryce during that time and had to clean that up (this is where I learned that Kai Krause can be a very evil man...)
Long story short, in that environment, you had to be agile, and given the insane hours, you had to be agile, and you had to really love doing it. OTOH, I wouldn't trade that for anything. We were outright cowboys by big-corp standards, and had a ball doing it.
In an environment like that? There's zero room for cookie-cutter technologies, or cookie-cutter programmers. (not accusing you, just sayin').
Thank Ghod I'm in Canada where we measure distances travelled in Kilometers
...that just means you rack up the units of measurement faster, leading to higher taxation. :p
(...then again, at least they can be a bit more granular about it.)