skysight-inc/HackerNews huggingface dataset:
I think in the majority of cases it's just going to be simpler to use a minimal base image like debian. And the overhead is pretty minimal - once you've got the base image, you only need to download the changes for other child images. Admittedly, you do incur the image overhead at least once per Docker host.

In short - horses for courses ;)
The obvious solution is to submit a patch to curl, such that when it's called as "wget", it emulates wget's command-line options, and vice versa.

Witten only partially in jest. I've submitted patches to both projects and both are relatively straight-forward code bases to dive in to.
Most of the time I'm using curl, I want to see the output. Otherwise I start it with >output.file.
Just for accuracy ...

The first Alto (mostly designed and built by Chuck Thacker at Xerox Parc) started working in April 1973. The original cost target was around $15K in the dollars of that time. We eventually made more than 1500 of them (actually close to 2000 by some estimates) during the 70s.

I recall that the budgeting was actually about $22K per machine, which would be roughly more than $100K in today's dollars.

There are a variety of points here. The biggest one is that -- being a rather practical field -- we tend to have ideas that are possible. A factor of 10-50 allows us to have ideas that our subconscious minds reject automatically, because we are used to working within "normal". We have to shift or get beyond "normal" to make big progress.

Best wishes

Alan Kay
IT'S OFFICIAL: Halliburton Buys Baker Hughes for $35B
Sorry Startup, it’s not you, it’s me
Spider Programming Language
is it just me or no one can agree on what the best practices for a REST API are?
Are you saying that it's just as good to have a URL be /fj3849-2qfjimpa as /customer? I agree that it is not strictly a REST principle, but in an API clarity matters. If we are talking about good practices, would your rather work with an REST API with readable, concise URLs or not? Maybe I am missing the point but the URL is one of the major building blocks of REST and choosing quality ones is a large part of API design.

I stated that HATEOAS is widely misunderstood so it isn't surprising that there are conflicting descriptions out there. No matter what your interpretation, this principle is about hypermedia and application state and says nothing about what a URL should or should not be.
Those interested in the history of beer should also take a look at Sacred and Herbal Healing Beers by Stephen Harrod Buhner.

http://www.goodreads.com/book/show/157268.Sacred_and_Herbal_...
OSIRIS spots Philae drifting across the comet
If you really want to geek out on old beer, you need to read @patto1ro http://barclayperkins.blogspot.nl/
I've always interpreted "hypertext" in this context to mean "a document containing hyperlinks" in a rather general sense - nothing about it being restricted to HTML.
It's easy to change/add 1000 lines in a week.

However, most code is rewritten/refactored many times. So only little of what you write in any week will be the _final code_.
"Not only that, but make tiny changes in even the initial conditions of the Big Bang and you end up with a sterile universe. Cosmologically speaking, it’s like we won every lottery every imaginable. From that vantage point we are special—crazy special."

Assumes life as we know it is the only option. Tweak a few parameters and you could easily have inelegant life growing up in stars or the 'void' between galaxy's. Life might operate at timescales billions of times faster or trillions of times slower etc. But, rarely do such articles consider all the possible universes we don't inhabit.

PS: There is something of a reverse anthropic principle at work where observed life adapts to best exploit the physics of it's universe.
"to have curl print to file -- when I _do_ want to write to a file"

You have it reversed. Wget will output to the screen/pipe if you output to the "file" --. Curl does not. "curl http://www.google.com/index.html -o --" does not output to the screen. It creates a file named "--".
Well debugged 1000 lines a week are actually quite a lot. I would be very happy with 20000 lines per year.
Rubbish! It is called an open standard for a reason. http://www.toptal.com/python/why-are-there-so-many-pythons
Fund DRACO research
This is your chance! You can help push testing forward on a therapeutic that may be effective against virtually any viral infection including Ebola. So please, choose to help drive the testing by making a donation. If just 2,800 people from each U.S. state donate $25, enough testing can be done for the FDA to approve DRACO as an Investigational New Drug. You can read more about this goal and how donations are used by clicking the link below.

