skysight-inc/HackerNews huggingface dataset:
The face cards appear to be rendering as PNG instead of SVG. Additionally, it would be cool to render the flip as a CSS 3d transform transition and fall back to jQuery flippy where not supported.

Also, I'm not sure about the mustache.js + hogan.js + jquery + backbone combo. That's a whole lotta libraries for something that would take around 20 lines in d3.js.

I don't mean this to put you down, but there are different ways of thinking of problems and you are approaching an interface/visualization problem from a templating background (which is possible, but not ideal).
seems legiter
sweet designs ill stay tuned for more
i think you did a terrific job here.. some people are just grumpy i think..
real.
Exactly, only you speak much more eloquently and precise than myself. Well put.
> Likewise, you are a programmer. If you are careless in resource usage in some parts of your life, it's likely that you will be careless in your coding.

> The analogy is apt,

No man, I'm sorry, that analogy is shit. The fact that I don't think twice about getting new / upgraded / better equipment means that I care about not having my ability inhibited by something as absurdly cheap compared to my salary as peripherals and a new macbook.

I think you really are looking at the Van Halen analogy backwards: If you, the employer, are reluctant to spend a few more bucks to ensure your investment in my time is as enjoyable as possible, then what other corners are you willing to cut?
Good point. I imagine you would have to find the right balance. Somewhere in the middle of anybody can join, and personally reviewing every single applicant.

I don't know a thing about this industry, but I'm sure if you make the applicant validate that they have a business license, and that they somehow prove their real identity, you could keep fraud to a minimum. Even when fraud does happen, I'm sure a company like Amazon (which you would probably build your service on top of) would return the funds back.
Tim, you have worked hard on this clothing and seems you are making some good progress. keep at it!
I think it's a very good idea. It looks like it could make quite an impact in your, and other people's lives.
one vote from me! I kept listening and hearing "blah blah km", but it doesn't mean anything to me so I had to look up what else is at 200kms in altitude.
Extremely awesome. Love the designs.
Anyone has comments on the implementation?
I have the same love/hate relationship with Factor: I'd love to use it more, the implementation is great, but the shuffling is hard to write and harder to read.
>> there is no reason to test on devices running Android 2.3 or earlier

Umm, not sure I buy this. Per article above (see Google dashboard image), over 55% of Android devices currently use Android 2.3 (Gingerbread) and about 13% use Android 2.2 (Froyo). Your testing plan leaves behind 68% of the Android userbase -- which is kinda huge.

FYI, when I build apps for my clients I tend to support Android 2.2 and above.

>> Use the application manifest's compatibility features to prevent the Play store from showing your app to users running with unsupported devices

There can be unintended consequences to this -- such as for example greatly impairing your marketing message.

Nowhere is that clearer than at a launch event. Say your app is ready to launch and you want to hold an onsite launch event. Based on your Play store exclusions, 68% of the people in the audience will have an unsupported device. Now for the fun part: on an unsupported device, your app simply does not appear in the Play store listings! Zero, zilch, nada, no results -- it's like your app does not even exist to those users. You now have a frustrated event audience, with all enthusiasm drowned out by the cries of people asking you why they can't find your app in the store. Not good.
Answers to your questions.

Execution: Generally no. There are sub-contractors, out-sourcing, COTS, etc. And there may be a program management team of companies.

Software only: The three I've worked on, no. Hardware, software, "mechanisms".

Outside of NASA: Yes, although the US government probably has the lock on the sheer number of such programs. Chip-makers, with fab plants, are one sector. Vehicle manufacturers (planes, trains and automobiles) are another. Construction--especially massive high-rises--is probably another.
Can't wait to see it take off bro!
On the one hand, I’m outraged that these fraudulent practices are being so lightly punished.

I wonder if the author of the article actually understands what the SEC fined this "dark pool exchange" firm for doing.

