korla

You are correct, there are ways to do so. There are also soft-locks which are states which are just incredibly hard to get out of (heat death of the universe type scenarios some times). Pikasprey yellow is one youtuber who chronicles things in that area.

But I think the commenter above meant that Pokémon was a game which was possible to complete in a twitch plays style because it doesn't result in game over like an FPS or platform we would for example.

Further: e: dialectal version of "det", i.e. "it" öa, åa: adding an a on the end of a noun is a dialectal way of expressing "the 'ö'" and "the 'å'", respectively.

Isn't the point that companies should be judged by the cost of their actions, and not the details of their implementations?

I think developer speed is more important than optimising clock cycles unnecessarily. Generally writing to dom is much much slower than evaluting a few thousand expressions.

For the cases when it's not, use memo.

My reaction as well. I remember leaving for Google as a huge step in my childhood.

I still recommend Name of the Wind. It's frustrating, but I would rather have loved and lost, than not loved at all.

Killing flash was not about UX. The issues with it were technical.

Flash was not the UX for systems, but for fun little games and a means to tell a story in a way which wasn't available on the Web 20 years ago. This UX is fine as it is IMO. Cool even.

DICOM is also the format used at hospitals for medical images. At least in radiotherapy.

I read it as: Svelte is faster in theory, but since people write bad Svelte code, it is slower than the React code the same developers would write.

My interpretation is that this can be attributed to either svelte being hard to write, or people being used to React. Both of which are a challenge to companies looking to switch to Svelte.

I agree, and the competition is at this point more between VS and other full-featured IDEs like JetBrains Rider, which is my tool of choice for .Net-development.

But, what I didn't know until this recent debacle, is how there is a theory that the reason the .Net-tooling in VSCode is so bad is the same reason we had this watch-debacle. There was some discussion on that in the other HN-thread: https://news.ycombinator.com/item?id=28968231

When I studied philosophy, we applied scientific methodology to understand complex topics, categorising them, and evaluating them against each other. The theories of moral philosophy are under scrutiny in a way very similar to the (other) natural sciences.

I think you're equating the pro-mask side with some pro-science side. None of which has to do with the validity of science, or what truth is. You're talking about politics.

What alternative methods do you suggest for the "domains it doesn't fit"?

When you can't measure what's important, what you can measure becomes important.

For me the biggest selling point is that the content I like is on YouTube. Everything else I can do without.

I consume it through their RSS, which is nice, I suppose.

I'm guessing here, but perhaps that is since apple revenue isn't ad-driven in the same sense Facebook is?

Hate speech is when you promote violence or persecution in some other way against any of the groups you mentioned. I am not sure what point A has to do with what hate speech is.

That is not what I am discussing. I am making a statement about how to design a stable society with humane values. From the perspective of the society. Instead you went to make judgements about my personal beliefs.

I believe you are conflating the definition of minority in this context. It means a disenfranchised portion of the population.

Are you suggesting it is not in a society's interest to limit hate speech against minorities? Because that is what is being discussed.

I think you vastly oversimplify how easy this fix is likely to be. For all we know this may mean touching code in multiple repos, each with hard-coded lists of which cards are supported for some case or another. At least that is what it would mean to change something like this where I am now.

If the technology is too hard to understand for the masses it's unlikely to provide much resistance to desinformation campaigns.

You're still off quite a ways in your analogy. I get paid to develop software that someone else owns and brands and makes all decisions for. For nothing more than money. It's nothing like my passion projects, which I do not get paid for at all. Most of the time. Maybe 1 in a 1000 that I will get paid for them in any meaningful way.

No, it might indicate a lack of demand for that particular qualification.

React has no invented language. You’re thinking about jsx which isn’t needed. It is recommended, however.

All of these (except 3) also get solved by moving dependencies to a hosted npm registry. Something which has been suitable for some projects I’ve worked on. And keeps ’git clone’-times down.

It absolutely is. It is in fact, one of my preferred ways to design systems when doing it in tight coupling between backend and frontend. Such as in a micro-fronted-style vertical. It’s very effective when the needs of the frontend dictate the needs of the backend.

I have to ask who pays for these systems? Is it the end user, or some business person in an organization?

In the latter case, the product is aligned with the need to sell the system, since the person who pays doesn’t use it.

If so, I recommend a consumer-facing job the next time you chsnge.

Aren't you just moving the client to the backend here? As I understand it we are talking about how whoever needs to render the data gets the data. GraphQL vs. REST vs. whatever is still as relevant in the backend-rendered case.

Don’t eject. The point of CRA is to abstarct away the current way to set up the build system. Instead let the guys behind CRA tune it, handle upgrades, etc. in complex projects the time spent configuring webpack and keeping versions in sync is quite severe. CRA lets you sidestep this. Somewhat.