skysight-inc/HackerNews huggingface dataset:
There is no such thing as "unlimited data", your speed is your cap.

Anyway, it's understandable that your ISP will want to have a talk with you if you push/pull 10+ TB every month (in this case, you're probably violating their "no commercial service on consumer line" rule), but 250GB/month is just ridiculous.
Works with a cookie though.

Still, I'm gonna bet that someone's gonna find a way to abuse this in a hillarious way.
Do you have any examples of how you'd like them to look in the browser? It shouldn't be hard to throw something together with d3 which simply takes an array.

edit: quick example. http://jsfiddle.net/R532h/
> Ranges will only start execution on input of known size and guarantee termination.

`range` can be used to receive values on a channel, which is certainly not a known size and doesn't have guaranteed termination.
How do these commands get invoked, and how do the commands get delivered to the individual cars? Is this something that people can invoke on the official Tesla web site after authenticating to it in some way, or is it something that people invoke on a web server running on their individual car?
ASAP sounds awesome. I mean, sure it should probably be an opt-in thing, but for people with no data caps it is a pretty killer feature. I usually pick a series and watch an episode or two when I get home from work to unwind before plugging in to whatever project I'm working on. If I could get 1080p all the time, I would be so happy. Netflix and Time Warner in general get used heavily around 6pm where I live, so connections are generally shit.

Change it to opt-in and allow users to select what level of clarity they want to cache (720p vs 1080p to save on data usage), and set a cap on the data usage used with ASAP and this is a great feature.
Right, since it has side effects this should be a POST action.
As I understand it, this is not true of RPG Maker 2000/2003 (which is what EasyRPG is attempting to target). Ruby support was introduced starting in RPG Maker XP, which was released after 2003.
I think its worse than that. This invites accidental hilarious fails much more.
Other discussion on this topic here: https://news.ycombinator.com/item?id=7961944
Flower and Bird Candle Holder  bit.ly/TIlceF
It is morbid. It's also a twilight zone episode.

http://en.wikipedia.org/wiki/The_Self-Improvement_of_Salvado...
> it fits in my head.

This. I love Go's simplicity. Coming back to Go code I wrote months ago, I can immediately understand what it does virtually every time, which required lots of discipline I didn't always have in other languages. Lots of languages have obscure corners that allow you to do really cool things that aren't obvious, but for the most part, Go doesn't have these; what you see is what's happening.

Are there things that would make Go a better language? Sure! Should the type system be improved? Yup! One thing that makes me cringe is when I open up library code and see interface{} and calls to the reflection package all over the place, but general solutions often require that in Go, and that's a problem. In practice, though, this is almost a feature: if you see that stuff in code you're reading, it's a giant red flag that this code is tricky and possibly slow, and care is needed.

Edit: speeling
Show HN: Media server built on Railo
> This is unofficial documentation of the Tesla Model S REST API

Very few concepts have been so hugely corrupted to mean exactly the opposite of what they mean as REST. This is probably the least REST API in existence.
or a PUT rather ;P
I would argue that www. domains are easier and quicker to read, as the domain is located in the centre away from the leading /
Yeah, I love the idea, but your last point is true. Not only continuous exposure to the outdoors, but to the rainforest environment! High humidity and plenty of fungi along with the heat from these devices could make them last weeks without some conditioning for the outdoors. I am sure they have considered this, and guess it would be one of the big challenges.
And sometimes, no matter how much you read about interviews, you will suck at it.

Interviews are hard for some people.
> to be fast, memory efficient and also easy to program in.

I think the issue Go detractors have is that it is none of those things, nor is there any pair of those things for which there is no better alternative than Go. If you want fast and memory efficient, you could pick C++ or C. If you want something a little easier to program in, you could pick C#, which dominates Go in all three categories. If you want to go easier to program in, there are plenty of languages like Python that are more powerful than Go.
I'd also like to see some kind of reform for the ridiculous situation created by IRS declaring bitcoin as property without any clear process of accounting and reporting it on your taxes. Look at this: https://en.bitcoin.it/wiki/Tax_compliance ...what am I suppose to do here?

