skysight-inc/HackerNews huggingface dataset:
The airframe is built to meet the intersection of hundreds of variables. Speed, stability, weight, repairability, and cost are a few. Needing to support a human is just one of those factors.

You can over-G an F-16 at 4G depending on airspeed and loadout. That's well below (trained) human tolerances.

Sure, you can build a drone that can handle 1000 cycles of 16G turns, but it's likely not going to be cheap, repairable, fast, capable of carrying weaponry, etc.
From my understanding, Marine air capabilities are typically for supporting marines on the ground. If a bunch of marines engaged in combat need air support NOW, its a lot more efficient for them (meaning, fewer jumps in the chain of command) to have their own planes than for them to have to call up the Navy and ask them to do it.
A lot of good stuff here, for podcasts, I have to add Dan Carlin's 'Common Sense' and especially his fantastic history podcast 'Hardcore History'. http://www.dancarlin.com/
Lego Doctor Who Trailer Revealed
If you like Angular's style you can use react-templates [1], most people just prefer the React way. In theory there shouldn't be any overhead, but since in JavaScript abstractions aren't free you're going to pay some price.

Also the angular equivalent would be

<ul><li ng-repeat="item in items">{{item}}</li></ul>

And the react-templates equivalent would be

<ul><li rt-repeat="item in this.state.items">{item}</li></ul>

[1] http://wix.github.io/react-templates/
Well, I wouldn't associate the European Parliament with democracy that strongly.
Disagree. Existing aircraft can already perform flight maneuvers that overwhelm a human pilot before the airframe reaches any sort of engineering limitation.
Yes, when a bubble pops surrounding industries are affected. That doesn't mean it perpetuate.
I agree with all of this. It is just impractical - hence adblocking...

> An example of a thing that I recently found amusing/annoying is that I purchased a large ticket home appliance recently, and for a week or more after that purchase there was a huge increase in ads for that particular large ticket item, as if I might buy more of them or something.

This is actually solid marketing. They are trying to re-enforce in your mind that you made a good purchase. This should prevent buyers remorse and is aimed to manipulate you into telling other people how great your new whatever is.
> If you break a mercury thermometer call 911 to request a hazmat team.

That's an over-reaction.

https://www.health.ny.gov/environmental/chemicals/hsees/merc...

http://www.epa.gov/mercury/spills/
I believe a reasonable person wills see the situations' similarity. I am not attempting to convince you since you are not interested.

There seems to be no good word for nonpayment of tax; tax evasion you take issue with elsewhere, tax avoidance is not the correct word I agree, but I don't know what word you really would like.

One thing is very clear: the IRS will take what it feels is due ('legally', or retroactively legal) and is willing to use the criminal justice system to do so. I and any freedom-loving American see this as a gross violation of the constitution.
Transformers Devastation Trailer
> Well, the thing is, nobody really needa a Wonderplane like the F-35.

The do-everything F-35 was actually supposed to be a cost management idea, since the exploding cost of new generation fighter programs was so big, we were just going to do one of them, rather than several for different roles. This would, the theory went, be cheaper in total for development, plus the shared parts would make them cheaper in operation, then separate role-specific airframes.

And, radically expensive and problem-prone as F-35 has been, that still might all be true. It might have been far more expensive, both in development and operational costs, to develop separate airframes for the various roles.
I don't know. I also don't find this a compelling argument in favor of maintaining absurd valuations
Thanks for your feedback, nice of you to submit this.

We've merged a completely new project homepage for 7.13 (out on the 22nd) that addresses some of the things you mentioned. It will not be configurable however.

Create issue is indeed only visible when logged in, makes sense to always show it, feel free to submit to feedback.gitlab.com

Searching is fulltext but can be improved.
I've experienced something similar, although on a much smaller scale.

A few years back, I got an e-mail that one of my open source tools was being used as a monitoring solution on a hospital ship. I felt pretty damn proud too, not having imagined the impact of open sourcing a project could have.

