The subject this post names, from the same vocabulary
the directory files beliefs under, and the word it uses that this site has seen
least often elsewhere. Posts are matched on those words alone —
nothing here is a summary of this one.
the jev release is giving react major version drop vibes. just a massive crashing wave, everyone rethinking fundamental stuff and thinking through the implications of a novel new primitive.
Domain experts consistently underestimate how quickly AI can master their field and surpass them, because they mistake human difficulties for universal difficulty.
I do not think those running the government testing understand what is going on, and believe they are reacting basically on vibes and what various trusted people tell them.
I long for the halcyon days of early Web 2.0 when it was predicted that all APIs would work with everything and data and control would belong to the user. Oh well - that didn't happen.
And yet, life expectancy about two years more than the national average is rather common in rich regions with selective migration, even in European countries with even access to health care, like France and Spain.
We have universal access. What we are trying to do is bring universal learning. So there's a vast disparity in how much kids learn during that 12 years that while they may have access to it, learning is very different.
Technologies from our community - CRDTs, sync engines, universal version control, and good old-fashioned open protocols and file formats - can give a nation more independence and control over its own critical software infrastructure.
the the breakthrough for us was realizing that AlexNet was not AlexNet. That AlexNet was an approach with deep deep learning that allows you to learn any function.
What this process can now do in creating understanding of the timeless and universal cause:effect relationship and enhancing and systemizing whatever one is thinking is mind-blowing. I believe that you will either stay at the cutting edge of doing this or you will be uncompetitive.
Like right now we're endowed with labor that can turn into uh that can turn into income. When that is no longer the case and we are now at the mercy of the of the elected official for like basic needs, right? So that to me feels like a power sharing arrangement that's really dangerous.
So, here I actually think it's even stronger. The thing with C++ is that if you make a mistake, right, in in JavaScript, maybe you take down your server, which is already bad enough, but in C++ when you make a mistake there, now it's actually a security vulnerability most of the time.
So that's unfortunate, and that's why some environments like Go, for example, has has Go routines and green threads, which are really language emulated lightweight threads that kind of do what I'm talking about, but but at a much lower cost. But you avoid the function coloring. So there is a bunch of different things, but but you know, but for an environment that already exists like JavaScript or like C# and and the Windows event loop and and whatever, this this was the right solution.
And we we full well knew that there was absolutely zero chance that we would appeal to the JavaScript ecosystem with a proprietary programming language licensed from Microsoft. No. No one was going to come. It had to be open source. There was just no two ways about it, right?
So, if we're checking 99% instead of 100%, well, heck, that's better than the 0% that JavaScript checked, right? And it gives you like language features that no other languages can provide because they can't get to 100%.
As the software industry is largely driven by trends and fashion, React's "cool factor" led to a mass amnesia regarding how to make normal, well-designed web apps made of HTML with a sprinkling of scripting on top and everything became one big tangled, brittle mass of Javascript that completely keeled over when scripting wasn't available.
none of us wanted to go through that extreme but lots of time when you are under a lot of pressure and no time to react other than just to survive that scale that keep on coming at you, you have to make uh decision that increase uh speed and velocity because speed and velocity allow us to build quick enough to survive
The internet is unique in the history of technology because there’s a list of things it improved (communication, access to information) but another list of things it likely made worse for almost everybody
To be clear, speed in itself does not mean labor markets and employment won’t eventually recover, it just implies the short-term transition will be unusually painful compared to past technologies, since humans and labor markets are slow to react and to equilibrate.
elements, JavaScript reigns supreme. SvelteKit's efficiency and reactivity make it my framework of choice, and TypeScript's type annotations bring a welcome layer of confidence to my codebase.
Including things like universal basic provision or something like that where a lot of the increased productivity gets shared out and distributed to society and maybe in the form of services and other things where if you want more than that, you still go and get some incredibly rare skills and things like that and make yourself unique. But there's a basic provision that is provided.
I used to think it required more churn to get progress to stay on the leading edge of new stuff. And I wrote this before I experienced the indignity of the 2010s in the JavaScript community.
the text embeddings across LLMs appear to largely converge on a "universal geometry" despite differing architectures, parameter counts, and training sets.
But the metaverse and 3D gaming in general needs something that's rather more powerful, more safe, more scalable, and more capable than JavaScript because the metaverse is actually a more difficult technical problem than a webpage.
As a Python and JavaScript programmer my favorite models right now are Claude 3.7 Sonnet with thinking turned on, OpenAI’s o3-mini-high and GPT-4o with Code Interpreter (for Python).
And Friedman advanced a policy that was really abstract and really it was devoid of judgment. It was pure and beautiful in that way but utterly impractical.
So, I think she comes back in to relevancy in a different way than Friedman does, because I think in some ways she's tapped into a more universal human longing for independence and autonomy and self-creation and self-discovery.
I think it's always going to be hard to pull off because I think Americans and their elected representatives don't want to provide a universal benefit. They want to provide a targeted benefit because they believe there's a moral component here.
Before this book I used to think that Javascript is "bad" or a "hacky" language. This book changed my perspective, understanding some tradeoffs and some remarkable strengths of this weakly typed language that is starting to take over the world. Note that this book is now dated
when you send someone a link to a post, they can't read it without loading the entire Mastodon frontend app into their browser, which will is a monster React codebase that will break if they have scripting disabled and also can take up to 30 seconds on older hardware.
I think life obeys universal principles. I think there is some deep underlying explanatory framework that will tell us about the nature of life in the universe and will allow us to identify life that we can’t yet recognize because it’s too different.
My hot take is that JS has the lowest bar of entry to building and being productive (a good thing) but one of the highest bars of any language and stack to building high quality, stable, and reliable software. Very few devs have the expertise to pull off the latter
Yeah, it is interesting because, when people react against you by saying you are being arrogant about this, 99.999% of the time, all they mean is I disagree. That’s all they really mean, right?
One thing that drives me crazy about the React ecosystem, and more specifically "tech influencers" and "thought leaders" in the space, is the infantilization of the developers using and working in it. I’m tired of reading takes like TypeScript generics, mapped types, etc should only be needed and used by library authors for most use cases. Or today’s discourse; Don’t use `useCallback’, ‘useMemo’, and React.memo. If you’re building anything beyond a simple CRUD app or a an incredibly focused app with few features, you _will_ need these features.
You can make survival guaranteed without UBI. What you have to do, is make housing and food dirt cheap. Right? And that’s the good world. And actually, let’s go into what we should really be making dirt cheap, which is energy.
RSC is the future of React. The React team has made this very clear and we are lucky to be in touch with their amazing team members to help us along this path.
I have argued that the probability of a bad equilibrium is only marginally influenced by the level of debt, but can be much reduced by a contingent rule making the primary balance react to an increase in debt service.
Multipliers are likely to vary a lot over time and space, but the bulk of the evidence is that they are different from zero, positive for spending, negative for taxes, and that they are stronger when monetary policy does not or cannot react to fiscal policy.
The analysis in
this chapter has shown that there is no such thing as a universal threshold over
which debt becomes unsustainable, and that the relevant debt level depends
on many factors, in particular the real interest rate on debt.
What what I find generally is if I don't understand something, I I try to read backwards and and and kind of the further back back I read, the more universal things I find. And the more things that I think are kind of remarkable and unique to our era actually turn out to be quite universal.
Did you know, the tests you write with react-testing-library look almost identical to the tests you write with vue-testing-library. Magic things happen when you don't test implementation details. :)
Visual Studio Code is the go-to editor for some complex languages like React using JSX or TypeScript and I finally agreed with Wes Bos that VS Code is better for development of React JS.
JavaScript allows us to mask network latency altogether. Applying this as a design principle should even remove most spinners or “loading” messages from your applications.
For text editing that is not specifically related to programming the Mac and iOS, I rely heavily upon BBEdit, where I do most of my Python, HTML, JavaScript and PHP editing.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.