skysight-inc/HackerNews huggingface dataset:
It is true [1].

"Cyprus President Nicos Anastasiades says he is battling against eurozone demands that all bank customers pay a one-off levy in return for a bailout.

Mr Anastasiades said he shared people's unhappiness with the terms, whereby all bank customers would pay a levy of 6.75% or 10% on their bank deposits.

The EU and IMF have demanded the levy in return for a 10bn-euro ($13bn; £8.6bn) bank bailout."

The key thing here is that the EU accepted the original proposal, they were okay with seeing deposits of less than €100k being hit, regardless of any deposit guarantee. Public fury resulted in the Cypriot Parliament rejecting the proposal and the EU back-peddling from the original terms.

[1] http://www.bbc.co.uk/news/world-europe-21824495
The simple fact that "professional arborist" exists as a profession might be hint enough to you that saying "trees exist in nature, therefore you can have them anywhere you'd like" might be a poor bit of logic.
He explained in a comment how he ended up transporting it with a flatbed trailer:

"It was transported by a semi on a flatbed trailer from Ohio to Montana. I looked into all kinds of less expensive alternatives including paying someone to drive it, but I couldn't get anything reliable to pan out."

http://geckodesigns.kinja.com/it-was-transported-by-a-semi-o...
Spotify Plans to Take on Netflix and HBO with Streaming Video Service
I find comments useful in two main cases:

1) When I'm not all that familiar with the language. This allows me to grok the purpose and actions of code quicker.

2) When the action being performed contains more lines than fit in the screen. Knowing a bit more context going in can make what follows more clear.

For 1, it's a matter of who you intend to read/modify the code after you. For 2, that's probably more a case for splitting that code into multiple functions.

From that, I think comments are best used by poor and great programmers, but the middle of the road may not get much benefit out of them. If you don't know how to split your complex bits of code into multiple chunks, or if you expect most people coming after you to now be as experienced as you, comment.
There's a tracking hash ("#.UU-2q9uRnOI.facebook") that probably should be trimmed before posting.
1.
I tried "pay what you want" while doing pro photography gig and it didn't work well at all - people got confused, people didn't know what to pay and just left without buying anything.

Bottom line #1: people need to be told what to do, including how much money they need to give.

