23 karma · joined November 19, 2014
After a full month of coordinated, decentralised action, the number of articles about Mr. Woodard was reduced from 335 articles to 20. A full decade of dedicated self-promotion by an individual network has been undone in only a few weeks by our community.
Human driving through painted wall:
Instead you have access to a fleet of specialized vehicles that are optimized for different tasks. Eg many trips might still be with only one or two passangers, and then a small two seater makes a lot of sense. If you need larger capacity you simple order a ride from a suitable vehicle class.
There are several presentations on the design and mechanisms. Eg
- https://www.youtube.com/watch?v=ws-Z8xKbP4w (Val: A Safe Language to Interoperate with C++ - Dimitri Racordon - CppCon 2022)
- https://www.youtube.com/watch?v=oFupPFniD9s ([IWACO23] Borrow checking Hylo)
A bit disappointing that this does not get more attention on HN. Using WASM as a sandboxed embedded compute environment has so many use cases outside the browser.
For example extensions/plugins in code editors is another very interesting use case.
There are huge problems eg with both the Unity C# approach as well as Unreal C++.
The swift approach is very interesting indeed, and Miguel de Icaza as the author gives additional reason to follow this effort.
Additionally the Verse project from Unreal is extremely interesting imo, and has much wider scope/implications.
Hopefully LSP specification can evolve over time and incorporate some of these ideas!
https://help.tana.inc/use-cases/tana-tour-with-maggie-applet...
https://docs.swift.org/swift-book/documentation/the-swift-pr...
IaC is a really powerful concept, and system initiative does not need to be in conflict with that paradigm, just another layer of abstraction that still allows IaC.
The main issue is how to combining UI state + and manual state.
The worst thing you can do imo, is to use a common representation, eg the UI would try and edit your manually written declarations. That is just a recipe for disaster.
The answer to this type of mixed editing is a layer approach, eg what is being done in the USD format (https://openusd.org/release/index.html)
Each authoring "instance" has full control of its layer, and composition semantics define how the layers compose to the final declarative structure.
Also the physical wheel was amazingly good UX, and very responsive.
For instance, in C#, with capital-case convention for variables, it is common to give a variable the same name as the type.
eg `public Player Player;`