www.thedracofund.org
I just want webview-based mobile apps to support basic platform navigation conventions like scrolling to top when the top of the screen is tapped. That one simple gesture immediately outs webview apps 90% of the time. I'll stop preferring native apps when webapps start offering a benefit to me, the user, instead of just the developer.
In this case I would either make albums a field of artist, or just leave it off altogether and just filter /albums based on the artist foreign key.
Write once, run anywhere
I'm a senior engineer who has written over 150k loc the past month :( . I have had to tackle some difficult problems that allowed the other engineers to keep moving.

My workaround so far has been to do most of the critical work during after hours or before everyone comes in the office, since my primary role during regular hours is to keep everyone unblocked. It isn't sustainable though, and I only do it at the moment because we are in crunch mode - 'tis the startup life.
The problem with multiple processes is the "share nothing" model. It works for some problems, but it blatantly fails for a whole variety of other problems. STM tries to address those problems where "share nothing" does not work, e.g. because there is interesting data to be shared (albeit with few conflicts) or the memory overhead of N processes is just too much.
CPython is hurting the ecosystem by being slow. I'll let you in on a little secret. People used to using C, C++, D even Java and C# laugh at the slowness of languages like Python and Ruby. Blah, blah, blah productivity gains. We laugh. We think, "I could write this in Java and go to production with three servers or I could write it in Python and use eleven."

People don't like to say it to your face, but Python is often derided and considered to be pretty silly. Oh, and its syntax is like Lego. Neat at first until you want something like a multiline lambda.
JOLT portfolio companies have raised a total of $10.5M
Federal Circuit: New decision regarding software patents
Took me literally 5 minutes to embed into my site. It's just copying over some HTML. Super easy.
Will it be a good fit if I, running on a hundred servers, need to scrape just the home page of a million sites? No analysis of the pages, that is done later.
Nicely done. I find that the most useful pedagogic tool for learning are extensively annotated non-trivial examples (with emphasis on extensively annotated).
Incorrect. Resources are identified by URIs, but they are opaque, n.b. The Opacity Axiom

"The only thing you can use an identifier for is to refer to an object. When you are not dereferencing, you should not look at the contents of the URI string to gain other information."

http://www.w3.org/DesignIssues/Axioms.html#opaque
Clojure Loops in Ruby
Flask by Example (series) – Updating the Staging Environment – Real Python
Seems to be an important change in decision making of the US courts.

Here, what the EFF says:
https://www.eff.org/deeplinks/2014/11/victory-court-finally-...
It's a pretty advanced library, and I don't think you should use it if you've only been trying Haskell for a few weeks. I've been using Haskell for about 7 years, 5 of which commerically, and I've never used it seriously. I find the smaller lens libraries, like 'fclabels', solve the most important problems 'lens' also solves, but with a lot less surface area and complexity. But even that can wait until you're further along.
Coming to a mall near you: a green alternative to Home Depot
> Turkish government has huge success for destroying historical remainings.

That would be weird since Turkey has huge interests in those "historical remainings": tourism is one of the biggest sources of income.
I'd be careful quoting the aphyr post in that context. PG also had some failures, even in the non-replicated setup: http://aphyr.com/posts/282-call-me-maybe-postgres

Failures are just a property of distributed systems, some fail in ways that are better for you, some fail in ways that are worse, but sooner or later they all fail. It's a tradeoff which one you choose.
Everything is script based- no gems, just embedded JS.
Show HN: An exercise in organization design
I don't think this is applicable to python. Only so many developers can work on cpython without stepping on toes. This led to the decision not to have cpython to be an implementation standard, not an experimental language, while pypy led the effort for expanding with a different team of developers. This is a good decision, because there are still more than enough developers to maintain a stable, full-featured cpython that pypy can conform to (to varying degrees). There aren't any competing standard libraries, for instance, and it's made very clear which libraries work on which implementations.

