LLMs are also good for this; point them at your repo and ask them to do a fresh install and note all friction. One time when the lack of context really helps.
Thank you for pointing this out! I always love a good competition and since I already have a workers paid plan it seemed fun. But I'm not eligible, so I guess I'll rebuild github without giving any IP to Cloudflare
I really wanted to like using a Macbook. I've given it a go a few times, amazing battery life and great build quality.
But I can't get over how it locks you down completely software wise. I wanted a sane WM and tried skhd and yabai. They are a collection of hacks on the accessibility API, and they will break whenever Apple decides to. To me that's unacceptable as a daily driver
README is very bare bones, needs a video or a picture too. The website should tell you some more things: https://kavla.dev (and now the demo does not require a login (also need to remake the demo to fit the new self hosted version))
It's still lacking an analytics agent for the local version though. I've explored using codex CLI, but it feels like its extensive system prompt cripples the agent a lot vs Kimi 2.7 that I've been using in the cloud version.
I think it would also be nice to lean into the fully local LLM setup too, especially for data that shouldn't leave the device.
Hard disagree. Sure their docs are bad, and it's sometimes buggy. But to me cloudflare is actually innovating and trying to offer "new" infrastructure. Durable objects and workers are super cool. R2 has free egress, isn't it insane that they could pull that off?
If what you want is a VM to run postgres then there are other offerings that would be much better.
Not saying they aren't evil though, they probably are, but the infra stuff is cool.
I disagree with your disagreement. I wrote the post and I am not blaming the innovation. I am blaming the chaos of innovation. Everything feels DISJOINTED.
The innovation is useful, the delivery of the innovation is the pitfall here.
This stance is a breath of fresh air. In my experience change management is the first thing to slap on when a bad release happens.
I've worked at a large enterprise that have a "Change Advisory Board", that you need to convince when you want to bump the major version on your linter. It has the effect of velocity slowing down to a crawl. Changes have to large, since otherwise it wouldn't be approved by the CAB. A slow mess.
At my current place we have to loudly declare "I CONFIRM COMPLIANCE" in every PR description. I'm not sure that anyone knows why, but it keeps the bureaucrats happy. Shrug
My favorite thing about CABing things that shouldn't be CABd is that it then bunches up changes that all happen at the same time... after the CAB meeting. Now if something breaks, it could be any of the dozens of things that just got pushed in the 15 minutes after the meeting.
10 years ago I rode my bicycle from Connecticut to Central America. I stayed in Antigua for a few days to just relax and reflect. Thanks for bringing those memories back!
I've worked on it for about a year, with 1700 commits. I've been going back and forth if I should just open up the canvas or also the multiplayer experience.
I've always had the dream to make some money from a side project, but I don't think this one is it, so I'll just make the entire repo public. Just want to clean up some stuff first.
Lots of fun tech used: duckDB WASM, Cloudflare Durable Objects, tldraw and pocketbase
The landing page is teasing. Then I clicked 'Open a Canvas', expecting to play around with a canvas to understand the tool. But bummer, a login screen. Maybe you can let people try before making an account?
I'm very impressed how well durable objects work for multiplayer experience!
Also looks like the table shapes broke, there should be data that you can browse and download. I've replaced those with screenshots just in case anyone else sees it
I concur with the author. Personally I think I just won't read fiction produced after 2023. There's so much good literature already produced, why bother with the new stuff?
I feel very sorry to any budding new authors. Maybe we are entering a literary dark age?
To be fair, reading new fiction is… Well, it is not a waste of time, but you really need a good recommendation from another reader you trust to find the gems in the manure pile. I don’t know how much of ”booktok” and whatnot is just cynical marketing and how much of all this ”romantacy” or whatever is generated by LLM’s, but it might as well be. And same goes to literature awards, oh boy are some of those award-winning books trash.
But the thing is, bad art dissappears. People simply forget, because bad art just is not interesting. Maybe it has a nostalgia comeback or two, but eventually it just dies away with the people who made it, who sold it and who read/experienced it. The great art stays, because it is found again and again by yet another generation. I heard kids have somehow found Count of Monte Cristo again. They are still making movies of Homeros’ texts. Joyce never went out of fashion, neither did Shakespeare, Rabelais, Cervantes nor Proust.
So only thing you need to do is wait, really. Meanwhile there is more classic’s around no-one reads in a lifetime.
I'm interested in why you feel like this. Do you take this action because you can't trust traditional channels (blogs, established tradpub authors, Goodreads et al) to self-curate LLM writing out of the pool of available literature you would normally be aware of?
Yeah I think it boils down to trust issues. I can't know how the text was created. Anything created before 2023 I know that at least a human had to invest a significant amount of time to produce the story.
Maybe I'm a bit too reactionary though. Thinking about it some more I would absolutely read something if it was recommended by a trusted source (which in my case is almost always a human I know in the physical world).
I get the sentiment completely. I am actually doing what you're thinking: if it didn't come from my List Of People Who Know Of What They Speak I want nothing to do with it.
We really have gone full circle! It's quite upsetting.
I've great success with friction logs: https://mikebifulco.com/posts/how-stripe-uses-friction-logs
If you are a platform team, going through this with your internal customers is both driving adoption and making your tools better. Highly recommended!