skysight-inc/HackerNews huggingface dataset:
Do you have a link to when Kent Beck was working on that log parser?
Exile and the Kingdom is also great.
Trump is more constrained in the US than he would be as a leader elsewhere.

There are a number of active lawsuits against him, most important probably being the emoluments ones. These take time to prepare and put in front of a judge.

I don't know what better solution there is to wannabe dictators than a free press. Trump hates the press that doesn't agree with him. That should be a big sign that they are a thorn in his side.

Life isn't perfect, nor is government. Sometimes you get a lemon and just need to deal with it with as much reason as you can muster.
Is there a tutorial available? Awesome to get something like this in terminal but seems like it has a steep learning curve.
Go for the "4 person" option instead? Then you cook more each meal.
Similarly, the hard part of Mathematics is the math itself. It's not because we don't have WYSIWYG math equation editor, that people can't understand advance calculus.
Calling Taiwan a democracy is like labelling the Culture Revolution a democratic movement.

When elderly Chinese who actually experienced the terrible Culture Revolution go to visit Taiwan, many of them had the feeling that Taiwan make them feel young again as they saw the Culture Revolution again in Taiwan.

Endless street politics for every single change to the society, hugely divided society, corruption from both sides, people are forced to pick which side is less terrible rather than which is better, President democratically elected used its official jet to move cash to foreign countries.

Personally, I don't want such toxic Taiwan to be integrated back to China, they can run their own circus on that island so people in the mainland can look at them and learn from their mistakes.
I was doing some research into the Comprehensive Test Ban Treaty (would ban underground nuclear tests, US has been voluntarily complying since the 90s but Republican Senators have refused to ratify) the other day. As I was researching, I stumbled upon an old Heritage Foundation position on the treaty. I knew of their reputation so I began reading with skepticism.

The author of the position piece made a number of very reasonable criticisms. He said that, for instance, while the treaty text bans "explosive" tests, and this is understood in some quarters to mean zero yield, it doesn't say that explicitly. He made two other sensible points that were at about the same order of magnitude maybe one more and one or two very hawkish points.

While I am not a diplomat or other professional in the field, I thought, hey some of these make a lot of sense, maybe they should workshop the treaty and fix these few points. I'm sure most countries would go along with a few amendments even if they've already signed it if they can get the US to say yes.

Instead he wholesale rejected the treaty and recommended that we signal total withdrawal and declare that we will no longer voluntarily comply with its terms. So essentially, he took a few reasonable points and then used them to support an extreme position.

I laughed and said aloud, "That's the Heritage Foundation that I know!"

http://www.heritage.org/arms-control/report/us-should-reject...
I haven't done too much looking, but that seems fairly common so far. Microsoft is also a "local business", and Google is an ISP. I mean, Google Fiber is really cool, but that's not how most people use it
I'm surprised Go doesn't compile down to an IR language where these differences in syntax are represented in a single manner. Seems like different ways to write the same thing.
I would turn that request on its head: can Shivetya produce any numbers to prove the claim about 10% of workers or the subway being the most expensive option? We're under no obligation to rebut a point that doesn't back itself up.
I'm fairly sure that almost every statically typed language has function definitions like that. C, C++, Java, Go, Rust and so on all have that style of function declaration.

Named returns are a Go thing mainly because of defer.
The flipside of this is that if nobody visits .feedback domains, they won't be able to scam anyone. Users don't need to learn anything to avoid them, because they probably won't ever hear about them in the first place.

If they have no audience, they can be safely ignored. No reason to pay $600/yr for hypotheticals.

All I meant was, the moment someone brings up a .feedback domain or "Google's new feedback service," just let them know it's a scam and move on.
C#. Resharper is a really, really good tool, and I also use NCrunch (a continuous test runner) when I do TDD.
sadly, the exact system was introduced into China before the handover, the broken system is not just screwing HK but a huge chunk of China including all major cities.
It's always good to remember that while Big-O is useful, it isn't the be-all end-all. The canonical example on modern hardware is a linked list. In theory it has many great properties. In reality chasing pointers can be death due to cache misses.

