Deno might not succeed as a project, especially with strong competition from Bun as an alternative to Node, but I would say that Deno has been more a force for bettering the ecosystem than not.

Many of those at Deno, including Ryan as well as some of those who have apparently left or been let go have been major contributors to the web development ecosystem. Thank you all for your work — we’re better off for your contributions.

there should really be one header tag and its level should be based on some nesting depth

and don’t get me started on the maintainability mess that is z-index… better we have a system to centrally maintain an ordering list than a distributed one which only works reasonably consistently if you already know everything in the whole system

Even if you think the harms of AI/machine generated content outweigh the good, this is not a winning argument.

People don’t just consume arbitrary content for the sake of consuming any existing content. That’s rarely the point of it. People look for all kinds of things that don’t exist yet — quite a lot of it referring to things that are only now known or relevant in the given moment or to the given niche audience requesting it. Much of it could likely never exist if it weren’t possible to produce it on demand and which would not be valuable if you had to wait for a human to make it.

I don’t really understand comments like these. Even if you’re exactly right about how it should work, how would you make this happen in the world we live in? Neither the tech community nor ISPs nor cloud companies decide these things. Just because a matter affects us doesn’t mean we have much of a voice in it especially if it’s legal.

Laws about tech are decided by (idiot) politicians/parties/governments and the consequences are enforced by massive fines, imprisonment, etc. by law enforcement and selective (and often politically motivated) prosecution. In some of the worst places the consequences could include death.

Afghanistan just lost access to the internet almost entirely. China and North Korea are famous for their firewalls. Much of Asia has internet blackouts whenever there are large scale protests. The western world’s government has more legal jurisdiction/economic influence on the companies that run these things and are increasingly leveraging that for their desired censorship.

If the answer to this is democratic influence, the populations of many countries don’t really have that, the majorities in countries that do have it certainly doesn’t know or care about these things and wouldn’t vote for the pro-censorship politicians in the first place if they’d then vote to cut off their nation’s access to uncensored internet while preserving the uncensored variants, and even if the majority ever did care to get the system to work in this way there’s a global trend away from having their opinions on such things matter anyway.

I’ve both been rewarded for dissent from leadership throughout my career and had greater respect for and advocated more strongly for those willing to stick out their necks and disagree earnestly and productively when in leadership positions.

Dissent isn’t the same thing as sabotage. There’s healthy conflict and open disagreement which helps illuminate risks and gaps and uncover opportunities in productive ways and then there’s just stirring the pot or trying to tear things down without bringing alternative proposals to the conversation — being unwilling to contribute in positive ways if you don’t always get your way.

The latter kills the ability for the team to work well while the former is key to allowing colleagues bring insights and value to the team

Most readers won’t notice the difference or disregard it as meaningless and if you have to explain to everyone your position on a matter of communication it’s likely that you are the one who needs improvement with respect to your communication, not the rest of the world.

https://github.com/tc39/proposal-pipeline-operator

It would make it possible to have far more code written in the way you’d want to write it

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

This is also widely known as WTF-16 (seriously, look it up!)

They also denied that she’s part of some well defined class for a class action. It’s not like they are saying there’s some other court she can go to.

US courts are generally infamous for denying justice whenever they see fit using technicalities like “standing” and other procedural grounds.

Environmental law violations, illegal surveillance programs, civil asset forfeiture like here, and constitutional violations are quite often practically impossible to get courts to address, especially if parts of the US government are the defendant.

React could be argued to have abandoned the fight for being the best client side framework technically (though they have dominance pragmatically). They are really all focused on Vercel’s Nextjs/SSR/SSG/RSC stuff in recent years

I’ve seen far larger messes created in redux due to tight coupling of things across large apps to a global store and the inability to work with things like Maps and Sets or other values that are not trivially JSON serializable.

In the other direction I have seen messes with observable-based state management systems where things become far more complex and too far abstracted (how often do you really care about anything other than the latest value and maybe the previous one?) or with proxy based systems that have too much fragile magic (valtio, mobx) or require wrapping your components and going all in on oop (mobx)

To me signals hit the magic spot of reactive without being overkill and keep code testable in smaller units while retaining performance benefits of surgical updates

I like xstate in theory — it’s a good way to think about complex state transitions — but in at least half of cases in practice where you aren’t interested in a derived value, someone is storing a value/ getting the latest value or toggling a boolean and it’s just such overkill for that. The reducer pattern itself doesn’t meaningfully show up much for similar reasons. The other common cases are with fetching states (idle, loading, refetching, success, error) but you often end up wanting things like cache management or maybe even optimistic updates so eventually tanstack query covers that ground better than rolling your own.

Jotai, mentioned briefly in the article, may not be built in but is as intuitive as signals get and isn’t even tied to React as of later versions.

I’ve very rarely met a state management problem in clientside state management where neither tanstack query (for io related state) nor jotai (for everything else) are the best answer technically speaking. The rare exceptions are usually best served by xstate if you want to model things with FSMs or with zustand if you actually need a reducer pattern. There’s a tiny niche where redux makes sense (you want to log all state transitions or use rewind or are heavily leaning on its devtools) but it was the first to get popular and retains relevance due to the fact that everyone has used it.

You can go a long way with useContext and useReducer/useState but few would opt for alternatives if jotai came batteries included with react.