pzmarzly

Seems like a bug in benchmark code for that test, opened GH issue https://github.com/fenio/modern-fs-benchmark/issues/35

xfs is by far the slowest in "ftruncate empty file to 1G" but the fastest in "ftruncate 256M file to 512M" - does anyone know why?

Why do people say SolidJS has no compilation? SolidJS 1.0 was already doing much more at transpilation time than just changing <h1> to h("h1"), and SolidJS 2.0 has a package called @solidjs/compiler: https://npmx.dev/package/@solidjs/compiler

1. A Windows app to change volume, brightness, switch input. I used to have PC connected to TV. I also was considering making Android app to replace my TV remote.

2. https://github.com/webosbrew/youtube-webos

3. https://github.com/MoazSalem/litefin

4. I promised myself to install LEDs one day https://houndhillhomestead.com/diy-ambilight/

If LG ever removes or restricts Developer Mode, I am selling my TV the same day.

> Personally, I think putting an interoperability protocol implementation behind a copyleft license is a little unfortunate!

Huh, haven't thought of it. Just relicensed ancs4linux to MIT.

They are not TB5 compatible though, and if you are going to drive monitors through it, or connect external GPU, 120Gbit (TB5) is much better than 40Gbit TB4 gives you. If you are willing to pay a bit more, consider TB5 cables from CalDigit, StarTech, CableMatters, or Apple.

I would like Zed to have feature parity with VSCode from 6 years ago. Working well over SSH or WSL, which it currently doesn't, is a part of that, even if I don't use that everyday.

I am a paying user, and have no plans to stop supporting them financially, but I wish they locked in and went through GH Issues queue, starting from the oldest.

One of the YouTube comments pointed out the issue is most likely the lack of support for SMB Direct (RDMA) in macOS. Would be nice to repeat the test on a Windows/Linux laptop.

Does it work across forks, or is it same repo only (like gh-stack et al)?

You might like https://uncloud.run/

That's what Thunderbolt 4 and 5 cables essentially are - USB-C cables with guarantees on speeds and PD power.

22B transactions a year mean an average of ~700 QPS for the NPCI switch. Of course the traffic is not uniform, it probably peaks at many times that number, but that still doesn't sound that bad - for comparison, a quick Google tells me Nasdaq TotalView ITCH feed peaks at 100k+ QPS at market open.

I hope they introduce some sort of public read-only view that an admin can enable. Discord has https://www.answeroverflow.com/ and https://www.linen.dev/

That would enable private repos on https://tangled.org/ , right?

> The range of things that can run an http server is much bigger than tftp

Don't go too crazy though, these UEFI HTTP clients are not well behaved. For example, last time I checked, EDK required the URL to end with ".efi", instead of checking Content-Type header.

That doesn't mean it's a bad idea, Building-Integrated Photovoltaics are its own market of products. But you have many much cheaper options there, at least in Europe. For example https://solroof.eu/en/discover-solroof/what-is-solroof/ or https://metsolar.eu/products/bipv-roof/

Does anyone know what changed in iOS 16.5 that made Google stop requiring the app? To me it seems to correlate with Private Access Tokens, aka remote attestation by Apple. https://developer.apple.com/videos/play/wwdc2022/10077/

TIL, and they look great indeed. Shame they are all sold out except for <= 0.3m lengths. https://global.lttstore.com/products/ltt-truespec-cable-usb-...

IIRC a few years ago I saw some store asking for 6 or 8 digit BLIK codes, I guess the latter was how they were planning to expand from supporting just Poland to supporting whole EU. But that effort seems to have died out.

https://tangled.org/ supports many jj features, but they seem to only offer public repos.

Jujutsu equivalents, if anyone is curious:

What Changes the Most

    jj log --no-graph -r 'ancestors(trunk()) & committer_date(after:"1 year ago")' \
      -T 'self.diff().files().map(|f| f.path() ++ "\n").join("")' \
      | sort | uniq -c | sort -nr | head -20

Who Built This

    jj log --no-graph -r 'ancestors(trunk()) & ~merges()' \
      -T 'self.author().name() ++ "\n"' \
      | sort | uniq -c | sort -nr

Where Do Bugs Cluster

    jj log --no-graph -r 'ancestors(trunk()) & description(regex:"(?i)fix|bug|broken")' \
      -T 'self.diff().files().map(|f| f.path() ++ "\n").join("")' \
      | sort | uniq -c | sort -nr | head -20

Is This Project Accelerating or Dying

    jj log --no-graph -r 'ancestors(trunk())' \
      -T 'self.committer().timestamp().format("%Y-%m") ++ "\n"' \
      | sort | uniq -c

How Often Is the Team Firefighting

    jj log --no-graph \
      -r 'ancestors(trunk()) & committer_date(after:"1 year ago") & description(regex:"(?i)revert|hotfix|emergency|rollback")'

Much more verbose, closer to programming than shell scripting. But less flags to remember.

I guess one way to protect yourself from this would be to use another IAM solution for SSO login to Google Workspace, but is there any reasonable choice for small businesses other than Entra ID or Okta?

You will run into problems if destination drive has different sector size than your VM, as GPT header won't be aligned.

QEMU defaults to 512B sectors, which isn't true for many NVMe drives. There are some flags to change that. https://unix.stackexchange.com/a/722450

I think it should be possible to make an image with many headers at different locations, so that it works on all types of disks at once, but I don't think any tools do it for you by default.

I haven't tested it, but this should be slightly simpler, and work better for subsequent review iterations (reviewing what changed once PR is updated):

    jj new main -m review
    jj new -m pr
    jj git fetch
    jj restore --from=big-change@origin .

Then keep squashing from `pr` to `review` as described in the article. When the PR gets a new version, rerun the last 2 commands.

The article should have also emphasized that GitHub's issues trigger is just as dangerous as the infamous pull_request_target. The latter is well known as a possible footgun, with general rule being that once user input enters the workflow, all bets are off and you should treat it as potentially compromised code. Meanwhile issues looks innocent at first glance, while having the exact same flaw.

EDIT: And if you think "well, how else could it work": I think GitHub Actions simply do too much. Before GHA, you would use e.g. Travis for CI, and Zapier for issue automation. Zapier doesn't need to run arbitrary binaries for every single action, so compromising a workflow there is much harder. And even if you somehow do, it may turn out it was only authorized to manage issues, and not (checks notes) write to build cache.

From website's FAQ:

Acme is currently available in the United States (including Hawaii, Alaska, and Puerto Rico) and Canada.

Decentralized or direct P2P micropayments are unlikely to work, true. But why are there so few attempts at centralized micropayments providers? The only success stories I see in the space are GitHub Sponsors and LiberaPay, where their entire thing is aggregating payments together (so you have 1 big card transaction a month per user, not 20 small ones) and doing KYC procedures with donation receivers (once GitHub, or rather Stripe, says you are legit, you can take money from any GitHub user).

I was once blown away by iPhone 8 editing capabilities. The keyboard seemed to work OK (minus swipe-to-type, but that wasn't great on Android either), and using 3D Touch to move cursor and select text was the most pleasant text editing experience, even better than on the desktop (arrow keys and vim hjkl).

And then it was all removed in a software update.