Often a linear search of a "dumb" array can be the fastest way to accomplish something because it is very amenable to pre-fetching (it is obvious to the pre-fetcher what address will be needed next). Even a large array may fit entirely in L2 or L3. For small data structures arrays are almost always a win; in some cases even hashing is slower than a brute-force search of an array!

A good middle ground can be a binary tree with a bit less than an L1's worth of entries in an array stored at each node. The binary tree lets you skip around the array quickly while the CPU can zip through the elements at each node.

It is more important than ever to test your assumptions. Once you've done the Big-O analysis to eliminate exponential algorithms and other basic optimizations you need to analyze the actual on-chip performance, including cache behavior and branch prediction.
If the problem is really just JavaScript itself WASM won't be able to help -- WASM is basically just asm.js, which is just a restricted subset of JavaScript, but easier to parse and optimize.
There is a bin/vdtutor in the git repository, which only has one sheet so far. Also the animated screenshot links to a page with a tour of the commands used. More of each are planned, but it seemed more urgent to release a beta right now. I'd love some help, if you or anyone is interested in helping put together another tutorial level or screencast or tour.
non-profit hospitals and non-profit universities have had exorbitant price increases in the last few decades so they aren't doing any better
Wait.. Levandowski took files from Google as leverage in case they didn't pay him his bonus? What did he plan to do exactly?
In what case does that ever make sense? One can't assume any ownership of or rights to the files whether or not Google pays them the bonus.
"Blue Apron's executives and venture investors own Class B stock, which gets 10 votes per share and gives them control of the company. It sold Class A stock, with one vote per share, to the public in the IPO. It is keeping around Class C stock, with zero votes, to use as acquisition currency and avoid diluting its insiders in the future. Dual-class stock, triple-class stock, nonvoting stock, entrenched insider voting power: All of these are things that investors profess to hate. But in hot IPOs like the one for Snap Inc., which sold nonvoting stock to the public, priced above its offering range, and then jumped on the first day of trading, investors seemed perfectly willing to ignore the governance issues and pay up for startups.

And then in ice-cold IPOs like Blue Apron's ... what? Blue Apron cut its valuation by a billion dollars -- and cut the amount of money it was raising by $100 million -- when it repriced this IPO from $15-$17 down to $10. What do you think the discussions were around the voting rights? Did any investor say "I'll pay $10, or $12 if you scrap the triple-class structure"? Did any banker say to the company "this deal is not going well, and we'll need to reprice, but you might get a better price without the triple-class structure"? Or is there just no tradeoff at all between governance and economics: Hot deals get done with bad governance, and cold deals get done with bad governance, but no one can just move a slider to increase valuations by improving governance?"

https://www.bloomberg.com/view/articles/2017-06-29/stress-te...
I look at these result functions and all I can think is, "Wow, it must be really delightful when you get a zero record back and what to know why your parser has a bug." I really hope these are didactic in nature and not a representation of industry best practice.

Why not just declare a record in scope and return that? Why rely on a sneaky little piece of syntax tucked away in the return value? Aren't gophers supposed to be all about a regular language with few surprises?
b) is what I meant. I know that would not have been the original intention but I still think it can be useful in some cases, and there does not seem anything wrong with it. (It clearly wouldn't be for static linking WebAssembly codes with C codes, like what you might do with JavaScript, although it can have different uses.)
This should really straightforward (like maybe 1-3 hours) for someone who knows use the Python3 modules for those databases. See the SQLite addon, for example: https://github.com/saulpw/visidata/blob/stable/visidata/addo...
I started reading PG's writings in 2001 on the advice of my computer science teacher in high school. That was pre-ycombinator. I read his stuff because it was really interesting and spoke to me (while it doesn't have the same valence it once did for me, at the time I really loved his article on nerds).