You're supposed to treat Bitcoin just like all other foreign currency is treated for income tax purposes: as property, because it is not currency for U.S. tax purposes. It's not rocket science; the basic principles are generally the same in almost all Western countries and have been for decades.
Part of the problem is that there are multiple parties with multiple definitions of what has become a catchphrase to generally mean "I want fast internet".

The EFF says net neutrality is "the idea that Internet service providers (ISPs) should treat all data that travels over their networks equally" (https://www.eff.org/issues/net-neutrality). That is, without regard to both source and protocol. They specifically list Comcast throttling the BitTorrent protocol as an example of a violation. The people leading the charge against net neutrality are very squarely opposed to the idea of QoS (malevolent and benevolent) at the ISP level.

I have very little issue with saying "thou shalt not different prioritize same-content traffic by originating IP" (provided said sources are actually not engaged in abusive behavior, ie, DDOS attacks or similar), but that's not what most people are talking about when they talk about net neutrality - they're literally talking about dumb pipes which carry and route every packet at the same priority as every other packet, and that's...just not how the internet works. Some packets are more latency-sensitive than others. You aren't really going to care if your BT or Netflix packets have 1k MS latency as long as the throughput is high, but you're really going to have an issue with your VOIP and online gaming packets when there's a 1-second delay on both ends of the pipe.
You can tell by the nicks on the side that they've been diecut - those nicks are created by small nicks on the blade, usually made during manufacture.
Contact your local print-finishers, I'm in New Zealand..
I'd humbly submit that PUT is the better choice. POST is to create the resource, PUT would be better to change its state. I don't want to make a new horn, just honk the one thats there. (PUT is also usually considered idempotent, honk as much as you want!)

PUT /vehicles/{id}/horn

{
"command": "honk"
}
Does that work in most cases? Most communities don't provide APIs. A few will provide RSS feeds - not clear if you can legally reuse them like that?
I agree with you, but I have trouble understanding the right way to implement "commands" like this - I must be thinking about it in the wrong way. How would you design a "real" REST interface for a command like this? What's the advantage a "real" REST interface gives you in this case?
Using a POST request would make sense in other ways, too. The endpoint could represent a timeline of all the honks that have occurred, and by POSTing to it you are creating a honk at the current time. On the other hand, PUT would make sense if you were specifying the time you wanted the honk to occur at as a parameter (and likewise that would be idempotent).
I want to kick you in the fucking nuts for autoloading the demo and not giving me the option to read about it first. You have text there but then you cover it up. Have a separate "Launch Demo" button, seriously.
Moore's law may have expired, but the Law of Lutz-Mutz has promise
Fair point. But on the other hand, Objective-C is pretty much all he writes about. Is it really necessary to mention it every time? I understand that it makes life harder if you come in for the first time, but you did figure it out, and I imagine he writes for his usual audience. Personally, I would say that this is a good case for making the HN title different from (more explicit than) the page title, although I know that that way often lies madness.

Really, I think this is just another example of how we should name everything using UUIDs rather than pronounceable chains of letters.
The URL includes the car's ID number, strongly implying that this is a centralized service running in a data center, not a server running on the car's computer.
POST doesn't have to create a resource; it can also be used to annotate existing resources.

The main problem with using PUT is that PUT is supposed to be idempotent; the result of two PUTs with the same content should be the same as the result of a single PUT with that content. But two PUTs to honk the horn would honk the horn twice, not once.

Since we're all being pedantic about HTTP methods here, we should have a link to RFC 2616 :)

http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html
2014: The Year Extortion Went Mainstream
That's a good point that if you're giving everyone say $20,000 a year you could still set taxes such that for a majority of employed adults you're net zero. So for simplicity you could assume just paying welfare recipients.

The point of doing it this way vs current welfare would be increased transparency / reduced bureaucracy and providing more of a sliding scale of income classes rather than welfare / non-welfare buckets. In principle the costs could be made to be nearly equivalent.
jun 7 and 8 happen to be sat & sun. so it is possible the author was browsing different shows and the tv trying to keep up with it.
Russia Bans GMOs
POST is for anything that isn't actually CRUD, too.

http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-1...

PUT can be creation (not only POST), if you know the URI of the resource in question, but PUT implies that the submitted data should create or replace the resource at that URI, and in the case of a physical horn, this is impossible. I don't think you should ever be able to PUT to something that it's impossible, even in theory, to create with a PUT.
Exactly -- where does something that is designed for "state transfer" get you when the goal is to only temporarily modify a state/send a command that modifies internal state for X amount of time, not really "transfer" one at all? REST maps very nicely to CRUD operations, but not to this.
> However, the non volatile, non unsafe parts of the code were an absolute joy. Testing was a joy, compiling was a joy, and benchmarking was a joy. I was impressed that it allowed me to bypass the type system completely and do nasty, nasty things in the pursuit of performance. I want a language that lets me do nasty things where I must, but that makes the other 95% of the program, and the job of compiling, testing, and maintaining that program easy. Go excels here. Rust, C++, Haskell, Scala will never be good at that

FWIW, I actually think that Rust positively excels at this sort of isolated low-level work due to explicit `unsafe` blocks. Furthermore, the type system is more expressive meaning the need for this is rarer[1].

In my experience, the rest of the language (i.e. non-`unsafe` things) works very well for maintenance and testing, also in part due to the more expressive typesystem, and things like algebraic data types with exhaustive matches by default (I've done some huge bug-free refactorings to the standard library and compiler, mostly due to the compiler automatically catching all the places that need updating).

On the other hand this comes with the cost of making the "job of compiling" more difficult: the compiler complains about more things.

Re testing: there's unit testing and microbenchmarking built-in: http://doc.rust-lang.org/master/guide-testing.html

[1]: in this case, the type system positively designed with making this sort of concurrency safer.
"Patent trolls" are not the main problem of the patent system, but patents with low or no invention height are the main problem. Also software and business models as such should not be patentable at all -- that just over-stretches the system.

Some times, I have the impression, that patent trolls are in the mouth of everybody to cover the fact, that they are more of a symptom than a real problem.

With bad patent-troll legislation, it could be possible to make things bad for legit inventors. Just think, somebody has invented something and is seeking investors. Now comes a big corporation and steals his invention and builds it. With a patent reform that does ignore such people, he even could be blocked to defend his patent (what is currently difficult enough, because he needs much money to do that).
I can see that you're a bit out of date on these issues, so let me inform you:

1) No, your speed is not your cap. Net providers are increasingly implementing "soft caps" that they don't tell you about when you buy the service.
2) If you think 250GB/month is ridiculously low as a cap, go try to use 10TB a month with most providers and let me know what your results are.
I can't wait for somebody to hack this and make every Tesla on the planet start honking at the same time. (Presuming there's a 3G hookup of some kind going on here)
(That said, they should definitely use POST here!)
One of the most famous planned, corporate-developed communities in recent memory is Celebration, FL, originally developed by Disney. It's got a very Stepford feel to it. Almost like living in Main Street, USA in Disneyworld or Disneyland. Some people dig that, though. It's not unlike the community mentioned in this article. I wouldn't want to live there, but I can see the appeal to those who would, and I don't begrudge them their tastes.

