Become a fan of Slashdot on Facebook


Forgot your password?

Comment: Re:Creators wishing to control their creations... (Score 4, Informative) 268

Why not? Why should the creator not be able to impose any restrictions they damn please?

Largely because of the first-sale doctrine, which codifies property rights sanity: if you sell me something, it is now mine, not yours. I can do whatever I want with it. Use my spatula as a screwdriver? Use a thermos bottle for a hammer? Watch scenes in a movie out of order? It's none of your business. I bought it. It is now my property, and I'm free to do with it as I please.

(Averting pedantry: of course that doesn't involve violating copyright. Straw men will be ignored.)

Comment: Re:100 TB @ 100 MBit/s == 12.5 days (Score 1) 528

by Just Some Guy (#48534421) Attached to: The Sony Pictures Hack Was Even Worse Than Everyone Thought

Hell yeah, I'll admit that I am King of the Geeks. Talk nerdy to me.

OK, OK. I'll double-check with a calculator that's not "bc" before publishing. I've done enough physics work, though, to trust that 1) calculations showing explicit conversions are almost always correct, and 2) calculations that don't almost never are.

Comment: Re:100 TB @ 100 MBit/s == 12.5 days (Score 1) 528

by Just Some Guy (#48532019) Attached to: The Sony Pictures Hack Was Even Worse Than Everyone Thought

For nontrivial math, I don't always trust Google's interpretation of the question to be the same as mine. That page is a little short on details of what it's actually doing. On the other hand, WolframAlpha is really good about showing its work. I just always forget that it's there.

In either case, yeah, I like doing it the hard way. Or as I call it, "learning" or "practicing".

Comment: Re:Why program in Python (Score 4, Insightful) 277

by Just Some Guy (#48518099) Attached to: Which Programming Language Pays the Best? Probably Python

They think it's great because, in a tragic case of hilarity, jumping into code with minimal design is what python is great at.

We think it's great because, among other things, it has first-class functions and a very high code:boilerplate ratio. This lets us write very concise, readable, and maintainable code.

If you're a diligent programmer in python/php/javascript/etc then, in each function you write, you're going to double-check that the type passed in is correct, anyway.

Eww, no. I've never seen good Python code that asserts types because it's not the idiom for you to care. For instance, suppose you write a function like:

def get_contents_of(obj): return

In this case, obj might be a file, or a web request, or a string (via the StringIO interface). Who knows? Who cares? As long as returns something, it works. BTW, this is supremely nice for unit testing when you don't really want to hit an SQL server 1,000 times in a tight loop.

Now, you could write something like assert isinstance(obj, file) to guarantee that you're only dealing with file objects. Of course, that lays waste to the whole concept of duck typing and people will laugh at you for doing it. So dropping that bad idea, you could write assert hasattr(obj, 'read') to ensure that the object has the needed methods. But why? Python gives you that check for free when you try to call the method. Let it do the heavy lifting and concentrate on the parts of the problem you actually care about.

Exceptions are one of the worst things to have become common - an "error" is almost always only caught outside the scope that it occurred in, hence the stack has already been unwound and thus there is no sane way to fix the error and retry the operation that caused the exception.

Yeah, that would be terrible. You almost never use them in Python like that, partially because Python tends to have a vastly shallower call stack than, say, Java (largely because you don't need 10 layers of abstraction between bits of code thanks to the duck typing we just talked about).

I think it boils down to you not knowing idiomatic Python. That's OK. I'm ignorant about lots of things, too. But I think you'd find that you enjoy it more if you stop trying to write C or Java in Python, because that almost never works out well.

Comment: Re:Why program in Python (Score 1) 277

by Just Some Guy (#48517037) Attached to: Which Programming Language Pays the Best? Probably Python

I agree, but remember that Python is interpreted in exactly the same way that Java is: both compile high level code to bytecode and run it on virtual machines. PyPy selectively uses LLVM to compile that bytecode into assembler for some enormous performance boosts, much as the Java JIT compiler does.

Comment: Re:Why program in Python (Score 1) 277

by Just Some Guy (#48517019) Attached to: Which Programming Language Pays the Best? Probably Python

Whatevs. I co-built a web service on Python that handled 250,000 requests per second with a horizontally scaleable design. We could bump that up to 1,000,000 requests per second by deploying 4 times the servers (which isn't as easy as it sounds because most things don't scale out well like that). I left that company and went to another employer that handled "only" 80,000 requests per second, averaged over a month. If you can ditch the chattiness of HTTP, well, I've written single-threaded UDP servers in Python that could handle 200,000 requests per second per server. How fast do you want it to be?

Unless you're seeing extremely low numbers or your design requires vertical scaling because it was architected in 1965, choice of language isn't all that important. Ruby is slow, too, but Heroku manages to shovel the data pretty well.

Comment: Causality? Who knows? (Score 3, Interesting) 277

by Just Some Guy (#48516771) Attached to: Which Programming Language Pays the Best? Probably Python

I love Python because it maps very neatly onto how I model problems in my head. I'm not averse to using other languages, but Python is my comfort zone because Guido and I apparently think about algorithms in the same ways. As it turns out, I make a decent living with it.

So, do I have a good job because I know Python, or is it because the thought patterns of the people who are drawn to Python are the same ones that companies want to pay for, regardless of language? If the former and you want a good job, then by all means learn Python. But if knowing Python is just a side effect of the properties that employers are actually looking for, then it's probably not going to help you all that much.

Comment: Re:First (Score 1) 446

by Just Some Guy (#48510107) Attached to: 18th Century Law Dredged Up To Force Decryption of Devices

You can install a firmware that is compiled from the open source you trust.

Ken Thompson had something to say about that. Are you hand-compiling that OS using your own tools and not the vendor-supplied toolchain?

There is still the possibility of hardware level backdoors, but there are a 100 different manufactures of Android devices, many of them have little to no presence in the USA

...and are largely from countries with no cultural history of valuing privacy. Now instead of being suspicious of Apple or Microsoft, you have to be suspicious of 100 individual vendors.

Versus Apple, Microsoft, etc who are easy targets for US courts orders

...and US court lawsuits. For the first time maybe ever, it seems like the non-geek people around me are starting to get why security is important and are taking it seriously. Apple and MS have a lot more to lose than $RANDOM_CHINESE_VENDOR who can still sell their bad-American-repped $30 phones in developing countries if they're kicked out of America. Take away Apple's North American market and they'd fold overnight. They've been bragging about their security and crypto for a while now to the point of making it a marketing point, and breaking their promise to consumers would likely be catastrophic.

If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's a design philosophy.