Dark pools are a growing part of the trading world and are legal but they do not disclose the identity of buyers and sellers. Quotes on securities are not displayed to the public, as they are with major mainstream stock exchanges like the New York Stock Exchange. Participants in dark pools have access to trades that other investors in public exchanges do not

The SEC fine was for "allowing" a dark pool to be not-so-dark. She seems to be arguing that the fine should be higher, which would mean firms would have an incentive to go "darker".

Dark pools are bad for markets. Allowing a select few (the wealthiest select few? why are they pooling in the dark?) to "collude" and thus have significant impact on the price of a security can hurt the ability of other investors to extract their fair value. Why is the general public being excluded from these trades that affect the FMV (Fair Market Value), and more importantly, does this pooling actually hurt FMV?

Maybe dark pools should be illegal. In which case a small fine here makes sense.

But what probably happened is that when this dark pool firm leaked the identities / trades of some of its insiders, those insiders freaked out. And now these dark pool exchange firms have been poked in the direction to "stay dark".

So where are the incentives to make dark trading more light? Can we invent some?

The SEC could reward firms that make colluding dark-pool firms more transparent. I'm sure there's something in the mission statement of the SEC (http://www.sec.gov/about/whatwedo.shtml) that would justify the need for fairness to aid in potential linkage of insider trading of securities that for whatever reason aren't public.

[edited for typos and content]
Las Vegas
* Opportunity- Young community that you can take part in shaping. Zappos is moving downtown and transforming the entire landscape. Money being invested in revitalizing downtown Las Vegas including strong startup activity, growth and investment. It is an exciting time. http://downtownproject.com/

* Quality of life- It gets hot in the summer, but is sunny year round and never gets much cooler than the Bay area. The housing market has collapsed in Las Vegas leaving affordable options in any part of the city. The city has excellent Entertainment and Restaurants. No State Income tax. Beer is served 24 hours a day. Cheap 1 hour flights to SFO.
Yes. I've enjoyed playing around with gambit, but the module system is a huge headache, and the documentation is quite sparse. R7RS, I hope, will at least give a better baseline for a newcomer like myself. (For the curious, C integration and speed are necessary for the project. Gambit is great for this.)
Thanks man, much appreciated.
I agree. Thank you so much for the comment.
I definitely hope it does. Much appreciated.
Would love that. Thanks so much!
Muchos gracias senora. :)
RIP Hans Camenzind, Inventor Of The 555 Timer
mhm cool.
"There's nothing revolutionary about the Falcon series in the sense that there are special gizmos hidden from potential competitors."

This is a common misunderstanding of launch vehicle design. There has long been the idea that "spaceflight is hard", that launch vehicles are inherently expensive, that the only way to progress is through revolutionary, bleeding-edge designs (aerospike engines, SSTO, composite fuel tanks, SCRAMJETs, what-have-you) or "special gizmos" that provide some sort of edge. This turns out to be exactly opposite from reality. The important thing is to have a clean, elegant, robust design which is streamlined for manufacturing. And that's what SpaceX has done. At its heart the Falcon 9 is basically a 6 decade old rocket design. Two stages, LOX/Kerosene. In some ways the Saturn-IB (first launched in 1966) was more advanced because it used a LOX/LH2 2nd stage. But SpaceX has concentrated on streamlining production and on making the rocket very robust (through greater damage tolerance in the engines, the ability to do on-pad aborts, etc.)

And it's this concentration on manufacturing and on robustness that has led to SpaceX's low costs. This isn't something that you can simply bolt-on to an existing rocket design (such as Soyuz, Proton, Long March, etc.) It's a property of the organization, and of the entire rocket design as a whole. And it's also not something that is easy to copy because as much as anything it's about corporate culture and institutional policies and talent.

