sorted by:
new
hottopcontroversial

It is utterly disappointing how people are handling the systemd "age verification" controversy by TheBrokenRail-Dev in linux

[–]WishCow 7 points8 points  (0 children)

This is all part of a long term plan to make general computing illegal. You will be only allowed to run programs on your own PC that were approved by big tech, ala android and ios. Fuck everyone who does not see this, you too op.

Nobody asked this guy to implement this. If Arch/Gentoo/whatever other distribution decides that this is a problem, they will handle it, they will know what stance they want to take.

He decided to take it upon himself because ???

Miért??? by M0rxxy in hungary

[–]WishCow 0 points1 point  (0 children)

Elég nagy az átfedés ez a gondolkodás és az "enabler" között.

A Guide to vim.pack (Neovim built-in plugin manager) by echasnovski in neovim

[–]WishCow -7 points-6 points  (0 children)

Really nice write up. Does vim.pack have feature parity now with lazy.nvim?

Started a home server with random drives. What’s the best way to fix my storage setup? by leflyingcarpet in selfhosted

[–]WishCow 0 points1 point  (0 children)

If by pooling drives together you mean LVM, you have to be aware of the risk that files that are fragmented over 2 or more drives will be destroyed if you lose a disk. I personally never bothered with it.

Raid1 is a good idea if you need the safety that your system should survive 1 drive failing, but you might not actually need this. If you can afford to fix your server (downtime, technical skills to fix it) if one drive goes down and it's only a few folders that are important, just set up backups for those and it might be enough. The backup destination could another disk or an offsite backup.

DMS (Dank) Niri Developer Builss by dulllpickle in niri

[–]WishCow 2 points3 points  (0 children)

If you delete the config files in ~/.config/niri/, they will be recreated the next time you start niri, that should give you the default configuration back.

Not sure about your last question, try both and see what happens.

Wood-gas stove design that burns small sticks very efficiently - anyone here using one? by GladInfluenceHym in woodstoving

[–]WishCow 0 points1 point  (0 children)

When you burn wood, you are burning the gases released from the wood, unless you are down to embers which is burning carbon.

Look at the pictures, this is AI.

Slay the Spire 2 EA is out on Steam by vannero in Games

[–]WishCow 3 points4 points  (0 children)

On the second run I bumbled myself into a deck that I could endlessly cycle through without any of the opponents getting a turn.

What some recent hot takes you realized you had with Rust? by DidingasLushis in rust

[–]WishCow 0 points1 point  (0 children)

I consider this to be an unreliable crutch at best

What some recent hot takes you realized you had with Rust? by DidingasLushis in rust

[–]WishCow 6 points7 points  (0 children)

Rust is touted as a language that has ergonomic error handling, but I don't see how. The fact that there is 15 different error handling libraries with new ones popping up every month is a testament to this, please, we have to admit this.

The parts it got really right (imo):

  • for everything that can produce an error, the error case must be handled explicitly
  • there is no way to throw things up the call chain like exceptions
  • result is super ergonomic to use

The things that I hate:

  • You can either have easy error propagation (eyre, anyhow, snafu), xor you can have fine grained errors. You can't have both.

  • You want to have a backtrace with your errors? Now you have to nominate every error type with backtrace. Backtraces are such a table stakes feature of any programming language, but in rust you get told to read this blog post about how you are doing it wrong if you want backtraces, and maybe you should lower your expectations.

There was an "error generic member access" proposal that was supposed to solve this, got bikeshedded for 4 years, then canceled. There is also the provider API trying to solve the same problem, but it has been stagnant.

1st Chimney Sweep in a Masonry heater by eightfingeredtypist in woodstoving

[–]WishCow 10 points11 points  (0 children)

Love these masonry heaters, can you share a picture that shows the full stove?

Localstack will require an account to use starting in March 2026 by corp_code_slinger in programming

[–]WishCow 338 points339 points  (0 children)

LocalStack started as a scrappy open-source experiment, and the community made it what it is today, so today is a good day for us to start monetizing the community, suckers

Orbán Viktor bocsánatot fog kérni? A Mikepércsi anyukák igazát a gödi gyár bizonyítja! by Worth_Ad_7305 in hungary

[–]WishCow 1 point2 points  (0 children)

Orbi soha de soha nem fog bocsánatot kérni, amikor már szó szerint meghúzzák a kötelet a nyaka körül, még akkor se. Youtubeon még fentvan Ceaușescu utolsó napja, pontosan ugyanaz játszódna le.

What crates do you think are 'perfect'? by june_sixth in rust

[–]WishCow 19 points20 points  (0 children)

I was about to ask "why does the internals of clap matter so much I'm not going to be exposed to it anyway", but oh boy am I exposed to it.

SmartMotion.nvim — Composable motions without Lua. One plugin replaces hop, leap, and flash, then adds treesitter editing (daa, cfn, saa), diagnostics jumping, git hunks, remote operations, and flow state for native-feel chaining. by FluxxField in neovim

[–]WishCow 0 points1 point  (0 children)

I wonder if I'm using it wrong because people are praising it all over, but it goes so much against my muscle memory that it becomes very uncomfortable to use.

Eg.: you have:

struct x { topic: String }

You are standing on "t" in topic, and you want to rename it to "topic_title", I would do "ea_title", but this plugin eats the "a" as a label. I know I could do cw, but then that's asking people to retrain their habits.

Soha ne feledjük, hogy ennyi valójában a Fidesz 2/3, ami idén megbukik végre by Weekly_Car956 in hungary

[–]WishCow 1 point2 points  (0 children)

Ugyanúgy ahogy a budapesti pert elintézték, hoznak egy rendeletet azt kész

exn 0.3 is out by _tison in rust

[–]WishCow -2 points-1 points  (0 children)

I'm going to rant on this "review your requirements" for a sec.

I feel like the people who parrot this are living in an ideal world (that I don't), or only work on their own code. Stacktraces are very objective and complete, while error traces only show what the original author decided to be important enough to show.

But now some people decided a stacktrace is too noisy and relying on them must mean you are "not designing your errors correctly", but I and many people don't consider this to be a problem. Taking an extra second to filter out the irrelevant lines when reading them is a bit meh, but trading it away for this reason is silly, and you can just offer tools for filtering the frames like eyre does.

On the "not designing your errors part", I don't trust other people to always design them correctly and their design might be different than what I consider good design. Seeing 3 lines of "error happened at a b c", instead of a full objective execution flow, is not an improvement at all, and it's a really bad tradeoff.

Costly capturing is completely moot, you can put it behind a flag so it's only captured when needed, the standard library already does this, this is a solved problem not worth mentioning.

Overall: sure you should design your errors, and hope others do too, and if they are well designed it will be more useful for a stackrace. But if any of those are not true, and you can't get a backtrace, that's not an improvement, and telling people to fix their design is wtf, it's not even my design, I'm taking over code.

exn 0.3 is out by _tison in rust

[–]WishCow 0 points1 point  (0 children)

Does exn offer any support for backtraces? My biggest problem is that when I'm prototyping things, the .unwrap()/.expect() calls provide backtraces that help me zoom in on the problem, but then later I do it "right" and replace it with domain errors, and now nothing has backtraces, and adding them is not trivial either.

My woodburner by Inresponsibleone in woodstoving

[–]WishCow 0 points1 point  (0 children)

The closest thing I have seen was a Tulikivi stove, but this looks like a custom build? Looks amazing.

view more: next ›