A little less extreme are some of the privately planned cities in Southern California, like Irvine or Mission Viejo. These are generally affluent "commuter cities" whose governments aren't necessarily privately run, but whose majority landholders (and de facto bosses) tend to be the original developers.

I'd say the jury is still out on how successful these projects have been.[1] The SoCal privately planned communities have done pretty well for themselves, but they've benefitted tremendously from the expansion of the city, services, and infrastructure around and between them. It would seem much harder to make an isolated, self-sustaining community work.

[1] As cities, that is. As corporations, they've done phenomenally well for their developers. The developer of Irvine is worth about $14 billion, which puts him in the running for richest man in Southern California.
Do teenagers really act crazy?
When we see children drawing on walls, we don't say they are crazy, we say they are children.

I don't remember acting crazy in my teens. In fact, I think I'm the same boring self that I was years ago.

What I think many adults are victim of, is being encapsulated in a little set of habits and behaviors, with the expectation that everyone else will follow the same rules.

Thus, when one sees someone old enough to not be a 'child' anymore, it's expected of them to immediately follow the same habits (thoughtless actions) then everyone else.

Well, it turns about that many habits are completely non-intuitive (and perhaps even irrational). For individuals going through the motion for the first time, they might pause for 2 minutes and try to understand what's going on, without ending with the same conclusions as everyone else.

