soamv

Well, the headline was great. I'd love to read a non-slop version of this article, if anyone were ever to write one.

Which clients?

https://www.youtube.com/watch?v=x73PkUvArJY

New nullable columns are kryptonite to large Corrosion tables: cr-sqlite needs to backfill values for every row in the table

Is this a typo? Why does it backfill values for a nullable column?

This is a great point! But there's an important tradeoff here about human engineering time versus the "learning in the open" benefits; a PR discarded privately consumes no human engineering time, a fact that the humans involved might appreciate. How do you balance that tradeoff? Is there such a thing as a diff that's "too bad" to iterate on with a human?

Yes, but: https://sqlite.org/wal.html

This leaves me with more questions than answers, how did these three companies come up with the idea of using that logo? Did they just independently arrive at same design (seems unlikely)? And how did the trademark registration process go for the second and third companies that registered it?

It might have, I remember attending a talk by Peter Chen when I was at VMware around that time, and I know there was some kind of collaboration. (I wasn't involved in record-replay at VMware, but I was interested in it due to some ancient work I did with userspace record-replay debugging, https://lizard.sf.net).

rr is fantastic work, mad props! And the multiprocess stuff in pernosco looks super neat.

Just accept the grief and venting

Maintainers do not owe you this, in addition to maintaining the software that you can use for free. You're entitled to be upset, and they're just as entitled to say "please go somewhere else to vent, we're busy".

I think you'll get a different distribution of answers to this question from managers and ICs :)

Here's a link to the actual paper: https://tangchq74.github.io/XFaaS-SOSP23-Final.pdf

Well, it may be legal to create such a painting, but (depending on details) it may be a derivative work, in which case the original work's copyright still applies.

In other words, in your example, the painter is not necessarily free to distribute their painting while ignoring the original image's copyright.

Great question. I tried it and I got `elephantmouse`. I was surprised by this, but FWIW I've never encountered this edge case in actual usage.

Nice app! How did you source the sounds? Are there permissively licensed tabla and santoor samples somewhere?

People here testing out the example on this page and reporting errors seem to be missing the fact that this demo is "trained" on one example. The linked paper[0] goes into error rates, and they get better pretty quickly with a few more examples.

[0]https://faculty.washington.edu/wobbrock/pubs/uist-07.01.pdf , page 8

Yes, and rather nicely done I think. The tagline in the footer is "Give ChatGPT root in prod. What could possibly go wrong?"

It's an interesting claim, but the post doesn't even try to support it with any kind of data.

A chess position, not a game (still very interesting though!)

The link in my comment is a long read but links to lots of original sources.

They are privately operated since the 80s, but the vast majority of their initial development was government funded.

As far as I understand the privatized companies are monopolies-- these companies were formed from the JNR by geographic area served (hence "JR East", "JR West" etc.)

The bloomberg story is really light on details for why and how the privatization occurred; for a much more in-depth view, see S.Y. Lee's Substack, for example this post: https://seungylee14.substack.com/p/the-death-and-privatizati...

(An interesting fact is that most of JNR's debt at the time was retained by the government while the assets and revenue were privatized)

help me determine what % of the company I'd be getting in this stage?

Just ask them what % of the company you'd be getting at this stage. They should absolutely tell you that; that's the high order bit of equity compensation negotiations. If they don't tell you up front they're wasting your time.

Early-stage startups need mutually trusting relationships in the team. If they don't trust you enough to tell you, or you don't trust them enough to believe their answer, equity comp numbers are not the issue here.

https://archive.is/uuBhc

wow, I've used emacs for a gazillion years and never thought to replace screen/tmux with it. I think I'll start now, thanks to your comment!

Does anyone use obsidian with any of the e-ink note-taking devices (remarkable/supernote/etc.)?

Hey, I like SQLite and I also like fly.io, but "distributed DB built with sqlite as storage" is really a very different beast from just "sqlite".

As the opening sentence of the article says, the report under discussion is specifically about Facebook's impact:

Meta has been accused of “whitewashing” a long-awaited report on its human rights impact in India

It's not fluff to me -- it's human connection. Why we cook the way we do is deeply linked to our history and our "life stories".

For me, the context and reasoning behind why the recipe does what it does is much more important than the recipe itself; that makes such apps counterproductive.

I can imagine that "just the recipe" is useful for very novice cooks, but most of the time it's much better to learn the patterns and techniques than to follow the precise recipe. You'll be much more prepared that way when things don't go to plan, or when you're missing a few ingredients.

And this may be unpopular here, but I often enjoy the "life story" too: for me, many of the joys of cooking are in the connections made to other people. And if the recipe writer wants to build a connection with the cook because they poured so much effort into the recipe, I'm open to that -- and whatever it may bring to the actual cooking.

(Maybe I should make a "just the code" browser extension for Github that deletes README files ;) )

Speaking of lights in the sky, I recently fell into a wikipedia rabbit hole and learned about the Gegenschein[0]. This is the backscatter reflection of sunlight from interplanetary dust. You need an extraordinarily dark sky to be able to see it.

[0] https://en.wikipedia.org/wiki/Gegenschein

There is no clear definition with universal agreement. It's a hype-y term applied with... varying levels of rigor.

However, roughly speaking, "serverless" rolls together 3 features:

1. Fine grained pay-per-use (e.g. pay for a query by the number of rows scanned)

2. The pricing dial goes down to zero when usage is small enough.

3. You generally don't control VM/instance-level scaling but something closer to the abstraction level of the product being claimed as "serverless". For example in planetscale you get no control over how many mysql instances actually run your queries. This is great for reducing operational complexity but not so great for controlling performance. Performance tends to be quite opaque -- for example there's nothing I can find in Planetscale's docs about latency and throughput. The operational benefits are real, though. It's a tradeoff.