2. When selling subscriptions (I'm the author of MemberWing - wordpress plugin allowing bloggers to sell flexible subscription packages to sell access to premium content) it is wiser to charge flat fee yearly access instead of montlhy access. Why? Because what people are willing to pay today is way different from what people are willing to pay tomorrow. Why yearly? Impulse buyers! When person is excited - he is willing to buy more and pay more.

Bottom line #2: Monetize positive emotion! It may not last long :)
What Windows Blue leak says about Microsoft's strategy
indeed there will be some further dilution, but typically there is not dramatic liquidation preference on winners, at least that we have seen thus far. if you like, you can double the exit targets I mentioned, but regardless we are looking for ~10-20 companies that exit north of $50-100M, and 25-50 that exit at between $10-50M.

overall 500 is currently about 22 people. of those, we have ~10-12 investment professionals, each of which is making 10-25 investments per year. if we are lucky, 1 or 2 of those might be larger wins, and 3-5 might be smaller wins.

since we generally do not sit on boards, most of our team is not spending the majority of their time in future years managing a large # of investments, altho they do spend time in the first year or so helping some of them get financing from downstream institutional investors.

hope this helps explain our strategy.
Yeah - I was thinking about a Java codebase I was looking at a while back that had ultra verbose variable names like "BackupCopyOfLedgerUsedInWorstCaseScenarioProjections" You couldn’t even do a simple addition in 80 characters.

This limitation seems fairly language specific, and has a lot of side effects for the rest of your style guide.
Comments - like documentation - are a liability. Most projects tend to treat them as supporting artifacts, but they are actually unidentified risks. Did you account for the time spent either rewriting documentation/doxygen/comments as you go (frequent chunks of small work) or an after the fact round of document backfilling (single chunk of large work) in your schedule?

No one even reads those documents. The client claims they are to assist future developers - internally or another vendor - but would you trust a Word document or a .cpp file when everything is on fire and you need to figure out a system's behavior? Same thing applies for code comments.

There is one source of truth in software, the code. You can pile on the design documents, wikis, and architecture diagrams but at the end of the day, what is coded is what gets executed. Make the code easy to understand and reason about. And then, if you really want to be nice to future developers, throw in a single page overview of the codebase (README) that gives someone an entry point.

Edit: I will just add the caveat to preempt the inevitable - this does not apply to public facing documentation of an API/framework/library etc.
I think the question misunderstands the nature of the task.

The HN page is a list with each list entry having a similar structure being made up on a number of components (like an up vote facility). the HTML table seems to fit the requirement perfectly.

As to "in line" styles and JavaScript - this approach would seem to me to be very well suited to the task of generating the individual components that collectively construct the list of entries. A small snippet of code can be used to generate each component. Maintenance is a breeze - adjustments need only be made in one place in the code base.

So all in all, what we see is a simple solution to a straightforward task.
> Next Big Thing is not a place for ... anything else flat out offensive.

Said Putin about Pussy Riot.
Closest you can find is news.arc, for example see a mirror on [1]. The canonical source should be in the arc distribution.

[1]: https://github.com/wting/hackernews/blob/master/news.arc
It's a huge anti-pattern, because then people train themselves to think that slamming out a lot of trivial and redundant comments is a good use of their time. Worse, then they get used to writing lots of trivial comments and the really important more complex or subtle comments go unwritten.
Dual Pivot Quicksort (better expected constants) [pdf]
That's kind of a silly thing to say: "Most people here are depressed because they don't have JESUS". I'm completely happy and content with my life despite my lack of "spirituality".

Also, you don't know this person. Maybe they're homosexual, TEAM JESUS is really going to help him out there.

I have no qualms with suggesting religion, it helps a lot of people get to a better place with it's structure. However, don't imply things about others.
What is your response to this point though? I don't see how it is anything but completely valid; the point is that there is no objectively defined action that is prohibited for one group and allowed for another, so the "equal rights" argument is a canard. Perhaps there are other arguments to be made, I certainly don't want to get into that here, I am simply responding to your feeling that this is an infuriating thing to say.
You do not have to rely on an application process when looking for a job. This isn't just advice for people who think they have a challenging story -- it goes for everyone. There are hundreds of stupid ways you get filtered out.

There are examples of far worse felons than the OP who are employed in CS. Find a way to tell the story honestly and in a way that shows that you learned from it.
(1) Become a top performer in college by working hard
(2) Make public works
(3) Build a network

Do that and you won't need to run an application test.
There is a history of putting large plants inside glass buildings at ground level. Because in a building with amazing views and glass walls you should make people look at something that is trite and artificial! Skyscrapers are already in a sometimes beautiful dynamic natural environment (the sky). Putting trees in the sky is absurd.
I think it's cognitive dissonance [1] You admire the works, but can't admire the man. Other people in this category: Mike Tyson, Roman Polanski, Roald Dahl, Julian Assange.

[1] http://en.wikipedia.org/wiki/Cognitive_dissonance
It seems like people are talking about a bunch of stuff like the ability of amateurs to create a web page easily and that sort of thing.

Maybe some of that stuff helped. But I don't think those were the big reasons. Look at how the web works:

1) Web pages work on all relevant platforms. If someone creates a new browser, most existing web pages will render on it, and failures are in the nature of bug fixes rather than complete rewrites. Compare this with e.g. new operating systems and C programs.

2) If you change the web page, the update is available immediately to everyone. Compare this to the morass of outdated, incompatible and vulnerable software on your typical Windows box.

3) All the code effectively runs in a sandbox. Users generally don't have to worry about clicking on a link and having it send virus spam to everyone in their contact list.

Those are some huge advantages. Advantages that more than make up for the fact that web development is a huge pile of kludges built against each other that only hasn't been discarded and replaced entirely as a result of the massive amount of mutual interdependence.

The primary competitor to the web was Java. But Java was hampered by horrible mismanagement on the part of Sun and repeated malicious attempts to destroy it on the part of Microsoft, so the web won. Which is probably unfortunate. Imagine a web where Java (or Go) rather than Javascript was the primary language.
I started writing code in a more literate style recently (where the code is a document with markdown interspersed with the code segments) and found that writing what I want to do first makes the development process much easier than just delving into code. Feels like writing a paper in many ways (you write the outline, flesh with your thoughts on how it should work, and then start writing code)

I put this tool together on a whim (although the github rendering is somewhat strange because I took liberties with the fenced code blocks): https://github.com/niggler/voc
They rare.ly last
Bad comments are like bad tests, they're bad. Good comments, like good tests, are a boon for complex software.
Florian's earned his money on this one by inserting the factually accurate yet misleading phrase "64 granted patents and 22 pending patent applications" into almost every story about this.

I also note the linguistic irony of accusing a rival's technology of being "proprietary" while at the same time claiming ownership and veto rights over it.
I'm not saying this was done on purpose, but I find this name and concept eerily similar to the music analytics startup Next Big Sound.
The downside with this approach is that, with active projects, you end up with hundreds of remote branches. They'll never get deleted with `fetch -p`, and if you remove them manually they'll just come back.
To verify that there's no foul play, there would also need to be a way to check that the code on github is what is actually running on the site...
The example you give is the kind of thing that Ember is really good at.

