skysight-inc/HackerNews huggingface dataset:
We've been experimenting with this at my office. We use yaml descriptions of all of our routes to generate test coverage. We plan to later generate our documentation and client libraries with the same docs.

Document-generated server behavior is something we're researching as well, to possibly represent business logic. We're hoping that patterns can be found and condensed into notations, like Regular Expressions do for string-parsing. We'll post about anything that we come up with.

One of my side projects us an Ajax library which allows javascript to respond to requests (LinkJS [1]). It has a helper object called the Navigator, which is like a miniature Web Agent. It retains a context, and uses the Link header from the response to populate the navigator with relations. It works out like this:

var nav = Link.navigator('http://mysite.com');
nav.collection('users').item('pfraze').getJson()
.then(function(res) {
console.log(res.body); // => { name:'pfraze', role:'admin' ...}
})
.except(function(err) {
console.log(err.message); // => 404: not found
console.log(err.response.status); // => 404
});

The advantage is that the link header is a relatively condensed representation of the resource graph. As a result, it's not a problem to send it and process it every time. You do gain latency, but the internet is only getting faster, and caching can be used. Meanwhile, the server can rewire links without interrupting their clients.

1 https://github.com/pfraze/linkjs
> This doesn't scale.

Most overused phrase right there.
Actually the article seems to be a bit confused:

> If you aren’t doing ordinal dates, you aren’t doing ISO 8601.

It seems ruby1.9 does implement ordinal dates just fine:

irb(main):002:0> Date.iso8601("2012-012")
=> #<Date: 2012-01-12 ((2455939j,0s,0n),+0s,2299161j)>
irb(main):005:0> Date.iso8601("2012-366")
=> #<Date: 2012-12-31 ((2456293j,0s,0n),+0s,2299161j)>

What it does not implement is the "YYYY-MM" format:

irb(main):010:0> Date.iso8601("2012-12")
=> #<Date: 2012-01-12 ((2455939j,0s,0n),+0s,2299161j)>
We could give a name to the language we use to define such files. It's a language that defines Web services, so perhaps Web Services Description Language? :-) http://en.wikipedia.org/wiki/Web_Services_Description_Langua...

Flippancy aside, maybe there's a need for a next generation of this that skips all the XML headaches after all.
McClure continued: "You're simply the best. Better than all the rest. Better than anyone -- anyone I've ever met." standing ovation
It's because Larry Wall wanted something shorter than associative arrays.

* http://www.nntp.perl.org/group/perl.perl6.language/2007/05/m...

* http://www.nntp.perl.org/group/perl.perl6.language/2007/06/m...
There are plenty of other good jobs that don't require Python. He has already said others like it but it doesn't work for him personally. Why beat it over his head for your preference?
I actually have no idea why the hal people aren't writing hal specifications for existing services right now--it's not quite as nice as "native" support, but the format supports it, and it would be useful to see what a hal version of the Twitter API looked like, for example.
I don't want anymore email. Maybe you can SMS me instead?
"You're being watched. The government has a secret system. A machine that spies on you every hour of every day."
The Cashless Utopia Mirage
I think that ruby, perl, python and javascript are similar only in purely theoretical way.

Python - is "executable pseudoscript". It does not have ruby elegance, perl "worse is better", javascript ... minimalism(?)

I'm using python for prototyping. As communication tool.

I can describe all python scetches to every programmer, be it javer, c-sharper, C-developer or SQL-er.

Can I use perl/ruby/CSharp/Java/F#/Haskel?

Answer is NO.

Perl: sigils, regexp everywhere (when it not needed), parameters passing, "use strict", strange OOP - all those features makes it impossible for prototyping.

Ruby: it's the same as for perl. It looks more pleasant to eyes but it is no way "pseudocode" that everybody can read.

C#/Java - prototyping is a joke. And I can't use sharp-code for javer and otherway.

F# - F# is looking a lot like "pseudo-script". But the main strength - type system is not helping in prototyping.