Maybe if there were competing implementations to ruby, it would still be popular outside the rails community. But it seems as if the vast majority of ruby core developers work on the mainline implementation, or forks thereof.
Blockspring is hiring: help build the ultimate library of functions in the cloud
This debate was settled almost a decade ago. URL forms don't matter in theoretical dissertation REST, but 15 years of practice has firmly decided they are indeed a core part of real-world REST.

HTTP based web services existed before Roy's dissertation and while the formalizing of them helped them mature rapidly, the idealistic principles aren't the final word on the subject anymore. Real world practice now is.
Chrome now uses clang for production builds on Linux
The other one on iOS is edge-dragging to go back/forward in the navigation stack. Neither of these things is -hard- to implement with current tech either!
Sigh, I'll give you the only honest answer it seems you will get here. Node.js runs JavaScript faster than anything runs Python, PyPy included. If you want speed and you like JavaScript just as much as Python, then use Node.js. When I say "faster" I mean you will use less servers/cores for your application with Node.js than you will with CPython or PyPy. V8 is just a better and faster VM for its target language.
Simon's Algorithm run on quantum computer faster than simulation
The following is my 2 cents based on opinion from what I've learned in business school.

The American way is about focusing on your core competencies and what you're good at. Banks outsource their IT services, real estate and etc to free up capital to focus on their banking services. This is what they've taught at my particular business school and this is how business "should" be done. It's just not efficient to spread yourself into other markets.

Asian businesses sometimes form large conglomerates because of the lack of infrastructure in place in emerging economies. There aren't many smaller companies that can make rice cookers. There aren't many entrepreneurs that will want to make innovative rice cookers. Access to capital and VC money, I would assume, is really tough in Asia. Samsung makes chips but there's no buyer for those electronic chips so they start to make products that use those chips and handle every aspect of the supply chain all the way to the end-consumer. You'll see that in North America, many companies are broken up to focus on just 1 part of the chain. Other parts of the chain may be less profitable and often gets divested or spun off. Shareholder pressure sometimes dictate that.
150 000 lines of code / (10 hours * 5 days * 4 weeks) = a sustained 750 lines of code an hour? That's impressive. Can you share a bit more about how you manage to achieve such productivity for those of us who aspire to be like that?
Why not pass a dummy value to satisfy the spec?
400 Bad Request is often a better, albeit generic, option.
Desktop is dead? I'm not surprised a "mobile software consultant" would say something so ridiculous.
1337biz - Our core claim is that an an advisory/coaching model is a better fit for the tech industry. It's why we brand ourselves as "Advisors", and not "Agents". In addition to compensation advice, we provide meaningful career coaching advice as part of the process - this helps you figure out which place is actually a better fit along non-monetary dimensions.

Also, our fee structure is much more reasonable than an agent's - we're charging 20-30% of the cash increase, or a $2k flat fee, whichever folks feel is more reasonable. Incentive alignment is important, but there are also cases where candidate may get a huge bump in equity they can't can't necessarily pay us out of.

It'd be interesting to consider derivatives-based model in the future to align incentives better by capturing the value of the equity increase, but that's a long ways off, and not terribly important to us at the moment.
> Are you saying that it's just as good to have a URL be /fj3849-2qfjimpa as /customer? I agree that it is not strictly a REST principle, but in an API clarity matters.

No, it is strictly a REST principle that the meaning of URLs other than the entry point is defined completely by the context in which they are used in resource representations and the definition of those resource representation (i.e., media types).

An implementation of a REST API may happen to present URLs with a consistent relationship of location structure to semantic meaning in the API, but that's entirely outside the scope of the REST API per se.

> If we are talking about good practices, would your rather work with an REST API with readable, concise URLs or not?

