Sabitlenmiş Tweet
What if instead of self-driving trucks we had direct lines between common shipping locations so traffic coulDAMMIT I invented trains again.
English
Alex Sexton
25.4K posts
Alex Sexton
@SlexAxton
Fun and cool/strong — onions are my own. Eng @pierrecomputer – prev @stripe @jquery @yayquery
Austin, TX Katılım Ocak 2008
1.2K Takip Edilen31.8K Takipçiler
@jlongster this is also how @fat operates. great minds, i think/hope!
English
Remember last week when Dax asked what feature we’re shipping this week? this was it
And he just publicly committed me to ship worktrees next week, lol
Dax is no longer ceo or devrel, he’s a product manager
(it’s good to have goals)
dax@thdxr
what pushed us to finally implement it is heavier use of worktrees now that i have sessions going across different worktrees very annoying to find them and open my editor in the right spot we'll ship the worktree feature out from the flag next week
English
@jtaby @cnakazawa he was the first one with CodeView access I think!
English
Codiff v0.5:
* UX/UI/Diff Improvements
* Extended the git markers the CLI understands
* Happy to report the original diff that Codiff was created for has been reviewed
brew install --cask nkzw-tech/tap/codiff
github.com/nkzw-tech/codi…
English
English
Come build @Flighty.
We need a 2nd product team. Must be elite-level.
- Sr. designer
- Sr. iOS + backend engineer
DMs open. Include work.
flighty.com/careers
English
@pierrecomputer @amadeus @mdo dang, this is my first time seeing this image but im glad my height and strength are accurately represented especially as compared to mdo and amadeus. 🙏🏻
English
PRIMITIVES
the team behind
diffs[dot]com || trees[dot]software || diffshub[dot]com
Pierre@pierrecomputer
diffshub[dot]com Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component. To try it out, replace `github` with `diffshub` in your address bar.
English
@devinjacoviello @fat @amadeus @necolas @mdo feels like we gotta accidentally end up in town again soon fyi
English
IMO what @amadeus, @SlexAxton, @necolas, and @mdo built here is probably the most impressive frontend browser feat i've seen since the figma editor.
not particularly close
Pierre@pierrecomputer
diffshub[dot]com Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component. To try it out, replace `github` with `diffshub` in your address bar.
English
@damageboy @jtaby It’s just requesting a patch file directly from GitHub for the demo, everything else is client side.
#codeview" target="_blank" rel="nofollow noopener">diffs.com/docs#codeview
English
@SlexAxton @jtaby Is there a guide on seeing this up for private repos, or just point an LLM and pray?
English
i try to only work on software where i can answer “yes” to the question “will it sandstorm?”
Pierre@pierrecomputer
diffshub[dot]com Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component. To try it out, replace `github` with `diffshub` in your address bar.
English
@birch_js @pierrecomputer that's pretty much the patch size plus the html for the syntax highlighting. always places to improve but on the big boys that's about what i'd expect. safari is the hardest for sure, at the moment.
English
Memory usage in Safari:
- on page load: 892 MB
- after scrolling the entire document: 1,470 MB
That may be justified, though? Depends whether it's an actual leak or just the cost of keeping things in cache so that you can scroll back and forth. CC @pierrecomputer
English
I tried out DiffsHub on Safari. No idea how Twitter is gonna compress this .mov, so here goes nothing.
It's pretty dang good. Some noticeable stuttering when there's both additions and deletions side-by-side. Still absolutely wipes the floor with GitHub, of course. Bravo! 👏
Pierre@pierrecomputer
diffshub[dot]com Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component. To try it out, replace `github` with `diffshub` in your address bar.
English
Ah yea, I guess what I mean is that the thing we're showing off here is our open source components. This isn't really a product we expect people to use directly (the comments aren't stateful, etc).
The hope is that all of the actual players in this space use trees and diffs from us to render so that everyone can be fast in the tools they know and love. (Diffs is already in a ton of the coding apps, codex/conductor/opencode/etc)
I think more folks will adopt the pattern! It's certainly possible with the primitives today!
English
@SlexAxton the problem is you need a PR on GitHub to access that state, but I need to iterate deeply with the agent before the PR exists
English
@dalmaer my honest guess would be if promised to never let anyone use this (the opposite)
English
What is the best way to get Safari to implement HTML in Canvas? Maybe this?
Andrew Prifer@AndrewPrifer
Dear frontend devs and UI designers. I bring you Liquid DOM, a complete and faithful implementation of Liquid Glass on the Web. - Shape morphing - All properties animatable - Dynamic refraction and reflection - Adaptive tint - Adaptive specular highlight - Dispersion - Full html integration - Super fast layout engine that works across Canvas and html - Pointer event handling - Framework and renderer-agnostic low level API - High level React API - Ootb @threejs and r3f integration And lots more. Read on for implementation details and demos.
English
the world needs an italian american nj based super hero that defeats enemies (fuggin jerkawfs) with a pizza peel
English
@bedesqui @pierrecomputer i'll add you to package.json authors rq
English
hey @pierrecomputer , i just found this from november last year.
just saying, i think i independently arrived at diffs before knowing yall were working on it!!!!!
English
im starting to understand more and more what this company is doing and where it's going and im liking it
Pierre@pierrecomputer
diffshub[dot]com Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component. To try it out, replace `github` with `diffshub` in your address bar.
English
Such excellent software coming out of pierre. Really interested to see their final product.
Pierre@pierrecomputer
diffshub[dot]com Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component. To try it out, replace `github` with `diffshub` in your address bar.
English
@brotzky @pierrecomputer *please be good* *please be good* *please be good*
English
i should write about the stuff @pierrecomputer is doing 🤔
Pierre@pierrecomputer
diffshub[dot]com Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component. To try it out, replace `github` with `diffshub` in your address bar.
English
@rawkode @mitchellh on github, it's both! with faster tools, it's *just* comprehension.
English
@mitchellh Nonsense. The problem with code review isn’t speed, it’s comprehension and this doesn’t increase that at all.
AI makes PRs bigger, and you’re smart enough to understand that reading a large PR quicker doesn’t solve anything.
English
This is how performant PR review could be. On any forge. Pierre is showing us that the only thing holding that back is a skill issue. Excellent ship here! They’re on fire!
Pierre@pierrecomputer
diffshub[dot]com Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component. To try it out, replace `github` with `diffshub` in your address bar.
English
we agree. i think the goal of this tech demo (fully just a demo, doesn't store state, etc) is to show off the open source components we offer and show that they won't be a bottleneck for whatever you're cooking. i certainly don't have any interest in reviewing anything this size, but also have hit many PRs in github that I *did* want to review that it couldn't render. The goal was to show the gap.
English
@mitchellh this is super nice as a tech demo. but no one reviewing that amount of code.. not in a scrolling manner. hopefully not at all.
English