LISPs - I think that LISPs are good for prototyping. The only problem - they are LISPs.
I was just about to make the same argument. I completely see why this is tempting, but it quickly makes maintenance into a new layer of hell, and anyone supporting your production environment will hate you. Added to which, knowledge transfer becomes a huge problem, and it takes new developers and production support people a small lifetime to learn all the pieces and their touchpoints.
There was a post here a while ago about a language that didn't use 'super' inside subclassed methods, but instead had something used in the parent class method to call the same one in any subclass. I quite liked the idea of that.

Looks like Module#prepend is there to do a similar thing.
The problem I see with lots of software is that you don't have an immediate view of the scale.
Suppose you're opening a random file. What do you see? Are those the atoms or the gears? You want to see the gears but there is usually no map to point you to the gears. The software is the map - yeah, right.

What are you supposed to do? Find the int main() and then make the program run in your head?

I can make an analogy with a car - I don't know every one piece of it but I can infer from the context. The scale is evident.
Palais de Mari is a great piece of music, very accessible considering the style.

is the recording available online, either youtube or for sale?
I love this presentation. So wonderful, precise and valid. I sincerely wish you best of luck for your future!
Why should you teach a child ed(1), instead of any other text editors?
In my opinion , it is one of the most sadistic common text editors in existence, and has been for several decades.
so, define web services as a json file. JSON-SOAP?
> In this world Rails doesn't deliver any particular value (in my opinion).

I beg to differ, though I'm biased. Rails still offers a lot. https://github.com/rails-api/rails-api#why-use-rails-for-jso...
The Case of the Phantom Ballots
Your first paragraph admits that he may not have any control over the pricing and then your last paragraph implies that he does. How did that happen?
Yeah, I wrote it in a bit of a hurry on the train. Will fix.
The article is making two somewhat unrelated complaints:

1. Date.iso8601 does not correctly parse some ISO 8601 formats like ordinal dates or month-only dates.

2. The Date class does not support year-only or year/month granularity.

