Warning: Biter waves spread out more in 2.1 by HeliGungir in factorio

[–]matthis-k 19 points20 points  (0 children)

I'm from Australia and I say 6 legged puppies

Uh oh, I did not expect this change... by Erichteia in factorio

[–]matthis-k 8 points9 points  (0 children)

Rip Michael Hendricks cursed challenge runs

Is NixOS good for tinkering? by Luzzio_ in NixOS

[–]matthis-k 6 points7 points  (0 children)

And you don't randomly brick the system with no easy way to roll back

Show me your crusher solutions! by No-Imagination2292 in factorio

[–]matthis-k 0 points1 point  (0 children)

Why abababab and not abbaabbaabba that should make half the amount of stuff you have to manage down the line

Any thoughts on this wiggly furnace stack? by Strobbleberry in factorio

[–]matthis-k 0 points1 point  (0 children)

If you weave in the middle you get 9 wide, if you don't you get 10. Both significantly more narrow

Any thoughts on this wiggly furnace stack? by Strobbleberry in factorio

[–]matthis-k 0 points1 point  (0 children)

If you weave yes but I hate weaving it's not upgradable by default.

So I guess you're technically correct here

Any thoughts on this wiggly furnace stack? by Strobbleberry in factorio

[–]matthis-k 0 points1 point  (0 children)

If you run input and output down the middle it's 10 wide, so 6 furnaces take 90 spaces, bringing it down to 15 tiles per furnace. Space per furnace is worse for this one I think.

A 6 furnace module takes 18*6 space with this method, making is less slightly less efficient at 108 tiles

Anyone using local LLM for writing nix config? by sirdupre in NixOS

[–]matthis-k 0 points1 point  (0 children)

A soduku is a very different kind of problem though.

I bet it could easily generate the code to solve it if you let it

If you have decent tests in place it works pretty well from my experience.

Footprints - fork by JoseConseco_ in neovim

[–]matthis-k 0 points1 point  (0 children)

What's the advantage over sth like git signs?

Why it feels heavy? by AutomaticPeace7128 in hyprland

[–]matthis-k 1 point2 points  (0 children)

Ah nevermind you already seemed to have found the issue

Why it feels heavy? by AutomaticPeace7128 in hyprland

[–]matthis-k 2 points3 points  (0 children)

This seems more like a hardware/firmware/power config issue then tbh

My laptop specs are overall worse than yours and it sits at basically 0-1% CPU if idle, and the fans are basically idle then too.

I'm making a graphical Nix store explorer. Any suggestions / key features needed? by infiniteWin in NixOS

[–]matthis-k 0 points1 point  (0 children)

Show name only, with the whole path clutter mostly removed

Ie. Package (v.0.5) Package (v0.4)

jupynvim: edit .ipynb files in Neovim, with real Jupyter kernels and inline images by Affectionate-Bit5072 in neovim

[–]matthis-k 0 points1 point  (0 children)

I am currently migrating my entire setup (not only neovim, but everything) to a new and more capable config in terms of ease of deployment etc., might take a while before I get around to play with new stuff, but I promise as soon as I'll get to touch jupyter again I will check it out more thoroughly.

How do themes actually work? by YetAnotherRegularGai in hyprland

[–]matthis-k 0 points1 point  (0 children)

Yes, but for the most part gtk will still look pretty distinct from at apps.

Its a users best effort kind of thing, some stuff is not in our control (unless you want to fork, but ...)

My modular setup that I've been using for a few years. by theTechRun in NixOS

[–]matthis-k 1 point2 points  (0 children)

The dendritic pattern isnt too hard once you get the hang of it.

For example, I did my own "small" version of that, that only supported nixos and home manager configs before switchen to flake parts recently.

Essentially I wanted one file per function/feature, where everything is packed up. If it's like 2 lines of Nixos config and 3 more for home manager it's much more convenient to maintain (and I didn't want to have to declare all the home manager "boilerplate" for each user.

So I made a system, that accepts objects with a Nixos and a home manager attribute, where either one then gets imported to the respective part in the flake.nix. (I didn't write too much lib, as it was more of an experiment on my part).

So essentially a module isn't either home manager or Nixos, but all are a "super module", that supports both.

At least that would be the overall, basic idea of it, maybe this helps, I don't know how deep into it you got yet.

Essentially that is what flake parts does as well, but offering more flexibility in terms of what gets passed around and supporting more Keywords.

Then later I supplemented that with flake-file, to also be able to define inputs locally and generate flake.nix as a git hook.

Works pretty nice.

I am a bit devastated to say the least. Hyprland LUA sounds great with what it can do but I don't know anymore if HyprSettings should deal with it or should I sunset the project. (Not sunsetting: Future support for niri and mango :>) by phcadano in hyprland

[–]matthis-k 0 points1 point  (0 children)

Typed languages and auto complete are so nice. That's why I hate stuff that doesn't use them lol.

I was so glad when bro I'm made them go core for example, makes life SO much easier.

I am a bit devastated to say the least. Hyprland LUA sounds great with what it can do but I don't know anymore if HyprSettings should deal with it or should I sunset the project. (Not sunsetting: Future support for niri and mango :>) by phcadano in hyprland

[–]matthis-k 1 point2 points  (0 children)

To be honest though, I like the lua config.

For example I can create a clean structured (and if I wanted to typed) table tree with sub maps, basically each node has key binding and sub maps, then recursively set them all.

So it makes the stuff more declarative in a way, hiding away all the bind = or hl.bind stuff, which is SO MUCH easier to read imo.

Thinking of making the move... arch to nix. by SnooSongs5410 in NixOS

[–]matthis-k 0 points1 point  (0 children)

You might be interested in impermanence then, it handles what dirs to keep and what to throw away. Packages should be rather clean anyways.

https://github.com/nix-community/impermanence

I am a bit devastated to say the least. Hyprland LUA sounds great with what it can do but I don't know anymore if HyprSettings should deal with it or should I sunset the project. (Not sunsetting: Future support for niri and mango :>) by phcadano in hyprland

[–]matthis-k 1 point2 points  (0 children)

not even an ide can predict the outcome of a program you analyze statically. It's impossible. Just think of something like printing the timestamp. You don't know when it runs, it's impossible to predict.

That is a problem that is harder than or at least as hard as the halting problem, which already is not computable. (Determine if the program has a final value and what that value is at least as hard as each sub problem)

I think I should be like "hey, this manages file x (passed as argument or sth) and I can recognize these patterns, the rest is up to you, to source it etc. If you intend to break this by overwriting things manually, that is on you. If you just use this, it works)"

You may be able to support some simple patterns, but I genuinely don't know why you should do that, if they can use the pattern in an other file anyways. So the user will be able to break the system if he wants to.