skysight-inc/HackerNews huggingface dataset:
I think the thing that puts me off the most is the lifetime specifiers:

let foo:'static str = "foo";

Whenever I see an apostrophe, my mind defaults to frantically searching for its counterpart at the end of the string they're enclosing. Just like for parentheses; imagine how confusing it would be if ' would have been ( instead.

let foo:(static str = "foo";
> I desperately need TypeScript React Hot Module Replacement Plugin

I worked on this for electron-compile but unfortunately React HMR itself (react-proxy) fails with actual classes (i.e. using the `class` keyword not-transpiled) or anything other than Babel's ES5 class keyword transpiler. Once they fix that, apps created via electron-forge or that use electron-compile will get TypeScript HMR automatically.
Fuel is funny, because you keep some, but you're paying more by moving more mass. It's sorta like a special case of th rocket equation.
Carriers would just get more money: "Your phone is too old for Google. Here's a link to our special offers for new phones that play nice with Google"
Flask lets you share state between requests; just have the route methods reference some global variable. You could also apply the route decorator to an instance method (although probably not using the decorator syntax).
That's still better than most other airlines. I'll definitely be considering SW from now on. I'm assuming they only do domestic flights?
MEMS would be solid state pretty sure.
Hmm. Those seem like very solid numbers. I wonder how the total accident count compares. Scratched cars are of course not important in comparison to a human life, but I'm curious whether my gut feeling of not being able to obtain an appropriate overview actually translate to accidents.

Fatal traffic injuries are quite rare over here (175 in 2015, which gives about 1/4th of the fatal injuries in traffic per capita of USA), with most seemingly being bicycles killed in intersections by trucks turning right in the city (We have far more bicycles than cars, and they seem to enjoy ignoring rules while simultaneously going "I HAVE THE RIGHT OF WAY AND PRIORITY OVER MOTORISED VEHICLES, SO I SHALL PROCEED BLINDLY").

I might be underestimating the intersection problem as a result of our "gentler" traffic (I don't recall ever actually seeing an intersection incident - I mostly see two-car incidents on the highway, where some idiot is too busy on their phone to see that the car in front is braking).
You may enjoy: http://www.cookingforengineers.com
Προγνωστικά στοιχήματος Παρασκευής 28/04/2017
Yeah, but the problem is that most tickets are now, in effect, standby, but not labeled as such. Hence why the parent suggested making the status (and the option to upgrade) clearer and more readily available.
FWIW, for the 2D graphics packages I'd argue Acorn has tried to do this in generating shapes where it has an interface letting one chain-together and re-arrange actions.

(shameless plug) I've tried taking the approach of making a plugin for existing tools (Sketch, Sketchup, Photoshop, etc.) to make accessing the large set of tools easier via touch gestures at https://thimblemac.com . It also tracks most-recently-used tools.
The fuel increase is marginal. You still have to burn fuel to carry that fuel to the next airport. And you have to carry the airframe with capacity for that empty seat. The 100 kg for a passenger+luggage is much less than the fractional weight of the plane required to carry them!

For some numbers, a 777-200 carries 313 passengers, weighs 135k kg, carries up to 100k kg of fuel, and has a max takeoff weight of about 250k kg. 313 passengers and luggage, averaging 100kg, weigh just 31.3k kg. Your ticket therefore pays for your weight, plus 5x your weight in airplane structure, plus (up to) 3x your weight in fuel.

If you don't show up, they're still carrying 8x your weight anyways, so saving 200kg isn't that important.

(PS: apologies for the 'thousands of kg' units. I thought it was more readable than Mg or fully written out numbers.)
Are you sure that's not spam?
Sorry, I can do better, just a bit tired of seeing shallow comments on hn.
A few links later and I found:

>So here's raising a glass to our kind. We have done a remarkable thing ... to set our craft on a long-distance mission in search of lovely blue oceans like those of Earth, and have it answer us with such gratifying certitude.

http://ciclops.org/index/8201/A-Subsurface-Globe-Encompassin...
But they usually don't use major, convenient airports.
Well 2ble highly unpopular opinion: russians are a tad baked in a very passeist ideology that may make them do a good things while they have ill intentions.

The data so far have been pretty checked, and pretty alarming on the actual state of democracy. To be honest it looks like NSA/CIA are now copying the worst of the KGB bad practices that made USSR being tagged dictature.

Russians thinks democracy cannot reform themselves and it will lead to chaos as the truth about USSR made USSR crumble down by losing their allies in the western world.

Is it sure?

Let Russia spend money thinking they undermine democracies while actually helping them being stronger.

Hell may be paved with good intentions and bad intentions may also results in good deeds.

Anyway, when you have lived during cold war it is fun to see Russia and USA swap their place.
There's another one called Orange Sunshine also that just came out. I haven't seen either, but they both get 100% on Rotten Tomatoes.
Yeah, his writing style reminds me of Ted Dziuba's past posts.

More people should read Arrington's post which has a classic Teddy Roosevelt snippet: https://techcrunch.com/2007/10/12/the-man-in-the-arena/

My memory may be hazy, but I vaguely remember him during saying something similar onstage during a past YC Startup School.
Uhhh nope. In TypeScript 2.2.2 your first example is definitely the error you'd expect.
> Using the C++ namespace separator of :: is just ludicrously obtuse for an extremely common symbol

Obtuse? It's sort of common. Multiple languages use it. Personally I like the namespace separator being distinct from the object/struct element accessor. At least they didn't copy PHP in using backspace...

> using the & for refs is archaic (I mean... you could have just called it a ref. ref T instead of &T. And then just ref(foo) or foo.ref to get a ref to foo.)

Please, let's not have more cases where things look like functions but aren't. Functions should look like functions. Operators should look like operators. You might have to learn a small set of operators for a new language. This is front-loading some confusion and learning pain for ease of use later. It may make the language harder to read for people that don't know the language, but anyone reading the source code with the aim to make some changes should probably know the operators at least. I'm not sure giving it a slightly more expressive name but making it look like something else actually makes life easier for those people.

> And I certainly would have argued for whitespace significance, at least as an option, instead of classic semicolon spam.

Optional whitespace significance? That sounds like a recipe for disaster, IMO. I can see a case for one or the other, but mixing of modes like that when it deals with something that is by nature somewhat invisible (or meta), seems prone to problems.

Also, examining why Python has had problems with functional style workhorses like map might shed some light on the negative aspects of whitespace dependent syntax.
Genuinely curious about the malicious behaviour at the root of this legal battle: if the case, was it worth it from the beginning? I mean, is there a lesson for the millions outsiders out of the SV microsystem reading this? In many different environments, you lose your job, credit and reputation for much less than this and for a fraction of the potential money involved.
After 100 Days Running Pinterest App Install Ads, Here Are Our 5 Keys to Success
Call your Congressional representation, for starters. Another thing you can do is pressure your state legislature to reinstate the rules, similar to what some states did after Congress voted to remove ISP privacy rules.
I would imagine that jobs that combine a high degree of fine motor skill with judgement and technical expertise, such as plumbing or dental work, will be some of the last to be automated. To make a robot that can do those jobs as quickly and safely as a human is going to take a while and cost a lot.
Ah, the Indian head wobble.
Ask HN: Best resource for learning devops as an engineer (js/ruby)?
In my career I've been spoiled with terrific devops coworkers who have generally handled everything from code to deploy. As a result, I feel I lack in expertise about devops that I should know as an engineer. Sideprojects of mine end up going on PaaS services like Heroku or Zeit and I don't really learn what it means to set up a server.

For instance, I could tell you that you likely have a load balancer (like nginx) which you can use to point routes to different services, and I know that services are going to be things like node instances running my code; but everything I know is fairly superficial and lacking in depth. What is the best way to share secrets? Is there a standard way of having your load balancer know what services to feed to? How does a load balancer that defines routes work with a rails or express instance that also defines routes? Should all my services be built on vagrant, or has docker made that less useful?

I've been having trouble filling in these gaps in deep understanding because it seems like every setup is different, so cribbing from convention is not really possible -- and then I read a litany of stories of setups that are wrong in some way and that feeds in to this paralysis of not wanting to do things wrong.

I tried setting up a Kubernetes cluster along with Deis, but there are so many layers of different/new services that I don't know how to conceptually tie those back to a broader understanding. For instance, K8s has a load balancer 'Ingress' -- does this negate the need for nginx? But then Deis installed its own load balancer so now I have two low balancers for zero services. It's just confusing because the big picture is obscured by the novelty of everyones setup.

Thank you in advance for your help.
The original X-COM was cancelled, but development continued in secret
A few years ago I had my identity stolen by someone from a large hospital on the east coast. They charged about $20K of merchandise, opened about 6-7 credit cards and failed to open a few more before I started getting bills in the mail. It took me dozens of hours and weeks on the phone to get things cleared up. They caught the person on Target surveillance camera and finally arrested and charged them at the federal level. There were ~40 other people who had their info stolen as well. They went to prison and will be there for a few more years.

The whole ordeal was a fairly stressful thing to deal with right after having major surgery. I looked into my legal options after I cleared things up, but I couldn't get anyone to seriously listen to my case. I wanted to know whether the hospital was responsible, but I guess I didn't know who to contact (the right lawyer, etc). Everyone I contacted either weren't able to help me or didn't know I should contact.
Utter Garbage, I've experienced both, getting fired is minor hiccup compared to divorce. Divorce is very similar to the pain I felt losing a brother, when he was killed in a car accident.
I'm lucky though I soon got a better job and a better (for me) new wife and wonderful kids.
But I will never forget how awful and surprisingly painful the divorce experience was for me, after just 10 years together.
GaInAs would imply 1500nm or some non-standard wavelength, at this point I would suspect that normal silicon would do, but you just have to get down to a low enough price point.
How is your friend taking the news? I can't imagine the level of sadness at the thought of your own biological birth mother giving you up like that. Freud says they go through their whole life trying to avoid abandonment.

I'd imagine the sadness easily turning into some sort of aimless wrath. It's like being told you've lived a lie to save birthgiver's face. Maybe that's what happened to Paul Le Roux when he found out he was not only adopted but that they didn't even bother giving it a name.
But they don't toss things out of windows, they toss Windows out of things
> The problem isn't overbooking. The problem is not auctioning the seats higher when overbooked.

This. Oh so very much this. United could have avoided this whole debacle simply by not imposing price controls on the market for seats when it became a buyer rather than a seller.
OK, I agree that the ships are relevantly cheaper than the moon rockets. On the other hand, there are many organizations -- and individual people -- who could easily afford to lose a billion dollars on a moon rocket today. It was common (in some sense) for a galleon-owning merchant to be completely ruined by his single ship failing to come back. So I don't see that the cost of launching rockets is so high as to prevent the activity.

It seems like all of the work to support the idea "20% mortality is too high" is being done by the observation "there is no pepper on the moon". It may be too high on a cost-benefit basis, but that's because the benefits are very low.

But if you think that the benefits are high, perhaps because an initial high-cost high-mortality phase is the prerequisite to a long-term and profitable low-mortality phase, or even a long-term and profitable high-mortality phase, it seems pretty easy to accept 20% mortality.
In the US at least, they are now considered as a commodity. But the consolidation of major carriers (American with US Air, United with Continental) may have changed that equation.
True, but that's a specious comparison, as taxation is always a forcible redistribution of wealth. No matter what you call a tax, people know it's a tax. It's very different when there are two opposing directions on an issue and you intentionally mangle language to hide your intent, or worse yet co-opt the language of the opposition to deceive.
How to Easily Protect Your Investments Against Market Volatility
Surviving the Pull: On Communication in Code Review
Well yes, but I would assume that this case would be for inference, since GPUs are pretty much train once and deploy everywhere (granted, hyperparameter tuning is still a point).
Oh, I'm not. But I don't think the other Maps engineers took home $100 Million.

Google clearly thought it was in their best interest, but I stand by what I said: As an engineer, the most well beaten path to wealth is building something that sells. To get paid and not even have to do that is itself something of an accomplishment, though not one I'd be very proud of.
You should watch Jonathan Creek - a murder mystery series about a consulting magician. Pure fiction but rekindled my childhood interest in magic. I'm currently, slowly, teaching myself card magic now. Starting with The Royal Road.
> 1000 small commits can add up to 100 small+simple components

vs.

> Commits might be patches, but they're sure not components.

make up your mind, are components (whatever that means for you) composed of commits or not? :)
as for commits vs patches, all commits are patches + description, but we use those terms interchangebly in the linux world with this understanding. in any case, i stand by what i said, we develop our code the same way upstream linux (or really any sane project) does. we're just not developing it for the purpose of inclusion, maybe that's the source of your confusion.
Sure, but whatever he was or wasn't able to negotiate in compensation shouldn't drive the outcome here. He and his (former) employer came to a mutually agreeable deal; how much or how little that number was doesn't change the facts in this case unless I'm missing something?
The Psychedelic Salon podcast has a few of his talks. He was insanely smart and well-spoken:

https://psychedelicsalon.com/category/people/nick-sand/

Especially interesting is episode 054, where IIRC he talks about how all the high-level LSD producers and distributors he was in prison with were the children of the folks who worked on the Manhattan project.
It's not just malls. NYC storefronts are emptying out as-well due to high rents and inflexible landlords, not to mention the convenience of delivery to apartment, office or pick-up location. This map captures some of those vacancies.

http://www.vacantnewyork.com/
I believe they did this in defference to residents after an earlier, more perfectly otimized algorithm ended up turning residential streets into main traffic thoroughfares.
I like how the narrator emphasizes billion like he didn't just say "1/4 billion". I guess "250 million" doesn't have the same level of shock value.
Well, it clearly wasn't the entire country . . . I'm on Shaw, and I saw no interruption. Still, it is pretty bad.
I've used Sibelius (and Finale) back in the day. For classical music, maybe it's indeed the right tool to use. But if you're writing modern music, with all its syncopation and irregularity, it's simply painful. Rests, dotted notes, and ties everywhere. Massive, piece-wide refactoring pains with even the smallest changes. Key signature horror. Obscure notation. Lack of true support for pitch bending and non-standard tunings. It's like trying to translate technical writing into a foreign language.

Classical notation was fantastic for use with pen & paper when music was much more conservative and on-the-beat. But we have computers now. We can come up with something better — whether it's software like StaffPad[1] as a first step or something even farther removed from classical paradigms.

I've also written a bit about this in my blog[2]. Frustration with classical notation was one of the reasons why I worked on my own "anti-DAW" music app. (Though it's a somewhat less ambitious project than Helio.)

[1]: http://staffpad.net

[2]: http://beta-blog.archagon.net/2016/02/05/composers-sketchpad...
A variant of rubber-duck debugging: Ask the question and hit Send. Invariably, no matter how long I've thought about it, the obvious answer will occur to me minutes (or seconds) after I've embarrassed myself my asking. (is there a term for this?)
Everyone talks about having more compute power in their wristwatch than the entire Apollo mission series did.

I figure that NASA simply retasked the Apollo computers to image processing. Waste not, want not, but the compute time now gets measured with calendars.
Oh god yes. I don't understand why it's so hard for people to report a bug.

I don't think other fields suffer from this as much.

No one goes to the doctor and says:

- I don't feel good
- What are your symptoms?
- I don't know, I just feel bad.

It's usually in the form of: "I have a sore throats and running a fever, it began x days ago", etc

What is it about computers that makes people throw their hands in air and say, I don't know, I just doesn't work.

They are smart people, and yet it's beyond them to think that, in order to fix it, the other person must at least know what's wrong in the first place.
A lot. Feels like there should be a way to automate it away or give it to a framework to do, but the best way I've seen so far is to give that work to the junior devs while I get to work on the more challenging aspects of a project.
The problem is that accessing shared state concurrently in a multi-process context is a non-trivial problem, so specific software emerged that handles these problems for you.

The simplest solution is to use a small DB system like sqlite. It is built into Python (import sqlite3) performs reasonably well and you do not have to run an additional service.

Now if a small DB like sqlite already feels overblown to you (and it really is simple and small) you might not need concurrent access either, so the simplest solution is to just use a file where you store your state.
Which I guess is the point of magic. Manipulative, but delightfully right :)
Or someone's about to be bombed.
I'd say it's like 50% for me, I wish it was less.
see: https://github.com/jbenet/transformer
Oh man. I lived in a developing nation for a while. A couple of times, I had a week-long bout of food poisoning from "cheap and tasty" unregulated food.

