jh3

What are you doing to keep a JSONL per session? Or is this something built in? I’m interested in estimating token costs in this way.

Wow, so "two bits" is what Roger says in response to Judge Doom in Who Framed Roger Rabbit. I can hear it now, but I never actually knew what was said.

Sounds like you're the miserable one?

I thought Drupal 6 and 7 were great, but this was about 5-10 years ago. Haven't looked at it since then. It was the first CMS I worked with professionally, so I may be biased, but once I "got it", it became quick to add features (not "Features", which wasn't very fun). This was before everything went headless and javascript :)

First time hearing about this client. I primarily use the Reddit iOS app, which seems fine. What's better about Apollo?

To name a few: YOB, Animals as Leaders, Neurosis, Pelican, Russian Circles, Isis :)

Exactly! Parental relief.

Now that I have my own children, I'm convinced this myth is a delay tactic perpetuated by parents :)

Yeah I can see that. The one I had saw regular use when in my possession, but I had it for less than 6 months iirc. It was still in excellent condition.

They retain value. You could buy one used and sell it for more, if not the same price you purchased it at. I think the worst case is you'll essentially be renting it for $100-200 if you really don't like it. This was my experience, anyway.

It's a great device even if your job isn't music production. Easy to use, lots of fun, though I didn't enjoy the form factor.

You can copy/paste the code into the console of your browsers dev tools.

What you're saying is false, but what you're quoting is correct. I definitely wouldn't say "always".

> I still fucking hate rebasing and get tripped up by it on the few times I end up having to deal with it.

When I had no understanding of what was going on, I didn't like it either. Now that I use it frequently, I understand it better, so I don't hate it anymore.

I like running `git rebase <main-branch>`, where <main-branch> is typically master, in my-new-thing branch because it lets me deal with any conflicts from upstream one by one.

I also like running `git rebase -i` in my-new-thing when I have a bunch of commits with redundant messages that I want squashed into a single commit before I push the changes. Basically anything that requires messing around with a range of commits is a good use case for `git rebase -i`.

Why do you hate it so much? There's really not much going on that you should have to hate. To me it's like a bunch of small, compartmentalized merges.

> You don't see structural engineers slapping together the first thing that works and patching the building later when parts of it fall down.

That's because if they mess up the first time people can die.

I'm guessing the likelihood of death due to a bug in most web applications is probably much less than that of a bridge :)

Software is great because it's possible to iterate quickly. But ultimately, you have a point. Developers should be willing to fix bugs they've created and/or come across in their projects. We should also try to limit the potential of bugs by releasing small chunks of functional work as often as possible. "Releasing" in this sense can mean to production or just to your qa/test/dev/stage environment. It's just important to have many eyes on the product before it's live.