If everyone was acting crazy, how would someone not acting like them look like?
Our infrastructure _is_ up to snuff. This isn't a technological problem. The problem is that our net providers suck and don't want people to use their service to the full extent of its capability...at least not unless they can charge them a LOT more for that.
I thought the port would take care of this
Canvas is bitmap-based, while SVG is vector. If you need to print the chart SVG is going to look a lot better. Also, if you pinch-zoom the chart, SVG is going to look better. Canvas doesn't support animation -- you have to code it yourself. SVG performance is quite good unless you have thousands of elements, which a chart isn't going to have.
If you truly care about speed you'll have different optimizations for int32 and int64.

Depending on who you are working with, the lack of generics is a blessing. Some developers can't restrain themselves and create over-complex abstractions that are used only once.
I humbly submit that using PUT is wrong. Argument follows, citing wording at

http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html

First of all, we're not "enclosing" an "entity" to be "stored" or "accepted", so neither HTTP verb is strictly appropriate.

PUT requests are for uploading a resource, and the uploader specifies the desired final URL. So PUT is only appropriate for creating a new horn. Relevant quotation:

In contrast [with POST], the URI in a PUT
request identifies the entity enclosed with
the request -- the user agent knows what URI
is intended and the server MUST NOT attempt
to apply the request to some other resource.
If the server desires that the request be
applied to a different URI, it MUST send a
301 (Moved Permanently) response; the user
agent MAY then make its own decision
regarding whether or not to redirect the request.

POST requests, by contrast, are sent to a handling resource, which decides what to do. POST is appropriate for several purposes, including "annotating existing resources" and "providing ... data ... to a data-handling process". Seems like a better fit.

But either way, REST is for documents (understood broadly), and I don't think I know how to understand "document" broadly enough to cover a horn. So it's gonna be a rough stretch, and in general, I'm skeptical about the value of applying REST semantics.
Ahh. Good point. I was considering PUTting the horn into the honking state vs POSTing horn honks for execution. In the first case, 2 PUT honks would just result in a honking car, in the second, 2 POSTs would get you 2 "honks" whatever those are defined to be.

I guess I was thinking of the idempotent "panic" button on my cars key fob.
If anyone ever manages to penetrate the central VPN server which Tesla uses for its cars, this will be total mayhem.

Also, which server are they using? That alone is an interesting fact, as it has to support tens of thousands of simultaneous connections...
> put anything you want in it, then assert the type of what comes out

... which is exactly what the article mentions and criticizes?
Something that involves this possibly?
http://www.paulhammond.org/webkit2png/

Might be overkill, but would allow quite a bit of flexibility.
Not fast enough yet:

http://tools.ietf.org/html/draft-hoffman-httpbis-minimal-una...

http://tools.ietf.org/html/draft-nottingham-http2-encryption...

http://tools.ietf.org/html/rfc7258

So, it turns out, someone IS finally seriously working on opportunistic encryption for HTTP like STARTTLS is to SMTP!