In response to the first, the documentation for Date.iso8601 (http://ruby-doc.org/stdlib-1.9.3/libdoc/date/rdoc/Date.html#...) says:

"Creates a new Date object by parsing from a string according to some typical ISO 8601 formats."

Not "all ISO 8601 formats," "some typical ISO 8601 formats." While supporting more formats is obviously desirable, the method never claimed to be a complete ISO 8601 implementation. It would be nicer if it were, but would also take more work and it appears that 100% spec support was neither prioritized nor promised.

I believe the second complaint is less justified. Asking a single class (Date) to support multiple granularities opens up a lot of semantic conundrums that have no obvious resolution. What should this return?

Date.iso8601("2012-01") < Date.iso8601("2012-01-05")

If one is truly month granularity and one is day granularity, then the two aren't directly comparable. It would make more sense to me to have the month granularity representation be a separate class altogether (YearMonth?) with easy and well-defined conversions between the two.
It smells like Linux has been here! I can't STAND that guy or anything he touches, so I burned the folder just to be safe. You can thank me later."

This pretty much sums up Microsoft's reaction to Linux in a nutshell. It's precisely why articles like the one we are commenting on exist. The answer to the question that the article poses is "Because Microsoft hates competition and acts like a petty spoiled brat. Get back to us when they grow up."
To prevent a search engine from poking
around links and executing actions
meant from human beings.

That's not how search engines interpret nofollow. You should use robots.txt instead.

EDIT: for details, see the original blog post, which says "those links won't get any credit" not "those links will be ignored": http://googleblog.blogspot.com/2005/01/preventing-comment-sp...
Zo kies je het juiste tuinhuis
Then why doesn't the NRA support most of its members when the vast majority of them want background checks on all gun sales?

http://www.washingtonpost.com/blogs/the-fix/wp/2013/01/31/nr...
Thank you, web designer of scantosecure.com, for blocking font resizing with "Ctrl +". It was extremely small, but the lines became wider than the screen itself as I zoomed in, and Readability didn't work on your page either. (http://imgur.com/a/jawW7#0)

I looked in and saw this:

font:13px/1.7em 'Open Sans';

What is this? Is this causing the text to be unzoomable?
The Settings File Format
Short answer: It would bring Google an incredible amount of grief. 99.9% of everything you read on the web is copyrighted text.
I don't see how writing JSON REST API descriptions isn't practically the same as writing REST API clients anyway: they're still clients, just written declaratively rather than procedurally.

If the point is "stop writing procedural REST API clients and write them declaratively instead" then that advice is by no means restricted to REST API clients.

If the point is "hey, I noticed that REST API clients are another thing that we can now comfortably write declaratively" then OK.
From the bank account. I know Barclays support this. Don't know about the rest.
It’s hard to author by hand. Ever added a comma after the last element in a list? It’s not very forgiving.
Yay, SOAP in JSON!
I like how he summarizes the post he links to as “go out there and do something worthwhile and stop regaling your heroes for their ability to shut up and ship”, and then totally fails to take the point to heart, by writing a gushing piece about TPW and his “ability to shut up and ship”. Obnoxious.
Thank you for reminding me about this. I am going to look into that.
Ask HN: If you could start a start-up anywhere in the world
With the one exception of the US, where would you pick and why? Are there any non-US cultures that really support entrepreneurship, embrace failure as a stepping stone to success, and don't also try to hammer down the nails that stick out?
Index soon to be portable "database-file program" for OS X
It's also for security. If you find a security vulnerability in e.g. the sound driver, you're not going to get root access.

Andrew Tanenbaum explains it well: http://www.youtube.com/watch?v=bx3KuE7UjGA
When I see this post, the first thing to pop up is SOAP as well. Just that SOAP is not human-readable. Then I suddenly remembered that it wasn't SOAP itself that include the schema but the SOAP providers would generate WSDL alongside a SOAP endpoint.
Rails 4 will ship with "1.9.3 required, 2.0.0 recommended," so I'm expecting that to drive a lot of adoption.
Am I the only one who doesn't like receiving direct orders from article titles?
MINIX 3: a Modular, Self-Healing Posix-compatible Operating System
Great product and neat work.
Fair pricing, unlike others who are charging a lot more.

I would definitely use your service for my next client projects.

Feedback:

1. Do whatever so that users will know your app exists in the first place.

First get known to lot of potential users. Let them know your app exists in the first place, then think of Bmodels. Charge little to none!

This kind of app needs more visibility and recognition across the web. Then everyone will recommend and refer your app over-time. It should only get better over time.
So don't charge more. Give it at a throw-away price. Reach all top blogs, top/newly launched products and give them to use free, with your branding. ( Your product is the easiest to get known, because of the nature of the app)

2. Long-term: Build a branding around.

When someone thinks of product tours your app name should be synonymous with tours. Always think this way, and do whatever to achieve this. ;)

3. Add a referral service.

If someone recommends and links back, give them 1 month extra? Don't pay back anyone for referring, but let them use your product more and spread the good message.

* And do reach me out, if you need any kind of help. :)
Please don't do free work for other people. If you want to build something without getting paid, let it be a really cool project that you can call your own!
This attitude is one of the largest problems with open source in my opinion. If people want to try and make money on software, it is their option. It's free for non-commerical use, and the most enlightened thing you could say is "eww"?

People need to eat, and writing open source software to provide for themselves seems like a much better model than doing it for free in their spare time off from some proprietary coding job.
Is it a right to have a Lawyer during a raid? It's not like they didn't have a warrant, and he doesn't have to talk to them during the raid - it's the equipment and evidence they are collecting.
The video is from 2010, but it provides an accurate introduction to MINIX 3.x by Andrew Tanenbaum himself. Version 3.2 was just released: http://news.ycombinator.com/item?id=5272980

