skysight-inc/HackerNews huggingface dataset:
A few years back, I was waiting for the bus at the Calgary airport and saw a guy with what I thought was a big husky. He was waiting for the same bus, and it was going to be a while so we started talking. I lead with, "Nice dog" and he responded, "That's not a dog. That's a wolf."

I was a bit incredulous. He explained that he bred dogs for security. After losing a few of his dogs to coyotes, he wanted tougher animals. He managed to acquire a couple wolf pups, raised them and bred them with with mastiffs to make them bigger and more controllable.

The wolves were impossible to keep entirely under control, and even the wolf dogs were hard. They're big, strong and wild. Under normal circumstances, they weren't too bad but when excited, they could not be stopped. Like, if you took a group of them on a walk down to the river, it would not be possible to keep them from running to the water once it was in sight. The "big husky" he was bringing on the bus was apparently one of those, though he assured me that she was manageable alone.

It was a rather incredible story. Coming from anybody else I wouldn't have believed it, but the man was covered in scars and was missing a bite out of his nose. The bus was the north crosstown, which would have taken him around the edge of the city.
With asynchrony you get out of order execution and non-determinism by definition.

That you don't have the concerns of shared memory concurrency, that's actually not such a big relief, especially given the right abstractions. And the underlying problem, that you need to deal with concurrency, doesn't go away.

I've just written an article describing how JavaScript's Promise leaks memory in "then" chains and that it shouldn't: https://alexn.org/blog/2017/10/11/javascript-promise-leaks-m...

The reception was actually negative, having lots of people telling me that I'm concerned about a niche use-case, but functional programming isn't a niche at all, being one of the two known ways to write reasonable, composable code that deals with concurrency and asynchrony, the other way being to have a draconian borrow checker, like that of Rust.

Mainstream developers are in general deluding themselves that the tools they are using are adequate, in spite of repeated evidence to the contrary, whereas most current breakthroughs in productivity were born out of functional programming, starting from garbage collection, but also actual libraries that people are now fond of, like React.

Haskell does shared memory concurrency. The JVM / Scala does that too. In Haskell you work with things like IO, MVar, STM (transactional memory) and many more. High level abstractions that have been borrowed by Scala as well, my current languages of choice.

I feel much more confident writing concurrent Haskell or Scala code, with 0% test coverage, then I am writing JavaScript code with 100% code coverage.
How can you explain that unzipping an archive under WSL filesystem is 5 minutes, while on the same machine atop of windows native filesystem it's 3 seconds?
There are huge indicators. People just jam it till it works.

IE. No user testing.
I guess I've been doing all my work and getting all my computing desktop needs from an imaginary box then.
Why down vote me?
Not really. The cable thing is easily solved - don't buy cheap cables. If you ever plan on using USB-C for thunderbolt, only buy cables capable of thunderbolt.

As for devices - I guess I'd say know what you're buying? How is it any different than the fact I have to know that some mini-displayport ports can do thunderbolt and some can't? Some cables can and some can't?

I mean... Belkin has already started putting the thunderbolt icon on the cables they sell that support it. This isn't anywhere near as complicated as he's claiming. The only gray area is people buying the cheapest possible cable they can find on Amazon then acting shocked when they get what they paid for.
I think these are actually the most minor problems with the USB-C vision. The VAST majority of consumers will never encounter a thunderbolt device, and the ones that do can be expected to understand the cable difference.

What is far more of an issue for the standard is the established network effect. USB-A has become so commonplace that its built into our furniture, and micro-USB is a legally defined requirement for device charging in some areas. These foundational forces will prove to be a massive deterrent to USB-C uptake, and far more of a risk to the vision than multiple cable types that are clearly labeled!

