skysight-inc/HackerNews huggingface dataset:
Uh, the point was that the definition of "property" not only changes over time, but that it can change quite radically.

The idea seemingly lost on you is that while property in some sense has always been fundamental to civilized orders, it has encompassed very different things in different times and places. Indeed, this remarkable flexibility may be the key to its endurance. And this vital flexibility is EXACTLY what anti-reformists try to obscure, deny, ignore, or otherwise wish away when discussing IP.

In their conception the invention of the Internet is irrelevant. They portray the current scope of property rights as rigid, fixed, ever-lasting, and absolutely supreme. And this particular stalling tactic is nothing new. In fact it's appeared time and time again - really, any time that society has evolved in a way that demands a fundamental reconsideration of what is and is not going to be viewed as private property, with its protection provided by the full force of the state.

Of course, the people who take the absolutist view don't like to discuss this history in detail. And why would they? Saying that the current configuration of rights - which evolved over time - cannot be allowed to evolve any further is a conspicuously indefensible position. So when absolutists raise the issue of "property rights" they are not trying to add anything to the conversation. To the contrary, they are attempting to shut it down. The hope is that residual deference to the once-sensible bounds will kick in reflexively, and people will suddenly stop talking about things that are certain to harm their economic interests and / or social standing if discussed openly.

And that pattern has been a consistent problem every time society has felt the need to redefine property rights. When confronted by the kinds of dishonest and self-serving assholes who would try to shut down or derail conversations of this nature, it's important for people to recognize who and what they're dealing with, and what kinds of tactics will be used against them. It's equally important for them to remember just how threatening and powerful open conversation really is, and why it's protected by the 1st Amendment.

I maintain that the conversation surrounding property rights in America circa 1850 is likely to contain an enormous number of parallels with the conversations surrounding IP today. For people looking for a roadmap on how to handle the recurrent problem of inflexible absolutists, it's a fine source. And it's not the only place where they can find echoes of the same losing arguments about maintaining outdated but profitable arrangements. Indeed, I strongly suspect that close variants of the same arguments will appear in every case where the scope of "property" has become a bone of contention.

Regardless, if you still think there is anything "unserious" or even "dishonest" about this perspective, please elaborate.
What's impossible is suddenly western standard living

Why do you, and others, keep bringing this up as if anyone asked for that?
Yup. We wasted a considerable amount of time going for silly optimizations like this when we should of been trying changing the entire copy and layout. It felt like we were doing something when in fact we were just spinning our wheels.
C++ is great if used with care, the problem is that it has too many features and many things are quite braindead. Features are hardly ever removed (I like the Python approach better) But for complex, high performance applications it is still the best choice.
There are two aspects to discoverability: A) listing all of the operations, and B) getting detailed method signatures for a particular operation.

A) is a noble idea but so far few people need to automatically discover and consume web services. B is the real issue: something like SOAP was necessary to make RPC possible over the web for typed languages like C# and Java.

REST was a counterargument made by some people coming from a dynamic languages standpoint who really didn't need as much information as the statically typed language people. Its too bad that people have taken A so seriously though and gotten confused or misled (probably deliberately) about what SOAP was for and then tried to make REST into that.

The most convenient and useful API, even over the web, is one that is as close to normal programming as possible. In other words, RPC-style (or some improvement on that like NowJS). That doesn't mean that you can or should forget that you are making remote calls, it just means that you have less other unrelated plumbing to think about.

If you want to do RPC in a dynamic language over the web, NowJS is your model. The problem is that dynamic languages and statically typed languages have different requirements. I don't think that either SOAP or REST are a good solution to making the two styles work together on a web RPC. I think we need to work on that more.

I guess one more thing complicating this is the fact that most APIs (just like most software systems in general) are in fact dealing with the standard create, read, update, delete operations on data, with some variations. Batch updates are the most common variation, which you could actually easily extend the CRUD model for. The thing is, you almost always have important deviations from that where the CRUD model doesn't fit. But regardless of whether you are doing CRUD or something else, you still want your API to be as simple and normal as possible and that means RPC.

Maybe as some point we can focus more on languages or frameworks that better integrate the CRUD concept and things like calculated fields and aggregation, and transparently handle tasks like persistence and shared state.

Just about all of the programs I write need to persist their data and transmit/share their state. Maybe we want a semantic data oriented networking programming system (or more of them). This would be inspired by dynamic languages like JavaScript but necessarily incorporate some kind of typing more integrally (inferred?).