Original post: http://news.ycombinator.com/item?id=1494386
Promiscuous -  replicating data across your Ruby apps
Modular design at any scale has a natural tension between looser coupling and higher cohesion. If you split up a large code base into many small parts, each part can be simpler and looser coupling between parts may improve maintainability. On the other hand, now you must to co-ordinate those parts somehow, and making up for the loss of cohesion introduces a kind of complexity you didn’t have before.

This tension exists at any scale, from a single-developer hobby project up to massive enterprise projects and OSS giants, so I challenge the original premise of this blog post that having a large code base is the root cause of the problem. Going too far in either direction can result in absurdity, whether that’s “enterprise software” levels of boilerplate (too much tight coupling) or DLL hell and typical Linux package management (not enough cohesion).
I've thought about it. The question is, should it bulk import everything from your bank account every time you open the app, and you just add labels etc to it/match it up with existing transactions, or should it be separate somehow? Curious to hear what people actually want, rather than what's available now.
Yes. Unfortunately, it did not help with my situation.
Exactly, $45 or $150 is not exactly going to break the bank for a commercial venture. If it is something you need, and it saves you a couple of hours of time, then you're ahead.
The comeback of static typing
It's free for non-commercial projects, so unless you are working on the next Instagram, there shouldn't be much to worry about.
Is there an article named The Dark side of mathematics?
Andrew Tanenbaum explains: http://www.youtube.com/watch?v=bx3KuE7UjGA
By "everyone" do you include the government? This always seems to be the big exception. We've moved in the direction of secretive government that wants to know everything about you, which is the opposite of what I'd prefer to see: open, transparent government that respects basic liberties.
Codequizzes - Free Ruby quizzes
Site Load Test
A practical tool for speeding up your website, helping you to receive more search engine traffic and making your ads perform better.
> it still uses string parsign

This is false, at least after tenderlove did all his work to re-write arel.
Isn't this what http://json-schema.org aims to provide? Or am I missing something. It's a solid spec.
Personally, I prefer django-admin-bootstrapped: https://github.com/riccardo-forina/django-admin-bootstrapped, but the more competition the better.
By Lemer & Company in the patent infringement claim that I received. I am guessing that after GTTA got sued, they decided to settle and license the patents.
Palette Extractor
Find design inspiration with natural image palletes extracted using k-means clustering algorithm.
Upload your image in JPG or PNG format. Then select any section of the image and click "Submit the Selection".
Exactly. In Python you still pass "self" to the method. In Ruby and Dart it's not needed.

In Python I've seen Python users discourage the use of classes. I haven't seen the same distrust of classes in Ruby for instance. It's as though Python has unresolved OO issues. Python could take pride in being "multi-paradigm", whereas languages like Ruby and Dart could take pride in being more OO.

Regarding the C extensions of Ruby, I think the bottomline is that from int, to booleans, to null, to classes, everything is considered OO even in the C code. So common functions can be applied to them even from C, say like Polymorphism would in other languages. From the primitives on up everything is like a high level Ruby. As Python is more "multi-paradigm" perhaps some of its C extension features aren't as OO as Ruby's are.

Funny though that those C extensions that make Python and Ruby so popular end up making other implementations of those languages that target other runtimes incompatible as they don't have access to those C extensions. So even in that regard they are similar.

Say we can't find anywhere in Python where Objects don't exist. Then welcome on board of true OO. Now show OO some love and stop discouraging the using of classes. Maybe drop the "multi-paradigm" approach. I know though that like JavaScript, sometimes you have to live with the shortcomings of the programming language in its support of OO. So while JavaScript could be said to have Objects everywhere, and it truly does, writing classes in JavaScript is not a settled issue. That's why I like Dart instead:

class A {
var aList = ['a', 'aa'];
get length => aList.length;
}

class B {
var aList = ['b', 'bb', 'bbb'];
get length => aList.length;
}

class C extends A {
var aList = ['c', 'cc', 'ccc', 'cccc'];
}

printIt(o) {
print("${o.aList}: ${o.length}");
}

void main() {
printIt(new A());
printIt(new B());
printIt(new C());
}

Result of running it:

[a, aa]: 2
[b, bb, bbb]: 3
[c, cc, ccc, cccc]: 4
"military high command decide"

No, that's what we elect congress to deal with. We do not want the "permanent undersecretary" problem showing up in the US like it has in various other governments around the world. Its bad enough much of the regulation we have to deal with was never voted on by congress after seeing what the consequences of their legislation was. That's where the money is in government and what directly affects the voters.

Congress cannot pass anything over a two year budget because that would be unconstitutional.
Dear industry, if you are going to add comments to JSON, please make it the /* */ variety.
> Are you suggesting that the need to do more than the law says?

No, all I'm suggesting is that Google removes this link [1] as asked by the author of the book. Again, I fail to see what's hard to understand.

> Whatever Google does, the content is still available. It's been posted to Usenet news at least once. (http://binsearch.info/?q=Object+Oriented+Software+Constructi...)

Google is not responsible for others indexing systems, I've never said otherwise.

[1] http://www.imagebam.com/image/e2e9df239055991
It's good to have this kind of drive, but writing replacements for existing tools/libraries because they're flawed, while fun, can be an incredible distraction from the end goal of shipping your product. I know this from experience. It's a balancing act: sometimes it's worth it, but often you'll spend more time writing the replacement than you'd spend using the bad tool.

Tom Preston-Werner is also incredibly lucky that he can write a spec and overnight a half-dozen implementations crop up. I wish that worked for me!
> Morton Feldman (1926-1987) was convinced that he was a major 20th century composer. That point of view put him in the minority. Now, 26 years after his untimely death, people are starting to agree.

It's Béla Bartók all over again. I wonder if there's an unwritten rule in nature that truly creative composers have to die before people recognize the value of their work?

A counterexample to this pattern is Philip Glass, who is receiving some recognition, but by virtue of being recognized in his own lifetime, may undercut his own reputation.
Segment Your Connections For Better Networking
Send email with diff after pushing to Github
Feature for Twitter, Follow, and REALLY Follow.
Getting lots of followers on twitter by following lots of people works well enough, but increases the noise to where you miss stuff from those you really want know about. Let me create a REALLY Follow list that bubbles up tweets from these people to the top and hides everyone else's tweets further down on the page or on a completely different one.
> there haven't been any releases since 2011.

Every commit is a release of rbx. Yay continuous integration!

That said, there hasn't been a numbered release in a while, through there will be a 2.0.
Albert-Laszlo Barabasi talked about this sort of fear a few years ago in his boot Bursts[1]. He figured Google would be the one to do it. Even with dropouts occurring when someone goes into a bus, people's movements tend to have low entropy[2]. Since most people's movements follow pretty predictable routines, over time the system can learn to predict most people's positions given noisy data.

It might not work well for criminals trying to avoid being seen by arial cameras during the day, hiding out away from their usual haunts and obscuring their faces. It will probably be a big win for marketing data analytics firms.

[1] http://www.amazon.com/Bursts-Patterns-Everything-mail-Crusad...

[2] http://www.barabasilab.com/pubs/CCNR-ALB_Publications/201002...
I think there's a difference between forgoing privacy when in public and forgoing privacy when in private. Having anybody be able to see me when I'm on a city street is one thing, having anybody be able to see into my bedroom is another.
I don't know if this is the answer, but I'm a fan of someone trying.

I personally never jumped on YAML or JSON. I liked that they weren't XML, but they each felt like XML++ too much for me. There was still too much, I don't know, weirdness/typing/oops! Don't get me wrong, I think they were better than XML, but only marginally. It would be nice to see more of a phase change type of approach. I'd LOVE to see something like this (or something else) that involves much less typing/special characters/etc than YAML and JSON.

Personal opinion.
An easiest way to get back of your resume
> But I am afraid that the existing solutions have soaked up all the customers

I used to think this aswell, and I was proven wrong. I think this assumption is almost always wrong. Unless you are building a facebook competitor, you will find customers, regardless how crowded the market is.
Oops, typo, updated to say $40.