skysight-inc/HackerNews huggingface dataset:
That could only work if one company can produce something so comprehensively better for every task that it would be madness to choose anything else.

The only other way to achieve this would be for one cloud provider to gain critical mass and then drop support for anything other than their preferred framework.
Though I do appreciate comments such as this:

/* Fetch the function body */
tmp = SysCacheGetAttr(PROCOID, func_tuple, num_pg_proc_prosrc, &isNull);

Newcomers have be be quite familiar with the internals to immediately see that the line fetches the function body.
Of course anyone who needs reliability and privacy will question the use of the specific public social networks I mentioned as examples, but the same principle applies when businesses deploy centralised in-house systems. They still handle messaging (and often a lot more besides) for their key functions using dedicated tools, so general purpose e-mail is no longer necessary for those functions. Increasingly these organisations also use VPNs to allow employees and other associates who are not physically present to hook into the same centralised systems remotely.
The first versions of EF sucked badly. But the last version is quite decent.
If you have no objection to a band, song or album cover that degrades your mother or someone else you love and revere, then hey, maybe it should all be fair game.

Do you understand where I'm getting at? That's how Christians feel with names like that.

P.S. I don't think for a second that the name of someone you love should be degraded. Nor should someone I love either. That's my point.
> Here's the thing: You probably disagree and even loathe the personal politics of many of the artists whose works you enjoy

The thing that is most infuriating about OSC is that his stories imply a philosophy completely opposite those he espouses in his political writings.

For example, one of my favorite short stories is OSC's Unaccompanied Sonata. The story has a message about the cruelty and ultimate impossibility of making someone deny their core self.

http://janlowman.escuelacampoalegre.wikispaces.net/file/view...

But then in real life, OSC says stuff like gay people already have marriage rights because they can get married, just not to their own sex. How can the guy who wrote the above story think something like that? Like I said, it's infuriating.
If you find RequireJS a bit too intrusive you could check out a dependency manager I wrote: https://github.com/judofyr/dep.js

It's tiny (411 bytes minified; 268 bytes gzipped) and only handles dependency management. It's excellent if you just want to avoid worrying about the order you concatenate your files, but it's also possible write a basic RequireJS-style script-loader on top of it.
I think the three file views side by side image is one of the best arguments I've seen for 80 chars. But I'm predisposed to like that image, because I like 80 chars.
This is obviously 'plan b' in terms of preventing a royalty-free video codec from being standarised, as evidenced by Nokia not being interested in licencing the possibly infringed upon patents at all.

In short they want to kill off vp8, or at the very least prevent it from becoming a HTML5/RTC standard. One would ask oneself what Nokia stands to gain, as it logically would make more sense for them to ask for a licence fee than to try to prevent VP8 from being used.

Of course, knowing that Microsoft holds the reigns at Nokia through Elop it's not that much of a mystery. Also highlighted by Nokia lying in their statement:

"We are now witnessing one company attempting to force the adoption of its proprietary technology, which offers no advantages over existing, widely deployed standards such as H.264 and infringes Nokia's intellectual property."

The hypocrisy and outright lying is frightening. VP8 is not proprietary in any meaning of the word, while it's being developed pretty much solely by Google it's done so in fully open source fashion, through a public git repo. It's advantages is that it's geared towards real-time video and of course entirely royalty free, the latter being what rubs MPEGLA the wrong way.

A court (or likely several as the patents are applied in several countries) will have to decide upon the validity of these patents. But of course the whole point of this is again to throw a patent cloud over VP8 in order to prevent it from being standarised as part of HTML5/VP8, these proceedings will take time during which h264 will likely have time to entrench itself as the HTML5 video option despite not being an official mandatory implementation.

The stakes are high as the members of MPEGLA are expecting to cash in on royalties by cornering the video codec market, and obviously a roaylty free quality codec is an enormous threat to their continous royalty-based cash flow.

I guess it should have have caused alarm when MPEGLA backed off VP8 like they did, I can ony assume they knew of this impending patent suit from Nokia.

I really hope Google stays the course and fights Nokia, but of course then some other sock puppet patent holder will likely emerge. In short, I don't see a chance in hell anymore that we will be able to benefit from a royalty free web standard and all the potential that this holds.

If Google backs off trying to standarise VP8 I'm certain MPEGLA cohorts will stop harassing them, unfortulately this means we will have an effective monopoly in the video codec market and that's bad for everyone but the MPEGLA members.

And what can I say about Nokia, a company I once held in great regard, now a Microsoft subsidiary in all but writing, led by a major Microsoft shareholder, how sad.
Nice side project!

A dual citizenship feature might be a nice touch - for instance travelling to Brazil is easier on a European passport than an Australian. So it would be great to know what to use when.

One bug report: On the one page -
Australian citizens require a visa to visit Canada.
Australian citizens do not require a visa to visit Canada.