If you are using HATEOAS, URL format, readable or not, isn't a feature of the API at all (its a feature of a particular implementation of the API, but its one that clients don't need to be aware of.)

> Maybe I am missing the point but the URL is one of the major building blocks of REST and choosing quality ones is a large part of API design.

You are missing the point. URLs as opaque identifiers is one of the major building blocks of rest, and if you are worried about choosing one as part of "API design", you aren't building a REST API.

The resource representation (media type) should tell you what the URLs used in it are for, not the URLs themselves.

> I stated that HATEOAS is widely misunderstood so it isn't surprising that there are conflicting descriptions out there. No matter what your interpretation, this principle is about hypermedia and application state and says nothing about what a URL should or should not be.

If you need to communicate the URL structure and identify relative URLs for various endpoints to describe an API, it is not a REST API following HATEOAS; "A REST API should be entered with no prior knowledge beyond the initial URI (bookmark) and set of standardized media types that are appropriate for the intended audience (i.e., expected to be understood by any client that might use the API)." [1]

HATEOAS clearly is misunderstood, as you've just demonstrated.

[1] http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...
HN for college essays
When I was in college, essays were a big part of the curriculum, especially in humanities. IFor subjects like philosophy or history they often made up the majority of the work, learning and assessment. Do any colleges use a HN-like forum for submitting and discussing essays? Would it be useful?
Leonid Meteor Shower Peaks Tonight: How to See It
So then this project isn't open source. I understand that it will be, but it seems disingenious to add the comment about it being open source.
URIs matter and REST matters because people have been using them incorrectly for so long. Common mistakes like putting verbs in URIs instead of using HTTP methods. You are correct though, about the design of verbs don't matter (outside of conventions) as long as everything is done correctly.
I am not trying to offend you, but I really don't understand when someone says "yes and no". I hear it more and more these days. Is this becoming a cliche? It can be "yes" or "no", not both together. "yes and no" is "no" for me.
What about collaborations? The nested hierarchy implies a directed tree structure, but the relationships are really a graph. And I've personally found no more insidious of a problem in data design than trying to shoehorn a graph into a directed tree.
Nice article.

As of lately, I've been using a bundled GHC app for OSX development. Makes it quite easy to keep (and switch between) multiple Haskell environments.

http://ghcformacosx.github.io/
If you are building a web service for the general public that you want to last forever (e.g. an interface to Wikipedia or something), follow theoretical REST principles and you'll be well served.

If you have actual paying customers that you'll need to support over many years then version your API. Paying customers won't tolerate API breakage and you can't always force them to update on your schedule. Assuming you still want to evolve the API and also sign up new customers, you'll quickly find out you'll need versioning.
The website doesn't do a very good job of describing the integration,and I've seen a few people asking about it. Basically this is just JavaScript that you embed on your page, no back-end integration required. All your comments are actually hosted by them so you don't have any direct access to comments on your back-end. I have been looking for a simple solution to comments for a personal site, so I tried this out. Integration was dead simple, copy & paste into your HTML. Wouldn't use on any bigger projects until I see the full source, but I will continue to use it for now.
There has been an alpha of fiddler on mono for some time now: http://fiddler.wikidot.com/mono, rejoice!
No, a mentally ill developer is not good for your team
C, C++, D, Java and C# are hurting the ecosystem by being slow. I'll let you in on a little secret. People used to coding assembly laugh at the slowness of languages like C and C++. Blah, blah, blah productivity gains. We laugh. We think, "I could write this in assembly and go to production on an Arduino or I could write it in C and have to use expensive servers."

People don't like to say it to your face, but C is often derided and considered to be pretty silly. Oh, and its syntax is like Lego. Neat at first until you want to understand what something is a pointer to.
But from the point of view of the traveler, it an take far less time.
All good points. I can't say what the future of Naiad is. What they have done to Microsoft Research Silicon Valley is disgusting (I worked there too for a short time).