I wrote a quick blogpost on the matter back then; https://ma.ttias.be/this-is-what-open-source-is-about-mobile...
Could Travelling Waves Upset Cognitive Neuroscience?
I read the title and was very confused, surely there must be some sort of bill or law or something called 'Panorama', because the only thing I can think of by that name is taking a long picture.

And then I read the article, and it truly referenced pictures.

What idiot thought legislating fucking long pictures was a good idea?
Doctors of the Future: 3 Promising Trends in Medical Education
I don't think pricing per user pack is what people expect, per user seems to be the more common question.
Or I could ignore what are obviously semantics following a clear retroactive change in US policy that affects criminal law. It doesn't have to be as complex as you make it out to be.

The NYT even called it a retroactive policy change!
Show HN: Compare LGBT Rights Between Any Country, State, or Province
Side question: I wonder how HN let this be posted as a duplicate - just the trailing slash in the URL?

https://news.ycombinator.com/item?id=9859511
Dietary Requirements of a Medieval Peasant (2006)
Google Fiber Has Accomplished More for Us Than the US Broadband Plan Ever Did
I'd love a TL;DR (fully admit I'm lazy).
>I really doubt the credibility of the author; as if engineers would overlook such a basic factor if it was that crucial.

i vaguely remember reading something/somewhere that less stealthy round instead of stealthier flat was a cost cutting decision.
I wouldn't be so quick to buy into the modern idea that this prohibition was always aimed at criminal laws. Excerpted from a paper I wrote in law school on the topic (sources at end of post):

Newly independent Americans in the late 1700s were very concerned with “this shameful abuse of power”, “those engines of oppression”, ex post facto laws. American businessmen were concerned with the macroeconomic effects and unfairness of interference with contracts by provincial/state legislatures.

One of the shameful abuses was the “paper money laws” that changed outstanding debts by permitting payment in paper money where the contract originally called for the use of gold or silver. There was widespread fear of the drying up of credit (in the context of an ongoing major depression at the time) as a result of concern that loans might not be paid back due to legislative intervention.

The dictionary of reference in 1739, Giles Jacob’s Law Dictionary, defined “ex post facto” as “a Term used in the Law, signifying some Thing done after another Thing that was committed before”.

Check out these sources:
William Winslow Crosskey, “The True Meaning of the Constitutional Prohibition of Ex-Post-Facto Laws” (1947) 14 U Chicago L Rev 539

Roger W Weiss, “The Issue of Paper Money in the American Colonies, 1720-1774” (1970) 30 J of Economic History 770

Elmer E Smead, “The Rule Against Retroactive Legislation: A Basic Principle of Jurisprudence” (1935) 20 Minn L Rev 775

Harold J Krent, “The Puzzling Boundary Between Criminal and Civil Retroactive Lawmaking” (1996) 84 Georgia L J 2143

W David Slawson, “Constitutional and Legislative Considerations in Retroactive Lawmaking” (48) California L Rev 216
Because the air force is run by fighter jocks.
Yes, every time I use Haskell, I miss them. Purescript also have them. Row-polymorphism ftw.
We've moved down this path from a massively complicated distributed transaction environment on top of MSMQ, SQL Server etc and you know what? With some careful design and thought about ordering operations and atomic service endpoints, we didn't need them at all after all.

Transactions can be cleanly replaced with reservations in most cases i.e. "I'll reserve this stock for 10 minutes" after which point the reservation is invalid. So a typical flow for a order pipeline payment failure would be:

1. Client places order to order service.

2. Order service calls ERP service and places reservation on stuff for 10 minutes.

3. Order service calls payment service (which is sloooow and takes 2-3 mins for a callback) and issues payment.

4. Payment service fails or payment fails.

5. Order service correlation times out.

6. Order service calls notification service and tells buyer that their transaction timed out and cancels the order.

7. ERP service doesn't hear back from the order service and kills reservation.

etc etc.

