Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Joy of joys! (Score 2) 109

Now I'll be able to communicate with some random, anonymous Internet person.

Yeah, first thing I thought was chats like this:

SPARTACUS19982: YO!

SPARTACUS4x9: 'Sup?

SPARTACUS12: U rite?

SPARTACUS19982: Wait, who said that?

SPARTACUS4x9: Said what?

SPARTACUS12: What?

SPARTACUS19982: That!

SPARTACUS12: What?

SPARTACUS19982: Yeah, what!

SPARTACUS12: Wait - which what?

SPARTACUS4x9: Dude, being Spartacus is starting to suck, ya know..?

SPARTACUS4x9: I mean, I don't even know who I am any more...

SPARTACUS@X0®: DISREGARD THAT I SUCK C0CKS!!!!

Comment Re:Vancouver example... (Score 1) 506

Actually, isn't it cheaper do go bilingual anyways? With French/English and Spanish added to a product's packaging and manual, you are essentially able to sell your product to consumers in all of the Americas, Africa and much of Europe without much little or no repackaging of your product.

Recently, a thousand signatures were gathered to require English signs in Richmond (though it failed to pass in city council), so it shows that BC people are not immune to fears of language hegemony when it is perceived to threaten their own identity.

http://www.vancouverobserver.c...

Comment Re:See you on the other side, Egon (Score 5, Interesting) 136

I concur. An inspirational nerd.

I sympathise, but as an old Canadian geezer, I always felt that by the time the US audience finally heard about them, the SCTV alumni had already done their best work. That troupe - and their cheezy, low-budget show - formed my sense of humour more than anything else. Dave Thomas, Harold Ramis, Eugene Levy, Andrea Martin, Catherine O'Hara... all of them went on to make memorable comedy in the US. I think Joe Flaherty was the only one who didn't make a big splash. (Which is America's loss, not his.)

But there was a time when all of them were callow, reckless youths with nothing to lose by making asses of themselves week after week on a second-rate Toronto-based network that was so small (it had only 13 stations at the start) it too had nothing to lose.

Back in junior high school, my week was centred around that blessed moment when the Indian-head test pattern would appear and the announcer would say, 'Don't touch that dial. Don't touch that one either. And stop touching yourself.' I still remember the intonation....

(... I never did stop touching myself, but that's another story.)

Comment Re:Code is closer to legalese than math (Score 1) 161

(Sorry for stereotyping but) you're a typical geek. You think that words can have a precise, context-free meaning, and whether something falls within the meaning of a word (or a technical term) can be done in polynomial time.

The real world is much more complicated than that.

Take for example, what is a male and what is female? You'd think it's easy enough to determine that if you have access to the genitals, but there's still difficult corner cases to handle. For legal questions, it can be even more complicated. Questions like "was there a contract?" "is this negligence?" "did the person have the 'intention' to commit the crime?" are simply too 'complicated' to have a deterministic algorithm for all the cases. And before you ask why there are so many lawsuits (I'd imagine many more than the number of people with an indeterminate sex), the fact is that for the vast majority of cases the question is pretty clear cut, and it's really the corner cases that seriously go to court for a dispute on issues of law (as opposed to factual disputes, eg. whether a person did indeed sign a contract, whether the accused did kill the victim, etc.).

Supposedly you can really write out all the anticipated cases in a super horrifically complex program. But then, even if we suppose we can resolve the controversial cases where the facts don't fit our intuition (eg. the many many many situations whether or not you can have an abortion), it defeats the other purpose, that the (general) legal principles should be understandable by a lay person. In fact, lawyers are human beings too (well, not going into the soul question), and if the solution is not understandable by a significant number of lawyers, it's not going to become law. That's where your argument comes in -- but honestly, when you're good at skill X, you'd tend to believe that skill X is all you need to solve the world's problems, until you realize that when you apply skill X outside of its usual domain, it doesn't work in practice. (Just check out the mad scientists cartoons/movies for how things that work in theory could go wrong) The fundamental flaw I see, is that people expect the law to *usually* work according to their *intuition*. Usually court decisions don't tend to go against common sense, and when it does, the legislature will "correct" the decision (at least for common law systems) so that the law is what people expect. The problem is, what people expect can be very self-inconsistent, and what people expect is usually optimized for the normal case, not optimized to reduce the awkward corner cases. If you have no idea what the "self-inconsistencies" of a normal human being is, try understanding a woman. (to please the feminists: or a man who's not a logician -- getting to understand the opposite sex makes you wonder whether everyone's brains are just full of inconsistencies)

And of course you can't just look at the law in its current state and simply declare it void because you have a supposedly better system "intelligently designed" by a genius. I'm not sure about you, but I personally would be very skeptical of any large "rewrite" of a system by a person who doesn't even understand what the system is about.

I do agree there could be a bit more inter-disciplinary research on how CS can assist in making law less complex, but ... from what I know and understand (not to say that it's a lot), I'm skeptical whether there could be any groundbreaking results.

I'd say, getting legislation to use a proper version control system, and if a git-blame could show all the people who voted for/against a particular law, it would already be a great win. :)

Comment Re:Long-term loss (Score 1) 520

Bandwidth and latency are neither free or infinite.

Nobody said it was. The issue here is that Comcast subscribers are not getting what they paid for, unless NetFlix pays again for the bandwidth. This is bandwidth for which NetFlix has already paid, and for which Comcast has already been paid by its customers.

Your argument is the same as saying that if you pay for a bridge with your taxes, you should be able to drive a fully loaded hauling truck (type Caterpillar 797F) on it. But guess what ? The bridge has not been designed to handle that load, it has been designed for lighter load (car, 40' truck, etc.).

You're dead wrong on this count. Comcast is arguing (speciously) that traffic to and from a particular destination doesn't deserve the same service as traffic to and from other destinations - unless the destination pays an additional toll. The fact that this is a popular destination is only relevant inasmuch as this increases Comcast's ability to extort payment for something which has already been paid for.

This is straight-up anti-competitive behaviour. If the US telecommunications regulatory environment made any sense at all, Comcast would be slapped down hard for doing this.

Comment Re:Code is closer to legalese than math (Score 1) 161

Law is fuzzy. Programming is usually not.
Law is often inconsistent. Programming (or the underlying logic) usually cannot be inconsistent.
Law is relatively simple once you get past the fuzziness and inconsistencies. A lot of software is multitudes more complex than legalese.
There's often an easy way to test your program. Not so easy to test a legal theory or opinion. (You go to court, spend thousands or millions on legal fees before you get a judge to decide on the matter -- and then you have appeals)
Lawyers are usually not very anal about making the law "efficient" and "easy to understand". Sometimes the law is more complicated than it needs to be, and the lawyers like it that way (after all, they make money by translating all that crap to plain language). Most good programmers, on the other hand, strive to make their code easy to read.

English common law is basically all about struggling with legacy issues and finding new applications for old "code". The concerns about "backwards compatibility" (i.e. not overriding previous decisions) appear often enough to warrant a mention.

Disclaimer: IANAL, have a law degree, and I'm a software engineer.

Slashdot Top Deals

"Everything should be made as simple as possible, but not simpler." -- Albert Einstein

Working...