skysight-inc/HackerNews huggingface dataset:
> Given that all laser pointers fall into a couple of very narrow bandwidths, surely it would be more practicable to filter these at the cockpit window.

Any changes you make to an aircraft are necessarily exponentially more expensive than equivalent changes in any other industry.

Since lasers are being shot from the ground it means that it will always hit the cockpit window at a high angle of incidence vs the normal to the glass surface. therefore wouldn't the vast majority be reflected anyway? unless the source of very far away, but that increases dispersion. does anyone have a video of what a laser strike look like from a cockpit?
Looking at the release notes, I see several mentions of QSV support.
This made me curious, how would you setup that if you want different domains for each php app?

From all I know, you need to pay $7 per app.
YouTube's rules have something against not displaying the video.

This will need to be updated to display the video to stay up.
In online and SMS Russian, a single ), reduced from standard :), is used so often that omitting it carries a kind of serious/angry meaning much like talking in a stern voice irl
Not to mention he's a troll.
The irony is that photorealistic imagery with three orders of magnitude bandwidth than voice has been essentially solved already. If it was solved, they would have replaced expensive voice actors in CGI movies.
What is the best way to ETL data from one Postgres cluster to another (by ETL I mean things like data sanitization and denormalization)?

a) I think most people end up doing some kind of batch synchronization, but I'm interested in streaming solutions.

b) A lot of folks use trigger based replication, but triggers have to be on the primary/master node, and not just on the replicas.

c) Another common solution is to force the database client to write to a message broker, but that opens the door to data discrepancies and synchronization issues.

d) In theory I think the best way is to do something like bottledwater-pg or pg_kafka [1] [2] [3], but I'm not sure how battle hardened these are. I think logical replication of the WAL is the right approach, but there is still not much tooling around this.

[1] https://github.com/confluentinc/bottledwater-pg

[2] https://github.com/xstevens/pg_kafka

[3] https://github.com/xstevens/decoderbufs

PS: There are a bunch of interesting MySQL solutions out there, such as Zendesk's Maxwell:

https://github.com/zendesk/maxwell
That's not true. It is never acceptable to threaten someone or be violent.

To be explicit again: the reason I say monetisation of suffering is bad is because monetisation of suffering causes more suffering.

You think you're being a Good person but you've not thought things through. Every time Gawker decides to provoke a group of people with an offensive comment it's going to cause some people to relive past emotional suffering that they don't want to be reminded of. Likewise, Nero deciding to take shots at radfem twitter isn't a victimless activity - every time he does so he riles up both feminists and gamergaters causing more of the same behaviour. Monetising suffering is bad for almost everybody but journalists and extremely powerful activists.

Other than that, please take your accusations and ridiculous conspiracy theories elsewhere. I'm done trying to talk sense into you.
Never said I stopped learning. I learn new things all the time. I just don't waste time trying to pick up new languages. I read about the features of other languages all the time and I try to glean insights to use in my Ruby code.

But people really underestimate how deep topics like object orientation really are. If you burn all this time figuring out syntax, semantics, standard libraries, toolsets, et al of languages, then you won't have the time or the head space to dive deep into them.
I'm quite content with shell-mode for most of the things I do (took me a while to get used to some of its quirks, but now I like them). For curses applications (like alsamixer) I use ansi-term.
I always despise such theories of what would have happened had Nokia selected Android instead of Windows. You have absolutely no idea what would have happened. What we do know is that selecting a single OS from a company that had ulterior motives was a key to their demise. It's clear the Microsoft decision was a failure and anything else is just rampant speculation. It was nice, though, to see Nokia get the last laugh by selling their device division to MS for 7+ Billion dollars.

As for Nokia, well, we'll see how they do when they re-enter the smartphone market in late 2016 free of Microsoft.
tl;dr: B3 will replace LLVM in the FTL JIT of webkit. LLVM isn't performing fast enough for JIT mainly because it's so memory hungry and misses optimisations that depend on javascript semantics. They got an around 5x compile time reduction and from 0% up to around 10% performance boost in general.
Migrated to github:

https://github.com/stathissideris/ditaa

(SF.net lists 2011 as SVN trunk date, github lists "13 days ago")

In related work, see also my Go port at:

https://github.com/akavel/ditaa