You would implement all those interrelationships with computed properties. Each computed property updates automatically if its dependencies change, and each view redraws automatically when the corresponding properties change. All that work of defining events and propagating them through the mediator is stuff that Ember does for you automatically, once you've declared what depends on what.

I'm one of the early adopters who built a rather big application in pre-1.0 Ember. It definitely pays off as the application grows larger.
Take your computer, and go to a place without Internet. It make take some time, and the first week will be horrible, but one morning soon enough, you will feel the urge to program again.

When it happened to me, Internet wasn't available yet, but I sold my computer and after one month, I was only thinking about programming I did a gig for free just to be able to program on a Mac (they weren't cheap at that time!). :-)
The PeepCode iOS App
This. Comments and documentation are pointless unless they are audited and vetted somehow, then there is the extra cost associated with maintaining them. Managers who don't know better think its just a bit of extra work that the developer does up front, but that is pointless without the above.
"There is one source of truth in software, the code."

I agree with this statement wholeheartedly. Documentation starts with readable code. Comments can go out of date and, worse, lie to you.
This isn't about the indentation.

From TFA:

Also, having the mandatory indentation whitespace increase the line width is a good visual way of minimising the nested loops in your code and suggesting, in a subtle way, to refactor anything that is indented more than about four times.
> Comments - like documentation - are a liability.

Tests, too. But you wouldn't advocate not having tests, right?
Not necessarily. You could build a smoke test (experiment) for a SaaS solution for dog owners (product)

You have your vision, but before you go into building a product, you test your target market.
Google Cache: http://webcache.googleusercontent.com/search?q=cache:vmu82nX...
With default bells and whistles your IDE provides enabled, you'd be lucky to have a 79 char wide editing area.

There are modern options though:

1. Disable unnecessary stuff on your IDE.
2. Don't use a IDE, use a dedicated editor.
3. Don't use an editor from a VGA console.
4. Stop pretending you code on a vt100.

I see no wrong with a sensibly long line which is longer than 79, just as I see no wrong in keeping multiple parts of code visible at all times. There shouldn't be hard limits or carved to stone guidelines.
Cool multiplayer card game website
I love how a lot of responses here are of the condescending tone of "we aren't using vt100s anymore, grandpa", as if advocates for the 80 column limit are still running VIC20s in their mom's basement. I see this argument pop up a lot against things like vi and Emacs as well.

Yes, we realize that monitors are bigger, resolutions are higher, etc ad naseum. None of that matters. What matters is code readability. So what if you can fit 120 characters in your code editing window? I can fit more than 400 across two monitors, should the new line length limit be 400? Why stop there, why not just let lines be endless and have the editor wrap them? Answer these questions, and you've answered why people still like the 80 column guideline, or even care about code formatting at all. Code is only incidentally written for machines to execute; it should be written for people to read.
> Try to tune out the negativity. I know it's hard, but just think of it as "systems analysis applied to people".

Hahaha... this is a joke, right? This reads like a caricature of someone being patronizing.

In case it's not a joke, let me be plain: you are being ridiculously patronizing. "I know it's hard, but..."? This is the way you speak to a child.

"Try to tune out..." Do you honestly think OP doesn't do this on a daily basis; that she hasn't been doing this for years? This is not a rhetorical question, I'm truly interested in whether you think that "tuning out negatvity" is a new, novel concept that never occurred to OP.

Ed: please take a moment to consider the tone of your post next time you are posting.
So change = bad?

Gotcha.

EDIT: FWIW, I use Windows8 and think it's superior to 7 in almost every regard :\
All joking aside, they really do need someone who speaks English natively to go over their content.
A test will at least fail when wrong, a bad comment will just be confusing.
Sadly, it is highly compressible, so air pressure would just crush the mylar ballon around it. If you could make this material rigid, so the balloon would be able to displace the proper volume of air, then you could make party balloons and airships without wasting helium.
I agree with the parent- in my case I use a 27" display @ 2560x1440. I split the screen in half- browser or shell on one side and Sublime on the other. So Sublime gets 1280 pixels.

With the project side panel open enough to see most of the project's directories it uses ~370px. The minimap (which I do leave open, and use, often) takes up ~50 pixels and the scroll bar for the edit window a final ~20 leaving me with 840 pixels that can show just at 100 columns. If I kill the minimap I get almost exactly 120 cols.

