skysight-inc/HackerNews huggingface dataset:
100 Days of the Little Lisper
I remember reading that great book 'The Little LISPer' by Daniel Friedman. I really enjoyed it.

With the rise of lambda expressions in C# and soon in Java7, and other developments like the Clojure language - it seems that these ideas are back on the radar, even in the Enterprise space.

This guy is working through the 3rd Edition of book in solving the problems in Common LISP. He's even got twitter updates going on @thelittlelisper. It's be great to watch him finish it off.
It isn't false. RIM didn't deny it loses bars when held a certain way. They were just pissed that that Apple showed it to be true. Apple did show it to be true so there is no false claim.
Huh? Were I to find out that Big Mac is people I would tell the press with the clear intent to damage McDonald’s brand name and profitability. Is that also libel? I would hope, anyway, that true claims are never libel.
I'm in a similar situation - great salary, great people, not so enthused about the company or the work any more. I'm starting to seriously consider taking a sabbatical of some kind too, good luck with yours!

I know a lot of people who can be very happy without caring too much about their job, but that's not the case for me (or you, by the sounds of it).
Simple put: awesome

this reminds me of when I took partial differential equations where the instructor said: "this shit is really hard, so we are going to learn to guess the solution so we can even have a chance at getting close to the solution".
A _lot_ of fruit, vegetables, oats, chicken and beef.
Are they done killing google yet?
I tried it on the 3GS with the antenna inside. It loses bars.
What's a google?
First Post from Android, a Taste of Freedom
It isn't. It's American slang for putting a competitor out of business via competition.
personally I would put the API version as an argument to the URL and I would make it a requirement. Most developers likes strict requirements, no developer likes surprises either.

/api/getstuff?v=1.1&arg1=x&arg2=y

If the version isn't there just return a useful error.

The only downside to this is that it's slightly more difficult to do analytics on the URL requests coming in.
i really like coffeescript.

one part i'm ambivalent about though is assignment and conditionals. there are too many ways to do the same thing, and i sit there wondering whether i'm using the "right" one.
True. My point was that serving static files is one of the easiest parts of a website to scale.
Has this been done by someone? I remember the same answer (use Clojure + Terracotta) being given months ago when someone in the clojure google group asked for erlang type distribution support. I was wondering if someone had actually done it to see how well it works.
Very interesting way to sell a programming language since haters gotta hate. I should have tried it with the programming language I wrote.
The slides didn't make a lot of sense (to me) without some sort of commentary. I presume from the title I'm not supposed to be familiar with the language.
Could you please provide a link to the implementation? I'm really interested in learning how this is done. Thanks.
Just put a version number in the API root -- it really doesn't matter where. http://api.mysite.com/1/ , http://api.mysite.com/?version=1 , etc, anything will work. In fact, you can support multiple styles easily.

Since it's REST, clients shouldn't be hardcoding any URLs aside from the API root. Therefore, if you think a version is ugly, you can make the sub-URLs unversioned for now and version them later if needed.
This is what, attempt number seven hundred and fifty two to create a mainstream language that encourages functional programming?

Incidentally, what's the most successful recent language that tries to make functional programming terser by not having an explicit "return" keyword (everything's an expression)? I'm genuinely curious, and don't think any significantly great number of programmers will ever find this style easier.
Any OS on that early hardware had this problem, right?
They do know and they do have a problem but they didn't address the topic. They deflected the attenuation problem with the Bold and parried by putting the emphasis back on Apple's design. That is how PR works.
There's a difference between being critical and being disrespectful or rude.

And the size of the market is irrelevant. To run with your analogy, the question is whether it is ethical to invite someone into your home to join a support group for small entrepreneurs and then fund a much larger team to chase their ideas once you learn about them. For an organization that aims to support entrepreneurs, this just looks bad. There is nothing wrong with competition, but they should have passed the proposal to someone else to fund.
It was usually used as an ultra- critical section. It would have been fine to simulate it as a scheduler-freeze for that process, preserving the meaning without getting hung up on the hardware implementation.

But instead, Intel decided to try to support actually messing with the interrupt enable state, resulting in years of highly-inefficient "solutions" e.g. trapping and simulating. Sigh.
OK for learning about what has been solved; kind of hacking-101. BUt the exploits involved have all been fixed in the products in that distro. What to use for the advanced class?
Counter-question: How many people have been so trained by decades of terror with multithreading horrors that they can no longer see when it is the right choice when you have a non-nightmare multithreading capability?