At step (4) you have an option to just chuck the message back on the bus to try again after say 2 minutes. If everything times out, meh.
Safety margins dictate that the airframe should be substantially stronger than the occupants maximum tolerance.
"If your industry is run by unethical people who would use your code, if developed in the open, in a way that would put your firm out of business"

Which is entirely the case in software.
> I really doubt the credibility of the author; as if engineers would overlook such a basic factor if it was that crucial.

The problem is that the F-35 had requirements that fundamentally conflict with each other.

It had to have a STOVL configuration, which probably dictated the nozzle design. But it also had to be 'stealthy', so the nozzle design and the wide fuselage needed for the STOVL requirement, negatively affected the stealth requirement. So much so that the stealth rating of the F-35 was downgraded.

It was also supposed to be more maneuverable than the F-16, but the other requirements resulted in aerodynamic performance that was less than what was originally planned. So much so that it lost a mock dogfight against a F-16. Granted that test is not the end of the story but it's not a good sign.

Then there's the fact that the military and Congress inexplicably decided that they'd throw the normal testing and validation phase out the window in favor of 'concurrency' where they're putting the aircraft into production before testing is done. This has the dual downsides of ensuring expensive retrofits when problems are identified but it commits the government even more deeply to a weapons system that may ultimately never perform as billed.
In the real world? With a munitions loadout? Without needing an immediate overhaul? I don't think so.

Limit loads are the design point, which are 1.5x lower than the ultimate loads, which are still lower on actual aircraft than what humans can handle (and are not meant for sustained or repeated operation).
Have you done Backbone? The idea is that you define everything in terms of models and that when one of those models change you call render() to run it through your templates and you're done. This is a simple conceptual model, the framework needed to execute it is simple (and well written in the case of Backbone), and it works really well for simple applications. The problem arises when you can't just call render: when you have input fields, when your rendered DOM has event listeners, when you're using a component with it's own internal state (e.g. a jQuery datepicker), or when you're doing something like a grid and generating too many DOM nodes. Unless you know this is coming and have a plan for dealing with it (e.g. the many Backbone addons), this is a complexity land mine since it does not show up in the small apps you build while testing out the framework.

You can (and I do) view the React render as an idempotent projection from state to DOM, otherwise known as a template. React is a very fancy template system. You build your fragments (components) up into views, pass in your data, and render the entire page as if you're rendering it from scratch. It handles or provides hooks for all the situations I mentioned in the previous paragraph and React's internals ensure that it's reasonably performant by default. Having everything conceptually fully render from scratch every change means there's no separate handling for the initial render versus updates to the initial render (e.g. you have an accordion, render it with an ejs template but toggle it open/close by toggling classes). It makes the Backbone model work in a way that's easy to reason about.

A real world example: I've implemented (B2B, not something I can link) a drag and drop layout builder as a contract. The workalike they wanted, which I had also worked on but didn't design, was ~6k lines of node/class manipulation and mousenter/leave hit testing while my React version worked out to be around 600 lines, most of which were generating virtual screen position hitboxes for the various drop zones. Hovering/dropping in a zone changes attributes in a list of JS objects and the visual feedback is handled by the rendering code you'd need to draw the layout anyway plus another 20% for the drop previewing/hovering.

Most savings aren't as dramatic but in general you wind up spending less effort getting your views right. The LoC isn't always that much lower but it's template code instead of manipulation code. There are other benefits like component composition just working, server side rendering, putting all your app state in one place lets you do session recording and time travelling debugging but this post is long enough as is.
http://www.moanmyip.com is still better.
Good point! I do really enjoy writing Angular templates. Embed the language in HTML, instead of the other way around. :D

As an aside, PyCharm is a great editor, it can understand Angular, HTML, CSS, and Jinja all in the same file, and does lots of helpful introspection for me. For example, I can command click any property to jump to it's definition, as well as syntax highlighting for all these languages.
You're basically saying that contracts are fictional. Try entering into a contract, then behaving as if it's fictional by ignoring your responsibilities in the contract, and you will quickly find out how real they are.
> I would probably define it as...

