skysight-inc/HackerNews huggingface dataset:
There is no standard, but what technologies are you planning on using? Personally I would consider using one of the Lisp dialects because they are so easy at writing DSL's you can even write it so that you have a simple DSL that can drop back to full Lisp as people grow in their ability to write rules. What platform are you targeting, if you are targeting the JVM then Clojure would be a good choice, if it is the .net platform then you may have to look at IronScheme are another variant, but they are not as well supported as Clojure. If you have a very specific platform then you could look at using Common Lisp.

The reason I would chose a Lisp is due to the ability to rapidly write a DSL, so you can build a tailored language for the rules engine further you can rapidly build variants for industry specific verticals, that conform to the jargon of that industry.

My secondary choices would be many of the scripting languages with JavaScript being the top second choice. JavaScript is a good candidate because it is simple to pick up and has a lot of material geared towards the non-programmer.

For me personally I would shy away from any languadge that enforces OO, not because I think OO is bad, I am actually a proponent of OO for certain cases, but rather because OO brings a lot of baggage with it that creates barriers for individuals that are not programming as a primary job role.

Finally, the idea of Rules engines have been great on paper, the promise of turning the power of decision trees over to business annalist but the reality has not been so favorably to rules engines. Most of the time the responsibility of actually writing the rules is pushed right back to the programmer. So the big thing you have to ask yourself is how is my idea different. I am not trying to be the rotten apple in your pie. I just want to highlight that the promise of rules engines has thus far been marred with failure. Which tells me that more people need to innovate in that space. I would just advise you to really question how you are going to deal with that reality. I think utilizing a Lisp is one of the keys to a proper DSL strategy and I think the lack of good DSL's is where rules engines have failed, hence my recommendation.
We're still building out the synonym vocabulary and we do that by analyzing user queries. I added "bloody feces."
I made a web based basketball play drawer. Looking for feedback.
I love House. I'm not sure I'm ready to replace him just yet.
Not excessive as long as Nevada has a complete monopoly ;)
Aren't they are using a lot of client side UI code in order to replace parts of the UI with updated HTML from the server?

They have caching on the server side but that can only account for some of this.

Although in my couple of years of using Basecamp in my previous job, I never found it particularly "snappy" but then I was one user out of a team of five, out of how ever many users they have.
Wow, this is actually quite big. I'd say, more significant than the previous decision by Poland (and then other EU counties) to suspend ACTA ratification. Suspension meant merely that they needed to think more about this. Now Poland comes out openly _against_ ACTA, and that's a _first_ among the participants and signatories of the treaty.

Congrats to the participants of the anti-ACTA protests in Poland (possibly the biggest ACTA opposition in the world), who brought about this change.
Locating Vintage Clothing Is Simple And Easy
I have to agree here. A major problem with client-side json is the need for additional documentation and likelihood of things breaking because of simple html edits.

For example, if you are populating a bunch of divs inside a parent div with the data returned using json, you would describe this using something like jquery selectors. Now if someone else comes and moves around the div during a redesign, he must go through whole bunch of js to make sure his shuffling of the divs around won't break the jquery selectors populating the data from json.

Now think about having a parent div that is simply populated with returned HTML from server-side and it seems way easier than using json to populate the data.
Candy Japan thanks you
Agreed, I have a grid of 4 whiteboards in my office, two are for actual white boarding, one is my open-ended todo list (sorted ideas) and the other is a done list of those ideas.

Anytime I get overwhelmed, I take a moment to review the done list and enjoy watching things shift from one to the other.

When friends come over I encourage them to draw me something fun on the done list which also helps me realize that life is about being happy with things you accomplish, not just getting them done.
The lightbox recommendations from slide 90 are implemented by Photoswipe. I integrated it into OurDoings as you can see here: http://ourdoings.com/brlewis/2011-07