I'd like to see more companies follow in SpaceX's footsteps but this is something that I think it's unlikely the established rocket makers will be able to do (because it would mean fundamentally reinventing themselves from the bottom up), but I do think it's possible that new companies will come on the scene that are able to match that level of pragmatism and efficiency.
Reminds me of https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/issue... (install script does rm -rf /usr for ubuntu) although I guess deleting /usr/local isn't nearly as bad.
I went into the one in the "Mall of Florida" in Orlando about a week ago.

I went right to the phones because, quite honestly, I've never even seen a Windows phone "in the wild". I picked up a phone and started poking.

The very first words I heard were from a sales person who snuck up behind me and are as follows: "you don't want to buy that". No "hello". No "how may I help you" or "are you looking for something specific". Nope. "You don't want to buy that."

Further questioning revealed that I did not, in fact, want to buy much of anything in the store because "there's a new Windows coming out soon".

So I didn't. Buy anything. Or even hang out. It just felt creepy.
Computer programming jobs in the USA have been in decline since 1990.

Stats from the Bureau of Labor Statistics (USA):

http://www.bls.gov/ooh/computer-and-information-technology/c...

2010 Median Pay	$71,380 per year
$34.32 per hour

Number of Jobs, 2010	363,100

Job Outlook, 2010-20	12% (About as fast as average)

Especially worth a look:

http://americawhatwentwrong.org/story/programming-jobs-fall/

"Over and over, Americans are told that education is the key to their job future. The more education you have, the better your shot at getting a job that pays middle-income wages to take care of your family. If we as a nation are better educated, the theory goes, we’ll be able to compete more effectively in the global economy, which in turn will generate more good jobs for everyone.

But some major flaws in this theory are playing out today in a field that was once thought to have the brightest future — information technology...

...In its 1990 Occupational Outlook Handbook, the U.S. Department of Labor was especially bullish: “The need for programmers will increase as businesses, government, schools and scientific organizations seek new applications for computers and improvements to the software already in use [and] further automation . . . will drive the growth of programmer employment.” The report predicted that the greatest demand would be for programmers with four years of college who would earn above-average salaries.

In 2000, the Labor Department predicted America would have 839,000 computer programming jobs by 2008. The department warned of competition from "programming businesses overseas where much routine work can be outsourced at a lower cost," but was nonetheless confident that "jobs for both systems and applications programmers should be plentiful."
Things didn't quite work out that way. The number of programming jobs has fallen steadily, in part because of outsourcing.

When Labor made these projections in 1990, there were 565,000 computer programmers. With computer usage expanding, the department predicted that “employment of programmers is expected to grow much faster than the average for all occupations through the year 2005 . . .”

It didn’t. Employment fluctuated in the years following the report, then settled into a slow downward pattern after 2000. By 2002, the number of programmers had slipped to 499,000. That was down 12 percent–not up–from 1990. Nonetheless, the Labor Department was still optimistic that the field would create jobs–not at the robust rate the agency had predicted, but at least at the same rate as the economy as a whole.

Wrong again. By 2006, with the actual number of programming jobs continuing to decline, even that illusion couldn’t be maintained. With the number of jobs falling to 435,000, or 130,000 fewer than in 1990, Labor finally acknowledged that jobs in computer programming were “expected to decline slowly.”
"
Stats from the Bureau of Labor Statistics (USA):

http://www.bls.gov/ooh/computer-and-information-technology/c...

2010 Median Pay	$71,380 per year
$34.32 per hour

Number of Jobs, 2010	363,100

Job Outlook, 2010-20	12% (About as fast as average)

Computer systems design and related services	32%

Information	12

Finance and insurance	7

Administrative and support services	6

Government	5

Especially worth a look:

http://americawhatwentwrong.org/story/programming-jobs-fall/

"Over and over, Americans are told that education is the key to their job future. The more education you have, the better your shot at getting a job that pays middle-income wages to take care of your family. If we as a nation are better educated, the theory goes, we’ll be able to compete more effectively in the global economy, which in turn will generate more good jobs for everyone.

But some major flaws in this theory are playing out today in a field that was once thought to have the brightest future — information technology...

