skysight-inc/HackerNews huggingface dataset:
My work has been pretty interested in "interactive" charts, being able to modify axis scales on the fly, change filter range, dynamically add and remove series that sort of thing. We use SAS (and a little bit of R internally) and those both have good charting capabilities but trying to do anything interactive in either of those packages is a real pain. In the past we have used a C++ library SL-GMS.

Even when compared with using C++ I have found using JavaScript based libraries difficult D3 in particular I found to be horrendously complex.
It honestly doesn't really matter - the differences between different editions are subtle and of interest mostly to scholars. If you can find an edition with good annotations go with that one; otherwise just pick up the one with your favourite cover - I've always been partial to the Penguin one myself.
There was a lot of FUD in BSD space back in 90s. People were worried they might get sued out of existence. And the original version of FreeBSD was lacking some critical things because they had to get rid of a lot of proprietary code to avoid the wrath of AT&T and its successors.

Additionally, FSF was in need of a Kernel and they chose Linux. There was a lot of evangelism involved. While BSD was recovering for the its troubled past, Richard Stallman and Co. were pushing Linux to the rest of the world.

Even Apple considered using Linux as a base for what would become Mac OS X — it was called MkLinux.

By the time BSDs managed to get their act together, it was already too late — Linux had gained critical mass.
Put the computationally expensive task in its own process, and have the UI monitor it as needed as part of its event loop.

(That won't work in every case, but it should be thoroughly considered first.)
Completely agree as well.
This is just an uninformed rant. Uber got me hooked with very low pricing and now I continue to use it heavily even though the pricing is much higher (not taxi level though) and I own two cars.
1) I'm mostly using vim. Been using it for development for the past 6 years and loving it.

2) Thanks! Duly noted.
Ford also has $222 billion in liabilities
It is, and I go there only as needed.
Question: Why does my head hurt?
Aristo is not sure about this one...

Aristo's best guess: It hurts because you're alive.

Confidence: 19.04%
[Live] Kent Beck: 3X Explore/Expand/Extract
If you want a more motivating example, try implementing generic array operations such as reduce, scan, each, reverse etc. Ideally these should be as easy to use as this example:

x := reduce(func(a, b int)int{return a*b}, []int[1,2,3])
y := reduce(func(a, b string)string{return a+b}, []string{"a", "b", "c"})

Rob Pike implemented "ivy", an array programming language, in Go but producing something like an array programming package that can be used from Go (sort of like NumPy for Pyhton) can be very messy to use or implement (even with the use of reflect package).
Smashbros Ultimate “how to play” page (try on desktop and mobile)
Traits and Trait Objects in Rust
I love "How to Cook Everything".... and I'm working on the newer "How to Cook Everything - Fast" :-)
Well let's not grab our pitchforks just yet.

I'm sure if this was a thread discussing Judge Leon's 2013 opinion that NSA metadata collection violated the 4th amendment, HN would be singing his praises. But in this case he's approved a merger we don't like so he must be a total idiot or (as is being suggested further down in the thread) was bribed and has family members that will be getting board AT&T seats pretty soon. Such is HN's fickle heart.

Unsurprisingly, the case involved more nuance than could be contained in a Bloomberg article, so if you really want to understand the arguments involved, you'll have to slog through the 200 page opinion: http://www.dcd.uscourts.gov/sites/dcd/files/17-2511opinion.p...

I'm generally depressed by the state of broadband competition in the US, but that doesn't automatically mean that Shapiro's "increased leverage harm" theory that vertical content-programmer-distributor integration will raise prices is correct. And even if it is intuitively correct or turns out to be right, it doesn't mean that we currently have sufficient supporting data for it to be a convincing argument to the courts.
Club salaries.
The app is using the app for background audio monitoring. Ios apps can't do that without displaying a big bar showing they are recording.

I'm assuming la liga app is background audio.
I work with PostgreSQL quite a lot and I don't think this is the case.

Yes, PostgreSQL is a mature project. But that has little or no bearing by itself on what degree it can scale; Linux is just about as old, yet it still drives most of the infrastructure we're talking about. In context, PostgreSQL has been under continuous development since inception and no more so than in the past decade or so with substantial community and corporate backing. To conflate project age with current robustness is to indulge in fallacious thinking (in this case "cum hoc ergo propter hoc", if I'm not mistaken). The project has advanced with the times. There are good examples of PostgreSQL running at scale, including at companies operating at scale such as Instagram, Skype (up to at least the point of the Microsoft acquisition), Pandora, as well as others. Most of these, I'd bet, are/were using PostgreSQL at scales substantially larger than that faced by GitLab.

Relational databases require good management and good design to function properly. There were people who specialized in this called Data Base Administrators (at least the management piece anyway). My feeling (perhaps unjustified) is in start-upish environments there is a tendency to minimize DBA expertise in favor of having more conventional developers that can "get the database to work"... which is a different standard than "getting the database to perform". That's mostly not my world, so I may be jumping to conclusions (I'm an enterprise systems guy on most days).