(side by side comparison: http://akavel.github.io/ditaa/)
IANAL, so this is based on my limited research trying to hire a student I know...

Legally, you can't work while on a student visa in the US. Unless you can somehow get your school to sign off on it as relevant to your degree. Your best bet is probably to just launch in your home country, even remotely if necessary.

If you're still a student, absent any other information about your skillset, I doubt you'll be able to get anywhere with an O-1. If your home country is in North America, you may be able to find a NAFTA-related visa although I can't remember the details on those.
Password cracking attacks on Bitcoin wallets net $103,000
If explaining that relationship destroys the joke, then the joke probably wasn't funny or in decent taste to begin with.
Rate limit exceeded. http://archive.is/Zp8IQ works.
Cool! Thanks for the tool!

> Imagine you've implemented a complex caching strategy for some objects in your database and a stale cache is simply not acceptable.

I hope you have a formal specification of that cache. That will help ensure your design is correct in the first place before you even get to running it in code.

I shall be playing with this soon. Cheers!
The genius of it all is there is no 'hate' or 'dislike' button. It only allows 'positive' or no results.

I suspect facebook and company will come up with a solution to the problem of how do you indicate that you saw something without commenting when it's not socially acceptable to 'like' it. For example a funeral announcement, you don't want to 'like' it but you want to say 'thank you' or something yet you might not want to comment.

A real dislike or hate button would simply result in a lower signal/noise ratio. Maybe new types of bullying where lot's of people 'hate' on somebody.
"Blame the white guy" is all the ethically bankrupt SJWs have left. I mean what are they going to do, have a sense of humor?
Visions of the Future - NASA's space tourism posters
Actually the bigger reason is compile time - better optimizations based on JavaScript semantics are a secondary advantage.
Its a bit off topic but is there a good alternative for windows? chocolatey doesn't seem to be a good solution.
I "heard" Stephen Hawking remains with his stilted American-accented computer voice instead of using a modern computer voice because people recognize it as him. That old voice is hard for me to clearly understand, as I was listening to his recent salutary message on gravitation waves.
In computer science, when we have too much data to process at once, we shard it. We separate it into manageable chunks and we stop looking at every single data point and just at summaries.

I was using this very analogy to explain the advent of CCG "formats" (MTG, Hearthstone) a few days ago and it seems like the same analogy could be used here. There is a point where a discussion/dicussion room contains too much data to be manageable and the only way to fix that is to break it up into chunks.

We see it on Reddit, too, with subreddits becoming "too big" and naturally breaking up into smaller subreddits.

I suspect there's a universal truth hidden in there somewhere.
The breakthrough would be more like saying, "the switch to heliocentric worldview was a major breakthrough for solar system modeling."

1) The reactors have been failing to generate sustained plasma due to specific failures.

2) The simulation models of the reactors did not correctly predict those failures.

3) The new model correctly predicts those failures.

4) Now you can iterate designs using the model with the expectation that these particular failures can be identified before building a full reactor.

5) Breakthrough.
So, this - the pile-on voting - is something folks get really frustrated about. Every system I've ever used that allows down-ranking has these regular screeds from one side or another about how the system is being ruined by gangs of like-minded voters blindly censoring dissent.

And for sure, it happens. And sometimes discourse suffers for it: good arguments get buried instead of being heard.

Then again, there are much worse things than getting your argument buried on the Internet. And Twitter has some of best examples of this... People being harassed, doxed, threatened, driven out of their jobs, their homes, their communities... All over <= 140 characters that some brigade didn't like and couldn't just downvote.

In a system mostly optimized for pithy one-liners, I'd argue it's a pretty serious defect that a bad joke can so easily escape the bounds of its intended audience and any semblance of context and cost you your reputation. But it appears that's what we've ended up with...

Twitter's userbase has a fine tradition of building social conventions to paper over the deficiencies of the system. In this case, they've reinvented the pillory to replace the hated censor.
Ageism is just a another way of saying wage suppression.
>"just don't show me things that are going to cause me to lose hope in the human race". Seriously.

How could twitter determine things that are going to make you lose faith in the human race?
Show HN: Get Started Developing Swagger API with BlueOakJS
If you read the technical explanation you will see that there are zero politics behind this.
Which is very cool, but still very experimental and appears to only block a single frequency range (not what OP was proposing). I've also yet to see any published specs at all for the stuff (i.e. what's the actual optical density at those wavelengths?), so I'm a little skeptical still.
Meaningless. As proven by iOS.
Migrating from App Engine to Kubernetes
The score is based entirely on the number of testcases you pass. If the company in question wants to look at other metrics, they need to do it manually.
Writing Functional Tests with Codeception
Yes it did, but it was more like this:

1234567890
* 11

1234567890
1 2345678900 +

shifts, adds, carries in the same register, and caries into another register. The fewer digits, the faster it took.
TL;DR: the bug is due to GCC's optimization feature called full redundancy elimination (FRE).

It treats "int a=* pi; * pi=a" as a redundant store and removes it, as explained in the 5th comment:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69776#c5
Toronto tent rentals
But your defending the problem we have now. People are encouraged to get into feedback loops and not ever see anything that disagrees with them.