...In its 1990 Occupational Outlook Handbook, the U.S. Department of Labor was especially bullish: “The need for programmers will increase as businesses, government, schools and scientific organizations seek new applications for computers and improvements to the software already in use [and] further automation . . . will drive the growth of programmer employment.” The report predicted that the greatest demand would be for programmers with four years of college who would earn above-average salaries.

Computer programming jobs decline

Source: Bureau of Labor Statistics
Credits: Julie Snider, Investigative Reporting Workshop
In 2000, the Labor Department predicted America would have 839,000 computer programming jobs by 2008. The department warned of competition from "programming businesses overseas where much routine work can be outsourced at a lower cost," but was nonetheless confident that "jobs for both systems and applications programmers should be plentiful."
Things didn't quite work out that way. The number of programming jobs has fallen steadily, in part because of outsourcing.

When Labor made these projections in 1990, there were 565,000 computer programmers. With computer usage expanding, the department predicted that “employment of programmers is expected to grow much faster than the average for all occupations through the year 2005 . . .”

It didn’t. Employment fluctuated in the years following the report, then settled into a slow downward pattern after 2000. By 2002, the number of programmers had slipped to 499,000. That was down 12 percent–not up–from 1990. Nonetheless, the Labor Department was still optimistic that the field would create jobs–not at the robust rate the agency had predicted, but at least at the same rate as the economy as a whole.

Wrong again. By 2006, with the actual number of programming jobs continuing to decline, even that illusion couldn’t be maintained. With the number of jobs falling to 435,000, or 130,000 fewer than in 1990, Labor finally acknowledged that jobs in computer programming were “expected to decline slowly.”
"
Evolution tells you that a fossil of a given type cannot be older than ancestral types, and is unlikely to be younger than descendant types. That sandwiches the age fairly nicely.

But if you want a prediction that applies to geology, evolution predicted - long before physical mechanisms were known for it - that specific land masses must have been connected in the distant past. And even put approximate dates on the connection. This lead to endless speculations of land bridges, etc - and also a crazy theory called continental drift. (Which was eventually proven correct.)

There you have it. Relevant predictions in the field of geology which depend in critical ways upon Darwin's theory of descent with modification.

