I was just stuck at this problem for half an hour. The issue was a bit difficult to figure out. I have this Express server (Node.js) running: var hmr = http.createServer(app); hmr.listen(8090, "localhost", function () { console.log('Listening on %j', hmr.address()); }); After

I'm excited to share my opinionated PlayFramework Template, PlayFast. It has the needed components and code conventions that make you productive and ready for production. It would have taken days to weeks (depending on the expertise level), with a large amount of googling, to set up these components

I was exploring how to build a slimmer non-JIT JDK to be embedded in a Desktop app on Apple Silicons Mac. To conclude, it doesn't seem we can completely disable JIT... or at least the JIT definition by Apple. There is a zero variant JDK [1], which will

I was working on a Desktop app and encountered a log error as shown below: SLF4J(E): A service provider failed to instantiate: org.slf4j.spi.SLF4JServiceProvider: Provider org.apache.logging.slf4j.SLF4JServiceProvider not found SLF4J(W): No SLF4J providers were found. SLF4J(W): Defaulting to no-operation (NOP) logger implementation

I've followed this tutorial: https://github.com/JetBrains/compose-multiplatform/blob/master/tutorials/Signing_and_notarization_on_macOS/README.md There were 2 problems that I've encountered. Unable to build chain to self-signed root for signer The command that failed: /usr/bin/codesign -vvvv --timestamp --options runtime

Why are people amazed that she likes her own music? Like, how are you going to make music if you don't like what you're doing? If you don't like it, you just change it until you do like it, that's art. (source)

A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system. This quote is from his book:

I just encountered an interesting UX issue regarding pressing a shortcut. I was using the KeyUp event for some of the shortcuts, and I've found it to be flaky and counter-intuitive. The main reason is that it's rather difficult to trigger the key up event when

Since I've moved to zsh, the history searching using the up arrow hasn't been working. Today I've decided to sit down and investigate. It turns out that set -o vi needs to be executed before history-search-end as shown below: # This need to be above