But, the bright side of this I think is Apple's adoption of the Qi charging standard. Its clear that an evolutional jump to wireless charging will entail new technology, so I see Qi taking up the "one way to charge everything" vision.
It could be done by color coding (or standardized icons, or something), but the standards body didn't actually go to the trouble of doing that. I don't think the OP is objecting to the connector; I think he is objecting to the failure to anticipate the proliferation of cable types and to provide some standardized symbology to differentiate them.
Hang on, it's not like type-A where it's just a single parameter (1.1/2.0/3.0). A USB-C cable has tons of potential features and a port has possibly more features still.

- Protocol: 3.0 or 3.1

- Power: QC, PD, or none of the above; how many watts

- Alt-modes: HDMI, DP, TB3

- Chipset features: UAS

Once you've assigned all of these to a color, the higher end cables are going to look like a pride flag or something. The solution is really not that simple at all and it's far from guaranteed that once adoption picks up that you can just assume your device/cable combo "obviously" supports what you want.

On top of all of this, construction of USB-C cables are far more complex than your run of the mill cable. They're active devices with apparently absurdly tight tolerances. Did everyone forget about the Benson Leung's spreadsheet of killer cables? Even if the industry can figure out a user friendly branding, it's still a roll of the dice for whether you'll fry your laptop.

Lastly, USB-C seems like a mandatory weakening of security. In a few years time, you won't have any other choice but USB-C and now suddenly any random charger (or cable!) could be the easiest rootkit ever deployed. The cute pen testing exercise of dropping USB thumbdrives with backdoored Word docs is going to get a lot more serious. I wonder how long until we have "hardware firewalls" that attempt to rein in USB-C devices. We're past the "USB condom" at this point.
https://media.giphy.com/media/gz945ghj1zMyI/giphy.gif
Amen.
Death's Human and Cynic's Focus are on my favourites list.
I will add:

Opeth - Blackwater Park.

Slayer - Seasons (1990).

Megadeth - Rust in Peace (1990).

Fates Warning - A Pleasant Shade of Gray.

Spiral Architect - A Sceptic's Universe.

Dream Theater - Awake.

Emperor - Nightside and Anthems.

Soilwork - Chainheart Machine.

Morbid Angel - Domination.

Dissection - Storm of the Light's Bane.

Gorguts - Obscura and From Wisdom...

There is always nostalgia for the ground broken in the 80's, but the 90's yielded many great bands' best.
Jane Kim is elected to represent SOMA's interests; should she install a border fence to force me to eat at SOMA restaurants instead of going a few blocks to the places I like better in the Financial District?
I also found this effect super annoying when I switched to using a car - having to sell my carriage, get rid of my stable, sell or rent all my horses. All my connections in remote stables were suddenly useless. And I had to sell of all that hay! And oil, I had to get lots of oil! And it's nowhere to be found! Outrageous, I say.
To the degree science is a matter of writing academic papers, there is probably some truth to the assertion. To the degree experiment and the application of scientific discoveries matter more...well, Shenzhen.
One shot and zero shot learning also use statistical models.
Can the devs send IBAN/PM it to me? I hate to pay some third party %charges? I am in France itself would like to make a Bank Transfer
Well, there is a little bit of emulation. We have to encode and handle Linux-style file permissions, which has some overhead.

We are working on making both the WSL layer and NTFS itself better. For example, in the upcoming Windows release, we have created a fast path for stat that should yield a modest speed improvement.

We have a lot more work to do, though.
I mean, doesn't the west have the exact same issues? p-Hacking, lack of repeat studies, focusing on experiments that will make the biggest headlines, etc.

https://www.youtube.com/watch?v=42QuXLucH3Q

https://www.youtube.com/watch?v=0Rnq1NpHdmw
Alto descendants from PARC, ranging in size (not year built) from the Dandelion (AKA Xerox Star) Dolphin and Dorado (an ECL logic screamer). You could boot them into standalone environments like Smalltalk, Interlisp-D, and Cedar/Mesa). By “standalone” I mean you loaded specific microcode into the machine and then booted an environment in which everything: OS, GUI, file system etc was written in that environment.

