Andrew Werner

@justinjaffray It’d be a real lame jit tho. I wouldn’t go around talking that shell script as a jit because I wouldn’t be talking about that shell script…

@justinjaffray Yeah, I think it is. Isn’t that kinda what the browser wasm engines are doing? I feel like we call that a jit. To me it’s fine to use the word jit to describe software that takes “logic” that is not native code, generates native code, loads it into memory, and executes it

@zguneri @fatih @MattJamesBoyle Snowcrash and Cryptonomicon are *so* different. I read Snowcrash after and my takeaway was primarily, “man, this guy has range”

@fatih @MattJamesBoyle Snowcrash bas been waiting on my shelf for a long time as well. I picked it up after really enjoying Cryptonomicon. Not sure about Snowcrash yet but highly recommend that one. It was a true page-turner for me.

So far I’ve finished 5-6 books this year. Currently reading “Bullshit Jobs” by David Graeber (and “Debt” in parallel). And here are the books I still want to read. Not sure when but I’ll finish them eventually.

@burntsushi5 The way I’ve been testing updating dependencies lately (also isn’t great) — I use `git diff $BASE > $PATCH` then you can use crate.annotation in WORKSPACE to tell it about the patch file (it’ll need to be in the workspace). Then I update the patch file and bazel detects that

@ajwerner I also had to include `CARGO_BAZEL_REPIN=true`.

I am trying to test some Rust code on Android (which I have no idea how to do), and someone help set me up with this Bazel thing to do it. I managed to get it to work. But now I want to test my changes to Jiff without publishing them.

@burntsushi5 One thing you can try is, in WORKSPACE, replace `"jiff": crate.spec(version = "0.1.13")` with "jiff": crate.spec(git = "file://<path to jiff repo>", branch = "<branch name>") Alternatively you can use `rev` or `tag`, see #cratespec" target="_blank" rel="nofollow noopener">bazelbuild.github.io/rules_rust/cra…

This is the repo I'm working off of: github.com/daylightwarble… (I find it extremely elaborate. Is this really the simplest way to test a Rust library on Android? Just... wow.)

Ever wanna just know if a line of code is being hit? Or how often? Or from where? In prod!? We've been hard at work making that just a click away with side-eye.io!

@thdxr What about neon or cockroachdb serverless? They have more bells and whistles than stock rds or the Amazon serverless database offerings and they scale to zero.

honestly what's killing things is the entry level price - way too high

we pushed aws rds serverless and data api as far as it'll go - unfortunately these just aren't good products going to flip to making normal rds easier to use (mostly networking from local machine) and that might end up being our default

@adamhjk What do you think of the wxWindows license? It tries to be friendly for wide commercial use and distribution while retaining the copyleft. Maybe it’s not standardized and reusable enough? How would the license you envision differ? opensource.org/license/wxwind…

I think we need a networked version of the MPL. We’ve licensed System Initiative under the Apache license, which I love. It’s clear, it’s easy, it’s digestible, and it allows folks to build what they need without needing permission.

@iavins For many distributed databases, you won’t see a failure unless the transaction coordinator node dies. It’d be unreasonable if any node dying lead to all transactions failing, but it’s hard to do better than that and it’s arguably not so bad given the app can die too.

Are there databases which let you continue the execution of a transaction on connection failures or machine restarts? Why don’t databases support such a feature?

@iavins If an http-based, request-response oriented protocol sat underneath your sql drivers, then maybe you’d see more such recovery protocols built into transaction protocols. Tl;dr to do it right it’s probably gotta be in the driver, and that’s a hard place to innovate

@iavins A big impediment I suspect is the wire protocols we use to talk to databases. They are generally bespoke and based on reliable streams. Recovering a tcp/tls/unix socket stream is not straightforward, it’s not like just retry the statement request.

@felixge I think I like @_rsc's take (IIUC): It's not so much that we care about major go upgrades breaking you as the end user compiling/running/monitoring your own programs; we care about making it impossible for your dependencies to break your code when you upgrade go. Seems fair

🚨 The //go:linkname party is coming to an end. The Go team is taking a very important step towards ensuring the future health of the ecosystem, and ensuring that people can always upgrade to the latest versions of Go.

@eatonphil @positiveblue2 container/list is pretty terrible and container/ring I’ve never used and don’t intend to. However, I have a certain respect for the container/heap API; it cleverly enables quite a bit of flexibility and can be used efficiently.

@positiveblue2 @ajwerner Didn't stop them from container/ring, container/heap, container/list

Does Go have no builtin sorted data structure? rbtree, btree, skip list, etc.

@iavins In cockroachdb, all schema changes are online and never lock tables

How do you run migrations on a large table, online? Sometimes, the DB might end up taking a lock on full table if not done carefully. Here is a short post which explains how not to do them in PostgreSQL and then a proper solution:

@GimbalNick Not if using oauth, which you should support.

@justinjaffray Just so I don’t mess it up, how do I spell the plural of thingy?

@rawkode @AlexJonesax I was setting this up today. I had to use both. The former is for connecting up for tracing, as in thingies with trace ids and span ids, and the latter for logging via the log appender thingy. Is that right? I feel a blog post coming on.

@AlexJonesax These are the only acceptable answers.

There are 15 ways to use OTEL in Rust and they are all deprecated