Readit NewsAlso updates regularly break my KDE session and I have to restart my display server.
Sometimes I have to switch to a tty and back to my graphical console to get my display back.
It is a mess all around.
I haven't managed to get my GPU working in Docker, ugh.
That said, it does work. Mostly.
Deleted Comment
Usually access increases the reference count (to avoid the object getting GC'd while you use it) and weak pointers are the exception where you are prepared for the object reference to suddenly become invalid.
Slows down every access to objects as reference counts must be maintained
Something weird that I never bothered with to enable circular references
Most functional-inspired languages would just have a single `f: T -> Result<U, E>` interface, which supports both (1) a specific error type `E`, which can also be an uninhabited type (e.g. never type) for an infallible operation, and (2) where `U` can be the unit type if the function doesn't return anything on success. That's about as generic as one can get with a single "interface" type.
[1]: https://docs.spring.io/spring-framework/docs/current/javadoc...
`for path in paths`
should be
`for (const path of paths)`
JS will immediately error on the lack of parens, but the `in` vs `of` iterates over indexes, not values, and those indexes are unfortunately converted to strings (since `for-in` is object field-name iteration). So even TypeScript would not have caught it when the (stringified) index is used as the first argument of `fs.watch()`.
But I digress.