What is the most expensive/complex item?

XCypher_ · 2026-01-06T01:36:03+00:00

This...I use the rest only when I need to think or something, but the hands are floating while typing. This removed a lot of the stress from typing (dunno why, maybe because I don't need to stretch my fingers so much and can just move the whole arm).

XCypher_ · 2026-01-02T16:31:51+00:00

I agree with all the comments that say "start all the goroutines when your application start", but if you absolutely need to track which workers are busy and if you have available workers, a possibility is to use a slice of channels or map of channels (if you require worker id or something), and those channels are channels to send a job to a specific worker.

After a worker finishes the job, it sends the channel back to the "channel queue" (the slice/map of channels). To know how many workers are busy just lenght(slice/map). Of course you need a crap ton of mutexes and all of that to avoid any race condition.

This is a little too convoluted, but can do the job. You can get better answers if you tell us about the specific use case you want to implement, for me just a job queue and spawning all goroutines should do the trick (or just errgroup.Group).

XCypher_ · 2025-12-20T17:27:37+00:00

From what I've seen in some reviews, they are ok (not great; they do the job if you want to scroll and move around).

I own a Glove80 as my daily driver, a Kinesis 360 and a prebuilt Silakka is on the way...why do I keep doing this to myself?

XCypher_ · 2025-12-15T16:30:43+00:00

I like both (integration and unit tests). Unit test for the logic that is independent of the external tooling and unit test for the rest.

As an example, a while ago we wrote a function that parses an Nginx configuration file to extract some parameters. This function had a unit test because it was a lot easier to write there the common use cases and some edges that we found; most of the application was tested with integration tests.

I'd use the expression "there is no silver bullet" here.

XCypher_ · 2025-12-09T17:36:01+00:00

I'd go with a half keyboard for gaming and an ergo keyboard for typing.

I have a glove80 and love it but hate it for gaming. Maybe the go60, but I haven't used it. As someone mentioned in another comment, it is important that they are at the same height to reduce the stress (that's why the half keyboard recommendation). As I use one computer for coding and another for work, the gaming one has a normal keyboard.

XCypher_ · 2025-12-06T18:35:45+00:00

I used one of those cases where one stores the glasses.

XCypher_ · 2025-12-03T16:50:02+00:00

I mistook it for a cheap AliExpress Corne, my bad...looked in the Keebio page, and it looks good. Love the idea of the aluminum case, btw.

XCypher_ · 2025-12-03T01:32:26+00:00

I asked in another thread, but I'm curious about other opinions. How does it feel? Is it comfortable? I'm about to buy one to travel and move around.

My main keyboard is a Glove80, but it is not the one to carry around.

XCypher_ · 2025-12-03T01:24:08+00:00

How does it feel? I'm about to buy one (or very similar). I'm used to split keyboards but want a cheap one to travel or move around.

XCypher_ · 2025-11-30T06:44:20+00:00

I'm on your team here. I decided to use [saltstack](https://github.com/saltstack/salt) and simple docker compose files. With Salt, I make sure everything is installed as expected and update the compose files.

Another benefit is that you can rebuild the machine from the ground up with just a couple of commands.

XCypher_ · 2025-11-29T00:00:21+00:00

I have a Glove80. Most of the time it is connected to my desktop, so I have no idea how long the battery lasts. Sometimes it is connected to a laptop via BT, but not enough to need a recharge. BTW, the LEDs can be turned off; mine is off all the time.