It's a nice idea, loosing regulations because the market will decide, but after a couple days on the toilet, shitting your guts out because regulations hinder innovation or whatever, you know what I'd say? Fuck an unregulated marketplace. I will happily suffer the innovation-suffocating burdens of regulation if it means not having to endure that shit (literally) again.
> Whenever I see an apostrophe, my mind defaults to frantically searching for its counterpart at the end of the string they're enclosing.

In fairness, you should never be searching for matching apostrophe. Single quote, maybe. The fact that it's an apostrophe should also trigger that it might have something to do with possession... (or that something was omitted).
Yep, and worse, closed as a duplicate to a question that's only vaguely related, with no relevant answer ;)
> Correct. For over 75 years now.

Have a look at Lenin's train and try 100.

Or, the dawn of time, depending.
The rules are different for the handful of people operating at this level, same as high level politicians who get away with things that would put you or me in federal prison for decades.
Absolutely.

In real-world projects, it is very often the case that much of what I do (maybe 75%?) is basically what I think of as "plumbing."

Not just in web development, where it manifests as marshalling and packing and unpacking data, but in multi-threaded embedded programs, where it manifests as packing data into structures and sending it between tasks using queues and serialization, maybe managing checksums and supporting retries and error-handling, transmitting between chips via serial, I2C, SPI, etc), and in GUIs (managing state, moving data between formats and cascading state changes while trying to keep everything sane and consistent in a multi-threaded environment. It's often a basic design element I've seen plenty of times before but it still needs to get written and it has to run flawlessly.

The remaining 25% or so can involve some real algorithmic thinking, or and state machine thinking, and that's more interesting, but there is almost always some tedious boilerplate around it unless I'm working on, say, a side project in Haskell, but even using a nice pure functional approach which makes gleaming, beautiful functions to express an algorithm, there's the "plumbing" and the tooling, monadic and weirder.

That's just something that is inherently hard about maintaining a long career in software development -- keeping yourself motivated to get through the duller parts so that you can enjoy the more interesting and challenging parts, and not just doing the minimal, but writing quality code and comments, not skipping steps, documenting your design, writing whatever documentation someone will need later to understand it later, etc. Even simplifying and revising it just for the sake of reducing complexity of working code, when something can be simplified.
Of course chance plays a huge role, but entropically speaking, the idea that all investors have equal skill seems a bit absurd.

Now, whether "investing skill" is something that can be meaningfully distilled and taught to others is a whole different question. I think the answer is closer to "no" than "yes". The industry-wide distribution of the long term performance of fund managers seems to provide cursory evidence to support this.