For me, I have no qualms about 79 cols for the limit and enjoy being able to use my windows split to half the screen and still have some breathing room around the right edge of my code. I also find it awkward to scroll horizontally to see what's going on in a long line.
Finally, a use for Twitter Lists
Can you provide any reference/elaboration for your claim that tree survivability is not a problem? It's directly counter to the arguments made in the article. Grasses and shrubs are a lot more hardy than trees, as anybody who's even been on a mountain can attest to.

Your other points are well taken and they are sort of addressed in the article in the form of the infrastructure issues. I think the author also would agree that it's sort of feasible in theory, but extremely expensive and impractical.
I would like to add one thing to this discussion: Martin Odersky's class (I took it last year) is also very useful if you use other functional languages rather than Scala. I have been using Clojure for about 2/3 of my development in the last year and I found this course to be useful. The lectures are also fun to watch.
Tests that are executed automatically as regression are fine. There is now way to regress with comments.

Tl;dr not equivalent.
Show HN: Convert face photos into a morphing film with FaceFilm app
Navigation Fragmentation On Android
The "Doesn't it suck" comment was not directed at Dapper.
You just gave MORE reasons why it can't happen, you never refuted any of the original claims by the article
I am not quite sure that I do understand. Firstly I don't have any problem with art mocking my mother or anyone else. Secondly I think mocking my mother is more personal than mocking my religion so your argument doesn't quite work. Thirdly people of many religions listen to black metal, and are aware that often it is a parody of itself.
It all comes down to: does the benefit out way the costs?

A well-maintained suite of automated tests provide an enormous benefit. A brittle set of Selenium scripts costs a project more than paying a Tester to manually run scenarios.
Valve was prescient about this.
If you actually need to know, rather than that just being an example: you don't. You used to have to fill in a form on arrival, but even that was abolished a year or so ago.
The problem of broken markup would have been better solved on the server side, rather than the client side.

As a general principle, pushing denormalized data as far to the edges of the system as possible minimizes complexity of the system as a whole.
You can already use those addons outside of Parse, Heroku etc. Maybe what you want is like a library of all available addons for all services?
Sure, but I think you would be hard pressed to find a company that didn't have some form of email system for dealing without people outside of the company etc even if internal communication is done by some other tool. It's a network effects problem, you could build a better email system but you can't get rid of email completely until it's as commonly used as email.

Such a common tool needs to be highly resilient to catastrophic failure in the same way email is.
For example the DDOS on sendgrid affected sendgrid and their customers but the rest of us were unaffected.

The implications of a system that allowed groups like Anonymous to cripple worldwide trade at will via DDOS would be quite scary.
A Populist Plea for Classical Music
Those companies are investing in that framework. It's currently in the form of a bunch of drafts on W3C. Web components and the shadow DOM are a few that embody what you're talking about.
The Leaky Bucket Myth
2 times 120 is 240. Which at 7px each clocks in at 1680. It'll work on a desktop monitor, but probably not on a laptop.
Dribbble's first shot: Working on the new shop
Looking for the best .net/mono orm with multiple backend support (Sql Server, MySql, PostgreSQL, Oracle, Firebird, Sqlite) ?
Take a look on ServiceStack.OrmLite
https://github.com/ServiceStack/ServiceStack.OrmLite Disclaimer: OrmLite.PostgreSql maintainer here
When did the web get do damn complicated?
Definitely not a mobile app developer, actual or otherwise. But, as a user, I look forward to the day when I can, say, take a newspaper article, and send them to GoodReader, or grab my boarding pass on singapore air, and put it into Omnifocus.

It is a little frustrating when I see the Doc/Object right in front of me - and I can't send it anywhere.

My current model of sharing files/docs between Apps is usually to Take a screen shot with the Home/Power button, which gets it into my camera roll, from there I can copy/paste the image into various apps that take paste.. Screen Shot + Camera Roll + Copy/Paste is my current iPhone Inter-App sharing process. I have to believe there is something more efficient in the future.
"would you trust a Word document or a .cpp file when everything is on fire and you need to figure out a system's behavior?"

There's a bigger philosophical problem here. If your development cycle is code -> comment -> code -> comment ... (where you write code and then comment), then your criticism is fair. But the right way is to comment first. When you describe what you want in words, then you or anyone else can go back and evaluate if the code matches the words.

(In my experience, 90% of bugs stem from developers thinking one thing and implementing something different, and these could be avoided if you had a normative document)

It's like writing a paper: you outline, sketch out what you want to say, and then actually start crafting sentences. The outline should guide your paper, and if there's a problem you first update the outline.
my point is that these questions seem either misdirected or simply answered. that is to say, it's not a framework. it's a set of classes. how you handle templates, how these classes fit together, etc is hardly a function of Backbone.

don't get me wrong. i've been there. i've had the same questions. but i think the answers i gave would have satisfied me when i was starting, had i had a mentor.