767 karma · joined November 23, 2022
How can you not care when companies choosing to go fully remote means you have less options to find in-office jobs?
For this reason I personally don't like `#[non_exhaustive]`. I don't expect my code to keep compiling when I upgrade the minor version of my dependencies, and as long as the reason is simple, like a new enum variant was added, then I'm happy that it errored and will happily fix it.
This perfectionist attitude towards semver is why so many projects get stuck forever at v0. https://0ver.org/
this makes it sound like the limit is automatic or applies non-discriminately to customers, but my first instinct is that this was manually set by someone, maybe the sales reps again?
"the fucking article"?
Well, maybe you need to train them?
This is how I feel each time they release a new version that promises to be both faster and at least as smart as the old version. To be fair, Turbo did get a lot smarter over time.
I guess you could make it part of an application that embeds (a browser for) VS Code, with which the keyboard code can communicate and receive this information from.
You could almost build it on top of a generic English swipe keyboard if you treat a swipe to shift (for camelCase) or `_` for snake_case as word separators, to match them in isolation to a generic English dictionary, and once the user presses space, you can try to match the fullIdentifierWithAllWords against a dictionary from the editor/LSP.