It should be located across from Reddit Island though, and smaller. Oh, and everyone on Hacker Island must have a hatchet and a monocle.
Perhaps a cave would be more appropriate.
2,233 karma · joined June 16, 2009
On Lobsters: moderation is public info, and so is who invited who. Downvotes require reasons, and they are undoable.
Send me an email (itistoday at gmail) with your HN profile and temporarily place your email info in your HN profile so that I can verify you.
It should be located across from Reddit Island though, and smaller. Oh, and everyone on Hacker Island must have a hatchet and a monocle.
Perhaps a cave would be more appropriate.
If you haven't seen the movie "Under Our Skin", go see it now. It's all about the insanity surrounding Lyme disease, and basically the conclusion is that you need to find yourself a real expert on Lyme disease, and unfortunately they're not easy to find.
Each core in Knights Corner runs at 1.2GHz, is supported by
512-bit vector processing units, has 8MB of cache, and four
threads per core.
That's 200 simultaneous threads. Wow. That's almost like a GPU. "THEY CAME FIRST for the phone app developers,
and I didn't speak up because I wasn't a phone app developer.
THEN THEY CAME for the flash developer,
and I didn't speak up because I wasn't a flash developer.
THEN THEY CAME for the desktop style app developers,
and I didn't speak up because I wasn't a desktop style app developer.
THEN THEY CAME for me
and by that time no one was left to speak up."
Yep Godwin was right : http://en.wikipedia.org/wiki/Godwin's_law
Neil Ellis said this on June 1, 2010 at 11:01 pmhttp://www.reddit.com/r/IAmA/comments/c9iq1/i_am_a_failed_en...
Roof patrols were also being arranged and nets installed
around buildings to deter suicidal workers, it added.
"If they jump, they'll fall into the safety nets, so
their lives will be saved," a contractor told the channel.
And the surprising bit: But there was no shortage of people trying to get through
the factory gates. Around 8,000 people apply to work at the
factory every day, Foxconn spokesman Liu Kun told the
state-run China Daily newspaper.That's odd, I thought this day was about fighting intolerance, not supporting it.
Funny. Intolerance is being used in two diametrically opposed ways here:
1) Can Muslims tolerate other's rights to express themselves?
2) Can Freedom-Of-Speecher's tolerate Muslim's intolerance?
Is tolerating intolerance tolerant or intolerant?
It seems almost like a koan.
I think the truly tolerant person would be very much like a "stoner" here: tolerating both those who draw pictures of Muhammad, and tolerating (read: understanding) the outrage of Muslims. "OK man... I see you're drawing a picture... OK man... I see you're stabbing that other dude..."
That right there is ultimate tolerance. Holding to no belief in other words.
Where do you find yourself?
"Conventional databases experience disk and user stalls within transactions. Rather than let the CPU be idle during the stalls, those DBMSs interleave SQL execution from multiple transactions during the waits so the CPU is always busy. This is what requires much of the complex latching and locking overhead.
VoltDB doesn’t experience user stalls (since transactions happen within stored procedures) or disk stalls (because VoltDB processes data in main memory). Therefore, it is able to eliminate the overhead associated with multi-threading (latching) and locking. Each VoltDB execution engine is single-threaded and contains a queue of transaction requests, which it executes sequentially—and exclusively—against its data. Elimination of stalls and the need for locking and latching overhead and allows typical VoltDB SQL operations to complete in microseconds.
For single-partition transactions, each VoltDB engine operates autonomously. For multi-partition transactions, one engine distributes and coordinates work plans for the other engines. VoltDB assumes that an application designer can construct a partitioning/cloning scheme and a transaction design that makes a large majority of the transactions local to a single virtual node. Many common applications such as order-fulfillment, software as a service (SaaS), Web 2.0 and trading systems have this property."
http://www.voltdb.com/_pdf/VoltDBTechnicalOverviewWhitePaper...
There are exceptions to most rules, including this one. Consider for example what has taken place with Blender. I know a lot of people who would have been learning 3DS Max (or Maya, etc.), but now know and use Blender instead because that's what they can afford.
And these students don't have to venture forth into The Industry. They can create their own that will topple the existing one. There are plenty of growing startups who would be more than happy to hire someone with "3D Skillz", and many of them don't care what tools they use, so long as the work gets done.
For me, coffee is drastically inferior to the high I get from earl grey tea (most black teas in general). I find that with tea the high is much smoother and lasts longer; if you can imagine a bell curve, it would be wider and with a smaller amplitude, whereas coffee would be narrower and with a taller amplitude.
Also, I've found a 20 minute nap at mid-day with green tea afterwards (about half the caffeine content of my morning breakfast tea) to be much more effective in improving cognitive performance than to skip the nap and rely solely on caffeine. For the rest of the day I'm caffeine free.
</personal-experience-disclaimer>
Though I'm struggling to think of even just one example of a human-created ecosystem designed to substitute for a natural one that's been at least as sustainable as those existing in nature.
Using the newer sys_epoll system call with Knot avoids this
problem and achieves excellent scalability. However, we
have used the poll() result for comparison, since sys_epoll
is incompatible with Haboob's socket library.
WTH? I admit I didn't read the entire thing (just skimmed), but are they actually comparing threads to poll() and declaring victory instead of epoll()? Intentionally? epoll() is radically different from poll(). Nobody uses poll() for heavy-duty event-based servers. They might as well not have said anything at all.I understand the basic idea of how Clojure's data structures work with STM and how they're immutable and how a "new" data structure is created upon mutation without copying the old one. But that understanding isn't helping me.
I don't understand Cliff's version well enough to be able to perform benchmarks in my head, nor do I understand either of the data structures well enough to understand the principles (as you said) to know when to pick one over the other.
So you said that when thread-count > 1000 I should pick Cliff's? Is it that simple? I would suspect not. What if there's only 2 threads involved? I'd just like a generalized overview of which is better for what types of situations, and by all means, to understand the "why" of it would be great too.
Or is the idea that because Cliff's version is mutable and does the whole "conflating state w/identity" thing, that it has no place in Clojure at all?
Does Cliff's approach result in a faster hash table than Clojure's? Is it "better"? In some situations or in all? If so, which?
When would you want to use Cliff's instead of Clojure's built in one? Would you at all?
Stop kidding yourself.
There's the conflict. Your art's success depends on the ability of others to say the same exact thing, in a symbiosis with your art.
Does it not go against the very spirit of art itself to tell other artists that they must paint your way?
I'm willing to believe that as a possibility. As in physically possible. You don't find that at least a little surprising though? Really?