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".
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 obj.read()
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 obj.read 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.
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.
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.
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.
I have a cheap combination lock that lets me set my own "key". This isn't exactly alien technology, and I think a judge would be able to see the analogy.
Nuh Uh! I vecame vegan, don't eat any fat or salt, take 10 different maintenance drugs every day, and live in a safe room except when I go to the doctors. I'm gonna live 4-evah!
Do you also have a fixie? If so, $5 says you're a software engineer at a Bay Area startup.
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.
Then schools and colleges can get back to academic disciplines.
Like basketball, which will suddenly explode in popularity. Or you'll have an elite rowing team picking on freshmen. Perhaps a thug squad of a lacrosse team.
If football were to go away tomorrow, I promise you something would replace it, and quickly.
I think you're really grasping at straws. Note that Apple is donating all of the proceeds to charity. It's kind of hard to make a profit in volume when you're losing money on each individual sale.
Given the parties involved, I don't. Mozilla Foundation and EFF are two groups I implicitly trust. That doesn't mean their proposal will be perfect, of course, but to me it means that their motives are good and that smart people are trying to do the right thing.
They did, at WWDC 2013. More to the point, I wonder why the Trim Enabler dev isn't signing his kext? Are there legitimate reasons, like he needs a special kind of thing that can't be signed using the provided tools, or is it because he doesn't want to pay for a dev license to sign the software he's selling? In a vacuum of information, there's not much point in speculating.
People replace HDDs in macs, they need to support it.
Why? Is TRIM empirically faster on your drive, or is this something you think you need?
I'm wondering about that myself. Early benchmarks showed that the 840 EVO benefits from TRIM, but that drive also had wonky firmware that was causing read degradation. Could the old firmware have accounted for some of the benchmark problems?
Side note: I applied the firmware upgrade myself last week and it went through without a hitch. YMMV, but I had an easy time of it.
Apple, for whatever dumb reason, has _never_ enabled Trim on non-Apple branded SSDs.
I don't work for Apple, but... Older MacBook Pros came with instructions for replacing the RAM and hard drive. This was considered a normal thing to do and didn't void warranties. For example, my 2011 MBP has normal Phillips screws on the bottom, and it takes me about two minutes to have the back panel off and the RAM and HDD snap right out.
SSDs have a history of notoriously horrible firmware. SandForce, anyone? Someone goes to Best Buy and comes home with a new SSD, pops it into their MBP, uses it for a month, and the thing asplodes and eats their data. They call Apple support to scream at them for writing a terrible OS that loses their data, and Apple loses money and reputation.
I can imagine perfectly non-nefarious reasons why Apple would disable TRIM by default and only enable it for drives that have been explicitly tested for compatibility. Even today, you can still turn TRIM on for yourself as you described, at the price of reverting to pre-Yosemite security. I haven't done so on the 840 EVO I swapped into my MBP because I've judged that it's not worth the tradeoff for me, but it's an option. Trim Enabler even has a GUI to do it for you.
I'd be hard pressed to come up with more of a manufactured controversy.
Apple has never enabled TRIM on non-OEM SSDs, which is probably the conservative and correct thing to do. If you're clever enough to install a new SSD, you're clever enough to enable it on your own (and presumably to know whether you should enable it, and whether it's even a benefit for your particular drive).
The current workaround involved a single software vendor who didn't sign their kexts. Apple's new security policy won't let you load random unsigned kernel modules unless you explicitly turn off the signature checking. While this is inconvenient for me personally - because I have a 3rd-party SSD and I used that software myself - on whole, I'd rather have a more secure OS than the dubious benefit of a possibly slightly faster SSD.
A Surface Pro 3 starts at $749 - list price, less in qty. - that gets you close to 'good' laptops and tablets.
RT Surfaces go up against cheap Android tablets, not iPads or good high-end Androids. $449 is way more expensive than the competition.
At $749, you get a bottom-end CPU and no keyboard, so you're not competing against laptops at all. It's also $150 more than an iPad Air 2 with the same amount of storage (although the iPad will have more available space after subtracting the OS install), so you're paying more for a tablet with less available tablet-centric software.
OP was right: Surface is a hybrid that does neither thing well.
And don't forget the alternate risks of mugging you're subjecting children to by having them carry around a $600 thief-magnet
While I don't disagree with your general point, theft rates started dropping as soon as Apple added Activation Lock to iOS 7. There's not a lot of street value in a device that can't be used, and they're not the thief magnet they were even a year ago.
because hybrid seeds are bred for intensive agriculture, they typically need chemicals to thrive
...unlike natural, free-range grains that are invulnerable to pests and thrive under the gentle light of the waxing crescent moon. Sorry, but you lost me at "chemicals". Yes. They're matter-based lifeforms, and need a whole slew of chemicals to exist.
Rephrased, AT&T just confirmed that their financial plans including deliberately breaking the would-be net neutrality rules. I mean, if they weren't, it wouldn't affect their plans at all.
At mine, it was specifically allowed. You absolutely weren't allowed to share work unless explicitly told otherwise, but discussing your approach and debating the benefits was considered a legitimate learning method.
Slashdot Mirror
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".
Your math's a bit off: (10^14B)*(8b/1B)*(1s/100000000b)*(1h/3600s)*(1d/24h) = about 93 days
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:
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 obj.read 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.
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.
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.
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.
I have a cheap combination lock that lets me set my own "key". This isn't exactly alien technology, and I think a judge would be able to see the analogy.
Nuh Uh! I vecame vegan, don't eat any fat or salt, take 10 different maintenance drugs every day, and live in a safe room except when I go to the doctors. I'm gonna live 4-evah!
Do you also have a fixie? If so, $5 says you're a software engineer at a Bay Area startup.
"We manufacture locks where the end customer makes their own custom keys. We don't know what key they might have made."
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.
Security by obscurity doesn't count.
Then schools and colleges can get back to academic disciplines.
Like basketball, which will suddenly explode in popularity. Or you'll have an elite rowing team picking on freshmen. Perhaps a thug squad of a lacrosse team.
If football were to go away tomorrow, I promise you something would replace it, and quickly.
I think you're really grasping at straws. Note that Apple is donating all of the proceeds to charity. It's kind of hard to make a profit in volume when you're losing money on each individual sale.
Why would you get a tax writeoff for buying something? They're the one donating their part of the transaction, not you.
Given the parties involved, I don't. Mozilla Foundation and EFF are two groups I implicitly trust. That doesn't mean their proposal will be perfect, of course, but to me it means that their motives are good and that smart people are trying to do the right thing.
Apple should find a way to sign these
They did, at WWDC 2013. More to the point, I wonder why the Trim Enabler dev isn't signing his kext? Are there legitimate reasons, like he needs a special kind of thing that can't be signed using the provided tools, or is it because he doesn't want to pay for a dev license to sign the software he's selling? In a vacuum of information, there's not much point in speculating.
People replace HDDs in macs, they need to support it.
Why? Is TRIM empirically faster on your drive, or is this something you think you need?
I'm wondering about that myself. Early benchmarks showed that the 840 EVO benefits from TRIM, but that drive also had wonky firmware that was causing read degradation. Could the old firmware have accounted for some of the benchmark problems?
Side note: I applied the firmware upgrade myself last week and it went through without a hitch. YMMV, but I had an easy time of it.
Apple, for whatever dumb reason, has _never_ enabled Trim on non-Apple branded SSDs.
I don't work for Apple, but... Older MacBook Pros came with instructions for replacing the RAM and hard drive. This was considered a normal thing to do and didn't void warranties. For example, my 2011 MBP has normal Phillips screws on the bottom, and it takes me about two minutes to have the back panel off and the RAM and HDD snap right out.
SSDs have a history of notoriously horrible firmware. SandForce, anyone? Someone goes to Best Buy and comes home with a new SSD, pops it into their MBP, uses it for a month, and the thing asplodes and eats their data. They call Apple support to scream at them for writing a terrible OS that loses their data, and Apple loses money and reputation.
I can imagine perfectly non-nefarious reasons why Apple would disable TRIM by default and only enable it for drives that have been explicitly tested for compatibility. Even today, you can still turn TRIM on for yourself as you described, at the price of reverting to pre-Yosemite security. I haven't done so on the 840 EVO I swapped into my MBP because I've judged that it's not worth the tradeoff for me, but it's an option. Trim Enabler even has a GUI to do it for you.
I'd be hard pressed to come up with more of a manufactured controversy.
Apple has never enabled TRIM on non-OEM SSDs, which is probably the conservative and correct thing to do. If you're clever enough to install a new SSD, you're clever enough to enable it on your own (and presumably to know whether you should enable it, and whether it's even a benefit for your particular drive).
The current workaround involved a single software vendor who didn't sign their kexts. Apple's new security policy won't let you load random unsigned kernel modules unless you explicitly turn off the signature checking. While this is inconvenient for me personally - because I have a 3rd-party SSD and I used that software myself - on whole, I'd rather have a more secure OS than the dubious benefit of a possibly slightly faster SSD.
A Surface Pro 3 starts at $749 - list price, less in qty. - that gets you close to 'good' laptops and tablets.
RT Surfaces go up against cheap Android tablets, not iPads or good high-end Androids. $449 is way more expensive than the competition.
At $749, you get a bottom-end CPU and no keyboard, so you're not competing against laptops at all. It's also $150 more than an iPad Air 2 with the same amount of storage (although the iPad will have more available space after subtracting the OS install), so you're paying more for a tablet with less available tablet-centric software.
OP was right: Surface is a hybrid that does neither thing well.
And don't forget the alternate risks of mugging you're subjecting children to by having them carry around a $600 thief-magnet
While I don't disagree with your general point, theft rates started dropping as soon as Apple added Activation Lock to iOS 7. There's not a lot of street value in a device that can't be used, and they're not the thief magnet they were even a year ago.
because hybrid seeds are bred for intensive agriculture, they typically need chemicals to thrive
...unlike natural, free-range grains that are invulnerable to pests and thrive under the gentle light of the waxing crescent moon. Sorry, but you lost me at "chemicals". Yes. They're matter-based lifeforms, and need a whole slew of chemicals to exist.
Rephrased, AT&T just confirmed that their financial plans including deliberately breaking the would-be net neutrality rules. I mean, if they weren't, it wouldn't affect their plans at all.
At mine, it was specifically allowed. You absolutely weren't allowed to share work unless explicitly told otherwise, but discussing your approach and debating the benefits was considered a legitimate learning method.
Undoubtedly. Side note: yet another reason why it's good to get to know your teachers before you're counting on them to have a good impression of you.