When I worked at PARC I mostly used Interlisp, but I did use all those environments.
A large employer in my past used to apparently conduct just this sort of "interview". I learned to my disgust a few years later that the division conducting those "interviews" were doing what they called a "brain suck". That is, they never intended to hire anyone, they were just using the unlucky "interviewees" to help them solve a software engineering problem for free.
This is a very common little device. The V-I characteristics are non-ohmic i.e. non-linear which make it very useful for feedback. Some notable uses I've seen it for floating around:

1. One of my DMM's, a Fluke 8600A, has a light bulb in it as part of the charge circuit: https://i.imgur.com/TMvRmKF.jpg

2. My Tektronix DM44 strapped to the top of one of my scopes has one as part of the ohmmeter input circuit.

3. Also used for amplitude stabilisation in feedback networks in the negative feedback path.

Very common tricks and very useful little things.

Only problem is they get hot, eat a lot of current and snuff it occasionally. They were replaced by JFETs for typical feedback applications.
What do you suppose I'm typing this on?
> Their democracy is even more of a joke than that of the US.

What democracy?
Can we not have a power-only USB-C condom / datawall?
Traceroute Lies: A Typical Misinterpretation Of Output
With all the hubs I still can't get my 2017 Macbook Pro 15inch to reliably run an external monitor. (it lags every now and then). So far I didn't find out yet which of the components is actually causing it. Crazy how complex it is.
Node is written using libev, which under the hood uses system calls like select, poll, epoll etc (whatever is fastest for the combination of the IO task at hand and the current kernel) to provide an abstraction called an event loop.

It acts as an intermediary between your application code and the kernel, notifying you as soon as some IO action was completed by the kernel via an event callback.

This notification is provided to you as a single queue of events; the event loop is hence single threaded.

The important thing this facilitates is making it easier to reason about your application code, since you can be assured that only one of hundreds of callbacks in your application can be running at any one time.

Does it put an upper limit on the amount of work a single server process can handle? Depending on your use case, possibly yes. NodeJS shines when most of the work each call to your server involves mostly IO, i.e. are IO bound tasks.

If on the other hand, if any of the calls are CPU bound (some complex mathematical calculations say), you're probably going to hit this limit much sooner.

Even in cases where you have to run CPU bound tasks, it is far 'simpler' to offload these to an entirely different process that uses some sort of IPC to run the calculations and communicate the completed results back to your main server process, rather than spinning up a new thread in your server process to handle those CPU-bound tasks.

Does it now not possibly involve multiple threads accessing the database concurrently? Well, yes. Databases though are rather good at handling races. Most mainstream databases provide some sort of locking mechanism to make sure that some shared record cannot be erroneously modified by two processes at the same time.

If database locks are not for you, there are other solutions possible for these kinds of issues as well. By implementing a proper message queue, you can filter out calls that access this shared record into a separate synchronous queue, while all the other calls can be made to the DB simultaneously.

Why bother with mutex locks and races in your application code when other people (authors of libev/databases) are willing to do it for you?
If you want TB3 support on each USB port, you will run out of PCIe lanes available on the CPU. Just with basic support for 2 PCIe lanes per port and 4 ports, you are at 8 already. Similarly with running DisplayPort to each port, your GPU doesn't have unlimited number of encoders.
No, async & single-threaded is not an abstract replacement for threads. Single-threaded async code can only use 1 CPU core at a time. For example, JS running in the browser without web workers. Multi-threaded uses multiple cores simultaneously.

Whether a thread is "virtual" - I don't know what that means to you, but threads are a primitive the OS provides. Some CPUs have hardware support for threads, and some don't. So, I suspect they are less virtual than you're thinking.
Not really. It was more of a "platform choices" comparison blog post. We're mostly a Django shop, so the Python project began a few months before the Clojure one. We had the feeling that Clojure might be a good fit for a few use cases that we have, especially mobile-focused API backends, so the post is a summary of some of the lessons we learned when using a Clojure web stack instead of Django.
What the Mainstream Media Is Not Telling You About Hurricane Ophelia
> I never understood the idea that democracy was a superior form of government. If, in the future, China (or some other nation) becomes the next world power, with superior scientific innovation, larger industry, higher standards of living, etc, will you still prefer Democracy to what they have?