When you encounter a new paradigm like this, its very important to work in it for at least a little and give yourself some time to untrain before writing off the usefulness of the paradigm. I work mostly in servers and the answer to your question is really quite a lot. (Unfortunately, I'm in the worst place, I untrained myself and am now able to see where this is useful, but not really able to use it at work. Sad.)

I am reminded of this I saw yesterday: http://www.reddit.com/r/programming/comments/cq6wo/why_dvcs_...
Need Startup Office Space? Rofo Helps You Connect to Brokers
John Valentine? That's childs play! Try having a name like Steve Schwartz, and then you can talk to me about how hard it is to show up on page one ;-)

Actually, I use it to my advantage. I started self-branding using the pseudonym JangoSteve for my web presence. Now, I can go out and cause all sorts of shenanigans, and I don't have to worry about people catching my shenanigans on google, because searching my name will find me somewhere on page 1,243.

Then again, if any of my startups really take off, I imagine that will become less and less true.

But seriously, he does have some good tips if getting your name up there is your thing.
Ruby.

(Technically Ruby does have a return keyword, but it's optional. Same goes for CoffeeScript, I believe.)
ok, so PagerDuty's main focus/differentiation is duty and scheduling management? I do see the value of such system, you want to wake only Joe instead the whole team up if he is on duty that night.

Maybe you should highlight that? My first impression was "what, yet another pingdom"? Definitely need a bit fine tuning there.

Wondering who will be your main target customer? Any website that has more than one sysadmin?
Make your own mini shake light:
http://www.instructables.com/id/Shake-it-like-a-Tic-Tac!/
THey can come after you for licensing. Patents are not a proactical way to Prevent someone from using your technology; they give you a path for getting paid for it.
Not really. You can see a smaller homemade version of the shake light here: http://www.instructables.com/id/Shake-it-like-a-Tic-Tac!/

That could almost fit in a AAA. The capacitor or battery would be the largest part after the magnet/coil mechanism.
Ugh. We know it's easy to intentionally reproduce the problem. But the only data anyone has suggests that, in practice, it doesn't seem to be affecting people much, just like I'm sure deathgrips aren't affecting BB users much. Can we move on from Antennagate now? Maybe talk about Erlang instead?
CoffeeScript isn't an attempt to encourage functional programming so much as an attempt to combine the nice features of JS with a more modern syntax.
Its called Pivoting, which every startup has to learn to be agile at.
It is one or less percent unit more, which means that if the 3GS drop rates are 1%, the 4 has drop rate of 2% which is 100% more dropped calls.

I made some research on this and found http://arxiv.org/pdf/physics/0210022 which says basically that drop rates among 720 different carriers have a lognormal distribution with mean of about 2.4%.

iPhone 4 might have better RF and baseband chain to compensate, but it's clearly not enough when the phone seems to lose the signal altogether.

Edit: Jobs said clearly that the 4 drops ~1 calls more per 100 than the 3GS. 1 per 100 -> 2 per 100.
We also just had to research this as well for our API.
Our solution is based on this - http://stackoverflow.com/questions/389169/best-practices-for...

This would always point to the latest API version:
api.example.com/clients/1/posts

If you want a specific version you do this:
api.example.com/v1/clients/1/posts

Since we're using ASP.Net MVC we could register a 'route' which points api.example.com/ to the API v1 code. Then when /v2 comes out we just point it to that and v1 is still available.
St Petersburg Paradox; Games and Statistical Decisions; RIP David Blackwell
Vinyl LPs are far from being dead, there's a huge (albeit a niche) market.
I've been using CoffeeScript the last few weeks (writing a library using Raphael) and I'm really enjoying it. My one complaint is that the documentation has a few holes - in particular, it took me a little while to work out how to do block comments (### on either end), and more importantly, there's nowhere near enough documentation on cake. Right now my Cakefile uses child_process.exec, which is kind of lame and also doesn't show compilation errors.
Don't do that. Companies routinely introduce routers to load-balance service hosts, and some of their bright ideas include using "Service Appliances"; crap that strips headers.

I had to take packet snippers to XML appliances :-/

API versioning is a good thing, and the best way to choose a version is via a parameter. Don't ever ever try to to encode the version into the security token you return to the clients; someone did that for succinctness, so that you could choose a version once upon connection establishment. It was a nightmare to debug looking at the logs.

With API design, your good design decisions will be taken for granted, and your bad ones will me immortalized in a mountain carving. Try to model it after some existing API that offers a similar functionality, or use an extensible design like the SugarCRM SOAP API, or Zuora's SQL-like one.
I forsee a Half-Life 2 mod consisting solely of people shooting dinner plates through glass windows.
Oh cool, an update to the old Seaman game for Dreamcast.
There are at least 4 things in that video that give it away as 100% staged. Bonus points if you can spot them.
Seems like a generalization. People are interested in evented web programming for applications/services that are less traditional in design - where memcached doesn't buy you anything and NNk requests/second do matter. If you're putting your evented application on an 8-core box, you most certainly want to leverage a good number of those cores.
The internet is Statistically consistent, which is all the attack needs.
The #1 danger to your API's usability is the half-assed implementation a 3rd-party will release to the public without your prompting or involvement. Don't let that happen. Take initiative and release libraries for as many languages and frameworks as you can, or risk the danger of being sabotaged by someone's indifference, or most likely incompetence.

You can't believe how many time I have had problems with an API just to discover the 3 year old client library was using some "sensible defaults" for required arguments.
I read it as a course book in an entrepreneurial course in the university and I liked it from the beginning. I read it all in 2 days...
I'm glad you picked out "everything is an expression" as the characteristic feature. I think that's completely correct -- everything else in the language is carefully compiled to make its use as part of a larger expression possible.

I don't, however, think that it's about functional programming. It's about flexibility: if everything is an expression, you can use any bit of code in relation to any other, and not worry about what parts of the languages are merely statements ... a JavaScript example being "var a = b", which cannot be used as part of a larger computation.

Having every function return a value is something that seems extraneous at first look, but ends up encouraging good API design. From the point of the caller of the function, returning a meaningful value is always appreciated -- even if it's as simple as returning "true" to acknowledge that the operation was completed successfully.
There are many ways to do it.

From an "academic" point of view, the versioning through http accept headers is considered the "best one".

I'm usually going with a path prefix as nearly everyone else does.

As you probably have a lot of API users that don't know and care about http accept headers (and their connection libraries usually don't either), it might be a lot of PITA to convince them doing it right.

So imho you can use the "academic" solution and hire some API Support stuff, teaching each customer the benefits and ways to access versioned resources — or just use the most obvious de-facto standard like /v1/posts/<id>.

That's why I use this compromise.

In Addition, the http accept header versioning allows you to version on each resource independently. This might be a good thing but usually the whole API changes and not only one resource (change as in incompatible change, not an addition of some attributes)
Is "square: (x) -> x*x" more modern syntax, or simply more functional? It surely isn't a new idea, maybe as old as Lisp, and a number of other new languages are explicitly imperative.
Notice a common theme here? Everyone who's worked with IDEA says it's the best, and I agree.

A few years ago, IDEA was even more the-best than now, because the gap with Eclipse was wider. Nowadays Eclipse probably has most of the functionality, but there's still the difference that usually exists between open-source and commercial software. The commercial software tends to be better to use.
I dislike a lot of what has happened with DNSSEC too and try to focus on other things since this seems to be a lost battle. I'm not sure I'm convinced it makes the Internet worse, but I'm certainly skeptical.

That said, one thing I believe you're wrong on is gethostbyname() which does have an error channel via h_errno. It's not pretty and more things need to be defined to correctly handle DNSSEC issues, but there is something there. I agree though, that we're unlikely to find a good transparent way to have this work right with old applications and that's a killer.

I don't share your enthusiasm about SSL/TLS fixing this problem. SSL/TLS has its own issues...
Going Global Requires Staffing International
You can also embed the version number in the API call itself, using a default if not passed or auto detecting based on what is passed.
Look at the javascript page:

http://www.cpedia.com/wiki/Javascript/AJAX_&_Javascript

Is this informative? Much less readable?
It would be interesting to see Clojure's transaction support extended across multiple machines.
Not to mention, it's from 2009
Thanks for the reply; I wasn't sure if you were following this thread. So, if I understand your argument correctly, you're advocating that domain experts create software in high-level languages so that we don't have to write code.

The problem with this theory is that it relies on what I've seen best expressed as "the neat separability of ends and means." This is also the fundamental principle of top-down design, and it's the reason people hire armies of (<cough>Java<cough>) programmers, give them no domain knowledge and ask them to construct the code while waffling about how projects are like houses.

In the real world that's simply not true. Engineering is where ends and means meet and overlap and are reconciled through the process of design. The result is, for civil engineers, blueprints; for software engineers, code. That's why I think you have code on the wrong side of the relation: because code embodies both ends and means it cannot be merely constructed, it must be designed.
About 80% through the post:

Well, I think this whole debacle demonstrates the power of the Internet to report in the wrong way, as opposed to the Tiger Woods incident, which I think demonstrated the Internet’s strengths

Um, what? What kind of person holds the coverage of Tiger Woods up as some kind of gold standard for how journalism should work? It's hard to think of a story that was trashier or more irrelevant.
It's definitely killing Wikipedia in the area of random text generation. Reading Cpedia is like dropping acid and having William S. Burroughs read you search results.
Some hilarious marketing speak here:

"You must first gain clarity about your personal brand"

I chuckled at the pompous language, but it probably is true that "digital dirt" can harm your reputation, and that many people will Google (or DuckDuckGo) you for all sorts of reasons.

So I will now depart to gain clarity about my brand - or just merely return to coding.
A country called facebook
Not dumb — in fact totally understandable — but yeah, that may confound interpretation of the test. Does your GI doc know this?

I'm not fully versed in the art of asking for another opinion, but I think it would be reasonable to get your doc involved. You could basically say that you appreciate the care she's given you and want to keep her as your GI doc (if true) but you'd also like to get another person to take a look at the biopsy sample, since it is obviously a very valuable and hard to get piece of tissue. I'm sure she could recommend another person to interpret the samples for you. I'm not positive that Celiac biopsy samples are kept, but I know that many other biopsy samples are, which is why I suspect that these are, too. At the very least, they should have images of the samples. Based on her apparent discomfort with the procedure, I'm half wondering if there was a misinterpretation, and I'm half wondering if she was unable to biopsy the right tissue; both of these concerns could be resolved by a third party. It wouldn't be cheap, but it has a small chance of saving you from having to do another biopsy.

That said, in the setting of a one week wheat deprivation diet, interpretation probably won't be totally clear even if you did have Celiac, so a second opinion on these samples may well not be worth it.
It's not an offending title in itself. However, virtually all other companies I know of use that title for entry level positions, i.e. for positions that have very little or no initiative. Google's different stance causes confusion among PhDs that apply there, as I have heard from many friends who get irked by the SW engineer title.
int[] a = int[]{2,3,3,4}
int s = a.Sum(i => i)

Thats C# by the way - lambda statements have implicit return statements.

Let me see, Ruby, Haskell and Scala uses this syntac.
They are really comparing apples to oranges in the sense that they didn't talk about the iPhone's design flaw, just RF shadowing which is obvious.

There isn't any phone other than iPhone that loses the signal altogether by just touching one point on the phone.
I like the approach that Peter Williams has suggested. That is to use a vendor MIME media type in the Accept header to specify a required API version. At least your URL stays the same. As it should be, because your resource is still the same.

http://barelyenough.org/blog/2008/05/versioning-rest-web-ser...
If the header is missing you could return a 4xx response. You could document that the header is required or return a message in the response body indicating the cause of the 4xx.
Please namespace your URLs by a version, such as "v1" (not just "1", which looks like a resource ID). If anything, this will motivate you even more to maintain backwards compatibility when you update your API, since there is nothing more infuriating to a developer than waking up one day to find an API call has changed (I'm looking at you Facebook).

Namespacing by version also is pretty "clean." Imagine updating your API in the future without the namespace. You'd have to implement the version in some difficult way (for the end developer) such as during authentication or as a request param or cookie or something ridiculous. This all adds complexity to the developers using the API. Its _much_ easier for a developer to just say "The prefix for all RESTful API calls is http://foobar.com/v1. No developer will say thats not clean.

So please, put a version number in your API, put it at the beginning, and put it in the "vX" format.
Experiments with 'Static' JavaScript: As Fast As Native Code?
Well good luck with that - I am a painter, a photographer, a farmer, a bicycle store owner and a private security guard, etc.

And that is from the google page, above the fold only.
Maybe we could--GASP!--teach them trades based on their interests and aptitudes. The current system is best described by the following Marilyn Manson lyrics:

"Trained to be stupid/Taught to be nothing at all/We're taught to be nothing"
I agree. The alternative examples were a bit confusing. Are they an alternative syntax or just an example of the "compiled" code?
Looking for a tool to help with online privacy? Maybe Abine can help.
Ask HN: The "Launching Soon" Page
Pardon the completely n00b question, but I'm hoping to get answers.

How do you come up with the webpages that simply collect email addresses for beta testing?

I see a lot of sites with very similar UIs:

1. http://ipadinterfaces.com/
2. http://www.nugrove.com/

Is there a simple template that is used to manage beta signups? I know Prefinery is one. Any others?
How To Create Ringtone From MP3 or YouTube Songs Online