The default animation is also a dealbraker if you plan on switching continuously desktop
2,341 karma · joined October 14, 2012
The default animation is also a dealbraker if you plan on switching continuously desktop
- Cross-compiling is perhaps easier these days, but it's still a pain to set up and takes time to compile
- WASM has compelling sandboxing abilities, I can see myself choosing a slower sandboxed client tool vs native binary, in particular to try out new stuff
I'm loosely following the progress of slint ui (formerly SixtyFPS), anything interesting in their approach or does it strictly matches one of your examples?
Thanks for trying it out!
It's not. `tuc` is a superset of cut and in that particular example there's no difference. If you wanted instead to cut on multibyte delimiters, or on a random amount of spaces, `tuc` would work, while `cut` would fall short
Quite the opposite, early on I started with `clap`, then moved briefly to `argh` before settling with `pico-args`. Compilation time and size where the main driving factors, alonside support for non-spaced values (e.g. -d' ').
Maybe if tuc had subcommands it would have been a different story, but I didn't find enough value in more blasoned arg libraries.
Good question, I struggle to word it properly, any help is appreciated.
Assume a file (we will call it "input"), such as
first line here
followed by second line
You can use a delimiter and cut inside each linee.g.
$ tuc -d ' ' -f 2 < input
line
by
or you can cut it "by lines", practically considering the whole file as your single "line" and using newline as delimiter $ tuc -l -f 2 < input
followed by second line
If you want to remove a line, or keep something inbetween it can be more practical/intuitive than head/tail or sedI'm surprised no one mentioned that there was no personal computer. Where else would you get a computer to develop free software back then?