Hacker News: kaeshiwaza

New comment by kaeshiwaza in "Mercurial, 20 years and counting: how are we still alive and kicking? [video]"

kaeshiwaza — Mon, 18 May 2026 06:41:19 +0000

jj is amazing, even as a solo dev on small projects. It's difficult to explain because it depends of each usage, but it's very easy and safe (you can undo everything) to just try and see.

New comment by kaeshiwaza in "Cloudflare to cut about 20% of its workforce"

kaeshiwaza — Fri, 08 May 2026 20:36:57 +0000

AI is so ineffective that compagnies that use it cannot pay their workers ! Poor guys tech bros.

New comment by kaeshiwaza in "Databricks acquires Neon"

kaeshiwaza — Wed, 14 May 2025 11:29:06 +0000

Taking a pause also... I don't believe serving IA can be aligned to serving devs. I hope that the part of the work related to the core of PostgreSQL will help the community.

New comment by kaeshiwaza in "Tailwind CSS v4.0"

kaeshiwaza — Thu, 23 Jan 2025 06:27:40 +0000

Locality of behavior can be done with few lines of js. https://github.com/gnat/css-scope-inline

New comment by kaeshiwaza in "Window Maker: X11 window manager with the look and feel of the NeXTSTEP UI"

kaeshiwaza — Thu, 29 Aug 2024 05:38:48 +0000

I use Fluxbox since the first version. Very easy to customize. I've just an issue with Firefox, the Firefox windows doesn't want to play with Fluxbox (on Debian)...

New comment by kaeshiwaza in "Htmx 1.9.0 has been released"

kaeshiwaza — Thu, 13 Apr 2023 11:44:00 +0000

Maybe the new feature 'hx-on' can help with that ?

New comment by kaeshiwaza in "Htmx in a Nutshell"

kaeshiwaza — Thu, 15 Dec 2022 10:45:01 +0000

As we use less and less Javascript, thanks to htmx, i'm no so reluctant to use vanilla JS when needed.

New comment by kaeshiwaza in "Htmx in a Nutshell"

kaeshiwaza — Thu, 15 Dec 2022 08:56:20 +0000

I'm using htmx in production since one year. From game (scrabble game with board refresh, chat and so on -with sse extension-) and cms to professional crud apps. With Go + stdlib template. Now looking at PWA, it seems to fit very well.

What i like with htmx is that it's very easy to upgrade step by step a legacy SSR app. And the opposite. I mean it will be easy to switch to an other ajax lib or if w3c add similar functionalities in 10 years. To use htmx is mostly to replace whole pages with fragments, that's interesting even when we don't use htmx, sort of server side web components.

In other world, just try !

I'm fighting myself to don't give back examples to the community but i'm so exited to upgrade my very old legacy apps !

New comment by kaeshiwaza in "Moving from React to htmx"

kaeshiwaza — Sun, 16 Oct 2022 08:27:41 +0000

I can replace all the iframe from my legacy apps without changing any logic !

New comment by kaeshiwaza in "Moving from React to htmx"

kaeshiwaza — Sun, 16 Oct 2022 08:23:54 +0000

Rendering html doesn't consume a lot more than rendering json, specially that with htmx you'll render small fragments... Anyway the bottleneck is most of the time on the database.

New comment by kaeshiwaza in "Ask HN: In what ways is programming more difficult today than it was years ago?"

kaeshiwaza — Sun, 02 Oct 2022 15:29:58 +0000

I still work like that 30 years after, thanks to Go... I would not like beginning today !

New comment by kaeshiwaza in "Kubernetes is our generation's Multics"

kaeshiwaza — Thu, 22 Jul 2021 07:30:50 +0000

It's where Thomson-Unix way win as KISS and still work for small to large scale.

New comment by kaeshiwaza in "Lessons from Building and Scaling Reddit's Ad Serving Platform with Go"

kaeshiwaza — Mon, 10 Sep 2018 19:25:03 +0000

Maybe they have other future projects with Go ?

New comment by kaeshiwaza in "A response about dep and vgo"

kaeshiwaza — Mon, 30 Jul 2018 07:44:05 +0000

In large software you'll not do go get -u for all packages, you'll upgrade each package separately, at the maximum version or at a specified one. It's just that it's you the user of the modules will choose what and when you upgrade, not the(this) tools automagicaly.

New comment by kaeshiwaza in "Russ Cox on Go dependency management"

kaeshiwaza — Sat, 28 Jul 2018 09:24:17 +0000

Dep has also issues, it's safer to continue to use Dep when you already use it but for new project it's recommended to switch now to go modules. Anyway, most of the time it doesn't change anythings to lock the version with dep or use minimal version selection.

New comment by kaeshiwaza in "Russ Cox on Go dependency management"

kaeshiwaza — Sat, 28 Jul 2018 09:20:54 +0000

It was a long series of "i will say you my concerns tomorrow" that just make stir up the sauce since month without any clear and obvious problem.

New comment by kaeshiwaza in "A response about dep and vgo"

kaeshiwaza — Sat, 28 Jul 2018 09:02:47 +0000

The implementation of vgo (so simple) cannot be compared to dep. It can explain why it was more easy to just do it than spend time to explain. It's often like that in dev, when we find a simpler solution in our own code we just do it and throw away the old complicated one.

New comment by kaeshiwaza in "A response about dep and vgo"

kaeshiwaza — Sat, 28 Jul 2018 08:39:25 +0000

I have exactly the same feeling. And remember at the time of the start of Dep that there was no consensus and a big hope that the final integrated solution will be more Goish than Glide. Very surprised by the begin of Dep. I don't believe that rsc and the go team didn't know since the begin that it will not fit sooner or later...

New comment by kaeshiwaza in "A response about dep and vgo"

kaeshiwaza — Sat, 28 Jul 2018 08:13:15 +0000

You didn't find example of failed Cargo because most of the time it just do like go get -u, and solve a non-problem !

New comment by kaeshiwaza in "A response about dep and vgo"

kaeshiwaza — Sat, 28 Jul 2018 07:38:21 +0000

Upper bound are major version, everything between should be api compatible (it's in the specs of go modules).