skysight-inc/HackerNews huggingface dataset:
Slightly-related: has anyone interviewing with Airbnb used the author's public starting offer of $220k total compensation to negotiate their own starting offer? Genuinely curious.

http://haseebq.com/farewell-app-academy-hello-airbnb-part-ii...
The Shikoku pilgrimage is still one of the best experiences I've had in Japan. The hospitality, generosity, and respect you encounter along the route, not to mention all the people you get to meet, are so unique.
Everyone already "knows" the US was "involved" in the 1953 coup but very little more. Britain was not the junior partner - as you say Chomsky thinks - but the instigator of the entire operation.

Britain has been deeply involved in the Persia/Iran for hundreds of years including multiple occupations and coups. In 1921 the British installed original Shah Pahlavi, father of the Shah Pahlavi deposed in the 1979 revolution. And before Pearl Harbor brought the US into WWII the British - in cooperation with the Soviet Union! - occupied Iran.

If Britian had not been weakened by WWII and terrible economic policy it is unlikely that they would have spent a year begging the US to assist them in Iran. Until this time the US had little involvement in the region.

We luckily live in a time (post 2013) when you can read the CIA's own fascinating history of the event:

http://nsarchive.gwu.edu/NSAEBB/NSAEBB435/
I'm sorry but I beg to differ, web programming 10 years ago was a nightmare. It's much better today. It's not web programming that sucks, it's programming with others. I bet most people won't complain much if they got choose what tools they wanted and worked alone. When working with others, different ideas and opinion clash heavily. Programmers are not best known for their awesome communication and the lack of it leads to more mental strain than necessary.

The reality is that one can drive the frontend with 100% javascript no frameworks, html, css, keep things simple avoid the framework nightmare. Use typescript if the project is large enough. How come people are not doing this? Because they are not putting in the time to learn the language, it's all about learning framework. I see the same in backends, people who know rails but not ruby, laravel but not not enough php, android framework but not enough java. This is the problem.
Can you elaborate a bit please? Does this mean not meeting half way between your offer and theirs? And then what?
According to this link[0] there are more multilingual people in the world, than monolingual. So that's at least 3 billion people who "will get a phone call".

[0] http://www.cal.org/content/download/1803/19986/file/AGlobalP...
That's why it's so successful. There has to be a reason something so terrible could possibly be this successful and you hit the nail on the head.
There was a session today at Interspeech dedicated to the study of animal vocalization, though participants acknowledged that the field is still nascent. One of the posters was on Dolphin communication: http://www.interspeech2016.org/Technical-Program
How do you know you watched for the exception well enough to react fast enough to prevent disaster when it happened?

At ~30k miles, chances are you haven't seen enough exceptions to make a judgment on that.

It is hard to stay focused on jobs that are extremely dull, except for the rare cases where they aren't.

There's tons of research on this because there are many people in that situation (watching radar screens for incoming ICBM's, guarding a facility, luggage screening at an airport, etc)
Twitter has way worse UI than Reddit or Amazon. It's flashy and barely functional, as opposed to crude but extremely functional. Whereas reddit pages load instantly, any Twitter page is a 10 megabytes-sized blob of Javascript that slows your browser to a crawl.
Using Webpack with the Amazon Cognito Identity SDK for JavaScript
The Fed admitted that a startup can predict its upcoming interest rate forecasts
My take is that if you removed all of the crimes committed by black and hispanic people, the US would still have a murder rate that is multiples of that in many other developed countries. Clearly there is some other factor - one which is objectively larger than race - that should be the top focus.

That's inaccurate. The European population in America has a crime rate inline with or a bit lower than European populations in Europe, certainly not "multiples". http://www.unicri.it/services/library_documentation/publicat...
Well I think it has something to do with the web's success.

For one thing, the HTML/CSS/JS separation of concerns made it so that someone could make a non-interactive, static web page with very little knowledge. The basics of HTML and CSS can be taught in a week. This is important! I think we would have far less success training people to create static documents with many of the various programming language UI Kits. Though becoming less important, there was definitely a time when this helped to increase the adoption of browsers (and I would argue still makes it easier to teach).

Another thing, is the HTML/CSS/JS were all open standards that have accepted contributions from a wide range of parties. Look at scheme: beautiful, consistent, and completely unused. HTML/CSS/JS would without question be much more pleasant if they had been designed by a benevolent dictator. But open nature of the RFC process I think both greatly helped adoption as well as contributed to the inconsistent nature of the APIs.