http://www.doineedavisafor.com/visa/australian-citizen/trave...
What about other languages? I find it harder in C/C++ when I have functions with too much parameters. It's almost less beautiful to look at. Do you change parameter names to shorter ones, add usings to avoid explicitly stating the scope, tab at 2 spaces instead of 3/4, increase the line cap to 90/100?

On a semi-related subject, what about the vertical limit of the code? I often heard that a function should fit in one page, but that also depends on the screen resolution. Also, the 80 chars rule would increase the amount of line instead. How do people deal with that in general?
Is there an open source version of HN anywhere?
> In some respects, the plethora of choice this problem represents is the power of the web, but overall I think it does the web a disservice because there isn't enough weight put behind a single platform.

Fair argument (I guess?) but the opinion comes down to, do you prefer an open and ever-changing ecosystem that has no limits on what you can build and how you can build it; or do you prefer a contained ecosystem dictated by a few powerful stakeholders who subtly apply their own methodologies and beliefs, to shape the capabilities and limits of the platform?

The latter seems like a slippery slope and would eventually serve the the powerful stakeholders rather than the people building the platform. The former, while it may require a higher learning curve, puts more competition between technologies that enhance the platform, and doesn't dictate what or how things can be built, serving the developers and users above all else.

Personally I would prefer the former.
From Mega Drive to PS4, how Team17 remade Worms for the next generation
Shameless plug: I built a small library to provide more Expect-like features in Ruby, since I didn't care for the interfaces exposed, for application development. Presently works on Linux and OS X for 1.9.3, and Linux for 2.0.0 (OS X untested, but assumed good)

https://github.com/cwuest/expectr
Skim the IE stuff, and use the book as a reference manual if you need to implement cross-browser functionality yourself. It's important to have a general idea about what won't work if you need to support IE in the future, but you don't need to know every single detail.
If you let Google choose, the platform will be in Java.

God, please no.

If you let Twitter choose, the platform will be in Scala.

God, please no.

That's why we are where we are. I don't want to develop in that gunk, but others do.
Screw arbitrary limits.

Personally, I prefer the 120 characters per line guideline. Most code I see starts looking very ridiculous when trying to accommodate the 80 characters max width, and it starts becoming hard to follow lines when exceeding 120 characters. So, to me a soft 120 characters guideline is the nice medium between the fact that it's no longer 1980 and the need to make lines easy to read.

Also, in most cases readability has almost nothing to do with line width (in fact it can suffer greatly from too much line breakage), and everything to do with how the programmer chooses to structure their code, aided by language idioms.
Commenting methods can often be redundant. But I find it is almost always a good idea to comment classes that contains any degree of complexity. Too often when digging into a new project I see a class like "ItemHelper", and have to read a few dozens of lines to realize something that could be summarized like: "Converts X-data to a format that Item can parse".

It makes it so much easier to get introduced to a code base, and comments like that seldomly needs to be updated.
Windows Blue shows why Microsoft may kill the Desktop in Windows 9
Startups have a sexism problem
How Apple's Password-Reset Security Breach Worked
Do you code on a netbook? 2x120=140. At 7px each, which is generous (even if you are using some non-proportional font for archaic reasons or misplaced machismo) that is under 1000px wide.
I find the 80 char limit nice as a suggestion/warning, a way of saying "are you sure your approach should require lines of code this long?" So, a good way to make sure that someone is writing readable code, which is otherwise the overall goal of PEP8. But, sometimes there are lines of code that are perfectly readable, maybe even more readable, despite exceeding 80 characters, and which become less readable by doing line continuations. (I would argue that line continuations make everything less readable, almost all of the time.)

The other rule that I personally ignore, and when I'm managing a project I have my developers ignore, is the suggestion to use spaces instead of tab characters for indentation. Of course, with Python, you must use one or the other, but I prefer tabs.

In both cases, it comes down to my belief that individual coders should have the ability to customize their experience without forcing it on everyone else. When you use spaces instead of tabs, and indeed, when you use line continuations, you're forcing your (the author's) exact view of the source code on everyone you're working with. If you use tabs, and don't use line continuations, others with specific needs (2 character tabs, 4 character tabs, 8 character tabs, 60 character-width editors, 100 character-width editors, etc.) can, with any modern editor, customize their view (using variable-width tab stops, and soft line wrapping) to what they're comfortable with.
In Dog Dental I really like how the bottom of the D forms the dog's neck.
Native iOS development made simple [video]
If You Can't Get Clients, the Problem is in Your Sales Cycle
Libraries can help- you can legally enjoy fiction and videos without directing additional funds to the creators.
The Walmarts you mentioned:

Lush:
https://maps.google.com/maps?q=walmart++Hilton+Head+Island,+...