It has been quite the ride to see this random dude whose work I started reading become a global juggernaut.
It is the acknowledgement of the receipt of the last message that is important. Wikipedia is not entirely clear on this one. The source of the problem are higher-order statements: "A knows that B knows that A knows ...".

Suppose A sends the message to B, B sends an ack to A but A's ack back to B is lost. Now both A and B know the time of the attack but B considers it possible that [A does not know that B knows]. B thinks if A really does not know that B knows then A may not attack out of the consideration of the possibility that B does not know. And this possibility may make B call off the attack even if B knows.

Each round of successful exchange increase the order of statements that are known, but there is a statement of higher order which is still not known and which can cause the attack to unravell inductively.

Look up 'Rubinstein's e-mail game' for a choice of payoffs that causes no attack to happen for any positive probability, howsoever small, of a message getting lost.
Sounds very cool. A couple of questions I had:

1) What happens if they lose their rocksdb with all of the messageIds?

2) Is their kafka atleast-once delivery? How do they guarantee that kafka doesn't reject their write? Also, assuming they have set up their kafka for at least once delivery, doesn't that make the output topic susceptible to duplicates due to retries, etc?

3) >Instead of searching a central database for whether we’ve seen a key amongst hundreds of billions of messages, we’re able to narrow our search space by orders of magnitude simply by routing to the right partition.

Is "orders of magnitude" really correct? Aren't you really just narrowing the search space by the number of partitions in kafka? I suppose if you have a hundred partitions, that would be 2 orders of magnitude, but it makes it sound like it's much more than that.
I would say this problem is quite different than Two Generals, because client doesn't need to know that acknowledgment has been received, i.e., a solution doesn't require the receipt of message to be common knowledge.
It it sufficient that server stops trying to send the message once it has received the ACK.
Pearl Automation, Founded by Apple Veterans, Shuts Down
Whose idea did he copy? TheFacebook was nothing like Friendster or MySpace, it came from a completely different angle. Also, why do you assume he wanted to be famous, or had some realization about how to be successful?

The truth is, he executed the shit out of a scalable idea, and he had the vision to see it through many orders of magnitude growth. The idea that there was some master plan is just silly, his success, like most big companies was iterating over time and making a series of successful bets.
> The law of reciprocity

The what? The only thing I can find about reciprocity is that antennas have the same characteristics in either direction. That doesn't mean your noise levels are the same, and you very often have different bandwidth requirements in each direction.
No, it allows the focused Transmitter to use less power.

Any excess power prevents re-use of the frequency in adjacent cells.
If that were really true, the BBB might have gone under years ago, and the Nigerians might stop asking for help in transferring great wealth.

There is no shortage of suckers in the world - as the old saying goes, there's one born every minute.
I think people should in fact test data, not code. Looking at it from purely functional point of view, functions should be either proved that they do what they should, or they should be asserted and QuickCheck-ed. But what really needs to be tested is that the input parameters (i.e. data) conform to some "hidden" assumptions that we had when we wrote the functions. Because as we modify the program, or even why we modify it, is that these assumptions have changed.
A very relevant rebuttal from page 91/92:

>Because you get really nice feedback. When you write a graphics algorithm, it draws a picture for you. While data can be re-
warding in its own way, in general the human species is wired to re-
spond much more strongly to visual things and things that have to be
interpreted from symbols. So there’s something fundamental there why
it’s a neat thing. But we do get to work on a whole lot of areas. I enjoy
all aspects of it, but games have always been one place where there are
challenging things and it has its own reward at the end, aside from the
problem itself.
No matter your intelligence, if you're having a heart attack, you go to the nearest hospital, whatever its tax status may be.
Chinese Province Larger Than Texas Just Ran for a Week on Only Renewable Energy
I'm pretty sure Go does compile down to an IR, but it's little more than an abstraction over different architectures. I could be wrong.
Still kicking after 3 billion years.
Yeah, the explanation doesn't make any sense. Even if he decided to release it to the public, that IP wasn't his to distribute, so he'd get sued out of the obscene $50m he had already been paid. At this point, I can't find a single course of action from Levandowski that would paint him in any good light at all.
Finding your life's work is the hardest part I think. Once you solve that the rest is easy.
Watch Wigan Warriors vs Widnes Vikings Live
> It's always good to remember that while Big-O is useful, it isn't the be-all end-all. The canonical example on modern hardware is a linked list. In theory it has many great properties. In reality chasing pointers can be death due to cache misses.