If you're a hunter or animal rights activist, it would be much better for you to be reminded that there are people out there that disagree with you.
I build thick controllers and rely on the database schema + DAL to handle the "model". 'course one could argue the array the data is dumped to is a "model" but its clearly not an object like MVC enforces normally.
Client side logic and rendering has a HUGE number of advantages when done correctly. Most sites don't but it is possible. API Churn is simple to solve (graphql, mvvm pattern, or as a proxy api wrapper can all be used quite effectively to solve it) and if you build an universal (meaning progressive enhancement enabled) application you can pick up the advantages of a SPA without losing the very limited advantages that a true server rendered app gives you.
The premise does align with my experience. Skilled people can adapt to and comprehend the business needs better than packaged tools. That said, well made tools can include lessons learned that could be expensive to develop in house. Often though those are only technical corner cases.
> statically typed, well designed languages that are easy to compile

Which ones are these? All of the statically-typed and well-designed languages I can think of are, at the least, hard to compile well, if not hard to compile in the first place. (Haskell and Rust both come to mind; there are few Haskell compilers other than GHC, and no Rust compilers other than rustc.) The languages that are easier to compile are either not statically-typed in a useful way, or not well-designed, or both.
I am way less sure of how to do that and can only hazard a guess.

Do not show me controversial accounts, tweets or tags not 'generally liked by the people one degree of separation away from me'?

I'd experiment to see if that helped, but if it doesn't try more things.
Same here. If you mess with scrolling, I'm going to close your site. Every time.
Way easier, way cheaper, and way less risky to buy a tool that a less-skilled person can use.

I see too much of this. Blog posts that attack a business's decisions, without demonstrating adequate insight into the tradeoffs involved in making that decision.

Skilled people are rare and valuable and hard to keep, even if you do everything right. Obviously the most effective choice in any situation is to use and develop human capital. But if and when that person leaves your company, your investment just went up in smoke.

Fungibility of skilled labor is something we should all learn to love. We want it to be easier to jump around and not harder. We want more options and not less.
There used to be ditaa.org which provided access to ditaa via a simple HTTP API. Unfortunately it seems to have vanished.
It might not be that we need to do one, the other, or a middle path. Instead, we can just focus through one of the mindsets on aspects of the problem. Remember that the projects are usually a collection of things. Each has to be solved independently with an integration. Then there's extensions. So, we can Right Thing key pieces of it even if not all of it. Further, as Gabriel noted, we can start with Worse is Better to get it moving then bring aspects into Right Thing status.

So, it's not all or nothing. My specialty, high assurance security, is Right Thing taken to the extreme for reliability or security. By the 1980's, they started kernelizing designs due to market forces making it impossible to apply to whole system. By the 1990's, they started doing it incrementally to increase uptake and financially justify the assurance work. Today, we've wisened up to try to concentrate our work on things that amplify overall correctness, reliability, or security. Type systems, compilers, kernels, protocols like Paxos (or Survivable Spread), model-based generation... anything where a little investment goes a long way.

Then we can smile knowing what people are using defiantly against our recommendations contains the results of seeds we planted earlier. Things got better even as they got worse. :) Just gotta figure out how to do that more often...
A regrettable consequence of cheap oil is that clean energy technologies become harder to deploy because they're competing against a lower cost alternative. The best thing EVs and solar had going for them was $100+ dollar per barrel oil in prior years.
Ask HN: What service/SW that no longer exists have you been unable to replace?
> I hope the people responsible for this disaster, their managers and the QA team were fired.

This is a actually a rather typical response, made with full awareness of the consequences of an action by people not under the same constraints as the participants in an incident. Diane Vaughan (an expert on risk, causes of incidents, and how organizations come to become error-prone) terms these actions 'ritualistic':

> Causes must be identified, and in order to move forward, the organization must appear to have resolved the problem. The direct benefit of identifying the cause of an accident as Operator Error is that the individual operator is the target of change. The responsible party can be transferred, demoted, retrained, or fired, all of which obscure flaws in the organization that may have contributed to the mistakes made by the individual who is making judgments about risk. The dark side of this ritualistic practice is that organizational and institutional sources of risk and error are not systematically subject either to investigation or other technologies of control.

To make it even better, you're now throwing away all the people most experienced in the conditions that lead to a specific incident. Unless very specific conditions are true, this is a sub-optimal recommendation. The evidence seems to be against building a culture of fear.
I imagine this can only work on getters? How do you use this when code makes state changes?
Yes in that instance you are correct that server-side rendering is easier. It doesn't make it any easier to build a mash-up application in which you are relying on multiple sources of data that you do not control.
I think it'd be an improvement:

Up/Down [ Agreement; no real filtering mechanic ]

Tag -> Reason [ Other filtering / reactions ]

Flag -> spam filter signal

However, I think a real universal solution is unfortunately just non-obvious and likely not anything we've tried so far.
Skype EXPLOIT 0DAY 2016 high risk
Twitter could do a million things to improve the platform (when it comes to reducing abuse), sadly they've chosen to introduce only orthogonal features nobody really wants, like "Moments".
Scoop? http://scoop.sh/
How to Write Articles That Get Traffic, Subscribers and Sales with Tim Soulo
Specialising LLVM for dynamic compilation might well come at the expense of LLVM's strengths as an AoT compiler, and it would probably not be easy in any case.

