miniblog.

← Back to all posts
Nov 28, 2014 at 23:48
"There are 2 webs now: document-centric, platform-agnostic presentation of content and the [platform] that is HTML5" https://news.ycombinator.com/item?id=8670541

Related Posts

Aug 18, 2024 at 23:45
I'm a huge fan of Swift's 'Error Handling Rationale' design document: https://github.com/swiftlang/swift/blob/9315673c003875158852579bd1f33480cdec5461/docs/ErrorHandlingRationale.md#fundamentals It carefully defines terminology and compares with other languages, so you can understand Swift's position and preference in the design space.
swift/docs/ErrorHandlingRationale.md at 9315673c003875158852579bd1f33480cdec5461 · swiftlang/swift
swift/docs/ErrorHandlingRationale.md at 9315673c003875158852579bd1f33480cdec5461 · swiftlang/swift
The Swift Programming Language. Contribute to swiftlang/swift development by creating an account on GitHub.
Feb 21, 2024 at 07:25
Fun example of a bunch of YAML gotchas all in a single file:
The yaml document from hell
As a data format, yaml is extremely complicated and it has many footguns. In this post I explain some of those pitfalls by means of an example, and I suggest a few simpler and safer yaml alternatives.
Jul 29, 2023 at 17:33
Go has a wonderful, accessible discussion of how it does inlining today, the downsides, and the plans for 1.22:
Go 1.22 inlining overhaul
Go 1.22 inlining overhaul
Go 1.22 inlining overhaul , with contributions from , , , and Last update: The Go compiler’s inliner has never been particularly good. It wasn’t until Go 1.12, released in 2019, that the Go compiler supported inlining more than leaf functions, and we’ve slowly chipped away at more limita...