Well of course I would. Would you rather be married to a rich man who beats you?

> It seems incredibly naive to assume the present state of the west is somehow the final and ultimate condition we can hope to obtain. If this is as good as it gets, I think I want to move to China.

I am extremely sceptical of American "democracy" but I see Chinese totalitarianism to be a step in the wrong direction.
I'm chronically ill so I value most of all flexible work hours and an understanding that there will be periods of time ranging from days to weeks to months where I'm derelict as an engineer.
Could Silicon Valley work if startups paid living wages?
Meanwhile the number of homeless grow.

It's like two separate worlds.
Seems it's back up!
Paperclips
> I really don't like intermixing mutability with allocation location. Those seem like two completely separate concerns.

They're not. The semantics of value types and reference types are different in the presence of mutation. So if you want uniform object semantics in a language, then objects that can be implemented as values must be immutable. There are many languages that have kept these independent and bifurcated their type system instead (Java, C#), but it's been a source a great deal of pain and frustration (e.g. Java's `int` versus `Integer` awkwardness).

Fortunately, there's nothing you can do with mutation that you can't do just as well by modifying and replacing an immutable value in a mutable cell – the compiler implements them the same way. Wrap an immutable in a mutable `Ref` and voila, you've got something equivalent to a mutable value type without exposing completely incompatible semantics in the language.
"Keep a low profile and cultivate thyself quietly."
Wow, this is a shitty article. How longreads has fallen. :(

Too long, don't read: Wright is not Satoshi. Wright is a con artist. And not a very good one, at that.
This sounds like a broken window fallacy to me. Inefficiency can manifest as more jobs, but that doesn't mean people are better off.
Yeah, I don't see why not. USB-C PD negotiation is not done over the USB 2.0 data bus.
No, I am not, by any chance, religious. I don't rule out the possibility of a God or God-like intelligence existing in the Universe, but that's simply as a result of the "absence of evidence is not evidence of absence" principle I hold to.

I don't really see how religion factors into this though... I feel like I'm talking about a simple concept too. If I show you an encrypted message and show you that other people can read the contents with a key, then ask you to read it without the key, why can't you? It's not magic, it's math.
Regardless of what you think of China, you can't deny its competence and growing influence. This simple chart from Google says it all:

https://i.imgur.com/T88SqnA.png
Not sure how much performance matters here. You're just farming it off to CPLEX or Gurobi anyway. If performance really matters, you'll do this part in C++ anyway.
I purchased a house last year in the Oakland Hills. I learned when I started calling around to secure insurance for it that it was in the "maximum wildfire risk zone", which meant none of the big national insurance companies will touch it - making it difficult to insure. And you can't get a mortgage without that insurance, so you have no excuse for not knowing the risks.

In addition to that, the City of Oakland (and other cities in the area) have strict fire prevention ordinances for those who live in these high risk areas. You are required to maintain a defensible space around your house, to remove dead trees and shrubs, clean up dry leaves, keep grass short, remove tree limbs < 6' from the ground, etc etc. and the fire department comes by at least once a year to inspect your property to make sure you do it. If they find you in non-compliance they fine you $330 on the spot and schedule another inspection for a couple weeks later. Again, no excuse for not knowing your risks.

Similar regulations are in place for utilities and businesses to reduce the risk. Seems to me California is doing a much better job dealing with natural disaster preparation, but there's only so much the state can reasonably do.
I think China will be quite good at applying existing methods or creating derivative works (despite the frauds) and ultimately that's what matters. Most applications in AI rely on simple systems, only a small part of them require cutting edge architectures or ideas.
China is a democracy. Almost all countries are. They even have fair elections I beleive. However, they do not have OPEN and fair elections. Only people who have been approved by the communist party can ever appear on a ballot. https://en.wikipedia.org/wiki/Elections_in_China
I guess my question is, if USB-C has to be this complicated, then how is it an improvement over having multiple port types? I would argue that it's worse, and I think that's the point of the linked article. Compared to how things used to be, USB 2/3 is a marvel. Chain a dozen things off a couple of ports, all of which use the same plug. And it (almost) always Just Worked. The connector design was an improvement over what it preceded, but still was ultimately problematic. USB-C is a definite win in terms of form factor and usability of the connector itself. But if not all USB-C ports and cables can support Thunderbolt bandwidth, then all we're doing is sowing confusion. Why not stick to using mini-DP for Thunderbolt and have USB-C keep the USB dream alive?
The solution to this is creating the right kind of framework for reproducible research...
1. Type of problems I'd be working on
2. Whether or not the company allows remote workers
3. Salary range
Can you explain how you organize them?
Been trying to do something similar but haven't gotten it quite right yet.
There's one filter that every single human has: ethics.

Not everyone's philosophy is the same; there are missions that I might find detestable and you might not.

But for goodness sake, please don't make me go through the process of filling out a long form, writing a cover-letter, and jumping on a 60 minute phone call before you tell me that you're building something to help the government kill people. Like, seriously, put that right at the top and save everybody's time.
Because when Pluto was discovered, they thought it was alone out there. Then they found that Pluto was a lot smaller than first thought (mass 1/5th of our Moon, roughly the size of Australia), and that there were a lot of other objects only slightly smaller in similar orbits (the Kuiper belt). And then we found Eris which is just as big as Pluto (slightly smaller in diameter, but more mass). So either they are all planets, potentially thousands of them in the Kuiper belt, or we redefine 'planet' so Pluto, Eris, and similar bodies are excluded.

So now a 'planet' is a) orbiting the Sun, b) mostly spherical, and c) mostly alone in its orbital neighborhood[1].

