In the past month, I was working on publishing a Java app to Mac App Store (MAS). It's quite a journey. While Java has come so far in terms of packaging a desktop app, it also lacks in some other critical parts. Sometimes I wonder how others publish

The first thing I'd do is to run the app in Terminal: $ cd /Application $ ./YourApp.app/Contents/MacOS/YourApp Then, we might see some useful outputs. If we don't see anything useful, then we should utilize Console.app that comes with MacOS.

I wanted to show you how to add another database in PlayFramework that uses Slick and Evolutions. That database is ClickHouse, which also requires a little bit of special handling. In the end, it works out quite cleanly. I'll later integrate it into PlayFast, an opinionated production-ready PlayFramework

It took me 1-2 hours to set up ClickHouse to work with a JDBC connector in Java. The ClickHouse documentation is somewhat obscure. For example, it shows all the ports from a ClickHouse server: https://clickhouse.com/docs/guides/sre/network-ports But the Server Settings page doesn't show

It gets a bit tricky to make the production code clean while making it convenient to mock a static method in a multi-threaded setting since Java and Scala don't support "monkey-patching" like Ruby, Python, and Javascripts. Mocking time is one of the mechanisms implemented inside PlayFast

Summary * Many virtual list libraries like react-window, svelte-virtual-list, and TanStack's Virtual cannot handle the total height larger than 16,777,200px due to Chrome's limitation. If you have a list of 1M rows where each row is 28px, you won't be able to scroll

Summary * Using local dependency like "your-package": "file:../some-path" or npm link doesn't work with Svelte because you will have duplicated Svelte runtimes. * What works is to use npm pack and then npm install <path_to_tgz> * Bundlers look for Svelte runtime in

This seems to happen sometimes in test and dev. After digging into java.sql.DriverManager, which is responsible for loading all drivers, it seems to use ServiceLoader to discover all subclasses of java.sql.Driver. Apparently, sometimes it fails in test. No idea why. To fix it, we can register

The example is in Tailwind: <div class="w-[200px]"> <div class="w-full"> <ul class="w-full"> <li class="w-full"> <a href="overflow-hidden text-ellipsis whitespace-nowrap">text</a> </li>