Looking very forward to when it'll hit the streets!
Yup.

SmartAsset (YC S12) has an awesome calculator you can use to play with various scenarios: https://www.smartasset.com/infographic/startup
The Economics of Long-Term Digital Storage [pdf]
Here's Roy Fielding's summary:

http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...

After reading this I cringe whenever I see any API claiming to be "REST(ful)".
The general idea is to render the chart in a headless browser and grab a screenshot.

http://phantomjs.org/screen-capture.html
> A lot of people mean different things by systems programming.

Actually, no. It meant one thing until Go proponents tried to market their language and realized that their target audience didn't actually care.
Right. REST is about Transfering the State's REpresentation. In this case, we want to transfer an event ("honk!"). You could argue that we want to transfer a state transition ("begin honking"), and let some other process (the car) handle the next transition ("cease honking") independently, but that's forced, and in any case it's not RESTful either.

As far as I can tell, REST is appropriate in very few cases.... although it IS appropriate for more cases than it might first appear.
Thanks, currently writing that google doc.

Combining customer support with a buyer role in the same person is interesting, hadn't considered that before.
Monadic futures are a fairly effective solution to the problem.

No callback hell, just a clean linear flow of imperative looking non-blocking code that runs concurrently but still guarantees order of execution.
Sure, but maybe you could think of POSTing to /honks as "creating a honk."

This would make sense if you wanted to GET /honks and see a collection of previous honks. (Modifying an existing honk doesn't make sense, so we wouldn't have to worry about it.)
It would be a pain in the ass to turn the wifi on/off frequently, but they take a wired connection. You can't use the Fire TV for anything at all without an internet connection so it's probably not viable.
> Lack of generics is part of the reason why…the Go compiler is faster than, say, Rust.

The speed of the Rust compiler has little to do with generics and everything to do with LLVM and its optimizations and code generation. (Run with -Z time-passes if you don't believe me.)
I put that "are you still active" there, because sometimes when I visit older websites I wonder if they are still in operation. I guess I could show that more indirectly by just showing recent content.
Not quite - I replied to a comment just underneath yours that has been deleted. It was something along the lines of "don't start a content business, investors HATE content businesses".
Doesn't it depend on the level of abstraction you see? The URI of the horn is known. The document is { remainingDuration: 1 }.
Haskell is nothing but indirect action (lazy evaluation...), which is why referential transparency is so important to the language.
7 Things About Apple’s iPhone Launch 7 Years Ago
Yeah. I think I like the bullet-point associations because I can provide a more abstracted index word and associate it with a point in the conversation, versus having to do a text-search, if that makes sense.

It wouldn't be hard to throw something together, either. Really I just need it to pull a timestamp from the recorded audio after every word I type and associate some meta data and the timestamp with that word location.

Might be a fun after-work project. I'm sure there are already solutions like that out there, though
Very nicely made but may give the impression that you need a specific setup/computer to be sucessfull / get things done (forget it, I won't say what it is!).

So, for me, the only insighful interviews are the ones w/ "strange" or "forever unsatisfied" people.
Free Mobile... when Android is not enough [pdf]
You call it misleading reporting, but don't actually explain what was bad about the legislation he's opposed or how it could hurt industries where the patent system works. Not saying you're wrong, because I don't know the guy's work, but you haven't actually said anything to convince me.
You would use RPC.
Is Startup Transparency Essential?
Yes, there are several Brazilian subscribers. Delivery is about 3 weeks after each shipment (which go out on 14th and 28th of each month).
I don't know the whole state of the vehicle. I don't want to. So I'll use PATCH. I know I want the horn to be in a honking state and remain in that state for 1 second. The implementation is responsible for doing what it needs to do in order to get the resource into the state (or differential state in this case) I told it to take.

I'm not usually in favor of nested API design, but complex resources like cars make sense, so:

PATCH /vehicles/{id}/horn
{
"enabled": true,
"timeRemaining": 1000
}