851 karma · joined March 26, 2009
http://graehl.org/2013/02/21/chronic-6hrnight-sleep-incompet...
I only meant to store it in addition because the alternative, storing an index into the list of divisors (and thus reciprocals) might be slower due to an extra indirection.
Coincidentally, I got better. That was probably just rest and time, but I'm grateful that the book helped me not worry so much.
I get the sense that many of us are just waiting for a few improvements (like generics and better GC/performance) before using Go for real work, but it seems mature enough for many uses already.
That said, people who modify code without seeing if the adjacent comments still make sense are bad. If something is wrong on your screen, you should notice it and fix it.
I guess the above explanation is too uncharitable, and people don't believe they're racist but do believe they (or the industry) are sexist. I feel like racism is somehow more evil. I think "low level racism" is a decent label - you shouldn't be surprised that at a superficial level of acquaintance (resume screening), people subconsciously pull expectations of competence/"fit" according to the reference class they see the resume as belonging to (oh, another 25 yr old brogrammer!)
Also, there are more women in the U.S., so if women and blacks were similarly discouraged from coding, we'd want to throw more resources at encouraging women, hypothetically.
Do you mean the opposite? Either way - "certainly" is a cheap trick. Reasons please.
Have you considered that you may just be lucky in not falling ill lately? I've had several >1yr stretches without illness and have never done endurance exercise (max was a single half marathon).
That said, cjdns and pump.io were interesting to read about. I don't see any practical benefit to using them now, but they look like fun hobby projects.
1. If you succeeded for cause, you can often identify exactly what elements are needed for success in the next instance (whereas if you failed, you'll think long and hard about the "lessons" you need to take, but that doesn't leave you with a recipe for success - you may have several more failures to go at your rate)
2. The visceral feeling of soul-searching, of really thinking, of facing reality, isn't something that should be reserved for post-mortems of spectacular failures. Why not all the time? Further, an unexpected success would, for me, lead to just as much deep re-thinking - I wouldn't just adjust my optimism set-point and move on; I'd want the to understand the elements of my success.
Good luck w/ your life, and it sounds like you really care about her. Hope you can tell her you love her or whatever at some point without feeling guilty about it harming her (then again, I'm sure she knows).
Does it have a tail-call->loop strategy? cpython, like JVM, doesn't have TCO.
http://stackoverflow.com/questions/13591970/does-python-opti...
For the sake of whatever competent programmers were already working on the system, I hope this is mostly PR noise.
Thanks for the recommendation. I respect LTU-respected language designers. I didn't know it was 15+ years old.
Stop-the-world might be ok for batch compute work where I care about amortized cost (as long as the GC itself could use all my cores efficiently).
I'd be interested in the debugger experience - since it compiles to C++, I'm a little scared.
MS wants to sell precisely one license but support both never-connected machines and cloud lending, but this was too hard for them to figure out and they're dropping the cloud part.
The cloud lending facility required expiring leases (think DHCP) to guard against the possibility of a purchaser intentionally stranding their license at a friend's house (or on a dead xbox, or one that loses internet connectivity), where that friend would play happily for weeks without connecting to the network.
If you believe in the effectiveness of copy-proof-disc DRM, then a single token permitting ongoing play can certainly just reside on the disc.
How about this:
1. disc alone doesn't suffice to play a game on an unconnected xbox (so never-connected users are out of luck)
2. net connected xbox alone can acquire the right-to-play token as long as the previous holder of the token is online. (physical disc from store would need insertion only on first use to create the initial on-net token).
3. an unconnected xbox that was the last one to use the net token may continue to play indefinitely without net access, provided the disc can be validated. this does allow simultaneous play of at most one online and one disc, but only as long as the xbox stays intentionally unconnected (this limits the number of extra licenses to at most 1, unlike a more lenient cloud-lending policy that allows continued play without check-ins).
I believe the renew-lease-every-24hr model already allowed simultaneous play in case of the last token holder being offline (if the game didn't require a connection to play, that is).
If absolutely prohibiting simultaneous play from a single purchase is a must (and I don't see why it should be; an average concurrency of strictly less than 2 sounds fine), then you just need to require explicit lease releases (and the disc becomes irrelevant again), which has an obvious customer service overhead when people can't release for whatever reason.
Alternatively they could implement a physical 'disc destroyer' that can move a game (one-way) to the cloud phone-home mode. Or just require an xbox to phone home before permitting a new disc (giving up on never-connected xboxes), in which case no physical destruction is necessary.
1. tool support (valgrind, gdb or better)
2. good performance - 64-bit on the major desktop OSes (mobile a plus, obviously)
3. real concurrency
4. libraries
5. build time for large projects ("compiles down to C++" makes me think this could be an issue)
Most new languages fail at several of these, for years. You'll notice that I haven't mentioned language design at all.