(I assume "clever progressive loading" refers to prefetching.)
Insecure Provable Protocols
Ex-Goldman Programmer Conviction for Stealing Code Reversed
Senators Ramp Up Fear Mongering To Try To Rush Through Cybersecurity Bill
I have had multiple people tell me that my site (https://www.sharelatex.com) has helped with this, firstly more advanced people are able to help learners, also the environment is already set-up.

The LaTeX wikibook is he best place I went to understand the basics of LaTeX http://en.wikibooks.org/wiki/LaTeX
This linked article is good:
the Performance Golden Rule http://www.stevesouders.com/blog/2012/02/10/the-performance-...

(submitted days ago but got no traction)

For years we have been told that we will have to wait on the database so it doesn't matter how fast your implementation language is...

Well it's half true, depending on what you consider your implementation language: server side or client side.

Front end performance matters just as much (or by this article) more than "backend."
How to Detect Dyslexia Before Your Kid Starts School
Google and 3rd party cookies in Safari - Ouch
Google and a few others use interesting tricks to fool Safari into accepting 3rd party cookies even if disabled (as it is by default). iOS and MacOS affected. Don't be evil, anyone?
We've started with the most common symptoms, but are building it out more. We'll add the armpit, thanks for the suggestions!

The AI component is the fact that we train our algorithm based on clinical data from real patients (started with CDC data -- 500k at the moment and counting as people use the site).

I've had bad experiences with the WebMD symptom checker like most people I've spoken to. Try typing in "chills" and you get "Lyme disease, acne, Bubonic plague" (no joke).

WebMD makes money on advertising, so they unfortunately direct you to the pages that are going to keep you on the site for longer. You may find what you have using their symptom checker, but it is really optimized to keep you clicking.
Graphviz is very useful for visualizing large graphs. You can learn to use it effectively in under five minutes. It's also very easy to transform CSV data into graphviz markup by piping it through one or two sed scripts.
DIANNA: Decetralized Internet Assigned Names and Numbers Authority
Postaljs-jquery: a jQuery wrapper for the in-memory message bus, postal.js
I wrote this small library after experimenting with postal.js, in order to make it a little easier (syntactic sugar) to wire up jQuery elements to postal.js. Comments and constructive criticism are always appreciated!
Configuration Settings Are A Dependency That Should Be Injected
Hacking America's Future [Radio show discussion on OnPoint]
This is even worse than the GP I had in my teens. At least he recognised that my headache came from a primary headache condition, and wasn't Hay Fever.
Glad to hear it worked out for you! Unfortunately, for every person that are helped by medical information, there are 5 who are caused unnecessary anxiety. We want to give patients access to data that lets them know when they should be concerned and when they should not be concerned. Microsoft has a great study on this (try Googling "cyberchondria microsoft research")

We're still building out our recommendations, so you can expect ours to also alert people to see a doctor when appendicitis is likely.
Yes I do. At least as long as it is required for them to be signed by Apple issued certificates.

As for the Big Brother reference, it was not name-calling. Apple specifically said we are not like the faceless, nameless corporate nightmare (then IBM, later Microsoft). Apple was different.

And now they have looked their customers computers down harder than Microsoft ever did and have taken from their users the freedom to choose. They have become what they fought against.
I've taught around 20 non-technical people LaTeX. I would say that these are all good tips. But really, the only thing a non-technical person needs to learn LaTeX is to have someone sit down with them and teach them 1 on 1. I have a fairly refined lesson at this point, and can successfully teach anyone LaTeX in 45 minutes to an hour and a half, depending on how quickly they get it.

I've taught mostly undergraduates (while I was one), studying Biology, Chemistry, Linguistics, Psychology, Economics, English, Classics, and Architecture, so I'd like to try to answer the question "Why?"

LaTeX is worth learning if you're regularly writing papers of any length. In all of the disciplines above there's at least one problem with using word that makes composing a paper longer than five pages a huge pain. More often than not LaTeX is able to relieve some of the pain of that process. For example, in Linguistics, sentence trees are fairly easy to create using LaTeX[1], or for a classics paper, being able to switch between typing in Greek or English with a single command is a huge win.[2]

Besides the field specific features, there are a lot of other benefits to LaTeX. It's true that just about every person that I've taught LaTeX to has been a little skeptical at first as to what exactly it could provide. The thing that I tell them is that it is incredibly helpful in structuring their document. They end up loving being able to do an outline with section headers, and fill in the body paragraphs. They like having automatic reference and bibliography insertion, and they love being able to comment out sections of their document.

I think there's also a reason why it isn't hard to teach a non-technical person LaTeX. When teaching someone a programming language, the student will need to learn or already know a fair amount about how a computer works, and what programming can accomplish. With LaTeX, students generally already know how to write a paper, and will be able to easily map that process in to their learning process.

I'm a huge LaTeX evangelist. If you don't already know it, find someone who does, and have them sit down with you for an hour. Ask them to go through the steps of creating a document that has: Sections, subsections, tables, lists, figures, floats, references, and math. By the time you're done, you'll have a good enough knowledge to google for anything you can't reference in the document you just produced. You'll be amazed at how easy it was.

[1] http://www.ling.upenn.edu/advice/latex/qtree/qtreenotes.pdf

[2] http://www.tug.org/texlive/Contents/live/texmf-dist/doc/gene...
I was referring to the "rule" given in the parent comment about not using the word girl in professional contexts (also implied that it shouldn't be used in other contexts, as well). My point is that stating (or making up) such rules without context is not useful. As an example consider the rule "Man must wear ties in a professional setting". Well, there are many of cases where this rule applies, but many other ones where it seems stuck up to wear a tie, you just have to adjust to the context you're in.

As to why the article does not use the word boy:

1. As I said, such terms are usually used as endearment, for the group you belong to. Phrases like "Us girls can program, too", or "Boys, let's go get this YC interview" are common and you cannot replace women and men in these contexts. I think the OP was using girl in this sense in her post.

2. The correct counterpart to the use of girl seems to be guy (although there are phrases like "old boy's network", etc.) mainly, I think, because of alliteration. Some opponents to sexist language are offended by guy, too.

To reiterate my point, as hackers let us think about and then act rather than regurgitate rules that may be dictated by others. Let us not do simple string matching for offensive words but set our regular expressions wide to check the context that words are being used.

P.S. An interesting parallel to this discussion would be the debate on the use of the N-word, which is considered taboo by many but used by others freely.
> "I really don't understand what's so compelling - unless those exact same actions are actually (YAGNI) used as endpoints of a web service"

Well of course it's not going to appear all that compelling after you rule out the most compelling use case.
You were not alone, that I can say.
If Groupon is breeching contractually agreed bonuses with it's employees, why wouldn't they challenge that in the legal system?

On the other hand, "Director of Sales" is already one of the most meaningless job titles that exist.
How does this (http://37signals.com/svn/posts/3112-how-basecamp-next-got-to...) get to be number one, while this http://www.stevesouders.com/blog/2012/02/10/the-performance-... goes nowhere?

Are we upvoting simply by name recognition?

http://stevesouders.com/about.php

He only wrote the book on high performance web sites...

http://www.amazon.com/High-Performance-Web-Sites-Essential/d...
> The advantages of having default arguments is not something that needs convincing. It's just very nice and convenient to have them.

The Google Style Guide disallows default arguments, and I find their rationale convincing enough that I never use default arguments in my own code: http://google-styleguide.googlecode.com/svn/trunk/cppguide.x...
And the other Intel CPUs are from 2004(!) and 2006. I'm not really sure what they are attempting to show by using 8 year old CPU as a reference.
I'm not sure how this article made the front page. The swathes of awkwardly (machine?) translated German and the fact there appears to be several "CEO"s mentioned makes it very difficult to understand.
I don't understand why "it can't possibly be close to as fast"? Is the idea that with client-side templating, you've distributed the rendering?

But returning a cached html fragment is the exact same amount of work on the server as returning a cached-json value. Plus, it's less work for the client to drop the already-rendered html into a container than to have to bind the model to the template.

I feel like I'm being super dumb, but to me this approach is going to result in faster rendering.
>> Please go check out StackOverflow's source code before bandwagoning on this topic.

Please read the article before replying.
How would you go about stealing code from Goldman without being detected?
Re: NHS Direct, I've seen it and agree that it's a cool tool. It's pretty much restricted to triage and doesn't give you a great sense of what you have, though. Also, only helps in the UK. :(

There's a good paper on it that explains most people feel that it just directs them to a primary care physician. We'd like to offer value to those people as well and match them to exactly the physician who can help them (ie OKCupid for patients-doctors).
The iPhone required one in the US, in the sense that you had to sign up for one when you bought it. That's no longer the case, if you're willing to spend $600+ on an unlocked one.
This is where someone on HN developes a remote-system-as-a-service.
Are you guys taking care to send as-plain-as-possible markup from the server to the client and then style it up to keep most the UI development in CSS or are you just sending through raw, styled HTML that gets inserted as-sent directly into the page?

This reminds me of the early days of Java Servlets when people would stream back HTML from inside their Java Servlet code to JSP pages to build it out... made it impossibly hard to edit the templates.

Then the Java world moved to templating engines, but it was still the same idea.

Just curious how you are managing this pain point (I am not a Ruby dev so maybe there is a well-known 'best practice' templating approach?).
I disagree. I work on an app that is entirely client side rendered. We use the JSON data approach. Step 2 is trivial. There are many JS templating engines out there. It takes almost no code. The part that's hard is step 1, figuring out if you have the right data or whether your data is stale. And then, to figure out which part of the UI needs to be redrawn. This is where frameworks like Backbone can come in handy.
What can anyone do about it really? They hide behind the 'is not a monopoly' excuse and there's nothing anyone can do.
The exception is when you're operating in difficult environments, where the cost of putting people there is huge (life support costs, hazard pay, losses, etc.).

Space is the obvious example (manned spaceflight might be a good thing politically, or for inspiring people, but no one contests that robots are far more efficient for almost any mission).

A closer to home example is commercial diving. They used to pay people $100-500k/yr to do saturation diving, fairly frequently, at deep sites. Maybe 3-6 weeks of prep, a ship, a transfer chamber, on-deck chamber, a team of support staff, a team of divers, and lots of equipment. Instead, now, they send down a ROV (usually operated from the ship above, but conceivably these could be centrally teleoperated someday too, or autonomous). Commercial divers are still used for smaller tasks, especially where they're not doing saturation diving, but the saturation diving industry in general has been increasingly restricted to shallower jobs or jobs requiring a large amount of work at a single site (involving lots of manual fitting). For the very deepest dives, ROVs and atmospheric diving suits (basically single-person submarines) have basically taken over -- the deep dive record was set in 1992 and no one has tried to match it.

There's also the EOD market (iRobot's packbot), hazmat environments, war zones, etc., where teleoperated equipment will get more and more popular.
Good point, I don't think there is. I'd expect custom UI tools to be built around the canvas element someday; we might look forward to UI objects then.
This isn't just about computational performance. It's just as much about power consumption. Diamondville sits at about 2.5 watts per core, while the A9 sits at under 300 mW per core, totalling to some orders of magnitude better performance per watt. Should we say that the comparison is unfair because of this as well? We could maintain that stance up until the point where we compare two CPUs with identical processing power and power consumption, but somehow that would defeat the purpose of comparing at all. And for the record, they could just as well have brought the Pineview and Cedar Trail cores into the picture, as fresh as the A9, which might've been more "fair", but very little still would've changed in computational performance.

These tests are really about showing exactly how much you can get out of under a watt of power when opting out of x86.
I find GWT to be the best platform to do full-blown fat client-side paradigm due to several reasons:

1) UI Templating (like XAML)

2) MVP Pattern + JUnit = test automation as part of your build with minimum investment to infrastructure (most JS based solution requires investment on infrastructure)

3) Resource Bundle (similar to Asset Pipelining) cut down HTTP requests

