8,592 karma · joined March 30, 2014
I see no evidence of this claimed misunderstanding in the linked article. And there's nothing "subtle" about it saying thought experiments lack value because they're contrived, that is the central point its making.
Your thought experiment postulates a pattern of matter that is identical to conscious matter but lacking consciousness. But the fact that you can imagine this does not mean it possible or even meaningful. You give no proof that such a distinction can exist.
"Consciousness" is a label humans apply to a pattern of matter that behaves in certain ways, in the same way "liquid" is a label we apply to a pattern of matter that behaves in certain ways. It makes no more sense to imagine a being that displays conscious behaviour but lacks consciousness than it is to imagine matter that acts identically to liquid but is somehow not a liquid.
In your example, if there is no observable difference between the supposedly conscious and non-conscious beings, then there is, scientifically speaking, no difference at all. They are both conscious, in that they both exhibit the behaviours that we call "consciousness".
If you hypothesise that there is a difference, then the burden of proof is on you to demonstrate it, via measurement — again, your imagination does not count — at which point we can use scientific enquiry to find out exactly how this difference arises. However, since the difference is measurable, it is part of the pattern of matter, and so the outcome of this process will simply be a more refined definition of consciousness.
But yeah, ultimately the pre-Corona model of London commuting, with basically the entire population of the city going into and out from the centre at the start and end of the day is not going to be feasible anymore, no matter what mix of cars, public transport, walking and cycling you have. But we should still try to achieve a mix than enables the best possible quality of life for everyone.
Complexity is emergent. Look below any complex system and you'll find a simpler one, but that doesn't mean the higher-level complexity is unnecessary. All the things you complained about have good reasons to exist, invented by people who actually work as professional web developers and need to solve problems.
The real problem is "seasoned programmers" who don't work in web development, but who expect to be able to jump in an master it in a day, based on the fact that they put together a GeoCities homepage twenty years ago, and are enraged and disgusted to find that things aren't so simple anymore. It's absurd. Developers wouldn't expect to be able to jump into kernel development, or database development, and find it to be a breeze.
Whenever I speak to someone working in a "low-skilled" job, I'm always astonished and embarrassed by how different their work environment sounds to the kind of offices I work in. There seems to be a consistent theme of employees being treated with suspicion, condescension and outright hostility.
This gets to the heart of the idea of "privilege", and why it can be so difficult to see yourself as privileged. Because it often involves nothing more than being given a basic level of trust and respect that, once you have them, can seem like a bare minimum, not something that you would need to fight for.
The article claims that the survival of the healthcare system in places that implemented a lockdown has nothing to do with the lockdown, but then gives no evidence at all to back up that assertion.
Therefore, from his perspective, the current lockdown is putting a huge brake on the progress necessary to help humanity and eventually reach utopia. Of course, more concretely, it also endangers his fortune and life's work, but people don't tend to like thinking of themselves as selfish to the point of acquiescing to mass death, so I imagine he rationalises his opposition to himself in this greater-good sense.
This is wrong. Naive React code is rarely fast in relative terms. This is because the whole design of React is not based on updating on the parts of the UI that have changed, but on re-rendering everything.
The whole concept of React, if you go back to the original "rethinking best practices" intro, was that Facebook wanted to bring the server-side practice of re-rendering the whole page for any change onto the client. This had the obvious advantage that, combined with normalised state flowing downward through the component tree, you would never end up with stale bits of UI, as everything would all always be kept up to date.
However, tearing down and re-creating the whole DOM for every single render was prohibitively expensive, so the virtual DOM was born. But, and this seems to get lost in a lot of discussions of React, VDOM wasn't some magical leap forward in UI rendering performance. It was a performance technique to make React's paradigm possible. Possible, but not inherently fast, because there is still a cost to re-rendering every component for every event. Any React developer who's had to add React.memo to half their components, and add visualisation to lists of just a few hundred items should know this.
Having written several substantial apps with both React and some of its competitor frameworks, I'm always amazed to see React-only developers continue to labor under the delusion than it is the fastest framework out there. It is not. Its paradigm is a beautiful one to develop with in most ways, but there is a significant price to pay in terms of performance.
"...scientific committees that advised Johnson didn’t study, until mid-March, the option of the kind of stringent lockdown adopted early on in China [...] The scientists’ reasoning: Britons, many of them assumed, simply wouldn’t accept such restrictions."
In order words, the scientists self-censored themselves on the basis of a political judgement about what the population would or wouldn't accept. But they weren't political experts, and weren't employed to be.
This seems like a big problem for basing policy on expert opinion. Most people are inexpert on most subjects. How do you ensure expert advice and decisions aren't contaminated by the expert's natural biases, and without it coming over as "stay in your lane" hectoring?
E.g. you have to make an element "display: inline-flex" to make it an inline flexbox. You can't just make it "flex" and have the parent decide whether it is inline, a block or whatever.
The consequence of this is that a parent component cannot properly layout a child component without knowing its internal layout structure. And if it doesn't don't know the child's layout (if its dynamically supplied for example) then it can't safely do anything with it. So long as this limitation exists, there will never be true layout encapsulation on the web platform.
For a while, the CSS Working Group planned to address this problem through the introduction of separate `display-inside` and `display-outside` properties. This would mean an element could specify its internal layout using `display-inside` while its parent could control its external layout using `display-outside`. Then, in their wisdom, they dropped it from the spec[1].
I mean, it's not like developing with encapsulated components is a popular approach on the web nowadays. It's not like many people are using React, or Angular, or Vue, or Web Components—the W3C's own goddamn multi-year effort to push component-based development—so why bother wasting time adding features that would help?
Step 1) "I don't like thing"
Step 2) "I really wish thing didn't exist."
Step 3) "Thing is probably dying/dead."
Step 4) "If event happened, it would really show thing is dying/dead."
Step 5) "Event can happen."
Step 6) "Event will happen."
Step 7) "Event is happening!"
Step 8) "Events 1, 2 and 3 can/will/are happening which forms a narrative proving thing is dying/dead."
Have you considered a career as a journalist?
It might sound crazy, but if a company is struggling to fill a position, offering a higher salary just never seems to enter the conversation. Instead you'll talk about working with a different recruitment firm, reformulating the job advert, trying to tap existing staff through a referral scheme, etc.
The only time I've seen salary seriously in the mix is when companies are going after a known individual who can make demands based on proven exceptional talent, or when looking for candidates with extremely niche skills.
By all means, upvote criticism that is properly argued and backed up with evidence. But upvoting these kinds of comments is the equivalent of posting anti-vaccination memes on Facebook.
The linked audio is only 9 minutes long, and it addresses this exact point. The Wikipedia figure for Canada is wrong. The straight acquittal rate is ~3%, but the other 97% are not convictions, only about 60% are.
They also interview a professor who authored a book on the Japanese justice system who explains why the conviction rate is so high. It turns out we can answer questions like this without relying on uninformed guesses by HN commenters. Amazing.