sauercrowd

qlot has lockfile support with qlfile.lock

that is actually really cool - I always felt like (and surely am not the only one) that vim is great keybindings but an okay editor. If someone addresses this that'd be incredible.

I was watching thorsten and the primeagen's chat yesterday https://www.youtube.com/watch?v=8XweSqTYdMQ and thorsten was describing a few challenges with translating vim's functionality into zed.

Part of it being that zed doesn't have an intermediate layer between keyboard input and keybindings, so by the time the vim layer is hit it has been translated to a keybindings - that limitation kind of put me off.

i definitely agree, and Id LOVE a snappy editor, but I struggle to trade thay off with everything else other editors provide

Cool to see a new editor in the arena with a lot of resources behind it, but I'm trying to find the selling point besides "it's really quick".

Great feature but there's a lot more stuff I need for a truly outstanding editor, what are the novel pieces?

The bar is ridiculously for editors (vim & emacs configurability, vscode just works, jetbrains can do it all) - what will/does it bring to the table to compete?

this way you can still see your existing recommendations, but you dont influence them unless you want to

i often start watching a video, enjoying but there's no great flow to then bring it back into your recommendations once youre in a private tab

with the extension you could just toggle mid video if you decide its a good one

> those things

what things?

?

Why?

very different from my perception - from unusual davids approach was to how the rails team formed through Toby and the others, merging with that other frameworks... so many small bits of history that are hard to digg up anywhere

I wouldn't mind it being longer but it's great they were able to put it together

Google: We're shutting down Google domains cause we need to focus.

Also Google: Here's the pollen API you guys have been asking for for ages.

That's a fair point, but that's essentially what fly does. If the only purpose of your VM is to serve your app (and not as a workspace for you or stuff like that), fly's great because you don't need to do any plumbing to deploy.

"Simply" using a 5$ VPS sounds great until you need to start writing systemd files, need to keep the box updated, want to deploy straight from GitHub,...

Also - this is worth calling out

If coldstarts are a problem, things like fly.io are incredible. Just set the minimum amount of instances to 1, pay 5$ a month and you don't need to deal with anything.

It wasn't immediately obvious to me how fly and Cloudrun compare, but the way I think about it now after having used both:

In Cloudrun you don't think about any servers, you give them your image and they'll do the rest. It feels serverless in the sense that you don't think about machines.

Fly meanwhile is much closer to the infrastructure. It feels more like "we deploy a docker image to a VM for you", which let's you much more granuarly control what's going on beyond that.

Less magic, but in a good way because more predictable results. Cloudrun has a few fun corners (like no CPU between requests unless you explicitly enable it) that can lead to fun side effects and just make it harder to reason about.

really depends on the traffic, but even if you're service ends up running 24x7 you'll end up paying about 10 dollars for a 1CPU/0.5GB RAM instance. So for a lot of stuff Cloudrun will actually work out pretty cheap.

Don't underestimate cold starts though. Will be a long time until you need to worry about that if you're backend is written in Go or Rust, but you can hit painful starts pretty quickly when it's Nodejs. Really comes down to (unsurprisingly) image size.

what are you referring to with "billions of handouts"?

Using the docker container is a breeze - add a POSTGRES_PASSWORD env variable and you're all set. I'd be curios how it performs for a TB of data but I would be surprised if it straight out breaks.

https://hub.docker.com/_/postgres

This a great summary - also a really good argument I observer when using GitHub's Copilot.

Using copilot makes it much harder to pick up new programming languages cause you'll end up working on much higher abstractions, since copilot is generating a good chunk of the code.

Not to mention that your own code is much more sprinkled in, making it harder to build up a coherent, end-to-end understanding of the underlying syntax and semantics.

I've been thinking about the same thing - this feels like it deserves a native API, so we can get rid of all these dark patterns currently being employed.

Does anyone have a TLDR/highlights of the release?

pdfgrep is great. Worked like a charme to diff updates to a contract