HackerTrans
トップ新着トレンドコメント過去質問紹介求人

muti

318 カルマ登録 10 年前

コメント

muti
·4 日前·議論
The abstract reads like copy for the Turbo encabulator
muti
·4 日前·議論
Thank you for prompting me to try with my own obscure question, Fable was able to find something from a poor description. I've been looking manually and over many sessions with different models as they improve, none have been able to find what I was after. Fable 5 just one-shot the answer.
muti
·8 日前·議論
Cool, been running my home server on podman + quadlets for about two years now and picked up a couple of things in the release notes

  podman quadlet list
Added in v5.6.0, lists quadlets and their containers

  podman system migrate --migrate-db
Flag added in v5.8.0. I remember seeing the bolt db deprecation warnings in the past but there was no tool to do the migration to sqlite, now there is (or just upgrade to podman 6.0.0 and it will do it automatically)
muti
·17 日前·議論
If the thing you are towing is so heavy you need a truck to tow it, maybe there should be stricter licensing requirements.
muti
·22 日前·議論
And for a cheeky example, here's a jandal you can buy with the plugger + bread tag combo from the factory

https://heresgolden.com/products/golden-g2-mens?variant=4362...
muti
·2 か月前·議論
See the image and caption at the top of the article

  Images printed with structural colour ink can be made both highly transparent to transmitted light (top) and at the same time reflect light from above in vivid colours (bottom) – two properties that are typically considered mutually exclusive
The printing on the phone is not visible when the phone display is on as the structural printing is highly transparent. When the display is off, the printing is visible because of the reflected light.
muti
·2 か月前·議論
Doesn't seem like a very insightful result. Kimi won with the naive strategy. Other models didn't slide tiles at all or didn't demonstrate understanding of the rules, claiming words that lost points. A strategy that did nothing would beat them.

We know these models can solve much more difficult problems, something isn't right.
muti
·3 か月前·議論
+1 on this, I also switched to jj when working with any git repo.

What's funny is how much better I understand git now, and despite using jj full time, I have been explaining concepts like rebasing, squashing, and stacked PRs to colleagues who exclusively use git tooling
muti
·3 か月前·議論
Building a selfhosted activity tracker inspired by wandrer.earth
muti
·3 か月前·議論
Unfortunate name furthers the SQLite is "lite" association i.e. underpowered or incapable somehow.

IIRC it is intended to be read as SQL-ite, as having some relationship to SQL.

PG Lite probably makes sense here though, and PGite is not appealing
muti
·3 か月前·議論
Fun. Not sure if this applies on desktop, but on mobile the quick/fast/blazing/skip text often blocks vision of the ball making it harder than it should be to make combos
muti
·5 か月前·議論
Suboptimal - likely. There is some utility: a green letter is more useful than a yellow. Checking for a in two locations when a is a very commonly used letter is __useful__. Still likely much more useful to check for the presence of a fifth letter than a chance at knowing more precisely the location of an a.
muti
·6 か月前·議論
Pay someone to sharpen them for petes sake. I can't fathom why you would suggest that seemingly off hand, secondary to throwing away and buying new knives.
muti
·7 か月前·議論
Active bookshelf speakers with HDMI Arc input are getting more common. Kanto Ren, Kef LSX II, Klipsch The Fives, Elac Debut ConneX

There's also the compact, simple alternatives to bulky receivers that are becoming available: Wiim amp, Sonos amp, Eversolo play, and the cheaper chinese makers like SMSL and Fosi. Each of those brands has a small device the size of an apple tv that will take an HDMI Arc input, and output an amplified signal to power some passive bookshelf speakers.
muti
·8 か月前·議論
Are you looking for solutions within git or jj?

In my experience with jj when resolving a conflict, as long as I do it in the earliest change, I will only have to do it once.

Git has the rerere setting [0] which reduces the need to resolve the same conflict over and over

0: https://git-scm.com/book/en/v2/Git-Tools-Rerere
muti
·10 か月前·議論


  if (!same) {
    return;
  }

  if (!number) {
    return;
  }

  if (!of_braces) {
    return;
  }

  println("but easier to read")