The legal standard for proving tax evasion disagrees with you.
No, safety margins are implemented by a computer limiter and are often set far below the occupants' maximum tolerance.
I'd wager "it's particularly big, expensive, incomplete, and not fit-for-purpose."

The other recent vehicle criticism that comes to mind has been over how much of the budget went into acquiring light vehicles such as hummers, and other RPG & IED bait.

Unlike with the F-35, this was actively costing lives, so something got done. We've slapped net armor onto a bunch of things. MRAPs have "Mine-Resistant" right in the acronym.
Before 2025 probably not, but a proxy war might be fought (say Pakistan/India or Israel/some neighbours or North Korea/South Korea flare-up).
Go 1.5's vendor/ experiment
The issue here is not that SSNs are used for identity (which is what they SHOULD be used for), but rather that they are used for authentication, which is retarded beyond belief. https://technet.microsoft.com/en-us/library/cc512578.aspx
If we didn't use the tax code to create bizarre incentives, we'd arguably have more honest behavior.
Yes, obviously. How did you think courts worked?
"The old system responded to requests somewhere between two and 10 long seconds; the new one takes 30 milliseconds, on average."

Wow, 30 milliseconds. Subtract out the RTT, and you have app request times on the order of 5ms. Outstanding. And impossible.
3) Reservation pattern.

This one really works well.
Ask HN: Inquiry About Apple and a Potential Job Offer
Hey, Everyone -

So it looks like my brother has a good shot of being offered a position in Apple's logistics/operations department (he isn't a programmer). The thing is, he currently has an amazing and solid position in Ohio with a very good company (Honda of America). Apple has already told him that he'd be doing essentially the exact same thing as he does now, but with room for more challenges, personal growth, etc.

He's very good at what he does (which is probably why Apple contacted him in the first place), but this would be a very significant jump for him in both pay, distance, and growth opportunities.

I and the rest of our family are very excited and supportive of him, but I'm just trying to gather as much information as I can to help him make a smart and informed decision.

For those of you who have worked for Apple in any department at any point in time, can you briefly discuss some benefits, incentives, likes, dislikes, etc. about your position and time there? I would greatly appreciate it.

Any information on the topic would be awesome! Please probe me for more information or details if necessary.

Thanks, all!
A giant graph could be in the cards for future work, schedule permitting.

As for https, I'm currently hosting this with GitHub, but using my own domain so my browser kept complaining (correctly) that the page was using a SSL certificate from another domain. Eventually, I'll move to hosting this on my own somewhere, probably when I get the urge to run some server side code. Then I'll most likely make https the default.
(this is all my own analysis...I could be, and probably am, wrong about much if not all of it...disclaimer disclaimer, etc.)

Let's assume that "the bubble is bursting" takes the form of there just not being a lot of available funding, and of general shakiness in the market.

So, the first thing to go will be companies that don't have a solid revenue stream. A lot of folks are all "fuck revenue mindless growth go go go", and once the VC life-support is removed they'll shrivel up and die.

The next thing will be that investors will be super conservative all of the sudden--just as we saw following the 90s. A lot of companies will take PE deals that'll probably screw them and destroy chances at good exits for founders and employees.

The long-term thing will be the acquisition of company's IP portfolios by companies taking advantage of fire sales, or investors looking to liquidate what they can to make their money back. This will bring about a lot of patent trolling, and other comedy. That'll take a while, though.

~

For the tech side, though, things will be interesting.

First, hiring will become a lot harder for everyone involved. Developers will be used to high salaries, and when they can't get them because bad funding, they'll be in for a rude surprise. It'll take a while for people on the coasts to learn what the midwest has known for years: programmers, removed from inflationary costs of living, are pretty cheap.

Second, the style of development will likely change. The merry outsourcing of all things IT and infrastructure to the Cloud goes away when the already-absurd AWS and GCE and Heroku bills start stacking up without investor money to pay them. The magical snowflake syndrome of frameworks and bespoke svg widgets and general excess supported by easy cash will go away (hopefully).

