skysight-inc/HackerNews huggingface dataset:
I grew up with a similar relationship to vice and the horror stories of cool points in place of real money later on, from almost every one I know that's worked for them in any capacity turned me off and most of the people i know in those circles
including the term "JavaScript" in a job posting makes it more likely to attract soyboys and Redditors
I completely agree. I've always said that I go to the gym to keep sane.
That's sounds a little absurd. A five year old child knows that 3 fingers is the same 3 as 3 ducks. Certainly 5000 years ago people understood 3 without ever knowing what an axiom is. The peano axioms didn't create arithmetic, arithmetic created the peano axioms. S(S(S(0))) follows | | |, not the other way around.
Right back atcha.
Replying here--yeah, the stores inside shopping malls typically lack the real estate to have all the shoes available in the main store and, instead, keep them in a stock room in the back. I've definitely been to both types; but, the mall stores are almost always the "pick a display shoe and have a salesperson bring your size."
I think I'm gonna need to see a proof that the approximation series converges, and doesn't just wander the phase space forever, before I accept that premise.
Seems like it's not such a crazy (pie in sky) idea after all:
https://www.technologyreview.com/s/609766/how-to-get-wyoming...
I think one of the overarching factors is that those new to data visualization (and web development) see D3's beautiful examples and assume that the D3 library is directly and fundamentally responsible for the visual quality. I've seen this a bit with R's ggplot2 as well among relatively experienced data scientists. To be sure, ggplot2 is a fantastic library and the fact that its defaults look great are a testament to the library's well-thought out design. But such design grace can be achieved in any library (e.g. matplotlib), albeit with less graceful APIs.
If a Canadian state decided to rename itself Maine, pretty sure Americans would have zero f*s to give about it. To quote Peter Griffin, "Who cares?!!".
Seattle City Council repeals head tax amid pressure from big businesses
Welcome to this entire conversation on why early employee compensation isn't fair.
Definitely not sparring. Mostly hitting pads. Something I could do with glasses on but I found it annoying as it got in the way of training.
Yes, the non-commercial license is the bigger problem as it's an ambiguous club that a hostile copyright holder could FUDgeon any sizable community with.

I had been thinking that with BSD, a gone-hostile company could make an argument that more recent changes were not actually intended to be released under BSD, whereas with GPL we know they would have had to have stuck with the license to build on top. But that latter part isn't true if they're arguing that they're the copyright holder.

edit: Actually what I was thinking is true IF there is an additional contributor who's patch got accepted into the main tree. But in this case, given that the ostensible goal of CC non-commercial was so that the code could be dual licensed, we'd expect any such contributor to have been shuffled into copyright assignment.
And if you check page 7 of the PDF there is a small table that indicates that this has to be at around 120dB to have an effect. I do believe that is up around the point where you risk physical pain and instant hearing loss.
Because there's always something to offend a feminist?

"We're looking for someone to manage a team" is apparently sexist, according the article. How can anyone take this seriously?
The whole point of what I was saying had nothing to do with lifting and everything about being careful if you're going to do something radical to alter your mood if you're a depressive.

My advice would have been the same if I had said to be careful about abruptly stopping a medication.

My lifting injury was related to my sciatic nerve. I could barely walk for months and sitting or standing for any length of time was a challenge. Taking on any other kind of physical activity was out of the question. The effect on my mood and the depressive episode stopping my workouts triggered was a pretty significant problem.

If you're a depressive and you suddenly start doing something majorly physically-taxing, get really good training and be very, very careful. But I had great programming and an industry-leading coach and I still got hurt.
In almost all cases, I completely agree with you!

In shops that require interaction to proceed beyond browsing (such as the shoe shops I visited yesterday) I want a salesperson to be attentive and help me so I can spend as little time as possible standing around waiting.
>Though choice is more commonly used in an alternate form such as Zorn's lemma

Speaking of choice & constructivism, did you know that there exists a constructive version of the axiom of choice? See here:

