85 karma · joined August 29, 2013
On a warm build on my machine, after editing a string in Zed's `crates/zed/src/zed.rs` and editing a string in Rune's `./cmd/rune/main.go`
Zed: `cargo build --release`: 284s (debug 30s)
Rune: `go build ./cmd/rune`: 15s
note I'm using a release build in Cargo to make it a bit fairer as all builds are "release" builds in Go.
Great work folks
Also of note: - Go's Swiss Table implementation is inspired by Cockroachdb's Swiss Table implementation which is inspired by Google's Abseil Swiss Table.
The linked section of the RFC is worth the read: https://www.rfc-editor.org/rfc/rfc6455#section-10.3
The real meat of this argument is that in the future DevOps won't be managing infrastructure to hand off to application developers. It will be creating meta programs that are designed to be used by application developers to let them build their own infra securely and reliably. This is what the `awsx` package in pulumi is. A predefined set of best practices that can be used by the application developer to create.
As someone who's worked as various stages of sysadmin throughout the past 10 years, I see this (pulumi-like) as the future. And I agree with the article in general.
This is exciting! It opens up faster possibilities for wasm apps
A = E; E = function(x){ window.secret=A(x); return window.secret };
As you can just change how the function works.