The script you posted is only portable in theory and not in practice. Executing it while using a non-POSIX shell like Elvish (even without having it as a default shell) makes it immediately fail.
Meanwhile, `#!/usr/bin/env` is completely portable in the practical sense. Even systems with non-standard paths like NixOS, Termux and GoboLinux patch in support for it specifically.
It is a valid strategy for privately owned companies. Look at Valve—they have their flaws, but they're investing into open technologies and actually improving their product because they know they're sitting on an infinite money printer.
If they went public, no amount of profit would be enough. They would have to squeeze every last cent out of their users for the quarterly reports.
There are lots of ways to cook oysters, which significantly lessens the briny taste and gelatinous texture.
While it's true that their rise in the West was mostly from clever marketing, oysters are just considered normal seafood in many countries and are cooked into dishes.
But yes, the premium price due to the raw oyster trend makes it not worth it if you live far away from the sea.
I'm sure there are some good ways to make it quite palatable but the issue is really the price that makes no sense.
In France, last time I calculated, they are more expensive by weight than a prime cut of beef, that's just dumb.
If they would make cooked products with them at a decent price I could have an interest, but since they make so much money by selling it as a delicacy with a premium price it's never going to happen.
It's just not a very competitive protein source, regardless of the taste/enjoyability and that's the issue in the end...
If you take a peek at the commit history [1], you'll see that the project started only last week with some very vague commit messages. The code is also quite messy and unoptimized. It's a cool project but not exactly industry-level software.
will be tidying/optimising as i use it more.
PRs are welcome! this is totally a tool i made just for me, to solve my problems. hopefully other people like it too.
Right, my bad.
Still, being able to do more to aid the creation and maintenance of packages than just install packages doesn't make something "not a package manager".
When I tried using Gleam, I loved that it came with all the basic tooling I needed and that's what I think is so wonderful about Lux. I don't want to spend my time fiddling around with setting up all the individual tools — I just want to write code. For me, Lux makes the broader experience around building Lua projects a lot more enjoyable.
If I can get lux to deal with the package management scenarios around a few turboLua projects, I’m pretty sure I’m going to ship much more Lua code next year.
It's impossible to parse arbitrary XML with regex. But it's perfectly reasonable to parse a subset of XML with regex, which is a very important distinction.
KDE has a lot of really nice little things, like how you can mute specific apps with a single click just like muting browser tabs.
I've used a variety of environments extensively (Windows, macOS, KDE, GNOME, Xfce, i3, dwm, you name it) and this is basically the one feature I find myself regularly missing from another environment.
reply