It gave me a moment of pause why Rust is part of the equation, but I concluded I'm too dumb
Another solution that "nix" solved years ago.
That's very strange conclusion. I think only person with limited exposure to tech hiring can produce that.
becasue it can be interpreted as acting against the company in first place
what is the difference between this and jiq and ijq?
Not only they become, if they cross specific size, different government agencies are more interested in you as you have impact and they formally or not, trying to force you to apply this tactics.
This GTK/QT flamewar went way too far.
Why not just using nix build system for that, it can create docker images for years now with a great speed.
Literally, there is "show" page on HN where a lot of people congratulates people for their achievements.
nix home-manager is really great at this (and declarative!)
Used custom images with NixOS few times. Works OK.
Why developers? In most cases I know this is responsibility of product people who explicitly want that.
But why to reinvent the wheel if Nix already exists? I guess one reason is cloud feature, but why not extending nix in that case?
yes
I wrote hundreds of those checks in scripts, makefiles, CI and whatever else. After I found Nix (and NixOS) it's ridiculous not to use it. Use it.
Relevant post: https://instagram-engineering.com/open-sourcing-a-10x-reduct...
> This is just silly, I think it is silly to use this one sentence without a context and start arguing. The whole paragraph in the article makes sense, gives context and advice is reasonable.
Any reason not to use `poetry` these days?
I'm using overhive, that uses tmux+Procfile and seem to do the job. mprocs seem a little bit narrow but if somebody adding such a function to the project from scratch, maybe worth looking.
Sorry, but this comment is so vauge and always correct in general (there will never be society agree upon truth). What's your point?
Is it for building AWS Lambda apps or to use lambda as execution environment? I can't figure it out from readme.
That's it. That happens when devs are leveling. At some point, when one finds about "patterns" or other cool feature, they need to put it everywhere, or rewrite everything to "go", or "rust", or "from perl".…
It gave me a moment of pause why Rust is part of the equation, but I concluded I'm too dumb
Another solution that "nix" solved years ago.
That's very strange conclusion. I think only person with limited exposure to tech hiring can produce that.
becasue it can be interpreted as acting against the company in first place
what is the difference between this and jiq and ijq?
Not only they become, if they cross specific size, different government agencies are more interested in you as you have impact and they formally or not, trying to force you to apply this tactics.
This GTK/QT flamewar went way too far.
Why not just using nix build system for that, it can create docker images for years now with a great speed.
Literally, there is "show" page on HN where a lot of people congratulates people for their achievements.
nix home-manager is really great at this (and declarative!)
Used custom images with NixOS few times. Works OK.
Why developers? In most cases I know this is responsibility of product people who explicitly want that.
But why to reinvent the wheel if Nix already exists? I guess one reason is cloud feature, but why not extending nix in that case?
yes
I wrote hundreds of those checks in scripts, makefiles, CI and whatever else. After I found Nix (and NixOS) it's ridiculous not to use it. Use it.
Relevant post: https://instagram-engineering.com/open-sourcing-a-10x-reduct...
> This is just silly, I think it is silly to use this one sentence without a context and start arguing. The whole paragraph in the article makes sense, gives context and advice is reasonable.
Any reason not to use `poetry` these days?
I'm using overhive, that uses tmux+Procfile and seem to do the job. mprocs seem a little bit narrow but if somebody adding such a function to the project from scratch, maybe worth looking.
Sorry, but this comment is so vauge and always correct in general (there will never be society agree upon truth). What's your point?
Is it for building AWS Lambda apps or to use lambda as execution environment? I can't figure it out from readme.
That's it. That happens when devs are leveling. At some point, when one finds about "patterns" or other cool feature, they need to put it everywhere, or rewrite everything to "go", or "rust", or "from perl".…