Fully paved:
https://maps.google.com/maps?q=walmart++Hilton+Head+Island,+...
I wonder if this was a concession to the limited browser code and slow networks at the time. With the img tag you know its going to be a jpg, gif, or png. If it was a media tag then you have no idea what it is. Imagine downloading a 10mb quicktime file or flash object on dial-up so the mime header can be read as you wait for the page to render. Its only recently that anyone has bothered to handle video in the browser.

Could web servers back then just send the client the header of a file? I think these guys were working with a lot of ugly limitations that we've only recently overcome. Andreeson recently said that he expected the back and forward buttons to be temporary but no one thought of a good replacement for them. We still haven't.
Yeah, but what about

// $set $foo to $bar
$foo == $bar;

// print out value of $foo
echo $foo;

// is $bar the same as $foo? if so, return true, otherwise return false
if ( $bar === $foo ) { // check if the same
return true; // great, it's true!
} else { // here we check if it isn't true
return false; // nope, not true, let's return false
}

I have nothing against comments where something needs to be documented, but not everything needs comments as most code is essentially self-documenting.

Edited for clarity.
I think that Clojure might change your mind about that.
Yahoo buys news app Summly from teenager
It's worthwhile to ask questions like this from time to time, and it's one of the values "new blood" brings to any community (asking the same questions but a year or so later since the last person). In this case, OP, you've "mixed metaphors" so to speak - your title is about tables, but then you mix in inline-styles and non-responsive which open the possibilities of the answers quite a bit. I think your question can be broken into two parts: (1) the design of HN, and (2) the tech parts.

1) Over the years, people have posted many suggested HN redesigns. Inevitably, they've made much more whitespace - making it more like {reddit | digg | etc} - and people always are polarizing in their comments ("Hate it - how can I function with this many scrolls?!?!" or "Love it - HN looks like crap currently!"). I suspect the "Love the current design" crowd is/has been in the majority or perhaps pg himself is in that group - either way, I've yet to see a redesign post that a large group of the community embraced. The end result: the majority of people seem like the way it is now so nothing has changed.

2) For the tech aspect, I have to ask whether you see "HTML-tables, inline-styling" as perhaps the reasons behind the "non-responsive"? Do you propose that moving to a CSS-based grid system with external stylesheets would make the system so much more responsive that we wouldn't have trouble? That's not necessarily the correlation you've drawn in the OP but it is possible that you think these are the reasons, I suppose (or contributing factors). pg/admins have talked about the server before (and it's recently been upgraded/replaced). They've also talked about the DDOS attacks they have been under as well (I think they are on Cloudflare now to help mitigate this). In the end, it's a single server managing a large community. Inevitably there will be problems when you mix those two.
Attrition rate for saplings is pretty high. So in nature when you see a bunch of trees on a hill there are many more trees that didn't survive. But in a building you don't get to have any attrition; you want all trees to survive.

And city buildings can generate surprisingly strong winds. "The wind loading on a skyscraper is also considerable. In fact, the lateral wind load imposed on super-tall structures is generally the governing factor in the structural design. Wind pressure increases with height, so for very tall buildings, the loads associated with wind are larger than dead or live loads."