My favorite example is adding and ordered list of items into a a simple tree, all you've really done is created a linked list. Big-O doesn't know what your data looks like but you generally should.
It increasingly does.

But it's been a process.

Go 1.5 was the first self-hosting release, with the Go compiler auto-translated from C to Go. But it was still fundamentally Ken's C compiler in Go syntax.

Every release since (Go 1.6, Go 1.7, Go 1.8, Go 1.9) has been cleaning it up and making it more Go like and less C like.

Meanwhile, the backend was also retrofitted. Go 1.7 included an SSA backend for amd64 (https://golang.org/doc/go1.7#compiler).

Go 1.8 included it for all architectures and added more SSA goodness.

Go 1.9 adds yet more, but some things are still not pushed down into SSA as well as they could be. (e.g. https://github.com/golang/go/issues/5147#issuecomment-247685...)

Nowadays we can add optimizations much more easily, including writing matching rules like in https://github.com/golang/go/blob/master/src/cmd/compile/int...

Meanwhile the whole toolchain keeps getting cleaned up and more hackable.

In Go 1.9, the compiler is now parallelized, which would've been impossible earlier. (https://tip.golang.org/doc/go1.9#parallel-compile)

So, it keeps improving. Just remember the Hello World compiler we started with.

Also amusing in retrospect is that when Go first came out, despite having a very basic compiler at the time, people coming from scripting languages thought we were so fast.
The original link seems to be redirecting to medium.com.

This is the correct link, if OP or admin can fix it
https://medium.com/the-mission/looking-for-the-one-how-i-wen...
Also, though it may not add up to much, you can donate a small portion of your Amazon purchases to them through the Amazon Smile program. Install the SmileAlways extension and all your purchases will go through Smile
I tend to prefer them, too. They're remarkably 'sticky' for me. I've been using Vim for at least 20 years, and mutt for close to that (can't recall exactly when I started using them).

Been wishing for a solid, console-based spreadsheet for a while, but I haven't really gone looking that hard, as I don't use spreadsheets as much as I used to. When I do, though, I find modern GUI spreadsheets want to 'help' way too much and frankly bug the crap out of me. I suppose if I used them more, they'd brainwash me into their 'right' way of doing things, but I generally get fed up and use Postgres. That works surprisingly well for a lot of things, but updating 'cells' via SQL gets tedious, and if I'm trying to get an understanding of the data, a more visual approach is really handy.

Definitely will check this tool out.
For the most part named returns are frowned upon, and while it is admittedly an oddity in the language, having one oddity is still achieving the stated goal of "few surprises". :)
> Why not just declare a record in scope and return that? Why rely on a sneaky little piece of syntax tucked away in the return value? Aren't gophers supposed to be all about a regular language with few surprises?

It's not a sneaky piece of syntax, in fact it is required to use that syntax if you want to reference or modify the return value of a function in a deferred function call.

I don't like the syntax and hate that Go forces you to use it in the above case, but it's definitely not sneaky syntax. Any regular Go developer should be expected to know about this construct.
This is the user guide:

https://github.com/saulpw/visidata/blob/stable/docs/user-gui...

(The link is broken in the docs/README file)

This is the walkthrough on sample data:

https://github.com/saulpw/visidata/blob/develop/docs/tours.r...
Yeah I had the same experience. Ingredient quality was fine, recipes were pretty good, but prep time was too long for just a weeknight dinner. Makes a good date-night activity, but my wife & I don't have time to do that three times per week.
> it just wouldn't feel right to live on money that was forcefully taken from someone else

You're going to be awfully disappointed when you learn how wealthy developed nations were built.
I agree, but how long does it remain high quality furniture if it's being used, abused and returned every few months? Repair costs could get out of control quickly.
I recall there used to be an argument around base-load generation not being fully suitable to be provided by renewables... That argument seems to have subsided however with reports like this. Can someone ELI5 what's changed?
Nobody can know your restaurant bill beforehand, since who knows what you will order for dessert, right? The hospital should still be able to give estimates for individual items beforehand. If they are not flying completely blind, someone must already know these numbers, it would just be a matter of making them public.

To me, the actual problem seems to be that they would like to make up the price after the fact, when they have a better idea how much they can charge and get away with. This gives them the unfair advantage of setting their own prices unchecked by market forces, and is frankly a reprehensible business practice.
An unethical and shamefully pathetic extortion scheme. This is really a disappointing and completely uninnovative, destructive direction to take the internet in
I don't do it, but mostly because all I would be doing is logging the error, and if some day it takes me a little longer to root cause some odd file close error, I'll still come out ahead.
Reminds me of GetSatisfaction back in the day. It was never as much of an outright scam as this, but they definitely had that protection racket vibe about it.
EarnGurus – Make World with Gurus
>Its funny how giant douchebags who are trying to "mitigate their risks" never seem to perceive the risk of everyone realizing they are giant douchebags.

The market doesn't really care if you're a giant douchebag so it doesn't matter to them if everyone finds out.
I've seen this too many times... TDD != Automated testing
What language that has static types doesn't have the func, params, and return type in one line?
How is this a scam? The result is obviously just a ratings site which never purports to be the sites referenced in their URL...why does it matter if you type in google.feedback or feedback.com/google or google.feedback.com into your browser? No reasonable person could be misled to believe that google.feedback/ was at all related to Google.

edit: Okay, I guess it is a pretty messed up website. If you go to reply to something, it gives you the ability to "officially" reply (as, say Google) for a mere $29 per message. This doesn't seem like extortion, but it is a pretty horrible business idea.
BSPs weren't new to the Quake engine (Doom had them). Gouraud shading, lighting, and TCP/IP multiplayer are what made Quake revolutionary for the PC. These things existed on SGIs costing $100k for years before too. The optimizations to make this on a PC is why Carmack is genius.
Petya ransomware hits SA – IT experts warn companies to be on alert
In California, the peak is actually at 6pm. At that time, Solar is generally producing 6.6 GW from around 9.6 GW at noon.

http://www.caiso.com/Pages/TodaysOutlook.aspx
Functional Programming for Deep Learning
Just a good related book recommendation: At the Existentialist Cafe is a great piece on philosophy and modern history.

https://www.goodreads.com/book/show/25658482-at-the-existent...
AMD Launches Ryzen PRO CPUs
Well, the reviews on stackoverflow.feedback are quite informative!

Dan Manny says:

Stack over flow made me loose money!!! Bad code with security wholes in it crashed my clients site!! Warning warning for scammers

and Antonio B. of Indonesia says:

Best site for solving programming issue!!!11!one!
The most user and newbie friendly site!

11/10 would recommend

You know you can trust reviews like this!
Zillow's initial demand letter included this:

"(ii) delete all images, and derivatives thereof, in Your possession and on Your site"

As Kate noted in her twitter feed, the decision to not use them in the future was hers:

https://twitter.com/mcmansionhell/status/880517699725668352

https://twitter.com/mcmansionhell/status/880517699725668352

The Innertubes may have kept her originals around, but being forced to delete them would have destroyed the value to her of a year of pretty concerted work on it. That would have acted as a very strong deterrent to speech.
I might want to include that IMHO all new TLDs are trick. Brand proprietors are compelled to enroll their name in a large portion of them.
What to Consider When Planning to Sell Your Tech Company
Could the major browser providers start just blacklisting these kinds of TLD's? Or grey listing with huge warnings?
JS is a much better compile target for many languages for the foreseeable future. "Without JS" is not a sensible end in itself.