I think GitLab probably has a complex software product and lacks the correct expertise in infrastructure (including, yes, DBAs) for their SaaS offering. I'm reading tea leaves, but that would be a perfect storm which would produce exactly what we see no matter how robust any one piece of this puzzle might be.
I submitted because the implementation of css animations is some of the cleanest and well implemented I've seen, and I find the context very unique.

Edit:

Even cooler is the "advanced techniques" page, which, if your ad blocker blocks their video file requests (to YouTube), instead displays an animated gif in the same spot.
If I had to guess I would assume the above poster is referencing that there is a push within China's political atmosphere to turn inward and start developing more critical tech at home.

At the heart of all the cheap Chinese android phones is generally a qualcomm chip, much to the chagrin of the Chinese government. BitMain is likely well positioned to take advantage of their governments increased attention and investment in the high tech sector.
But even then, unless Uber develops and owns severe patents on the self-driving technology, the self-driving car inventory would just be a commodity available to every competitor too — meaning it would be a race to the bottom on prices and potentially fewer barriers to entry, unless they use lobbying to create a livery licensing racket for self-driving cars to protect some oligopoly of ride hailing services.

My bet is some form of oligopolistic regulatory capture is the long-term plan (similar in spirit to ISP oligopoly), because if self-driving cars are a commodity it still doesn’t look like that offers a path to profitability.
Agreed and now all the discussion on HN is about _where_ it's hosted, instead of the content itself. It's the first thing everyone noticed. My guess is they did this on purpose just to generate controversy
Well I'd argue it's the opposite -- that it is an excessively Euro-centric view of the world we mostly learn.
North Macedonia is probably the only solution that can pass a referendum vote.
NFLX also makes a profit, whereas Uber is burning cash faster than any startup out there
Must not have been during rush hour. Ain't no way you'd even get in a car around here during that time, if you had a choice in the matter.
Hello Tello, programming a drone with Go
Such evaluations are useless as a training set because they inherit the biases of whoever wrote the evaluations. Of course, if fairness isn’t a desired property, feel free to carry on.
> The Poles were a little bit more courageous than us and that attitude saw their country split into three.

This is very simplistic way to describe reasons behind partitioning of Poland, which was by then standards very large multiethnic country with borders from Baltic to Black Sea and ability to raise considerable military power to defend its borders in times of need.

Commonwealth's dissolution came from the inside. There was no centralization of power in Poland. King was de-facto figurehead with real power being divided between hundreds of nobles. Everybody else was professionalizing their military, but that was impossible to do in Poland because we were 18th century country that relied on King rallying nobles rallying their bannermen for military. There was no chain of command, grand strategy or even unified arsenal. That was ridiculous but nobles wanted it to stay that way so king or congress could never contest their power. What happened instead was country being partitioned and nobility getting the boot from new rulers that did not tolerate private kingdoms, private armies or having to negotiate with every single noble if they wanted to change something.
The classic solar sales and installation company business model isn't shaping up very well. Operating margins aren't the best due to the need for local assets in frequently changing markets as incentives come and go. It's definitely more profitable to sell batteries/panels/etc to the solar installers than to run the operation itself.
> problems caused directly by excess body fat

I would say this is putting the cart before the horse. It's not excess body fat that is the source of health problems. It's the lifestyle (diet and movement) that leads to excess body fat (as one of the many symptoms of growing health problems) from choices.

In other words, baldness, obesity, sluggishness, headaches, etc... are not the source of health problems - they are the symptoms.
Under Linux, you don't need threads. Threads and processes are basically the same thing. You just provide different flags which tell the kernel how it should view that process, which will impact things like memory isolation, copy on write, etc.