Third, entire sectors of developer-to-developer and first-world-problems apps will just dry up, for reasons explained above.

~

What to do?

I'd suggest boning up on native development, SQL, and everything that is in demand in line-of-business application programming. I'd also rediscover and refresh on how to live in a Cloudless world: how to provision and administer servers, how to do networking, and generally how to be an engineer using only bubblegum and ducttape. If you can do that, you'll be fine.
The law should be based on how humans actually behave, not tortured theoretical outliers that rarely happen. The law is a sledgehammer, not a scalpel, and should not be based around extreme outliers.
Engineering safety margins, not occupants safety margins.
Why This Tech Bubble Is Worse Than the Tech Bubble of 2000
Luddites in Paris
The fact that they aren't changing the law is a sign?

By the way, for what it's worth, there was no attempt in 2001 to invade the Assembleia in Lisbon. There was a large demonstration, during which a commotion forced the police line to back up a little, nothing more.

Curiously, the time where there really was a deliberate (and successful) attempt to break the police barrier (though they stopped before entering the Assembleia) was during a demonstration by other cops.
Unfortunately the shared parts ratio is far lower than what was planned. It was supposed to be 80% commonality between variants but it's more like 25%.

Furthermore, because they tried to make the aircraft meet contradictory requirements it has resulted in a plane that doesn't do several things as well as even the aircraft it is replacing, much less newer aircraft on the battlefield. All at an astronomical cost.

At a certain point it just doesn't make sense to pay far more for a weapons system that doesn't do anything well.
The round nozzle is a tradeoff for weight. It's a single powerplant aircraft so the IR signature was probably considered satisfactory versus twin rectangular nozzles. The T-50 (prototype aircraft that Russia can't afford to further develop) and the Su-35 he brought up for comparison use two round nozzles, but he somehow neglected to factor that into his comparison.

The rest of the 20 different systems he compares the F-35 to either would bankrupt Russia if they were to ever put them into mass production, or the comparisons themselves isolate one feature of the F-35 against some long-shot (probably exaggerated) capability of such-and-such Russian system. I could say that the F-35 could use its low-observable phased array radar to detect the Su-35 from twice the distance of the latter without triggering the enemy's RWR, fire off an AIM-120 and turn around before the Su-35 detected it. And pretty much every shortcoming for the F-35 (sensors, supercruise, stealth) he brought up is far worse for the F-16, A-10, and AV-8B which the F-35 is intended to replace.
IDEAL VENUES IN NAIROBI FOR FAMILY OUTINGS
Yes, that's the worse part of this.
> What would you call this?

A career and life choice they made. Opportunities here are likely better than their country of origin, so they (hopefully) weighed the risks and benefits of the choice to immigrate here for work. If those calculations no longer hold true, then likely a new course is to be chosen. Slavery implies force or coercion, not a regretted decision.
So for comparison of 50-yr maintenance costs (in Maine):

- Low-use gravel roads are ~50% of paved road maintenance cost.

- Moderate-use gravel roads are ~350% of paved road maintenance cost.

Yikes.
Hard work and productivity are really two different things. They are sometimes the same, not always.
How can it be arbitrary given the fact is so astoundingly crazy?...
Totally. I'm hungover, and all the animations made me nauseous.
Don't conflate streetcars and interurban's with all passenger rail.
Comic geeks and enthusiasts unite at Comic-Con San Diego
https://en.wikipedia.org/wiki/White_flight#Roads
Tripbright.com

Allows vacation rental hosts to recommend/sell travel activities to their guests. Commissions on sales are shared with the hosts.

For sale, or looking for a non-technical business/growth partner to work on it part-time with me.
Git is also under GPL, so I am not sure how much of an argument that is.
aren't the cost of input the lowest in the world already in china ? Why they go down if so ?
Redefining privacy and anonymity through social networking affordances