The How and Why of Fitting Things Together - Joe Armstrong
Вставка
- Опубліковано 30 вер 2024
- Erlang Factory SF Bay Area 2013
More info and slides on the website: www.erlang-fact...
Software is difficult because the parts don't fit together. Why is this? Can we do anything about this? And what's this got to do with Erlang? Come to my talk and you'll find out!
Mills and Dijkstra were adamant about proving correctness before writing a line of code.
The key part is at 33:56 that states that Types + FSM specifies the contract between communicating entities as the means to "Fit Things Together".
24:05
Erlang as a universal middle layer language
Theory: Order decreases to O(N)
Practice: Order increases to O( (N+1)²)
....
It is - most probably intrinsically - impossible to design and implement things that will fit together. The best we can aim/hope for are things that can be glued together 'as they are' where the glue has to provide and deliver significant functionality (and perform some syntax-level conversions). Inherently, 'design for the unexpected' only delivers intermediate and partial solutions where the 'finishing of the task at hand' will involve commitments that cannot survive future requirements. More info: store.elsevier.com/Design-for-the-Unexpected/Paul-Valckenaers/isbn-9780128036624/
That is a gross misrepresentation of the purpose of HTTP. It's almost never used for transferring static files anymore.
No, it really isn't. HTTP has simply been abused for purposes that it literally has no business being used for. HTTP is HyperText Transfer Protocol. Its only use is transferring a single document (file) at a time, (HTTP 1.0) or a few documents (files) asynchronously (HTTP 1.1+).
I feel like a lot of people could chill right out if they knew joe had solved all their problems for them in the 80s