Under Windows, it is a different story. Threads and processes are wildly different constructs, and threads are more lightweight. Sometimes, still not lightweight enough, so they came up with fibers.
This data is also consistent with the idea that people leave expensive areas in order to have children in cheaper areas.
Under this logic I think so, it would be the same problem.
But AT&T certainly is, as would be the combined company.
Sexual Harassment Rampant in Science, New Report Reveals
How #Goodtech Can Help Brands Change the World for the Better
This is the HN quote of the century
It reminds me of a critique of threads in The Art of Unix Programming (available at http://www.catb.org/esr/writings/taoup/html/ch07s03.html#id2...). And now that I look it up, it actually cites the Ousterhout paper! This suspicion of threading was one of the few parts of that book I found unconvincing, personally, but it's another witness that they have worried some people for a long time.
AT&T blocked FaceTime because they were afraid that thier crappy overburdened network couldn’t handle the load. [1]

But for some reason, they weren’t worried about other video chatting apps - for instance you could use Yahoo Messenger at the time. What competing app did AT&T have?

[1] https://www.washingtonpost.com/blogs/post-tech/post/atandt-l...
I think my point stands, which is that not every possibility is an eventuality, and we shouldn't assume that to be true without a willingness to accept a very bad panoply of preventative measures masquerading as corrective measures.

That said, whether or not an activist judge allows a presumptively lawful merger to occur is hardly a hill worth dying on. We have remedies for activist judges through an appeal process. Where an appeals process is not available after the merger, we have remedy for anti-competitive companies through regulatory influence, regulatory agency, rule of law, and a court system to back that up.
> What does "magically" mean to you?

That by virtue of using a C compiler the code will, with no effort on my part, run faster than equivalent code written in a different language. That, if an implementation exists in C, that no other implementation can beat it.

I'm railing on against it because I've met people who believe that first paragraph, literally.

> If I say "the C compiler has millennia of work by a small army of clever people", do you think I'm saying it's "magic"?

No. But one can use the same backends as the current C compilers for other languages. The results will be the same.

> In that section you only mention C and assembly. It is not until much later mention other AOT languages.

My bad. Sometimes things are obvious to me and I incorrectly assume that other people will get what I'm saying.

> Is that not also a myth? https://en.wikipedia.org/wiki/PDP-11_architecture#Myth_of_PD....

From the link you posted:

"However, the C programming language did take advantage of several low-level programming features of the PDP-11, resulting in their inclusion into new processor".

I'd say no to the myth question. Reasonable people may disagree.

> C was implemented for other systems within its first year

I don't doubt it. Those systems were far, far simpler than an last-gen x86 processor.

My point isn't that "it's fancy PDP11 assembly", it's that today's hardware isn't even close to being represented by C. Or, at the very least, no more so than alternatives.

I've seen a lot of people write that they can see the assembly that would be generated when they read C. I don't think they've looked at the output of a compiler in a long while if that's the case.
Vegetables contain protein.
OData comes close to one, although it does not use SQL as its query language: http://www.odata.org/getting-started/understand-odata-in-6-s...
I think I still have my nv3 graphics card. Fun to think of how Nvidia grew.
Mayo is easy to make at home using a stick blender and a jar: https://www.seriouseats.com/recipes/2011/10/two-minute-mayon...
It's an established metric that uses club salaries. Is it predictive? The top 4 on that metric are Brazil, Germany, France, Spain.
Whomever thought taxing employment was a good idea needs to check their logic.

If Seattle politicians wanted to fix homelessness they would loosen zoning regulations and pass measures to combat NIMBYism.
> You just picked the easiest questions and left out the rest...

You were just saying you shouldn't directly trust people and I'm saying you should also dig. You asked a lot of questions, I don't have the answer to all of them, but somebody might. And that's why I say dig. Somebody might have already done the work. I for one am not omniscient, don't just counter everyone with "well you don't know everything", it isn't useful and is a non sequitur to the topic at hand. The answers were to illustrate a point, not to provide exactness. And your entire reply missed what I was saying because you were caught up in minutia.

> You should question this as well.

Are you talking about when the asteroid hit or are you suggesting a fictitious example? If the former I suggest looking at a timeline of human evolution and studying more about animal behavior. The latter, yeah thought experiments are fun. Who is saying they aren't? I'm definitely not. I'm not even disagreeing with your main point, I'm expanding on it. I'm literally saying don't just ask a question and stop. Ask a question and search for an answer! And you might like a story called Night by Isaac Asimov. It does discuss what is likely to happen with civilizations capable of communication, mythos (and included exaggeration).

> This would explain why the Bible claims that light was created before the sun.

We're taking about questioning things and you're taking the Bible as directly literal? Maybe you should question that.
Probably from half-remembered Tesla marketing spiel, at a guess.
There's a couple issues with your comment: first, the restriction you're talking about is related to preflighting, not to whether requests are allowed at all.

Additionally, you're thinking about the "wrong" Content-type header: the limitation you're mentioning about urlencoded and so on is a limitation on request headers, not response headers.

The CORS headers are required for the GP's described request to succeed, but not for the reasons you give.
Why does it need to be fair? Serious question.
Not OP, but a someone who uses D3 every day, it gives you (almost) total freedom. You can decide where to put your x and y axes, legends, labels, etc. You can decide how data determines not just how something appears on the screen (like a bar chart of y height) but how the underlying data determines its classes and styling, etc.

D3 is awe-inspiring in its scope, and learning to use it has a steep learning curve. But for anything beyond trivial use cases the freedom it affords you is worth the effort.
Sure; point being that employees ought not have to pay for their equity, because then it's not really compensation.
>This merger is bad news for the citizenry.

It is. And had it been successfully blocked, the message would be clearly understood by media outlet owners far beyond CNN's owner.

It is in fact lose-lose.

Same goes for whatever ends up happening to Amazon/WaPo.

This is the only anti-trust you can expect to see now.
Yep, not what happened. Google didn't make one; they acquired one. Google sunset that reader (I'll agree that in retrospect it was the wrong move, but regardless), but at no point did RSS readers stop existing. Two notes:

- RSS readers are _dead simple_ to build. If you're an average programmer you could make an MVP within 2 days.

- Many of the RSS readers are/were free. I don't think Google having Reader caused any great migrations, but even if it did I doubt it would have caused other readers to implode or anything like that.

I _believe_ what happened is that Reader had a small but vocal user group who were (understandably) upset at the sunsetting, and caused a big hubbub about it. I _suspect_ many of today's Reader complainers have never actually used Reader, and are just piggy-backing off some low-hanging Google bashing fruit.

Again, I'll happily nod at the badness of Google killing off Reader, but I intensely dislike the amount of hyperbole in the statement that Google "killed RSS". It's a thing that never took off. That's all that happened. It's still accessible, there are many clients you could use, and so on - it just so happens that most sites don't bother creating an RSS feed.
It's mostly a "day 1" concern, is all.

Once you get over it you find that you can do whatever you need.
Agreed, check out the top500 article or the direct ORNL System Overview. https://www.olcf.ornl.gov/for-users/system-user-guides/summi...
Something that saved me was the extensive amount of documentation-via-Stack Overflow, particularly the number of answers provided by D3's author, Mike Bostock--often with links to working code to illustrate his answer! The amount of effort he's put in to helping people understand how to use D3 is almost as impressive as D3 itself.
For when bitcoin mining cease to be profitable. Bitcoin mining rewards halves ever so often.
You (like Linus) are right in that microkernels don't provide much of a security benefit in-and-of themselves. But taking full advantage of other advances in information security research requires a new OS architecture.

The financial consequences of poor security are becoming more severe and the cost of developing high-assurance code is dropping rapidly [1]. If we haven't crossed the cost/benefit ratio yet, we are very close.

Microkernels are already the preferred architecture in niches that don't require legacy software. Monolithic kernels (and the Linux development process) can't catch up to the state-of-the-art.

[1]: https://microkerneldude.wordpress.com/2016/06/16/verified-so...
I live in San Francisco, I understand the problem well.
The scale is irrelevant to the property issue.
We have a system where all of our static assets are prefixed with the SHA1 of the git commit that produces them. It's a great cache-busting technique for CDNs. But this also means we cannot use paths like /img/background.jpg but rather /<insert 40 hex chars here>/img/background.jpg when we refer to such assets. Of course most of the time we can compute this by JavaScript on the client side but it's often easier just to use <base> and get rid of that piece of JavaScript.

Another use class is to change all links to open in a new tab by setting only "target" on the <base>. This happens on marketing sites with a lot of third party links so the marketing department naturally wants those links to open in a new tab instead of the current tab.
I don't claim these are "go-to" solutions, but only that there are multiple solutions to pick from.

One solution is processes (mentioned in the post). Fork a process which does your computationally expensive thing and then get the result when you are done. For the security minded, we've seen this make a bit of a come back because separate processes can be run with more restrictions and can crash without corrupting the caller. We see this in things like Chrome where the browser, renderers, and plugins are split up into separate processes. And many of Apple's frameworks have been refactored under the hood to use separate processes to try to further fortify the OS against exploits.

Another solution is break up the work and processing in increments. For example, rather than trying to load a data file in one shot, read a fraction of the bytes, then on the next event loop, read some more. Repeat until done. This can work with both async (like in Javascript) or you can do a poll model. Additionally, if you have coroutines (like in Lua), they are great for this because each coroutine has its own encapsulated state so you don't have to manually track how far along you are in your execution state.
Those stats aren't for autosteer (which is the point of contention) alone, and include AEB which no doubt saves lives.

This brings me to a crucial point. Nobody doubts that assistive technology save lives. Not just automatic emergency braking, but even lane keeping assists. What Tesla does is however take lane keeping assist and give it more responsibility of actively driving the car. It's not clear if that is safe. Even if it's safe, it's not clear if it's safer. You shouldn't be comparing autosteer to just a human, but a human with lane keeping assist. The difference is between the human driving actively, and the car driving itself actively.
My problem with d3 is that it's a very leaky abstraction, and there's no clarification about what, when, and where things must happen, versus can happen, versus must not happen. A core example is data joining. If you don't include .merge in just the right place, everything breaks with no warning or errors. A better design would eschew the implicit "state" of a selection (entering, updating, or exiting) in favor of providing three distinct, named handlers for the three stages.

The result of things like this is that d3 encourages mindless copy/paste, and you either have no idea how it really works, or else you've scoured the d3 source to understand what's going on (which then requires expert level of javascript knowledge).