You only have zero-install (i.e. ships with the OS) because the web got wide spread adoption, and I think HTML/CSS/JS contributed to that.
cool read, thanks for sharing!
How can programming with others be the reason, if the OP is saying they find programming for the web with others is much harder than applications development with others?
However, far fewer of them are Americans....
It's this kind of personality that I look for in my organisations, mainly to isolate and slowly get rid of. The focus on "me" is so toxic. No amount of brilliance makes up for circles of damage to other, modest, hard working people.
> the Doctor responded directly to my review, calling me out by name and essentially calling me a liar (I wasn't)

That seems likely it would violate HIPAA in some way...
You made some very valid points, and I'd like to point a few things out:

"He didn't get a 250k salary, that was total compensation, largely RSUs on a standard vesting schedule."

Yes, and he purposefully chose (as he describes) the more "illiquid" of two offers.

"He also donates 1/3rd of his pre-tax income to charity."

Admirable and very commendable (I can't stress how much I really respect this about him), but irrelevant.

"If you spend 15 minutes talking to him, he'll leave an impression."

-- the definition of "charisma"
That doesn't mean it isn't terrible to work with and couldn't be much better. Unless you think the tool flaws are inescapable aspects of reaching a large audience?
This is a particularly interesting anecdote about someone faking his way into Google, and then later starting a company almost as famous.

https://www.wired.com/2013/04/fakeit/
It's the same like any other open source project: it gives you 100 ways to hang yourself and maybe only one way to do it right. Your job is then how to find that one way.

Frameworks? use them when you need to deliver crap, fast! :)
Deep Brain Stimulation surgery fails to outperform placebo (2015)
Ask HN: Does JavaScript have race conditions?
During an interview, I was asked how to avoid race conditions in JavaScript. When I explained why JS did not have race conditions(single threaded event loop) the interviewer looked unhappy. I googled and received mixed answers. Some say yes while others say no. Any experts here can help me with this confusion?
it was a nightmare (because of the browser support), but it was a nightmare with a hope that it will get fixed (browsers will get better, there will be simple thin abstraction libraries added, etc).
It's been ruined by a generation of developers who believe it a good idea to build stateful applications on top of an inherently stateless document-centric infrastructure.
I use GWT for anything serious. It's not what the cool kids like, but it feels super-solid compared to the flake that I experience when working with a heap'o JS libs. And debugging it years later is awesome (barring a couple gotchas) because it makes sense.

I've always thought GWT has a crazy learning curve until we did a project in Angular2 on top of ASP.net core, using a customer-selected template that required tons of JS fun, with random CSS class names that have zero obvious semantic benefit so you have to look everything up. Not even Typescript could save the feeling that we were building a house of cards in a strong breeze. Same with Django + JS. Just felt too scripty for me.

I don't like leaky abstractions but honestly the modern web fundamentally forces you to use them for anything vaguely complex. It's not getting easier, it's getting much, much harder. GWT at least gives me a way to trade off complexity for a clunky but solid language, and I get to reuse code on the front and back ends.
An 'academically good UI' should be easy to understand. Sure, that doesn't mean people will use it, but the ability of users to understand the UI is pretty fundamental - if they can't understand it, the UI is not 'academically good'.

Some places like Craigslist choose to maintain their rougher UI, since a slick UI will scare off some users.
The real problem is that 1 was turned into 2 without replacing 1. It's kind of amazing that HTML and CSS have survived all the way through 2016, and don't look they're going to be replaced for a long time.
I am in opposite thinking, that they have great UI, but sure everything can be improved
The OP was opining that the web stack is hacks built on top of hacks, not that web developers are poorly skilled. They use what's available to them.
> it did seem to me that the core team is not interested in this feature.

It was proposed by a core team member, even. Changing a language takes time. There's only so many people and so much work to do: the author of that RFC has also been working really hard on incremental recompilation, for example, which a lot of people have been waiting for.

To re-phrase someone from the Reddit, you can't win: if we don't add new features but fix bugs, people claim that you ignore feature work, but if you add tons of new features, people wonder why you're bothering to add new features when there's lots of bugs open. It's tough.
I agree, and I decided I won't accept the hacks and compromises anymore, and started building everything in Go (even frontend stuff) in my free time. There's much to do, but at least the foundation (type system, type safety, etc.) is very solid.

This way, I don't have to build on top of the hacky and messy things anymore, but slowly take my time and do things very right.
anyone can come on board and contribute.

The corollary to that is that the system uses components that target the lowest common denominator. I'm not sure "anyone can contribute" is a good foundation for any complex technical endeavour - if we are speaking specifically of implementation.
Complicated to create UIs? Win32 was complicated. MFC was complicated. GTK is hard

HTML and CSS aren't as complex as those. Not even close
There are billions of dollars made annually that depend on the web being a complicated clusterfuck of spaghetti. It's all about tracking and targeted advertising that wouldn't be possible if a random website couldn't indirectly load a script that indirectly loads a script that loads an image that indirectly drops cookies from a thousand different domains based on a hundred things just sniffed from your browser and the current marketing efforts of thousands of companies bidding for impressions or clicks or whatever.

My pet theory is that commercial politicking is at the heart of everything wrong with the web. Apple, Google, Microsoft, and Mozilla basically sabotaging initiative after initiative for decades trying to fuck each other over in the short term and long term. Like why didn't xhtml catch on, why did IE never support xpath, where did flash go, what happened to silverlight, there are hundreds of "how did we get here?" stories. And I imagine for every minor decision that had far reaching repercussions on web development there was a highly strategic debate at each respective company with high level executives weighing in on technical subjects they had no business weighing in on with shit like "if we support this simple protocol we risk losing our control over this other simple protocol". Basically a bunch of cut throat executives playing statecraft with their browsers.
How Does It Feel to Make the Front Page of Hacker News?
Remember MS-DOS also succeeded because of its "strengths" in some very special, narrow sense. In the more ordinary sense, it succeeded in spite of its weakness, but Windows has slowly recovered from that and is now a good system.

The modern web is somewhat the the reverse: it is worse than its progenitor. HTML, HTTP and what would eventually be called ReST were all good ideas and succeeded because (a) they were a good way to put hyperlinked multimedia on the internet and (b) hyperlinked multimedia turned out to be the thing that masses of users wanted.

The subsequent effort to retrofit that and turn it into a zero-install software delivery platform is where all the insane hackery comes from; and the hacks that succeeded didn't have to be good. They are just what worked at the time with some combination of IE, Netscape and Flash.
GM: 4m vehicles recalled over safety bug
Javascript is platform-independent code. If you mean something closer to assembly/machine code, then that's exactly what asm.js/WebAssembly is.
Alternatively, an existing Airbnb employee who negotiated a raise based on the same information.
Volvo and others can say whatever they like, until they bring something to market I will assume they are freaking out as how they will slowly be made irrelevant.
Sound is out of sync in Safari (9.1.3).
>Didn't Brazil recently require WhatsApp to cease service in the country for a short bit of time?

No, a judge had whatsapp blocked in Brazil and it resulted in a backlash from citizens.
I think any programming model that's been around for a long time is complex. Backward compat is the devil. Take OpenGL for example. All the compat stuff has made it practically impenetrable.
Home Healthcare service for India
Thats great, except Google has already done this.
Is LiDAR worthwhile despite rain and snow detection? Can that be ignored in software?
Ok, you're right, and I wasn't completely sure myself when writing this sentence. There are cases (integration of web services, the overall architecture) when some difficulties from the web architecture swap over to the backend.

But wouldn't you have a similar problem if you try to integrate something other than web services, too?
That is so true !

I have come to believe that getting a job is either luck or accident.

Qualification is just the other half of the whole story. And by qualification I mean not just the scale/standard by which I would be measured during the interview but also formal educational endorsements.

Am I qualified to get a job ? Maybe. Am I lucky ? I'll find out. Same holds for any job seeker out there as well. Will I do anything meaningful at work or release more bugs than anybody else out there... Time will tell.
> I read the the US government estimates a 80% civilian mortality if the power grid is down for a year.

Our food production, waste and water treatment, hospitals, etc run on electricity, sure. But 80% doesn't seem anchored in reality.

I feel like this irrationality about the risks posed by a blackout is what the article is meant to address.
Cool map! Is that coded with Cesium?
Hasn't Google Maps been collecting driving data from users of their app for years now? https://googleblog.blogspot.jp/2009/08/bright-side-of-sittin...
> laravel but not not enough php

I haven't used those much, just glanced over a system written in them. But that sounds bizarre: I thought the whole point of PHP was to be bland and mainstream. If you know how to program at all, then what is there to learn about it?
Me too - android 6,latest chrome. Works fine on Firefox on the same phone...
That's how default judgements have always been. The person ignored their chance to plead their side of the case, and thus they don't get a say in what the damages are ordered, and the only figures the court has are what the plaintiff asked for. If you don't want to have the exhorbitant amounts usually asked for in an initial suit, show up to court.
This is exactly why I've always been puzzled by the urge to move more and more logic to the frontend. In backend development you have a choice of many mature languages, tools and frameworks which are fairly sane. I'll take that environment as the foundation of a web application any day and apply the mania of client-side javascript to it selectively in cases where we need to minimize server roundtrips.
Javascript, CSS and HTML can all be used powerfully, performantly and in a managed way where anyone can come on board and contribute.

I disagree. Compared with other languages and technologies used for similar purposes, none of JS, CSS or HTML is particularly powerful or efficient, nor do any of them provide particularly good tools for helping new developers get up to speed or co-ordinating large teams working on the same project. I initially wrote a huge set of specific examples to support these claims, but on reflection I'm not sure criticising JS/CSS/HTML in excruciating detail would really advance the discussion here. Suffice it to say that best-in-class programming languages, document preparation software like TeX or high-end DTP applications, and representations like PostScript and PDF, have all been doing everything JS/CSS/HTML can do and much more for a long time.

Facebook, Google and Microsoft all use the web stack to run huge companies.

That's not the whole story, though, is it? For example, both Facebook and Google became successful primarily for the hard problems they've solved on the back end, particularly in terms of scalability. Facebook's main web site is nothing special in general UI terms, and their web-based tools for advertisers are awful. The search engine that took Google into the big leagues was famously extremely simple on the front-end, and while today they also have applications like Google Mail and Docs/Apps/whatever it is called this week in their portfolio, again the front-ends for those are still relatively simple in general UI terms and would probably be unremarkable in any other context.

To broadly paint this web stack that so many people poured countless hours into making, as 'impossible' to use is doing it a great disservice.

I don't see anyone saying it's impossible to use. However, it's probably fair to say that the state of the art in front-end web development is between one and two decades behind the general programming community, and that many relatively inexperienced people working in the web field are slowly but surely learning the same lessons (and repeating the same mistakes, and repeating them again) as the rest of the programming world did before. One of the biggest problems, IMHO, is that quite a few of those people now work for influential businesses like Google and Facebook, which means quite a few even less experienced developers assume they know what they're doing. And that's how you get framework fatigue, left-pad, "living standards", sites and apps written more than a year or two ago no longer working in modern browsers, and other such madness.
We put people on the moon without benefit of "scalable" languages, we built entire operating systems in C which is notorious for quickly becoming unreadable, and we've somehow built an entire world of content using HTML and CSS.

JavaScript is just a language, and while improvements to it are being made constantly, the biggest obstacle is not the language, nor the way browser makers support it, but the absurdly slow pace of some organizations to update their browsers to something sane.

Pick a language, any language, and then restrict yourself to features only ten years old. That's what JavaScript is like in some cases, but the good news is ten years ago some pretty good things were happening.
Angry Birds and Candy Crush are clearly superior uses of time.
Obviously they are implying a lack of skill.
Vested interest probably thinks that would cheapen the brand, since "customers don't want electric cars". You don't have to go further back than 2012 to see media commentators routinely use the term "clown car" or "golf cart" to describe electric cars. Would not completely surprised if parts of BMW management are of similar persuasion.
You can transpile to ES5 if you've got compatibility issues. Not really a problem.
"it's not web programming that sucks, it's programming with others."

Most non-trivial systems require several contributors. 'Professional' means among other things being able to work with others.

"When working with others, different ideas and opinion clash heavily."

Sounds like herding cats. Any complex system should have a technical lead/architect who actually has the authority to say which technologies will be used. It does not mean he shouldn't discuss this with others - but the fact that there is one authority in the end simplifies things.
Someone needs to interview this guy's coworkers and ask them what they think of him.
I think you're extremely overselling the complexity of things. Sure, there's a lot of layers and parts involved in making web pages work and in the popular web development ecosystem in general, but they were usually created to solve specific problems, and knowing of them can help you recognize how problems you may run into may be solved. None of them work by magic or are beyond comprehension.

The browser speaks the HTTP protocol to a webserver, and receives primarily HTML. The HTML is styled with CSS and can execute Javascript. Javascript running in a web page uses the DOM (Document Object Model) to interact with the page's HTML.

Javascript bundlers (Browserify, Webpack, etc) let you modularize your code across multiple files and bundle it up into a single output file for browsers to download. Javascript minifiers exist to strip out everything from a Javascript source file that's not strictly necessary to execute it (comments, whitespace, original variable names, etc) in order to make it smaller for download. Various compile-to-javascript systems exist: Babel to let you use upcoming Javascript features, Flow and Typescript to let you use annotations for static typing, emscripten to let you C/C++ on the web, etc.

Like any other popular programming language, there's a healthy ecosystem of libraries for Javascript. There are a lot for algorithms and data structures like any other language, and you also have plenty specifically for adding abstractions to using the DOM. The DOM is definitely usable on its own, but many applications benefit from using abstractions from libraries to interact with the DOM. This isn't very different from the popularity of GUI libraries (Qt, GTK, MFC, wxWidgets, etc) in desktop applications over the raw OS windowing APIs. jQuery provides a fluent API for manipulating sets of elements directly. React provides a system for making modular user interfaces taking some inspiration from functional programming and de-emphasizes manipulating elements.

All of the parts mentioned above were introduced to solve a specific problem. If you understand the problem they were built to solve, then their designs are often intuitive. If you don't currently understand the problem they were built to solve, then (for anything after the 2nd paragraph) you probably haven't hit that problem and often don't need to use them.
Lol Hostgator
APNIC's new Statistic Portal launches
Cool! when tab is not active, the rhythm slows down in Chrome/win7.