In addition to that, dedicated implementations can take various shortcuts to make their job easier - there are some nice examples given in the link. LuaJIT is example of a compiler project that benefits from being heavily specialised to a particular job, to remarkable effect.
Good work. I am a big fan of PostgreSQL. It has made life easier for me.
Heh.

If you want to realize those advantages, you will end up introducing a "simple" solution like GraphQL. In an insecure environment.

Read, man. Don't just react.
Broadly speaking I'd say the premise of the article is spot on so far as most large non-tech companies are concerned.

Data in the enterprise is a mess. A fancy tool won't fix that, only skilled people can.
Well, first, one would have had to try mangoes. Although I'd heard of them, I'd never had one until I met my friend. So me, born in the USA, might love mangoes because of the cultural revolution. :)
The Care of AI to Come
From their examples:

+--------+ +-------+ +-------+
| | --+ ditaa +--> | |
| Text | +-------+ |diagram|
|Document| |!magic!| | |
| {d}| | | | |
+---+----+ +-------+ +-------+
: ^
| Lots of work |
+-------------------------+

Typing this out is a lot more work than creating it in Visio...
Optimistic SF was very much in vogue last century despite two world wars and the cold war. In contrast, early SF writers in the 19th century had a very dark outlook on the future. Despite the fact that Europe was at the peak of it's influence and the relatively small amount of conflict in the back half of the century (particularly compared to the era of turmoil in the first half), many writers thought the human race was done for and science was at it's limit (Kelvin didn't help that thought).

Obviously there are outliers on both fronts (lots of Verne, Orwell, Ellison, etc)
Awhile back I had a Chrome extension that would show a fork of a source repo if it had more recent commits. This was super helpful for finding interesting bits of code. I can't find it anymore, anyone know what I'm talking about?
ThinkPad Edge E545.
Well I would assume the point is to build up expertise more broadly... not just one person that knows everything and screws you when he/she leaves.
Yeah, more interesting is having them rediscovering Turbo Pascal compile speeds.

EDIT: I wonder why the positive effect to re-discovering that not all compilers need to be like C and C++ compile speeds and that it was once upon a time mainstream, is worthy of downvotes.
The article contains several examples for the different interpretations. CISC vs. RISC is an example of "worse is better than incompatible". Unix vs. lisp-machine is an example of "worse is better than complex". But the bottom line, for this specific author, is that worse is better than nothing.
I don't know if an actual 5-year-old would be able to understand this, but kudos for the attempt!
Well, OK, but usually I want to go the other way. How about something that can take a drawing produced in some sort of reasonable drawing tool and produce ASCII art that I can include in some kind of ASCII-only file (like program source.) Originating a drawing in ASCII-art is about as fun as a poke in the eye with a sharp stick.

Certainly, there is value on ASCII-art to nice-graphics mark-up, but only to the extent that the ASCII-art is used as an intermediate, human readable, common-demoninator storage format. Authoring in ASCII-art just needs to stop.
Are you using J2EE?
But with human voice actors, you can't modify the dialogue in your game, or change/improve the part of the story that's tied to that dialogue, without scheduling new recording sessions.

That can get expensive and actors aren't always going to be available (which is another problem when you're trying to make sure you get the same voices for DLC & sequels etc.)
>Cross-platform app distribution is a hard problem! [...] At least on OS X, things are a little easier with Homebrew

well.. yeah.. Every OS has an easy way to distribute binaries, the hard part is having something that work on each of them.
> I feel like this is one of those cases where someone rejects currently existing tools, but then goes on to throw out the baby w/ the bath water when trying to come up w/ an alternative.

Humorously, this is exactly what the current set of client side MVC libraries did.
Getting Deep Speech to Work in Mandarin
I wonder why this wasn't caught by the extensive set of regression tests of GCC.
Long term yields lower in response to tight money, not loose money. Economists who study market expectations found that the 10 year treasury actually rose with QE expectations, for example. This is rational: lower inflation and stagnant economy -> lower interest rates.

At one point in time (sorry, I forget when) there was a surprising (to some) announcement of QE during which you could observe the result directly. The Fed announced it would buy more long term bonds, and the price of those long term bonds fell.

It is also possible to disturb the equilibrium in one direction while moving it in the other direction. In the example above, the change in equilibrium (higher interest rates) outweighed the disturbance (lower interest rates).
This is awesome. I was _just_ looking a few days ago for a good tutorial on how to distribute some bash scripts via homebrew and could not find a great resource. Thanks for the writeup.
That doesn't show the actual values in the closure. Which are subject to change anyway.