Maybe just start with NowJS, bake in some kind of CRUD generation based on nested schema definitions, put that on the server, add a way to indicate that operations need to be batched (for transactional consistency and practical network performance) and make the nice MongoDB criteria and now aggregation stuff baked into the client-side also. That would be cool (much cooler and more useful than me thinking or caring about HTTP PUT or DELETE).
Of course C++ can do what Go and Rust do, C++ can do everything, but that is the problem with it. C++ tries to do everything and it leaves it not being very good at nearly anything. Also, C++ code-bases are all using different subsets of functionality. It makes becoming a product commiter to a code-base to longer than it should.
Micropayments support would be wonderful
Right, but it was, from the get go, a knock-off, right? They didn't really innovate, they just tried to copy something that was successful (Flash), which most tech people hated (high CPU usage, annoying plugin updates, etc), and which was clearly going to be replaced by better, more open, more universal standards.

That's what's worrying. The "best and brightest" just played follow the leader to nowhere.
London, UK. Full time.

Designer & Front-end Developer at Newspaper Club.

http://www.newspaperclub.com

We help anyone make and print their own newspapers. We believe the web is too important to be left to screens, and that newsprint is a highly evolved technology too. We build things that combine the two, using each medium for what it's best at.

We're looking for a great designer + front-end developer to work alongside our co-founder and engineer (me, @tomtaylor) and form the start of a tight knit development team.

We want to overhaul our existing in-browser newspaper layout tool + API, launch a print-on-demand marketplace, and develop a number of products and services that use completely personalised newsprint in smart ways.

Things like the Postcode Paper we built for Data.gov.uk. http://blog.newspaperclub.com/2009/10/16/data-gov-uk-newspap...

Or the prototype Telepaper, which turns Readability + Instapaper content into a delivered newspaper. http://telepaper.newspaperclub.com/

You'll need to be able to go from sketches and conversation, to working code in browser yourself. We like generalists who can think both like designers + engineers, with a good sense of product intuition. Someone who can code their own designs, and enjoys working closely with a backend engineer.

Bonus points if you have a solid understanding of how to build well structured Javascript web apps, using frameworks like Backbone.

You've probably got a few years experience working on public sites, either for yourself or others, and can show us sample projects you've worked on. We value code over experience, so show us what you've done.

We run a small, friendly ship, in a relaxed environment we share with interesting folks in Shoreditch. We've got a proven business model, and are generating real, actual, genuine profit, with very little investment. We're doing this on our terms, and building the kind of organisation we'd like to work for.

All of which, I'll be honest, completely astounds me.

In return, we can offer a competitive package of salary and equity, in varying proportions.

If you're interested, drop us a line at jobs@newspaperclub.com, with a note about yourself and links to things you think we'd find interesting (eg. Github account, CV, portfolio).
Ergotron: http://www.ergotron.com/
As tempting as it might be, no. I would never do this. Not only is there an issue about professional trust, but it's a vulnerability that you're deliberately building into a system.

