every compiler project expands until it creates its own version of TableGen. after that it is swiftly replaced with something that is "not as difficult to use", and the cycle continues
@whitequark I'm unfamiliar with TableGen and am trying to read the docs to try to get the joke better. It's very confusing and I don't understand it tbh... which feels fitting I guess.
Since Stack Exchange decided to jump the shark as well, this is a reminder that the whole network's data is licensed cc-by-sa 4.0 (a decision made in the beforetimes, and one which they're likely regretting at this point). This means anyone can setup a mirror/browser of this data as long as it's attributed back: https://archive.org/download/stackexchange
@fasterthanlime it's funny to me that because your TLD matters to the name, none of the mentioned domains make any sense or clash with your naming anyway
This is the best job I've done conveying why I'm so enthusiastic about #wasm – or at least, the most succinct job I've done! We walk from the 1960's right up to the present day and, as a bonus, uh
I think with #wasi 0.2 out, #wasmcloud 1.0 just released, and the huge push for #federation right now, it would be a perfect time for someone to create an ActivityPub/ActivityStreams WASI proposal and get a Mastadon server compiling to Wasm.
I'm starting to think the phrase "ambient authority" distracts from what matters.
The reason ambient authority is problematic in traditional systems is that it's
coarse-grained (eg: you can do anything the owning user can do), and
not conveniently interposable (eg: it's seccomp time!).
"Ambient" focuses on the way authority is presented, but systems can have coarse-grained handles with inconvenient interposition, and have the same problems.
@sunfish I think ambient security is also less scary when it's over a closed scope (e.g. a component) and those scopes can be safely nested (e.g. composition)
I've been doing some thinking about "Component-Aware" optimizations to implement in component-opt.
I realized that we can think of this as Whole Program Optimization (WPO) or Link-Time Optimization (LTO) for Wasm components, which helps distinguish it from the kind of optimizations wasm-opt does on single modules.
Don't you love when in the middle of your VS Code: Remote WSL session, VS Code updates itself, restarts, and then crashes immediately and without an obvious fix because it now depends on a more recent glibc.
@brettcannon maybe I accidentally hit some hotkey, but I definitely didn't do it intentionally.
I was able to get everything out (though it was a bit painful since I was using GitHub auth in VS Code and had to add a new ssh key and...) and am now in my Ubuntu 20.04 WSL and have set it as default now.
I sometimes wonder: “what if Rust bools were just another enum” and while not actually practical or anything imo, it’s a pretty fun thought exercise?
If/else statements are a really fun one here. We don’t want to have to write:
if let true = x {}
but instead we want to be able to write:
if x {}
Which I think we could do via a trait. But if we allowed that and made the trait stable, other enums could be “truthy” or “falsy”, which I’m not sure we’d want.
@yosh IMO truthiness as a trait implementable on any type isn't ideal. It's nice that people have to do .is_ok() or similar to explicitly produce a truth value from a non-bool value.
If you happen to remember my struct syntax proposal, this is effectively implementing that idea via a function decorator. If there's enough positive feedback I will consider writing a PEP to propose this as syntax.
@sunfish hey! I wanted to reach out about wasi-logging – through Dylibso, I'm starting an effort to create a wasi-observe WASI interface 1. I'd like to depend on wasi-logging; do you think that would be a good course going forward?
(Also, if you have any tips about navigating the WASI proposal process or early feedback about the proposal, I'd be grateful – this is the first WASI proposal I've worked on.)
@isntitvacant@sunfish with the structured concurrency coming in preview 3 async, there are some interesting options for the host to handle span enter/exit, manage trace ids, etc. automatically that I think are exciting.