http://web.archive.org/web/20170222112602/http://www.jonmste...

[Historical side note of somewhat fleeting importance on something which, besides me, nobody so far seems to have really noticed:

It seems that van Heijenoort 'overtranslated' Hilbert's infamous boxing gloves paragraph. Here's the original German, from Die Grundlagen der Mathematik, Abhandlungen aus dem mathematischen Seminar der Hamburgischen Universität 6 (1928), 65-85:

"Dieses Tertium non datur dem Mathematiker zu nehmen, wäre etwa, wie wenn man dem Astronomen das Fernrohr oder dem Boxer den Gebrauch der Fäuste untersagen wollte."

Here, van Heijenoort's translation:

"Taking the principle of excluded middle from the mathematician would be the same, say, as proscribing the telescope to the astronomer or to the boxer the use of his fists."

Here, a more literal translation:

"To take this Tertium non datur from the mathematician, would be about how when would want to proscribe the Astronomer the telescope or the boxer the usage of the fists."

Now, the point of this doesn't consist of the sentence now sounding rather different (and somewhat badly phrased) - in fact, that seems rather typical of intentionally more literal translations, as usually, translation also involves fitting the translated version of the text into the common use of the target language. No, the point consists of the fact that van Heijenoort should have left the latin expression "Tertium non datur" in place, see the following reddit comments thread about TND 🆚 LEM for why:

https://www.reddit.com/r/dependent_types/comments/33tc28/jon... ]
Yeah, we happened to be near the mall yesterday for an unrelated reason so I decided to give it a shot. DSW is always a good option; but, I often find myself frustrated with my size being fairly common (translation: often sold out).
Can you tell how it was and how it was resolved, and what you'd do differently if it happened again, if you would?
Dunno for me D3 feels like they are trying to do everything at once resulting in an overly complex and hard-to-learn library.

When I look at the examples at their page I see stuff that I could make in 2 ways:

- Just write a small program from scratch that visualizes one in a week or 2. It will be small, I will know the ins and outs, so easy to change and will be a ton of fun to write.

- Use D3.js (I dont know this library, but i've used complex charting libraries in the past). Likely it will take more time, not because I am thinking of the interesting parts, I will spend most of my day cursing on StackOverFlow to figure out how to skin that one tricky part of my app.

So in the end I dont really see a good reason to use d3.js unless my full time job is to develop data visualizations.
I think of it in an engineery sense - if the edge case is possible, it will happen.

Maybe that works for software engineering, where it's a good idea to pause a release in case someone uses scripts to send a shitload of bad requests to our API and crashes a server because of our bug or whatever, but I understand that that doesn't work 1:1 with the real world, where it doesn't make sense to not have the aviation industry until we perfect self-flying planes.
Use Clojure, it has built-in Software Transactional Memory support.
But after months, the flap does settle back. So while it never heals the risk of rubbing your eyes dislocating the flap is rare.

Nevertheless, I do worry about this a lot.
This is sadly my experience too. Both my parents are educators and life long learners.

It still floors me how many conversations they had with my younger siblings friends parents (I was present) were it more or less went. Friend parent makes baseless or incorrect assertion my history buff father retorted and they just said well I don’t care anyways.
iirc Austin is one of the few places in the US that has a full feed-in tariff, that is they buy back all your solar through a dedicated meter at feed-in prices (usually closer to wholesale vs. the retail prices you purchase at) and apply that as a credit.
BTW, you're wrong about your "reflexive" theory.

I use far too much Google stuff. I'm on GMail. I use Chrome. I am a Node developer which uses their V8 implementation of JavaScript. I hate it but I mostly use Google for search, habits die hard. It will be a huge pain to me if I have to fall back from using Google. I criticize them because I do use their products. When I stop, you can be pretty sure I will also stop writing about them.
Anti-trust is so royally messed up in US. It hurts the economy.
It's an older style of dealing with the pronoun-of-a-hypothetical-person problem. It dates the writer (or style guide) a little.
It's also interesting to look at the labels on our food in the US. Spaghetti sauce? Added sugar. Loaf of whole wheat bread? Added sugar. People may not see the addiction, but it's added to most everything right in front of our face.
Seems like it should be straightforward to test it before jumping to conclusions and making accusations right?

Get a clean "air-gap" computer, and see what's really on it.
I wonder if the ice might help protect against extreme low temperatures? Fur on animals traps air, acting as an insulator, so it might be similar here. As the fungus (presumably) provides negligible heat output, it would probably only protect against temporary cold flashes, rather than sustained lows - perhaps unusually cold nights?
The worst is when they ask if you need help finding anything and you think they’re an employee and then they hit you with a sales pitch.

Dude I’m just trying to find the mold spray and get out.
Maybe in north america...
I guess I can see it both ways, but in my mind, if GitLab's UI is too confusing for a new user to even navigate, then maybe it isn't good enough to migrate to. I do agree that familiarity with GitHub helps, but by that logic, a normal blog (maybe on Medium) would've been even better. The fact that it's formatted as a git repo (which is honestly sub-optimal for a tutorial), yet not hosted on GitLab, just felt strange.
Cryptocourt? Bitjudge?
If you get stuck at an American Banker paywall, just search on Google for the article

"Radius in Boston working with fintech firm on online business checking platform"
Of course there's a software solution to this: http://eyedoc2020.blogspot.com/2017/03/best-apps-to-remind-y...
A serious practical problem with threads mirrors the same problem with C++, which is that many programmers reach for it first when they should be reaching for it last. Both of these technologies are like swallowing glass, and the wise programmer will avoid them if at all possible.
They're just quotes.
NSA could have access to data on Microsoft-owned GitHub
That's not surprising at all. Untrustworthy people doing untrustworthy business are the people most in need of a platform that doesn't rely on trust.
Ideal fractals also don't exist. :-)
"To date, the only proven model for treading new ground in space is large defense contractors spending gobs of State money."

This is exactly the problem Space X is meant to solve.

Costs need to come down radically, and State money is too fickle to be relied on for reaching long term goals.
This is a real risk. A colleague of mine who specializes in hardware security research recently received a modified mainboard in an otherwise normal amazon order. The supplier literally modified (with or without their knowledge) the part sent to him by adding an extra unidentified microcontroller that has been soldered into the IO bus. Removing the part caused no loss of performance. It was there for some kind of surveillance OF THE RESEARCHER.

In another case, his air gapped laptop was found to be emitting subaudible tones by modulating the system can.
Ouch! Seems that a company does need a goodwill explicit contract between partners so that in the case of a split or disagreement, the company can use the assets already created, even if copyright is still owned by the parties themselves. Or else all that work can be killed by one spiteful party (or one aggrieved one). Yet... in this case, would that be a good thing? Conundrum.
You don't have to do state management this way, sure, but this functional reactive style of state management has its own set of compelling benefits, like making it easier to reason about side effects and complicated state.
Image allows you to do this more or less. The problem to be solved here is that if you write the resize logic just once, you are accessing pixels from the image via the interface in a tight loop, and most of the time taken by your image resizer is the overhead of that access.
> People are somewhat irrational in nature and fear rare, but spectacular events more than the mundane. This is the number one problem with nuclear that I see it: no other power source has had anything on the scale of Chernobyl. The only thing that I think offhand could come close as far as potential deaths is a hydro dam collapse.

You don't need to think of the potential. We have already had power generation accidents far worse then Chernobyl. The Banqiao and Shimantan Dam collapse in China killed 170,000 people, and destroyed the homes of 11 million more.

And if you want to rank energy safety by KWH generated, you can look at:

https://en.wikipedia.org/wiki/Energy_accidents

We've also had a pipeline explosion that killed a thousand people, we have five Chernobyls every year thanks to the poor safety record of coal mining... The list goes on.
> As a result of my occupation, I think I know a bit about where operating are going in the next decade or so.

> While I could go into a long story here about the relative merits of the two designs, suffice it to say that among the people who actually design operating systems, the debate is essentially over. Microkernels have won.

That's a theoretician confusing theory and practice.

And note that Tannenbaum isn't one of the "people who actually design operating systems". Tannenbaum designed toys to demonstrate concepts, not OSes for real-world use.

And, was Tannenbaum right that NT was a microkernel design? I have this vague memory that the drivers were supposed to be in user space, but they moved at least the video drivers into the kernel for performance reasons.
It's irrelevant what Washington or anybody else said. The common name for the North and South American landmasses is America (note: not Americas). The land between Canada and Mexico has no more rights to that name than the rest of the continent (or continents, depending on what model you prefer).

Abroad, Hollywood has popularized the use of "American" to refer to citizens of the USA. Also, most languages don't have any other way to refer to US citizens because of its odd name. I'm only aware of Spanish "estadounidenses".

It's no different than if the most powerful European country were to call themselves Europeans alone.
I was joking, but to a point.

The problem is that "100%" =/= "All". But most of the time, it is considered to be equivalent. The "almost all" phrase is used instead of "100%" precisely because dividing by infinity doesn't yield a useful result in some contexts.

In more... "conventional" cases, if I tell you that 100% of the items are blue, you can conclude that none of them are red. With the intermingling of countable and uncountable sets, this statement fails. You have a situation where 100% of the items in the superset are blue, and there are also some red ones.

So it's "almost 100%" in the same way it's "almost all". I'm using the word "almost" to mean "infinitesimally close to"
Structured threads aren't that hard (e.g. task-based systems, thread pools).

Unmaintanable raw-pthread messes are a nightmare sequel from the director of Endless GOTOs.
What's even more confusing is that v3 -> v4 includes a bunch of breaking changes, and yet they didn't update their typescript definition file. Not to mention the web is full of v3 examples that mysteriously don't work with your d3 lib (and versions are never mentioned anywhere).
BeOS was pretty good, and now that i'm wiser in the tooth, they were basically implementing the Actor model, except since it was in C++, it was really hard to guarantee that the programmers wouldn't do stupid things with shared state.
In French, some people say étasunien (or États-Unien, Étatsunien) to avoid saying américain.
États-Unis d’Amérique meaning USA.

https://fr.wiktionary.org/wiki/%C3%89tasunien
Activists tend to conflate a visible change with a useful change. The problem with tinkering with the language is that you might get (some) people to change their speech superficially, and you're going to chalk that up as a success. But you have no real notion as to whether it's doing anything productive. We've had a host of gender-neutral terms in professional life for decades now, but when I'm reading stuff on women's issues, I don't get any sense that women feel better off because of this. It's just more linguistic landmines in the workplace.

And the article is counting stats on how many women apply. That runs headlong into the fundamental problem with diversity metrics: proportions in an organization not matching proportions in society are by themselves a genuine problem, but it's taken for granted that this means something terribly dire. Then when you do some stuff and those numbers change, you have no idea if it's due to anything you did, or if things are actually better. And you're playing tribal politics, so it's hard to see that "my tribe benefited!" is better for society as a whole.
"#!/bin/bash" absolutely is portable when writing a Debian package for installation on Debian or Ubuntu systems. bash is guaranteed to be installed in this scenario as it ships in a package marked Essential.

Further, for the purpose of a distribution package, "#!/usr/bin/env bash" is wrong, as it'll prefer /usr/local/bin/bash which could be anything. Since the distribution package uses real package dependencies to express what it needs, it'd be wrong for it to use anything in /usr/local.
1995 was a different era.
A lot of work in programming languages over the past decade has been devoted to providing a safety net and guard rails for avoiding the pitfalls of thread-based concurrency. See in particular Rust and Go. It's still quite possible to corrupt data and get deadlocks, but our languages have come a long way to making it harder.

But the point of this article is to say if we ditch the notion of threads entirely and go with this other thing, we won't need safety nets anymore because it will be impossible to deadlock and corrupt data (as opposed to less likely).
Apple's App Store Privacy Crackdown May Hurt Facebook's Onavo
What does that have to do with AT&T buying HBO, some cable channels and a movie studio? This is to compete with Netflix, not about providing broadband.
Mostly because a car is too heavy :p
https://i.imgflip.com/2c40f3.jpg

(I know, I'm sorry)
Not sure if I totally buy it, but the economic argument here [1] is interesting. Essentially the claim is that proof of stake actually takes just as much resources as proof of work (marginal cost = marginal revenue), as no participant in the market is able to extract a rent.

1 - http://www.truthcoin.info/blog/pow-cheapest/
In theory this seems like a great solution to many data privacy problems, but I suspect strongly that this leads in reality to very hard to support products as you can't make that many assumptions about the data stores. Performance and reliability of datastorage makes up a large chunk of the user-experience of any web-app, so having this out of ones control is a tough proposition for anyone actually wanting to build a business ontop of this.
Google, AI, and National Defense
As mentioned in other comments, Ousterhout is the inventor of Tcl/Tk (among other things). At around the time this was published, Tcl was my favorite "play with" language, and it naturally lacked sort of built-in threads abstraction. Also at the same time, Tcl/Tk had just become a project at Sunlabs. One of their early projects was to take the event-loop that was the underpinning of Tk and add it to Tcl.

I started a new project back around then to build a system for deep caching of web sites to give time consistent access offline. I implemented as a web proxy with an online/offline button. As you browsed web sites, it would crawl recursively following a set of rules. The intent was to precache content near what you already explicitly accessed, to make it available offline later on (we called this the "detachable web").

While not the primary purpose of our project, I put together a demo to optimize the Alta Vista search results page, which at the bottom only had a "Next" button (unlike the "1 2 3 4 5..." you see at places like Google today). When you clicked "Next", it took Alta Vista a few seconds (4-5) to return the next page of search results. My system would prefetch the 10 pages of results by POSTing the "Next" for you, basically while you were still reading the first page resuls. The result was "Next" became instantaneous. Again, this is not why we built this system; this was just one novel approach I used it for.

I mentioned all this because the entire project was implemented in Tcl. Being influenced by the lack of thread support in Tcl and by the paper mentioned in the OP, my project utilized a event-driven model for everything, since every inbound user require could fire off dozens of background fetches, all of which needed to be done in parallel. Events (and continuations) worked well for this. I have a paper up from the 5th Tcl/Tk workshop:

https://www.usenix.org/conference/5th-annual-tcltk-workshop-...

I had used for the project Tcl because it let me support all three prevalent platforms of the time: UNIX, Windows 95, and MacOS 9. Day-to-day work was done on FreeBSD.

I think have some commentary in the paper on the effects of the event-driven approach. What's funny is that I was taken off the project for v2, which the team then decided would be written in Java using threads, because, well, Tcl wasn't mainstream enough. In 1997, Java was the rage. The downside is that they could never get v2 working reliably enough because of the explosion in memory and processing power it required to accomplish the same work. In Tcl, having 60 traversals active when it was just 60 continuations (events) just worked. In contrast, the Java implementation needed 2-3 threads per traversal, and it just couldn't scale up to that.
Reminds me of: https://www.history.com/this-day-in-history/thomas-jefferson...
Cable companies created regional monopolies with municipalities and used that protection to lay their lines. By the time the 1992 Cable Television Consumer Protection and Competition Act rolled around, they'd established natural monopolies based on that infrastructure and they have benefitted from that ever since.

They don't want to be "dumb pipes", but they also won't give access to those dumb pipes, ensuring that no one else can compete with them upstream. Seems they shouldn't be able to have it both ways, but here we are. So, the next-best-thing would be to assign protection through edicts like Net Neutrality and rigorous anti-trust policing.

Yet, these are now being dismantled as well. Not a good place we're heading.