4) Resource splitting (follow up from #3) to reduce the size of the responses when it comes to resources

5) JS binding (like C binding, C++ binding, JNI, etc) to support popular JS library

6) Top Notch Compiler (arguable... but it's there) that can also prune dead code

7) JS switching based on browser's request (IE browser will get IE-specific JS)

8) CSS variable substitution (like Sass)

9) History framework.

10) Flexibility: end point can either return JSON, XML, or use the built-in XML-RPC mechanism (Java only).

The disadvantages are: it's Java and requires compilation.

I like GWT the most so far because I don't have to find libraries or tools that support all of the above (Sass, mustache, various js unit-testing tools, library to merge and compile css/js, etc).

YMMV.
We're actually planning to print some of those at full size as office decoration.
This obsession with self-promoting links is what makes reading sites like BoyGeniusReport and everything in the Engadget family so frustrating.

Editorial rules seem to be that any in-story link MUST be a self-reference to some keyword match inside the site and the only external link (singular) allowed is the one at the end of the article using text like "Source" or "via XYZ.com".
And the big brother reference was Apples own: http://www.youtube.com/watch?v=HhsWzJo2sN4
Fed up with instructors trying to teach him how to think
Workers are actually pretty expensive, more than $20 dollars per hour plus benefits. Then there is the risk of injury which is quite common in construction and mining. The workers in india wouldn't have those problems. To them it would like a video game (no injuries) and their pay would less than $1 per hour, no benefits.
We already have pilots flying drones in afghanistan from nevadda in real time.
The costs of this equipment are not much compared to the labor costs, so outsourcing is viable.
Just curious if you tried using LSM (Latent Semantic Matching) on the titles and/or their contents to determine what you like and don't like. It might take some time to train the data to "your liking" but might return some decent results. I know Apple has an LSM framework in Lion that could be of some use. Just wondering if you gave that approach a thought?
Launching your mobile app at SXSW? Maybe we can help.
Apple CEO: No pressure from Microsoft, PC industry is chasing MacBook Air
Google wins slide-to-unlock patent as Apple battle heats up
Odd how he dislikes both not having a way to create disjoint types and the way provided to create disjoint types (define-record-type).
Maybe execution is everything, but you can't execute something that there's no demand for. Find a pain point in your life and make it more efficient. Go out and ask people if you can follow them around while they do their "business and finance" for the day and see if there's anything that can be improved.
I was just reading a bit about publishing medical research, and a researcher whose department has decided to publish everything in a combination of R and LaTeX, with Sweave: http://www.statistik.lmu.de/~leisch/Sweave/

Their term for this is "reproducible research."
A major politician admits he was wrong. This doesn't happen often, and in spite of Tusk's many flaws should be recognized. He deserves respect for being able to admit he was wrong.
CodeRace: Ryan Carson Wants You To Code... Fast
Beyonce, Jay-Z move to trademark Blue Ivy
Sorry that it's down. Getting a lot of HN traffic.

I tend to agree with your wife (I'm a 4th year med student at Hopkins), which is why I'm building my own.

I think it's easy for websites to just say "if you are concerned, see a doctor" but I also believe that to be the problem. Obviously, if it were costless (time, money, opportunity cost) people would go see a doctor, but they in reality are weighing those costs. We'd like to make it easy for people to weight the risk vs. the benefits of seeing a doctor.

Moreover, for too many people "seeing a doctor" means going straight to the ER. There they wait for 4 hours (nat'l average) and are frequently told to follow-up with a doc anyway. We want to let others know that there are other options (eg urgent care centers) and let them know when such care is clinically indicated.
My suggestion: teach people how to use Markdown and then use markdown2pdf (which first converts to Latex and then to PDF).