I know that it's hard, but if you suspect that a client isn't going to pay you, don't do the job. There's no point in 1) doing the project and hoping (if they don't pay, then you're not only not getting that money, but you're losing time that you could have spent looking for more reliable clients), or 2) wasting time building in vulnerabilities and then charging the client for the privilege.

If you realise after you start a project that a client may not pay, talk to them about it (in writing/email), and either cut off the project then (once again, no point throwing more time at a bad client), or take them to court (even just small claims court).
Ask HN - why is ISBN so expensive, compared to a domain name?
This is a question for those who've written and published books on their own. Just saw the prices for ISBN - at isbn.org, it is 125, I didn't expect it to be this expensive. Isn't it the equivalent of domain names, to books? Why does it have to be so expensive?
Half the memory, with ECC. Since 16GB is pretty sufficient for my needs, I think I'd use the extra 16GB for pure caching. (Riak has an in memory mode so you can run two backends- one backed by disk and one not backed. Using the in RAM one gives you a distributed cache over a bunch of machines. If you keep 2 copies and you have 4 machines, that each have 16GB dedicated to this in memory backend, that gives you a 32GB of distributed cache where any item in the cache is at most one hop away.)

I recently tried to research what ECC means operationally (I'm not really an operations guy.) Is ECC good for correcting bits flipped by cosmic rays? Or is it going to tell you that memory is failing? I've never, in the past 20 years, had memory fail on me over time.

Also, I'm not going to be running a single server such that if a server goes down my service goes offline.

I'm running a Riak cluster, of at least 3 nodes, maybe 4 to start. If any server goes down, the service stays online.

My software architecture is, near as I understand it, well suited to commodity hardware.

The 10 euros extra per month, on 4 servers is 40 euros, which is nearly enough for an extra server.

So, wouldn't it be better to have 5 commodity servers than 4 servers with ECC?

I wouldn't know what to do if I started getting ECC errors anyway (I know, I'm stupid, but we're a startup, no budget to hire an ops person.) I'd probably just ask them to give me a new machine.
What syntax should one use to define link relationships in a RESTful service?

Most of the examples I've seen extolling the virtues of HATEOAS use XML, specifically the <link uri="..." rel="..." /> element. That's great for a single media type (XML), but what about JSON, which is by far the dominant media type used in RESTful APIs?

A google search for "hateoas json": https://www.google.com/#q=hateoas+json&fp=1

reveals...a bunch of people asking how to format link relations in JSON, without a definitive answer that I can see.

HATEOAS and discoverability are principles that sound great in high-level discussions but I have yet to see them implemented in a meaningful, helpful way.

Anyhow, you seem quite knowledgable on the subject so perhaps you can enlighten me. Usually it's my own ignorance/obstinateness that's to blame rather than a flaw in the concepts themselves...
Converting light to sound in cold quantum systems
When starting out with backbone.js I also had a difficult time just using the documentation. Backbone is kind of the opposite of other popular MVC frameworks in that its un-opinionated, it doesn't enforce any strict organization which gives more flexibility but also makes it more difficult to learn.

What worked the best (however not optimal) for me was to combine the techniques used in the PeepCode(https://peepcode.com/products/backbone-js) screencasts and Thoughbot's book (https://workshops.thoughtbot.com/backbone-js-on-rails). Once you start getting in the groove of things the documentation is actually really good for quick look ups and you'll start to see that the framework is actually surprisingly tiny.

I also have a couple sample apps up on github that I used to learn backbone if you'd like to see some more examples:
https://github.com/jwarzech/inspire_board
https://github.com/jwarzech/realtime_hn
I noticed you put HD and SD lessons in the same feed on ITunesU, imo providing two versions of the course as the Stanford guys did is a better idea.
As a developer i love Git. I love its speed, its decentralized nature, merging, branching. I even love submodules. We use git to deploy with - github hooks lets us auto pull from all our ec2 servers - changes are globally available in seconds.

As a collaborator i think it has failed us. I simply cant convince non-programmers to learn it. People who only occasionally use versioning systems simply do not need as much control. They need a much simplified layer over Git - that prevents them from screwing up . I have tried SmartGit for this - not simple enough, it still exposes the complexity.
Is there a way to report broken links?

http://www.curvio.com/glee/season-3/episode-10/yes-no/quinn-...

Clicking the sweater would normally take me to an online store I assume, but on this page it leads to a 403 on the J. Crew images server.
Translucent Blue Spheres Rain Down in the UK, Mystifying Meteorologists
I think what you're hearing me express is skepticism that the (self-appointed) elite that makes standards or writes dissertations about architecture is in any way the final word on what constitutes the web. Without the hundreds of thousands of crappy applications that actually populate the web, it would be an academic exercise.

Regardless of what the RFC says, the CGI interface that provided the foundation for the original wave of web apps was just a series of getenv()'s. It was absolutely not the case that web developers in 1995 were careful to make sure that they represented state consistently or provided discoverable resources. Then as now, most web applications (and APIs, where they existed) were black boxes with parameters defined by expediency.

Also, even Fielding doesn't claim that RPC interfaces are wrong. He seems to have a much bigger (and more reasonable) problem with people pretending that RPC interfaces are REST. There are plenty of interfaces that make just as much sense in RPC as they would in REST; it's not unlikely that there are plenty of them that make more sense expressed as RPC.

I also don't understand the emotional appeal. CORBA vs. REST isn't a moral issue; people who sacrifice their health to make sure we're not using SOAP have their priorities screwed up.

(Thomas, please, btw).
Free PSN Card Codes 2012
I understand a lot of people are unquestionably hoping for this is what unleash. You shouldn't that can with consideration look for everyone to uncover the PSN Greetings card Laws . Best PSN Codes is presently offering and i also is certainly giving out back to you throughout the next step put up.
And half the technology you and I use everyday would not EXIST if there was no Israel. If you like, you could think of Israel as a global R&D facility.
This is not just for testing SQL (which it could be handy for), but for sharing. Suppose you have a scenario where you have a few tables, and you run some SQL and it's not giving the result you expect. You can create a SQL fiddle, post it on your favorite Q/A site, and other SQL experts can quickly tweak your SQL to work right, and share the result back with you.

I'd use this tool.
Exactly, I just updated the post with examples of why slice and elemMatch don't work.
Archiving is for discovery, backups are for recovery
Right. Even X11 got ported at some point, so there is not really a reason why it wouldn't work other than lack of interest.
Thanks!
1) fixed, I guess I wasn't really thinking of others using it
2) Duh!
Agree with other commenters, re: more important things to spend your time on than this list, but WHOA.

I'm borderline offended that this article would claim that getting social media accounts for your Startup would come after ANYTHING. For me, checking availability and reserving social media accounts comes all the way back at "what should I name this thing" and am searching for domain names. Sure, some are vastly more important than others (Twitter, FB), but holy moly. And of course, picking a name comes WAY down the list after finding a business model and some customer development. But, when you get down to picking a name...

Getting/reserving FB/Twitter accounts should be part of the process in choosing a name and domain (Branding!). I've heard of bots that will try to grab your Twitter handle as soon as a domain is registered with that name.

Netflix showed this importance of this with the weed-smoking Elmo and the @Quikster fiasco.
India's premature $50 tablet little better than a prototype
Or use postgres. Whichever.
At least in the start-ups I work at, the team, who should have access to all the version-controlled files, is more than just developers.

There are the bosses who want to do a quick wording change, there are the wording guys, there are the designers changing images, there are the HTML people, there are the operations people, there are the translation people who are entering Arabic or Chinese strings into the translation files.

If they are not able to do these changes directly, they all have to go across a programmer's desk which is a waste of their time. Further, these other employees are not as empowered as they could be, to do changes themselves.

Sending such things to the developer as email attachments, meaning they have no idea which version had been changed, isn't this exactly the problem that version control was designed to solve?
ok..so instead of x- ..what should we be using for none standard header?
Not really an SQL tool, but if you use a lot of SQL then maybe you need to apply DDL and procedures to various environments. I have been working on an installer to manage your DB schema using migration scripts - http://dbgeni.com
That is a myth.
You are not allowed to show symbols of an organization who is against our constitution, but only if it is not in the matter of science or history. The second law is, you are not allowed to call out for violence against a group/minority.

Censoring is illegal from our constitution, so you can only get sued by a court, but when you take it down it usually would be dismissed. It is not even an important public topic here.
Thanks for the feedback. Just curious, what are the advantages / disadvantages of both approaches?
HATEOS is a design constraint, WSDL is a spec. HATEOAS could accomplish a lot more than what WSDL does with appropriate specs and a widely adopted programming model or two. This has taken a long time to improve.

So far we've only see a few like AtomPub and its extensions, or the discovery protocol stack (http://hueniverse.com/2009/11/the-discovery-protocol-stack-r...).

The challenge has been, IMO, a programming model that fits the Web, which can then fit into a media type spec or two that adopts it (similar to how HTML was codified for the experience of a web browser). WSDL basically is the procedural programming model, where networked interactions are usually mapped procedure calls. This model a whole bunch of long discussed problems when dealing with wider scale interoperability.

I've tried to outline this challenge in detail in my keynote at last year's WS-REST workshop on the "Write Side of the Web": http://www.infoq.com/news/2011/03/web-write-side

Is WSDL richer and more productive than documenting a bunch of URI patterns for a complex API? I'm not sure about that. WSDL tends towards code generation for very specific sorts of interaction scenarios, and ignores things like cacheability of results, the safety or idempotency of the request, and the ability to access data across endpoints without a lot of a priori knowledge in the client. Many of those properties are easier to implement with plain HTTP used in a RESTful manner.
I've read that book, and i can say for sure, its a very worthy read indeed. There are some serious eye openers in there that just cant be covered in a blog post or executive summary.
We're using Stripe and it's been awesome right from day-1.
1. The so called "illegal downloads" aren't illegal. It's the uploads that are illegal. Hence the downloads can't "remain" illegal.

2. The courts do not deem copyright infringement to be "theft". They deem it to be "copyright infringement".

3. A productive balance of interests between creators and consumers is probably more intricate than "all rights go to producers, no matter how convoluted they want to make the lives of consumers" or "all rights go to consumers". The reason why producers are given imaginary property rights is to facilitate development of useful arts (it says so right there in the American constitution), not because those rights are "holy" like right a right to live.
Just a small nit, Go does not use a VM. It's compiled to machine code.
Thanks for the feedback. We'll make the necessary changes.
From page 3 (http://tools.ietf.org/html/draft-ietf-appsawg-xdash-02#page-...):

employ meaningful but currently unused names
I build most of my apps this way. The main idea is that any time users can add content, it goes into its own collection. This way, records don't grow indefinitely (and hit the 4mb limit) but it also gives you a lot more querying power.

You sometimes want to just get the blog post object too, not all the comments. It's worth it to have to do two queries and get the extra selection power vs one round trip to the DB, but you have to potentially sift through a lot of data to get what you want (or get back a lot of data you don't need).

This is, in my opinion, the perfect mix of the relational/document schemes. You can nest things when they don't grow continuously, but you still get most of the querying power of a relational database.