Gitlip Editors: Demo Launch 🌷
Gitlip is a collaborative coding platform, and today we’re launching the demo for Gitlip Editors - our take on collaborative coding environments.
If you've ever wanted to collaborate on Markdown or code with the convenience of Google Docs, our demo is for you.
@cakemakerjake I realized my name was Ephem over there, so I updated it to my full name when I saw this to make me easier to find, so should be visible in search now. Thanks for pointing this out!
Oh wow, rollup-plugin-preserve-directives is almost at 30k weekly downloads, it's probably time to make a stable release.. 🙄
I should probably add a pipeline and tests too, especially with all the new directives flying around, I just wish days had more hours.
Interested in how to host Infinite Git Repos on @Cloudflare? ⛅️
At Gitlip we’ve accomplished this using
- Cloudflare Workers
- Durable Objects
- @libgit2
- @nixos_org
- WebAssembly
- @emscripten
and now we’ve written about how we did it.
@alvarlagerlof This makes me want to add this function. What it would do is populate the cache entry with "🐟🐠🐡" as a helpful means of finding that you've made an error.
Would also take longer than usual, because fishing is about waiting.
@TkDodo Not only that, having "isomorphic" globals that are scoped per request on the server would also unlock moving a bunch of stuff off of context altogether. Imagine instead of having to do useQueryClient and pass that around, you could just import queryClient anywhere.
@sebastienlorber@pleunv@sophiebits@oljimenez Yeah, I can't decide if your example up top can accidentally break, or if it is accidentally working. Glass half full half empty kind of situation I guess. 😆
@pleunv@sophiebits@sebastienlorber@oljimenez Oh yeah, it only becomes a problem when it becomes a problem, like when your app is suddenly suspending at a level it didn't before. There are unexpected cases like an error happening on the server and that top level Suspense boundary is now used to retry on the client.
@pleunv@sophiebits@sebastienlorber@oljimenez Yeah. We had bug reports in React Query about doing:
const [queryClient] = useState(() => new QueryClient())
when there was a Suspense boundary above that. If that boundary was hit, a new queryClient was created.
Same with this promise thing: https://t.co/ATzO2R8Skj