Pluto, Eris et. al are still more than mere rocks, they have been reclassified as dwarf planets[2].

It was a similar story with the asteroid belt: They found the first asteroid (Ceres, I think) and called it a planet. Then they found another, and another, and soon it became clear that there were a very large number of small bodies in similar orbits. So they decided that they weren't planets after all, and called them asteroids instead[3].

The difference with Pluto is just that it happened so recently.

[1] https://en.wikipedia.org/wiki/IAU_definition_of_planet

[2] https://en.wikipedia.org/wiki/Dwarf_planet#Dwarf_planets_and...

[3] https://en.wikipedia.org/wiki/Ceres_(dwarf_planet)#Classific...
You have to consider well-known posters.

This user is known: patio11
They are bad performers for Tesla. That does not mean they are bad performers for other companies. The acceptance threshold at Tesla could be at a very different level.
They have a new 3D object content type for the feed, which can be rotated and such by tilting your phone; has some support for AR using the phone camera. The assets come from their modelling app and such.

Full WebVR content will follow. They're easing the masses into VR via changes to the feed.
There are actually many more "dwarf" continents (the usual name is microcontinent). The Kerguelen plateau and Madagascar are the two other large ones, as far as I know. Australia and Antarctica are much larger, and in fact microcontinents are defined as being smaller than Australia.

Zealandia is just in the news because it's the latest one to have been formally called that, possibly because it's the largest one (but not enough to be in a different category) and probably also because there's an English-speaking country on it. But it's actually not especially notable.
Like all stats, it is easy to cherry pick.

I find this graph is a better representation of the current state of the world

https://imgur.com/a/oyPzT

Puts things in perspective I think a bit better
>It's how we organize ourselves politically.

You're trying to re-install economic partitions at the national level which currently aren't there; "that's how we do things" isn't an argument. "How we organize ourselves politically" with respect to economics has been as an integrated global civilization since the mid to late 20th century.

If economic partitioning is an unqualified good, why not go much smaller than country scale? If it's not an unqualified good, what makes national borders optimal? Doesn't it seem a little bit suspicious that a country grown over hundreds of years of political wrangling just happens to the mathematically optimal economy size?