pavel retweeted
Agents reinvented how we produce code. It changed our tools and half of our workflow. It’s time for the other half to catch up.
Today, we’re shipping Entire: the Git forge for agent-human collaboration. We’ve built @GoEntire using Entire. Now we want to see what you'll build with it.
Here’s why and what’s different. 🧵
pavel retweeted
Performance matters most in the age of cloud agents. With Entire-Native branches, agents can continue pushing code even during an upstream outage. 🏃entire.io/blog/entire-dispat…
pavel retweeted
Git your clones ready. Marvin guides us into a new multiverse of coding soon. Let the rebellion begin. 🤖
pavel retweeted
In 2007, Linus Torvalds said "If you're not distributed, you're not worth using." For Git hosting to sustain through the era of agents, we must now return Git to its original promise: Decentralization. My thoughts 👇
entire.io/blog/how-version-c…
pavel retweeted
friction is when learning happens. if you hunt for removing all friction, you are unlikely to learn.
it's easy to remove tons of friction using agents. but when you and your agent inevitably hit a wall, the friction you now face is no longer under your control.
pavel retweeted
Node.js now has the ability to directly run code with TypeScript types!
github.com/nodejs/node/pull/…
Current limitations:
- Experimentally flagged
- No transformations (enums, namespace, etc...)
- No .js extension for .ts files
- No running TS in node_modules
pavel retweeted
# on shortification of "learning"
There are a lot of videos on YouTube/TikTok etc. that give the appearance of education, but if you look closely they are really just entertainment. This is very convenient for everyone involved : the people watching enjoy thinking they are learning (but actually they are just having fun). The people creating this content also enjoy it because fun has a much larger audience, fame and revenue. But as far as learning goes, this is a trap. This content is an epsilon away from watching the Bachelorette. It's like snacking on those "Garden Veggie Straws", which feel like you're eating healthy vegetables until you look at the ingredients.
Learning is not supposed to be fun. It doesn't have to be actively not fun either, but the primary feeling should be that of effort. It should look a lot less like that "10 minute full body" workout from your local digital media creator and a lot more like a serious session at the gym. You want the mental equivalent of sweating. It's not that the quickie doesn't do anything, it's just that it is wildly suboptimal if you actually care to learn.
I find it helpful to explicitly declare your intent up front as a sharp, binary variable in your mind. If you are consuming content: are you trying to be entertained or are you trying to learn? And if you are creating content: are you trying to entertain or are you trying to teach? You'll go down a different path in each case. Attempts to seek the stuff in between actually clamp to zero.
So for those who actually want to learn. Unless you are trying to learn something narrow and specific, close those tabs with quick blog posts. Close those tabs of "Learn XYZ in 10 minutes". Consider the opportunity cost of snacking and seek the meal - the textbooks, docs, papers, manuals, longform. Allocate a 4 hour window. Don't just read, take notes, re-read, re-phrase, process, manipulate, learn.
And for those actually trying to educate, please consider writing/recording longform, designed for someone to get "sweaty", especially in today's era of quantity over quality. Give someone a real workout. This is what I aspire to in my own educational work too. My audience will decrease. The ones that remain might not even like it. But at least we'll learn something.
pavel retweeted
Telegram is notoriously insecure and routinely cooperates with govs behind the scenes while talking a big game about speech and privacy. Even their limited opt-in (roll their own) encryption is sus. The more you know 🌈
pavel retweeted
By the end of 2024, you’ll likely never need these APIs again:
• useMemo, useCallback, memo → React Compiler
• forwardRef → ref is a prop
• React.lazy → RSC, promise-as-child
• useContext → use(Context)
• throw promise → use(promise)
• <Context.Provider> → <Context>
pavel retweeted
Zed is now open source!
Our mission is to revolutionize developer collaboration, building the world's best code editor in the process. After working together in Zed as a small team, it's time to scale up to transform Zed into a collaboration platform.
ALT There's room for many more Zed contributors!
pavel retweeted
REACT!
Just got caught up on all the posts 😅
I'm near the top of the list of people who could justifiably complain about how they've handled communication, community, and technical details of the project
But I'm not going to 🤗
With a spotlight as big as theirs, you're gonna find some warts--real and imagined--as you would with anybody
imo React is still the best rendering library for the web and the people behind it are just doing their best, and actually doing a great job
Fighting against it is going to set the web back a few years if you're successful.
React has been been leading the pack for a decade now because it keeps raising the ceiling for UX with wonderfully encapsulated abstractions. Denying this is silly because every alternative looks exactly like it now
They're doing it again with RSC, as part of the work they've been doing for several years that's finally coming to fruition.
RSC is a solution to many problems most developers don't even know exist, that's why many people think it's "too complex of a solution" for the ones they do understand.
As a framework author (and web developer since before JavaScript was created) I see them as absolutely revolutionary. If you can't acknowledge this, I'm not sure you've spent enough time on the front or back end of the stack of successful products with varying audiences.
Yeah, the React team has fumbled the ball a few times in the last few years, most especially by accidentally torching relationships with prominent members of the community who didn't go work at facebook (I'm not alone, I have many DMs) and then accidentally coupling to Vercel
But they're fixing this in earnest, and none of it was malice (I'd say just incentives)
In the near future you're gonna feel like a kid in the candy store again building with React and we'll all be posting cool stuff we're doing instead of complaints, like it's 2014 all over again 🎉
pavel retweeted
Announcing React Aria Components v1.0.0! 🥳
Over 40 components with built-in behavior, adaptive interactions, top-tier accessibility, and internationalization out of the box, ready for your styles.
react-spectrum.adobe.com/rea…
pavel retweeted
> I don't know what the mode would be for Server Components if not SSR
Perhaps, instead, we discuss what things render to:
Server Components render to an "RSC Payload" (JSON-like) that contains the rendered result of server components, references to client component rendering instructions in the JS bundle, and any props that should be passed to Client Components when they are rendered). Initial and subsequent navigations receive this payload (notice, no "SSR" so far).
The optimization step (which I begrudgingly call "SSR") takes the RSC Payload from above and renders the Server Component parts AND Client Components (using the references and props) to a dumb HTML string. This is purely optional: everything would work without this step, except you wouldn't see anything while the app booted up on the initial load. The term "SSR" in the context of React, is nothing more than a screenshot of the first frame of what your React-powered app will eventually look like. The term "SSR" outside of React is doing any work on the server.
Rendering to the RSC Payload can happen at build time, during revalidation, and runtime (initial load and subsequent navigations). Rendering the RSC Payload and Client components to HTML can happen at build time, during revalidation, and runtime (initial load only).
pavel retweeted
We wanted to show the performance and the insane power of the Static Hermes native FFI. But we don't yet support the all language features needed to compile React Native (soon though!), so we improvised.
We imported the bindings for DearImGui (a popular C++ imperative game UI library that renders meshes), and Sokol (an amazing lightweight 3D backend in C) and wrote a small demo.
"Imperative UI" means that the entire UI and the state of the screen is recreated on every frame, which suits our purposes to demonstrate SH very well.
The demo runs 100% compiled native code. JavaScript runs in every frame and recreates the entire state of the screen. It is portable to all platforms, though the screen layout is not optimized for phone.
We wrote the demo in C++ and in JS, to compare, and they both ran with the same performance.
In the attached videos you can see the demo running at the stable screen refresh rate - 120Hz on my Mac, 60Hz on a old Moto G5 phone.
It includes some widgets, an n-body simulation of planets, a playable game demo, etc.
pavel retweeted
@patrickc on Stripe:
“My intuition is that more of Stripe success than one would think is down to the fact that people like beautiful things and for rational reasons.
Because, what does a beautiful thing tell you? It tells you the person who made it really cared, and you can observe some superficial details, but probably they didn’t only care about those and did everything in else in slapdash way.
So, if you care about the infrastructure being holistically good, indexing on the superficial characteristics is not an irrational thing to do.“
Couldn't have said better and proud to have Patrick as an investor in @linear.
We shouldn't accept poorly made things and that lack beauty.
