vim-guru

yuck

Once LLM's become smarter than us and start replicating; we are doomed. They will likely no longer require GPU's and massive amounts of power, so the growth of AI and robotics will be exponential. We will not understand what the AI is even up to, it will all seem like magic.

Would be nice for GUI components of a game, but I kind of hope people don't run with this on regular apps/websites. Also, I expected tooltips and submenus to have some flair to them as well.

Very impressive! Well done

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.

Looks good. I'll stick to Emacs and tramp though.

TIL about SPDK. Thanks!

I don't get why we get all these kinds of things to support writing in markdown when org-mode already exists and can support pretty much any use-case. Its not that difficult to master.

This was already in place in the EU back in 2024. Lookup DDAW. You can turn off warnings, but it will still keep on monitoring the driver

There's also GUIX.

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.

I'm at the opposite end. I feel AI is sucking all the joy out of the profession. Might pivot away and perhaps live a simpler life. Only problem is that I really need the paycheck :(

Apples products are still the best on the market, but if they keep this up; they will sooner or later become irrelevant.

Very much agree! Apple has been dropping the ball lately

This has been the default for us using magit for years.

Why are some of the pages upside down?

I've been using EDN for years without ever wishing for something different. It's unfortunate that it hasn’t caught on outside the Clojure world.

I know. I don't even use vim bindings any more.

I haven't used google in years and didn't realize it was this bad. How are they able to keep their market position?

Nostalgia! However; dired (and wdired) is more powerful, so I won't be switching back any time soon.

I could have written these exact words. Marriage needs a certain balance you know ;)

Excel hates CSV

It clearly means CSV must be doing something right.

What an ugly logo, and the kerning is all wrong. Man!

I agree with the author. I've written my fair share of typed code, but it is way more valuable to probe your program while running. I feel Jack Rusher puts it quite nicely in this talk: https://youtu.be/8Ab3ArE8W3s?t=1477

This works surprisingly well for logo design. Cool concept

So, kind of the opposite of https://github.com/lovrosdu/klor but with the same goal

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

https://nats.io is easier to use than Kafka and already solves several of the points in this post I believe, like removing partitions, supporting key-based streams, and having flexible topic hierarchies.

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.

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.