HN user

vim-guru

255 karma
Posts0
Comments96
View on HN
No posts found.

For speed-limits, I believe most of these new cars use multiple sources; so likely information found in the map at your location and cameras to spot signs. For some freak, unknown reason, the map-data is usually more trusted with the car vendors then the camera's it seems. Just don't rely on map-data for speed-limits and this would be a solved problem I think.

I switched to a split keyboard about four months ago and decided to change layouts at the same time. Adapting to the split itself wasn’t particularly difficult, but switching layouts definitely takes some getting used to. After all this time I’m still only at around 30–40 WPM, so it’s not something I’d recommend to everyone.

That said, I do believe the change will add a few more good years to my career, so I’m committed to seeing it through. I went with a relatively inexpensive keyboard and a modified Engram 2 layout. The reduced finger travel and more natural arm positioning have already made a noticeable difference.

Give it another year and I expect to reach an acceptable speed as well. All in all, I’m happy with the switch.

Emacs: The macOS Bug 12 months ago

On macOS and Linux, I haven't noticed any performance issues with Emacs. On Windows, however, the performance is significantly worse. To make matters worse, I even have to patch w32.c just to get it to build:

@@ -10298,7 +10298,7 @@ w32_read_registry (HKEY rootkey, Lisp_Object lkey, Lisp_Object lname) /* mingw.org's MinGW doesn't declare _dstbias. MinGW64 defines it as a macro. / #ifndef _dstbias -__MINGW_IMPORT int _dstbias; +__MINGW_IMPORT long _dstbias; #endif

/ Fix a bug in MS implementation of 'tzset'. This function should be

I prefer: <short description> <BLANK LINE> <Detailed information> <BLANK LINE> <footer>

Using a type is to contrived, because your commit will often include e.g documentation and a feature. Splitting them for the sake of following this pattern makes no sense.

Why Clojure? 1 year ago

I've been working with Clojure on and off for over a decade, and I've found it exceptionally efficient at solving a wide range of problems—making it one of the best general-purpose languages available. However, I sometimes envy the capabilities of OTP, which provides a straightforward way to build fault-tolerant servers without the overhead of managing containers or databases.

Additionally, while the growing number of compile targets in the Clojure ecosystem is impressive, it can also create confusion for newcomers. Whether it's compiling to native code with Jank, generating quick script snippets with Babashka, or using subsets of ClojureScript like sci or cherry, the diversity is both a strength and a challenge. I believe a concerted effort to unify configurations across these targets would help streamline the ecosystem and make it easier for developers to choose the right tool for their needs.