As for slaver ant behavior, you asked for a prediction from evolution. The detailed study of ant behavior was undertaken exactly because evolutionary theory predicted specific behavior. Thus it is a prediction of evolution, regardless of the fact that you can try to explain it with selective breeding. But that said, the time it would take selective breeding to match the exact ratios predicted by theory is sufficiently long that you wind up with evidence of evolution. Evolution further predicts that the actual genetic mechanism by which this behavior is controlled is likely to be conserved across many ant species. I do not know whether this has been studied (it probably has, but I cannot confirm that), but there is another prediction for you.
node is compiled to native code at runtime, and the compiler uses runtime type information to generate that code. C (without LLVM's JIT, of course) is compiled to native code before runtime, and as such, cannot take advantage of runtime type information when producing the code. So in this case, node does have a theoretical advantage.

But to be thorough, one should also compile libmysql's parsing routines with LLVM and turn on runtime JIT compilation, and then write a benchmark that will exercise the code long enough for the JIT to kick in.
Money in the Valley
Maybe they should pivot (slightly, more like adding a new feature) and offer a Kickstarter-as-a-service SDK to products that would fall outside their liability-acceptance zone.

This seems like a natural, albeit complicated and delicate evolution. It shifts the burden from ks on high-risk projects elsewhere and in doing so can put it in the hands of people with experience navigating the niche-fields. It further expands and helps crowdfunding grow; go for it I say.
I really like using Tamsyn, a bitmap font, for my Xterms. I just like the way it looks.
Rasmussen is well known to have a decent conservative slant because of the way they select their population and perform their polling. I'll leave it as an exercise to the reader to decide if this is intentional or not.
When the back is just as gorgeous as the front
Congress has continually cut the SEC's budget at the request of Wall Street. Wall Street has bought off their cops just as much as the Mexican drug cartels have bought off their cops. The only difference is that in Mexico the population understands what's going on, here people don't understand it and probably wouldn't care if they did.
C-like control over the layout of data in memory is provided by the Binary Data proposal for ECMAScript: http://wiki.ecmascript.org/doku.php?id=harmony:binary_data&#...

I think the GC issues and codegen are the most difficult, actually. When the GC bites you you rarely have any other choice than to use free lists, which are always a pain. Furthermore, JS codegen is always complicated by the fact that JS is a JIT, and so many optimizations commonplace in C compilers tend to be skipped in the name of faster compilation. (You would be amazed how many of the common JS benchmarks end up boiling down to compilation speed.)

Despite all of this, however, I'm bullish on the future of JS with respect to performance; it may lose on head-to-head competition with C, but modern JS performance is perfectly adequate even for 3D games and the like.

(Also interestingly, Emscripten works around all of these difficulties surprisingly well -- you get low-level control over memory with it; you never GC; you get LLVM's optimizations.)
Bookbot: Books flowing into new NCSU library’s robotic stacks
btw, though it says that class doesn't start until Oct 08, materials are already up, so log in and get started!
What about a counterparty that just does due diligence? They can dig further and figure out if the team can actually accomplish the task and if the service is vaporware or real.

This could be a simple badge program (for some upfront fixed vetting fee) that lets people say they have been verified.

The problem is that Kickstarter isn't just filtering for viability. Some sort of DD would help say that the project is feasible and eliminate the politics.
I think there are (intentionally) qualities to the game that can be addicting to some people, but that's common of a lot of video games and not unique to WoW - though they do seem to have the formula down to a T. It comes down to the person playing, though.

Me, I can play a video game for 20 minutes and stop and go on to something else and not care. My husband used to play WoW for hours and hours at a time at the expense of work and family, to the point that it was having a negative impact on his health, his relationship with our child, and putting a huge strain on our marriage.

But I think WoW was just feeding the problem, not causing it. I think it was a reaction to a deeper depression and WoW was just something to get sucked into and escape reality.

He stopped playing WoW, switched jobs, and is going back to school, has friends over on a regular basis for some real interaction and is happier than he's been in a long time.

Now he sits down some nights and games for an hour or two after the kid's in bed and that's that, unless we have something else planned, and then he doesn't. The tendency to get sucked in for hours at the expense of all else has disappeared.

I think, in the wrong circumstances, that escape that WoW offers can be addicting, dangerous and damaging, but I think it's less often the game that's the actual root cause of the problem.
Facebook 'likes' automatically being added 'without user-clicks'
Empty set is not equivalent to nothingness. Therefore mathematics can not be constructed from empty set. So reality described by mathematics is not based on nothing.
The Patent, Used as a Sword
I went with PNG over SVG because I wanted to keep things unfancy until later given that SVG versions are much bigger than PNG versions and I've heard rumors of SVG issues on Mobile Safari. Optional SVG support will likely be added later.

Re unnecessary rigging (hogan.js, jquery, backbone), they're there because this hack was original built as part of a larger project. I'll be tearing them out as time allows because they're definitely not needed.

Re d3 and approaching problem differently, I wholeheartedly agree. I'll be happy to use a 20 line d3.js version if someone comes up with one. :-)
> It correlates!

Not extremely well. You've cherry-picked your data to support your theory.

Specifically, I notice you don't touch on those who reject vaccinations, practice homeopathy, or believe Feng shui goes beyond aesthetics.

As someone living in a very large, liberal city and hailing from a rural, conservative town, I can tell you the Republicans of the world are not the ones debating if vaccinations cause autism. The ones I know think it's moronic & hideously irresponsible not to vaccinate your child.
The caveat to this is if your software will be in an App Store, initial bad reviews can effectively kill the product.