89vision

We're on use1 and havent seen any degradation

Agreed. First adopters will buy it, give feedback, and then Apple will iterate. Just like the first iphone

that's a great book

Both. Setting up the editor took a little doing, but it works well. https://code.visualstudio.com/docs/containers/quickstart-pyt...

I haven't used these since docker

Get in the tobacco business

sql alchemy is an orm, where ibis looks to be a dataframe api that is sort of a dsl over sql. It doesn't try to map relational domains to an object oriented paradigm like sql alchemy does

> working with SQL is nicer than Pandas

Really? I prefer working with dataframe apis. You get a nice sql-like paradigm plus all the control structures of the runtime.

Neat. I love that there's a rust implementation. Types make everything better

reminds me of https://en.wikipedia.org/wiki/Hillsborough_disaster

yeah, I've done both, but I far prefer writing protobuf markup than swagger. YMMV

I once worked on a home built browser grpc implementation where the protobufs were serialized over the wire in base64. It certainly had it's kinks to work out, but sharing/generating the service definitions and models from the same protobuf markup between backend and frontend was really nice.

OP should have used k8s to scale their workload

for non-dark pattern use cases where it is beneficial from a usability standpoint to share cookies across domains

We just block all external ip addresses except for github's in nginx for webhooks. To access the ui you need to be in the vpn.

but it worked on my machine

I used this in conjuction with home assistant to build location based automations. I'm glad this exists

I don't think this is hostile in the slightest. Nobody should expect free work

I think scala strikes a pretty good balance here. It's statically typed, but the compiler will attempt to infer types if not explicitly defined. If you want an implicit type conversion the type conversion function needs to be defined and in scope

In 2013ish I had the XPS 13 "Developer Edition". It always felt extremely underpowered for the specs, so I wonder how long they've been doing this.

Seems to be working for me. Is it only blocked for users that are logged in?

Argo workflow looks like the best of both worlds to me. You can easily build up complex etl/data processing dags where each step is a docker container, so you can choose the best tool for the job. Argo has all the retry/backoff logic built into it and you can plug the workflows into Argo events. It runs on kubernetes so you can scale your compute according to your workflow demands

I tend to go with RPC style apis with JSON/Protofbuf payloads for most things these days. IMHO it's the best of both worlds.

I really like gRPC. I've even worked with a browser implementation of it. SerDe costs were painful but the developer experience of it was great

Not a SOAP advocate by any means, but there's nothing stopping you from sending a curl command with an xml payload to a soap endpoint

Anecdotally, it's worked well for my current project as any other branching model I've worked with. It allows release validation to happen while developers continue to work on features.

The author seems to bash the workflow without offering up any solution or alternative.

interesting anecdotal response to the well cited research

To bake a pie from scratch, first you must compile Hadoop.

Sounds a lot like a phone