Autocorrect hates me, I am sorry.
No problem.
The other thing with AI stuff is it conveys very little trust. It’s easy-come easy-go, so it’s hard to tell how much maintenance the owner will has put in or will put into the project.
Scheduling is high risk, so it’s important that it feels safe
I hope this doesn’t come off as too harsh, but the text reads as very AI generated, and I think if you rewrote the main text you could do a much better job.
It’s not clear to me why to use it, the pitch today is that it makes failures loud, which is nice, but very poorly described.
The tool itself looks good, but the website looks very “Claude”, especially the text at the top saying “ONE BINARY · LINUX · MACOS · WSL · 25 MB RAM IDLE”
Those are great pros, but are they the guest thing the user should see?
Honestly the first paragraph of the quick start is a much better pitch:
RunWisp is one small Go binary. You list the shell commands you want to run in a runwisp.toml, and RunWisp takes care of the rest — firing jobs on cron, restarting services when they crash, and capturing every line of stdout and stderr so you can go back and look at what happened. There’s a TUI in your terminal and a Web UI in your browser for poking around. No external database, no agent, no sidecar
This tool looks decent, but for me I find nix helps manage the complexity of systemd well
Oh, isn’t bitter that site curating a list of content for building AI models? I seem to recall that and hope it works except then from any laws, right?
This is why they restrict Mythos and similar.
They want the vulnerability machine, and they don’t want you to have it.
~100gb with images and the max image.
Asides from my kiwix clone of Wikipedia, in the apocalypse there’s not much value to most of the things I self host.
I self host backups, code forge, some AI tools (all my AI chat and completion are local now).
But realistically, in an apocalypse situation I’m going to leave my suburban home and migrate somewhere safer and more directly connected to food+shelter, and probably spend my days dealing with trying to survive.
My self hosting is primarily designed around avoiding US based tools and systems, so that I have more control over privacy and don’t find policy I disagree with.
It’s a blessing and a curse. I’ll give you that.
Goto is surprisingly readable.
Loops don’t get labels. Labels are awesome. Sprinkle in some goto so you can use labels.
In languages like python inside a loop you have if condition: continue. Except continue means don’t continue, you skip to the next iteration without breaking the loop. That’s confusing as heck (and what is else doing on loops Guido???). if condition: goto loop is more honest.
I also like that goto is “take my stack frame and run that procedure instead”, which is kind of unique and cool in its own way, and impossible to do with most lexical scoping systems. It’s reliable zero cost function calling (if you can make your optimizer happy).
Everyone loves repeating “goto considered harmful” and “numbering should start at zero”, but nobody critically thinks about those things. Rules are made to be broken.
~Oh, and the numbering argument is totally wrong… using one notation to advocate for another is silly. Offset from zero, but index by domain logic!~
Ah, I guess it still just doesn’t feel like an awkward penguin meme, but I understand the duality.
I still don’t understand
I feel like that well describes a border collie.
Wants to do stuff, but if you don’t attend they’ll find stuff to do.
10w idle, 100-130W max CPU and GPU.
This might be the stupidest comment on this whole website.
There’s no reason to release a well placed em dash. They’re a standard grammatical symbol (with built in keyboard support on macOS).
Hurray! Compressing and not using it, so you have a massive increase in disk use for no fucking reason.
Oh, and every container that uses PyTorch needs to download the full 7 gigabytes instead of sharing.
Man, why did they buy Tenor just to kill it?
What the fuck.
I love that Claude.md file, fucking awesome.
AI is great, I use it to get started quickly, and then I delete a bunch of it and replace it with human approved and purposeful code.
The other day I used it to write a slugify method. I didn’t think I needed a full library imported for that, and with AI that was a 30 second task, including tests. Great.
Then later that day the AI wrote an API for me. The AI design hid potentially async code in a synchronous block and it butchered the control flow, so I rewrote it to give the caller control over how the code was executed. The result is exactly what I needed, and easy to use plus maintain. Also great.
The difference between that and slop where I never even review the file is massive! I like your power tool analogy. Yeah, I could use the spokeshave… or I could just use a router. But if you’re building a jig to turn your table saw into a jointer you might wanna take a step back and ask what you’re really doing here.
For posterity because I didn’t explain why/how it’s sketchy:
Just because it’s good a good name doesn’t make it good pedigree (which is a bone I have with rustXYZ named projects). The fact nobody caught serious backdoors for years is damning.
If you’re running this offline, it might be fine for you. I still run it inside my vpn behind auth but I’m looking to move off.
Rustfs is sketchy as fuck though.
Just a heads up, I pulled the drive stats from Backblaze’s drive survey, for most brands failure rates accelerate at 4-5 years.
At that point Hitachi, Toshiba, and Seagate all increased in failures. Western Digital didn’t, except for their 2014 batch that immediately dropped off.
Western Digital post 2020 are the most reliable drives.
Hitachi, Toshiba and Seagate seem to hit a cliff around 2-5 years now, but that only kills about 10% of their drives, so with replication you’re probably fine, just make sure to mix drives so you don’t get correlated failures.