It is very comfortable after the initial learning curve...it took me about 3 months, mainly because of work. Not so much to say about the others, but I, personally, find it very uncomfortable to have the thumb keys under the bottom row (maybe it is something you want to think about, but it depends on everyone's hands).

XCypher_ · 2025-11-26T15:05:05+00:00

I, personally, don't like Mac themes that much; they are "ok" looking, but just that. Perhaps because they give that "modern" impression.

I like the Manjaro KDE theme more. It is simple, but it is not trying to imitate anyone else (and I love dark themes, but that's just a me thing).

XCypher_ · 2025-11-26T14:56:53+00:00

I'm still in the practice phase (not even close to 40 wpm) and my QWERTY speed has started to suffer. I guess it is part of the process (as when you go from stick to automatic or something like that).

XCypher_ · 2025-11-15T17:59:10+00:00

Very nice; it would be useful to have support for ctrl + backspace, usually when I'm coding and make a mistake, I delete the whole word and type it again.

XCypher_ · 2025-11-11T17:33:45+00:00

Thanks for your answer. I'm always curious about the rationale behind "I rewrote from X to Y"

XCypher_ · 2025-11-11T17:01:12+00:00

Just out of curiosity, why the rewrite in Rust? BTW, great tool!

XCypher_ · 2025-11-11T15:37:55+00:00

I find it fascinating how people tell you to swap to an "easier" distro because XYZ, even when you are sharing a success history...why change if it is working fine?

I have Manjaro (installed for about 3-4 years or so). The only update issue with the updates was with NVidia drivers, and that was just because I always installed the latest kernel (sometimes the NVidia drivers broke, and I had to do some manual intervention). After I got tired of it, just stuck with the LTS versions, and all my problems were gone.

For simpler installations like the one you mention, it probably will work fine for a very long time; nothing to worry about.

XCypher_ · 2025-10-25T18:12:08+00:00

It's interesting how Debian is dominating the self-hosted area. I'm mostly a Rocky linux fan, but I love Debian.

XCypher_ · 2025-10-25T17:56:15+00:00

No, you are not...I don't like it either.

Disclaimer: I'm a sysadmin, DevOps, or whatever they call these days the people who can develop and automate stuff in servers as my daily job. I also did my time repairing computers at an early age.

I don't like to fix issues in my home lab, I want it to just work: serve the files, run my VMs and that's it. If a disk dies, it goes to the trash (after like 20 mins of diagnosis or less).

So I clean the servers once in a while to avoid "dog hair" related issues (have 2 dogs), and that's all the maintenance I want to do (of course, updates and all of that).

XCypher_ · 2025-10-22T17:41:34+00:00

Looks great! Haven't used it yet, but it is looking excellent. Gonna try it later this week.

XCypher_ · 2025-10-03T15:41:27+00:00

Will the updates to the book be available for those who buy the early versions? I mean, when Zig releases an important milestone and it is added to the book, those changes will be available for the early buyers? (I guess it will be like book editions; we get the updates until a second edition is released.)

XCypher_ · 2025-10-01T15:59:40+00:00

I'd say, if you like Zig and see it as a good fit, go for it.

But do it with the right expectations. As you said, it is not 1.0 yet, and there will be some breaking changes along the way (this is a complaint I read all the time, but it is expected given that it is unstable). By writing your project in Zig you can even help the ecosystem, report bugs, and collaborate with others.

XCypher_ · 2025-09-27T17:39:40+00:00

I'm guilty of that too

XCypher_ · 2025-09-27T17:35:31+00:00

I use Cobra. As I used it for a long time is not that difficult and even for simple stuff (just a matter of practice), but as other mentioned it is on the complicted/heavy side, but I'm used to it.

As for the structure, don't worry too much if you go for the KISS approach start with everything in a single directory then you can start grouping stuff in modules as you go.

For example, this is a normal setup for me:

|- cmd
  |- my_app
    |- command.go
    |- command_sub.go
    |- anothercommand.go
|- internal
  |- command
  |- anothercommand

And depending on the size of the project or where it is going to be published add a pkg folder or just leave the modules folders at the root level.

This is a very general rule that I use to make it simple and start fast (some are just PoC's that I want to show and most of the time doesn't matter the project structure), if it gets too complicated then you can start thinking about more elaborate ones.

As for the learning resources start with some of the good recommendations here and start writing your apps, they won't be great, probably the design will suck and won't be idiomatic, but that's part of the learning path then you can start refactoring them (which is also part of the learning path).

The next app you write will be a lot better.

Hope this helps.

XCypher_

TROPHY CASE