fat

7 ms·

1.
by fat 4mo ago
lmao - thank you!
2.
by fat 7mo ago
Sure – our API is built specifically for common LLM workflows. Here's a great example. LLMs are often used for changing code. If an LLM creates a patch that touches 10 files, you need to take the following steps to save that patchfile
3.
by fat 7mo ago
Git is ~ really ~ great at document storage :P We have folks using us to back crms, design tools, and all kinds of "non-code" stuff. Please reach out - would love to connect!
4.
by fat 7mo ago
To be fair to GitHub (which i have a lot of love and respect for), we're building very different products. GitHub is a social consumer coding product first. There's user models, review and discussion primitives, ci, etc. Code Stor
5.
by fat 7mo ago
We're actually meant to be less of a consumer product than i think you mean by this (but i may have misunderstood). We're more targeting enterprise as storage infrastructure provider – selling directly to platforms who generate a
6.
by fat 7mo ago
thanks for the feedback – we definitely have work to do on communicating what we're up to. Sorry about the audio - will get that patched
7.
by fat 7mo ago
Ahh good question… Here's the timeline if you're interested. 3 years ago we started building a direct competitor to GitHub with the theory that you need to build code storage, code review and CI to truly compete. We spent about a
8.
by fat 7mo ago
planning to share more in the next month or so :) But have been slowly signing folks up – if you want to shoot me an email, can get you setup jacob@pierre.co
9.
by fat 7mo ago
pretty much - low friction git* repos for massively parallelized agentic use. (can think of it kinda like what stripe does for payments… headless git infra, where you get an api key, and store / create as many repos as your customers n
10.
by fat 7mo ago
Hey everyone, Wow, you scooped us! we weren’t really expecting to launch here just yet, but happy to answer any questions y’all have :) First, Pierre is building code storage for machines -- think GitHub’s infrastructure layer, but API-firs
11.
by fat 7mo ago
not open access yet, sorry :(
12.
by fat 11y ago
haha <3
13.
by fat 11y ago
all upgrades will be free, once v4 is stable :)
14.
by fat 14y ago
fwiw, we generally just try to do what the language does: border-radius <- css dashes document.createElement <- js camel (except constants, etc.) etc…
15.
by fat 14y ago
I'll probably write up something at length about this decision when/if it happens… but this is the current thinking: CSS transitions are just total shit to deal with in javascript. What people often don't realize is that there is an event f
16.
by fat 14y ago
yep, twitter has been great. And mark and i didn't leave to start a bootstrap support company :P
17.
by fat 14y ago
ha, well that is definitely not happening anytime soon… but, here is a whole thing on "why less" I wrote up about it a long while back, and it still holds true today: http://wordsbyf.at/2012/03/08/why-less/
18.
by fat 14y ago
haha! mark loves these, i think he started doing them way back at zurb. we took them away because they are hooorible for perf – and were exposing a memory leak bug in chrome i believe
19.
by fat 14y ago
hm… sorry it came off that way. :( fwiw, the amount of technical things i've learned from working on bootstrap is not proportional to the amount of work i've put into this project… at all. But, i never expected it to be, and that's totally
20.
by fat 14y ago
yep, lots of legal hurdles to go through – took us like 6 months – but now they have a full time opensource shepherd @cra which makes this much smoother
21.
by fat 14y ago
aww <3
22.
by fat 14y ago
right now it's under the Apache License v2 – but we're working to move it to MIT for 3.0.0 I think of the community as owning bootstrap at this point… maybe that's cheesy? Or naive… I also think twitter played a larger roll than just hardwa
23.
by fat 14y ago
Mark and I built bootstrap while we were employed at twitter on twitter hardware. Also, undeniably it was largely influenced by our work there (and later would largely influence a lot of the code at twitter as well as power lots of projects
24.
by fat 14y ago
awesome! This is exactly what we were running into too :D
25.
by fat 14y ago
aww no problem :) Hope it's useful!
26.
by fat 14y ago
why would you name something after an already successful project with the same name. face palm
27.
Coffin: The Skeleton Drawer by fat(github.com)
1 points by fat 14y ago|0 comments
28.
by fat 15y ago
this was switched up a bit today. That said - for the ladies out there - girls can be bros. total bros.
29.
by fat 15y ago
yeah we felt the same way, but we're trying to move off of mustache.js for performance reasons (also for size in our new tweet embeds projects).
30.
by fat 15y ago
lol sorry, i'll take the blame for that. The link was originally just a placeholder for our awesome designer @dhg (who rocked the site in like an hour). I missed the link before it got pushed, and forgot to swap it out. When first published

More ›