(https://en.wikipedia.org/wiki/Tall_buildings#Design_and_cons...)
I don't quite like the loop split, but that's because I've never like "continue the next line under the first argument of the series." It makes next lines start at inconsistent places and makes it harder to read. I usually bend that rule and follow the four space indent 90% of the time.

But I do like the loop split better than the non-split, despite the above.

I like the smatch split too. It looks like how you'd arrange bullets in a bullet list, one below the other, so you can see/scan them at a glance, without having to labor over where the next item is in a single line.
I don't seen how your experience with growing trees is any different than the original author's experience. Both of you may be professional arborists, yet you fail at growing trees. Therefore your conclusion is trees are hard to grow. Maybe you both are bad at growing trees.
Want Press Coverage for Your Startup? Master Your Media Pitch.
Merge sort and inversions in C
They actually rewrote it in python because in 2003 open source implementations were of much lesser quality, also, hunchentoot didn't exist, and neither did the modern lisp frameworks like caveman/clack or restas. CCL and SBCL are way better than CMUCL and clisp, which is what I believe they used(CMUCL is barely used these days, and clisp has a bunch of rough edges and being byte compiled is slow, unlike ccl and sbcl which are pretty fast). These problems are no longer valid, and if reddit were to be written today, it would be less likely to be rewritten in python. Lisp has gone a very long way in the last 10 years.

Using common lisp and restas + Postmodern(for postgreSQL access) today is actually a better choice than using something like flask or sinatra. And since i dislike full stack frameworks, my personal opinion is that it's better than django or rails too, for a small team of good hackers.
True, I'm just saying it seems possible to construct facades with plants where all the water and nutrients are supplied from within the building's walls through pipes and stuff.

I wonder what the technical limitations would be to building that on a skyscraper ... we can have running water on top floor, so why not running water in the facade?
what? do programmers still layout their code using whitespaces manually? use code editors that support declarative stylesheet for layout and enable intuitive structural modification.
Friction with the ground slows air down near ground level, so air 500 feet above the ground will, on average, be faster-moving than ground-level air, regardless of elevation. See http://en.wikipedia.org/wiki/Wind_gradient
It's not just authors, any time you make a transaction you risk pushing money in a "bad" direction. In many cases worse than somebody just having an opinion but actual bad stuff happening.

For example if you are strongly anti-war it could be argued that you should quit your job and start claiming as much welfare as possible to try and deny the government funds for buying weapons, if you pay tax you are literally funding war.
Twitter censors, Facebook censors, Hacker News censors, and they took off. I can support my argument. Can you with yours?
Still, at least consider if climbing vines on trellises might serve better before putting a ton of effort into trees per se. They provide most of the same greenery benefits, can be made to fit the space, don't have dangerous roots, and are in many ways more robust. Plus they can have flowers or fruits near floor level.
Wow. That sounds like a very intense experience. Could you elaborate on what that was like and why you found it wasn't for you?
The title is inaccurate. The article is not announcing a trailer, just a teaser poster. From the article:

> Tomorrow you will get your very first look at the battle room with the reveal of the teaser poster on Yahoo! Movies.
80 character lines is perfect. Allows me a reasonable number of splits in vim and most importantly makes diffs/code that I get in my email readable.

That being said, as with all things(especially guidelines), apply common sense liberally. Which in Python is one of the guidelines of pep8 on writing readable code.
Why should Nokia help Google for free to reduce its licensing costs on things like Youtube when Google has used its search profits to dump a free mobile OS into the market thus hurting Nokia's profits? The "not willing to license" stuff is just legal posturing, there's a right price for the licenses which it wants Google to cough up from it's $50B cash. This has nothing to do with Microsoft either.
Please Keep a Changelog For Your Open Source Library
Git can be a deployment tool by using the post-update hook in a server-side repo. In my setups it also runs tests in a "test" repo before deciding to push into a "production" one.
It's not coming up. Load problems I suppose.
You might like lamernews[1], made by antirez, which uses redis.

[1]: https://github.com/antirez/lamernews
Great idea! How to control buoyancy? I guess you need some ballast to keep the whole system close to air density, and a pump to put / remove air, for fine tuning depending on conditions (temperature, ...) and what you want to do (go up / down)
This is a good occasion to read the source code of a non-trivial piece of Go code. The documentation of the project seems rather sparse, but at least, the app has readable tests.

That said, if you are looking for an open-source platform as a service, OpenShift, or as others mentioned, CloudFoundry are more mature options.
I prefer the pure OO trait-based solution to the expression problem that isn't supposed to exist; pattern matching is not the only way to do it. Scala is just that good.
Once more into the screening breach: The NY Times did not kill your patient
I think it is helpful to know if the check is just a sanity check or if there's an already known set of conditions can lead to that particular error.

The function comments I also find very useful. Read a few of them and see how much information they carry. Preconditions for the function, reasons why it does what it does, assumptions it makes... These functions are used from throughout the code and it's important to document them well.

I'm purposefully not quoting specific parts of the file, because of course if you look at each and every one of them, you'll find a few that could be improved. But the OP asked for a well commented code base and if PostgreSQL is not one, then I don't know what would be.
I'm ok that people don't use email/vim/sublimetext2 with splitting panes, but don't people use meld / kdiff3 for reviewing they're changes? And on my 1366x768 120-chars would be too wide to show in meld.
.ly is a tld

http://en.wikipedia.org/wiki/.ly
It's not a point of view I necessarily agree with, but it is a legitimate point of view that could be argued, as opposed to (say) gay people are paedophiles, which is clearly stupid.
99% of the time when you are writing a single line comment you should instead be either renaming a variable or using the extract method refactoring using some abbreviated form of the comment in the new name.

For the remaining cases it's more important to make sure that you're documenting the "why" of something in the code. If you find yourself often in the situation where making changes to the code requires modifying the comments to keep them up to date that's a big sign that you aren't writing comments appropriately.
This isn't about the indentation. Look at the examples. you can see that allot of his code is indented heavily.

This is about the amount of time and distance required to scan my eyes across a line to understand its meaning. How much do I have to read to understand a simple concept?

This is also about the amount of screen real-estate i have to use. We arn't programming on VT100 terminal any more, damn right. NOW I get to have the compiler output and continuous integration output to my left. The directory, class structure and documentation to my right.

I also get to split my screen to have two editors open for comparing snippets of code line by line.

Merge conflicts and diffing are hugely common operations. merges have three parallel windows open at once!

You, still, only have 80 characters to work with.
Re: Adria Richards — Am I making things better?