In our experiences the performance claims with Spark have been more hype than substance. Naiad on the other hand has been hard to find a corner case for.

Naiad is open source licensed under an Apache License so one can only hope...
I wonder if the desktop first attitude at the Rails Rumble had something to do with when Rails came on the scene? That when people started using Rails desktop was king and mobile was painful. (wml anyone?)

I would bet that a node.js or a MEAN stack hackathon would have a higher percentage of mobile friendly results.
Had a similar sentiment earlier this year.

http://kevinsuttle.com/posts/the-right-questions-to-ask-mobi...
Drupal 8 is now built on top of Symfony. Slow? Never had that experience, it has always been super fast for me. It runs on php, and that is dangerous in and of itself.
Well yes, it's not ideal for all development, but you professed a need for smaller filesize, which it's ideal for. Naming conventions can alleviate most of the variable issues, it's just another way to solve the problem that has some advantages and disadvantages.

(I don't use it myself, due to the current project being too large, so I use require.js in conjunction with amdclean which removes a lot of the module loader overheads.)
Hi! I'm the post author. Desktop is dead in the way TV and newspapers are dead. Yes, they're still around but there's no growth. They certainly shouldn't be the main focus for a web developer building a personal site from scratch.
> HATEOAS (the 4th principle) also seems to be gravely misunderstood. It only means that the API should have a version that is fully useable in a web browser.

No, it doesn't. In fact, a REST API can fully meet the requirements Fielding lays out without having any implementation that uses any communication protocol used by any web browser. REST is an architectural pattern that is independent of communication protocols.
like every other developer ever, i have often been asked to do coding tests for a job interview. personally, i think ten to twenty hours of work is reasonable, if it's a place i really want to work.

what i have a problem with is companies that want you to do the coding test before they've even talked to you. i may rule them out as a potential employer as part of that process, in which case it would be a waste of time.
Elastic SIP Trunking
Currently working my way through all the Dean Koontz books.

Also recently read the Sports Gene which was good.
This layer of soft dust in low gravity is hard for me to get my head around.
If you are interested in this, you might be interested in my (warning: shameless plug) 5 part blog series located at http://blog.caseystella.com/pyspark-openpayments-analysis.ht.... I'm using the python bindings for Spark to illustrate doing data analysis on healthcare financial data on Hadoop.
I suppose one must first define the qualities between a good and a poor API. I would say that it is the same as any code: The design should be readable, maintainable and modular.

The plurals or not thing isn't a big deal. I really just object to the author picking one and claiming it's better with justification.

Putting "vi" in your URL decreases both readability and modularity. All things being equal, concise URLs are more readable. "v1" are extra characters without significant benefit. It also creates huge maintenance overhead. How many APIs do you think you can simultaneously maintain well? I am happy with one good one myself. Every extra new version you create (as opposed to gracefully improving the existing one) is more technical debt.

Let's take the nesting example: /artists/8/albums. What if you want to access an album by itself? You also need an /albums resource so you've just created two resources when you need only one. The /artists/8 response should include a list of albums that hyperlink to the /albums resources. If you absolutely have to have a clean list (without the artist header information, just filter it with a query string /albums/?artist=8. This accomplishes the same thing in a more predictable and consistent way without magic URL params. The major benefit of this type of design is it makes tracing execution from the interface to a code location much clearer by avoiding spaghetti URL routing.
Ask HN: Genetics/Mol. Bio. Startups playing with lots of data?
I'm interested in getting back into mol. bio. I've a background in dealing with massive datasets and am a trained molecular biologist (undergrad, but did real research, didn't just wash glass).

I'm looking for something very cutting edge, massive datasets, huge implications. Broadscale SNP analysis, something perhaps similar to what GenePeeks does (I know them already). Trying to get an array of options...
Autoscaling, Welcome to Google Compute Engine
I too wondered that while writing the post, but I can't think of anything about Rails that inherently makes the framework desktop-first.
Really? See Javascript.