No, but they do seem to after just 1 or 2 back and forth sessions in email. Maybe a way to hand it off to some enthusiastic scambait or security research people for the reply part? Heck, you could probably set an LLM with the right prompt to write a set of plausible replies to bait them into sending the payload.
> the command basically creates an empty file or updates the file change date if the file already exists, not more.
GNU coreutils touch does a lot more than that. My local copy is about 95k; it allows for choosing from multiple different timestamps to update; suppressing the (default) creation of an empty file if it doesn't already exist; operating on symlinks directly rather than following them (if the system supports it); specifying a custom timestamp rather than "now" (including by parsing a date string), and of course outputting a help message and a version.
And how much of that feature-rich version touch is actual executable code?
I did a quick estimate by disassembling touch with objdump on macOS (163 kB executable), and it was approximately 6 kB (1500 instructions * 4 bytes/instruction). There is a lot more to an executable than executable code.
I was going to suggest that even that logic wouldn't account for a binary size three times the RAM of my first machine, but from the man page:
> DATE STRING
> The --date=STRING is a mostly free format human readable date string such as "Sun, 29 Feb 2004 16:21:42 -0800" or "2004-02-29 16:21:42" or even "next Thursday". A date string may contain items indicating calendar date, time of day, time zone, day of week, relative time, relative date, and numbers. An empty string indicates the beginning of the day. The date string format is more complex than is easily documented here but is fully described in the info documentation.
I would hope that the date formats parsed by GNU touch would still be at a lower level of complexity than the dialect of Pascal supported by Turbo Pascal... but you never know until someone checks.
You'd think they'd put this bullshit inside some .so where it could be reused by all other coreutils; but no, it's re-included in every GNU tool that deals with parsing dates.
It is correct. But only 'date' and 'touch' use it, so I am not sure how much benefit there is in making it a shared library.
If size is really a concern, we have supported building a single 'coreutils' binary since 2014, which will be more effective in saving disk space. It can be done with './configure --enable-single-binary'.
> But only 'date' and 'touch' use it, so I am not sure how much benefit there is in making it a shared library.
There is also the rest of the whole "gnulib" folder inside the coreutils repo. Yes, I know that Gnulib explicitly states in the docs that it's a source code library but it doesn't bother to explain why exactly it chose to be that instead of being a .so à la glibc (beyond some rather unrelated "but supply chain attacks!" segment in the docs — if I cared about that, I'd statically link the relevant parts of glibc as well, in fact, that would be a much higher priority).
Read section 2.2 [1]. Each package that uses Gnulib maintains a list of modules that its program(s) requires. I.e., each package has a different library built as libgnu.a.
Gnulib also doesn't make API stability guarantees like shared libraries do. If a distribution installs Gnulib as a shared (or even static) library, and then links programs to that instead of the vendored sources, they will likely end up with broken programs.
Yeah, I've read the section of 2.2 in its entirety — nothing you said in your comment is in it.
Also, "Gnulib doesn't make API stability guarantees like shared libraries do" — a) do you mean ABI? b) why not? The gnulib seems like something that's perfectly suited to be a shared library, even more so than the glibc, since it's not a language runtime.
Yes, it can be. You can run `strings "$(command -v touch)"` yourself and then compare the output with the strings in parse-datetime.y [0]. Look for e.g. "FORTNIGHT", "sixth", and "error: parsing failed, stopped at '%s'", they're all inside the touch's executable.
Well, guess we have to be grateful that Ulrich Drepper never really got around to mess with gnulib, unlike he did with glibc.
And the .so dependency hell is real. You try to build some older version of a certain language runtime, it complains that your libssl/libcrypt lacks the functions it needs (those functions were in 1.0.1f, but 1.0.1k dropped them because that's how semver works), and of course your distro doesn't have the older version of libcrypt packaged for it so you take the package from the previous version of your distro, and it complains that your libc is too new and segfaults. Well, you sure as hell ain't rolling your system's libc to an older version so you try to rebuild libcrypt from the source, but the build with default config/flags still doesn't satisfy this certain language runtime and oh my god why am I even wasting my time on this, "docker pull certain-language:ancient" it is. Yeah, sure, this image has essentially Ubuntu 14.04 inside of it but at this point IDGAF. Why can the same 6.16 kernel run the user space both from today and from ten years before it, but the userspace from today can't run the program from eight years ago?
> you learn that the benefit in question is actually that the method is less useful than conventional means. … hope for … an actually useful feature of the unconventional method in question.
People write these things, and use these methods, specifically because they don't conceive of usefulness the same way you do.
In this case, the justification offered doesn't mention all the various keybinds that have been pushed down to the "how" section. But clearly the simplicity is a feature:
> D will download images locally, b goes back a page, a will save bookmarks. All of this makes browsing in eww truly enjoyable.
The point is the same as usual for TUIs: you don't have to switch over to the mouse and hunt out a button, as the necessary key is always literally at hand.
People who find this sort of thing "truly enjoyable" (what clearer statement is there of featurefulness!) commonly take it for granted and don't explain the virtues of it very well. That sort of explanation is found in think pieces about TUI design more generally.
TFA describes a goal of avoiding distraction. That is not at all the same thing as "inconvenience and impracticality". Clearly the author finds these keybinds quite convenient and practical. It's just that they don't cover a bunch of web interactions that you perhaps value, but the author doesn't.
You mischaracterise me. I am an Emacs user and I use qutebrowser as my web browser, which uses Vi-like bindings and Python configuration. When forced by circumstance to use other browsers, I use browser extensions to add Vi-like bindings. I find it extremely efficient and enjoyable.
The keybindings aren't mentioned in the "Why?" section of this blog post, and clearly aren't the point of the post. You can get extensions to add Emacs bindings to full-featured browsers, and there's even the Nyxt browser which has Emacs keybinds and Lisp configuration.
The core reason listed in this blogpost for browsing this way is the very fact that it is less featureful and less convenient. As someone who uses Emacs, I know that eww isn't as convenient as a fully-fledged web browser and I know that sometimes the hard way of doing things can be beneficial. I found this blog post disappointing because it doesn't afford you any new information, nor tell anyone about any actually useful features about browsing in eww.
> I found this blog post disappointing because it doesn't afford you any new information, nor tell anyone about any actually useful features about browsing in eww.
Well, for people who haven't previously heard of eww, it's all new information :) Posts like this also exist to market Emacs to people who aren't using it already.
(I've always used vim and it's the model I understand, so my side-project text editor is based on fixing the things I don't like about that model. But Emacs still intrigues me and I'm happy to watch its users and evangelists use and evangelize it.)
This is why I find the whole emacs conversation confusing
You’ll have people who demonstrate their whole set up and interactions and hot keys and shortcuts and everything and then when you say OK well why would you do it like that it all boils down to:
“This extremely precise implementation works for only me and my specific workflow”
I found that it’s almost more useful to think about emacs users showing off their org mode bindings are basically like Warhammer players showing off their painted figurines
I mean, I get what you're saying. There's an element of that with Emacs and super bespoke setups in general, of course.
But also, consider this: maybe they just have very specific, unusual needs that you're unable to relate to because they're very different from your lived experience. I'm not saying this as a criticism. I feel like most people struggle to comprehend just how different someone else's lived experience can be from their own. I certainly do. Usually, when I read these emacs setup blog posts, I'll dislike most of their setup, but often there will be some nugget in there I'll absolutely love, and then I might add that nugget to my init.org.
Let me try to explain my singular point of view. I have very severe ADHD-C, and GUIs always felt horrible for me to use. Especially big complex GUIs. Things like MS Office, Photoshop, big IDEs etc.
Why? Multiple things:
1. Visual processing:
ADHD can include strange visual processing or spatial reasoning problems. It's very hard for me to describe this one in a detailed manner, but suffice it to say, Icons don't make sense to me. Text does. I am capable of learning some icons, certainly, but certain ones never stick. For example, the protonmail web client has the reply and forward button displayed as arrows pointing in opposite directions, I always click the wrong one. Every time. And everytime I'm positive it's the right one and click it immediately. As I'm sitting here now, looking at an HN textbox, I can reason my way into understanding that to the western mind things flow from left to right, and so left should be reply and right should be forward. But when I'm actually there wanting to reply to an email, I hit forward every time without thinking. If on the other hand the buttons just said "reply" and "forward", this wouldn't happen. I can't explain it even to myself really. That's just how my brain brains.
2. I lose my train of thought extremely easily:
You know how sometimes when you walk into a room, you suddenly forget why you're in there? This supposedly happens to most people occasionally. For me it's more like 15 times a day, not just with rooms, but any sudden sensory transition. Like a pop up window. Ah yes. I'm in some stupid baroque GUI program. I realise I need to change a setting. I locate the settings button from the dropdowns, which every program seems to have in a slightly different place, big settings window pops up covering most of the main window. I immediately forget why I'm in the settings. I try to remember why for half a minute, and fail. I close the settings window and try to remember what I was doing before. 2 minutes later I remember which setting it was. I open the settings. I forget why I opened the settings again. Ok, annoying, but not that big a deal right? Oh but you see opening the settings is just the first roll of the dice. The settings window has 15 different tabs. And some of the tabs have buttons that spawn new sub windows, and even some of the subwindows have tabs(looking at you, Microsoft. What is wrong with you people?!). I call it menu purgatory.
3. Extraneous information distracts me very easily.
This one should be self-explanatory
4. My hand eye coordination is not fantastic, so I often click the wrong thing, which then feeds back into the wrong thing, which then feeds into 2 and 3 again. Keybindings don't require coordination, only muscle memory.
On a bad day, with a shitty piece of software like that, I can spend literally half the day locked in a cognitive battle of attrition with the software instead of getting work done. That's not an exaggeration.
Because I'm so hampered by what to other people is just minor annoyances, I need software that I can configure completely arbitrarily. No change can be off limits. That is almost never the case with GUI software, at least without cloning the source and patching it, figuring out the build system, possibly learning the implementation language. With Lisp software, the config file is really just a hotpatch. And Lisp is my favourite language, so yay. I would prefer Common Lisp, but beggars can't be choosers and Elisp isn't that bad once you learn to avoid the footguns. Certainly better than vimscript, which I've always found incomprehensible.
So that's why my setup is roughly this:
Never use GUIs with the exception of Firefox(I want to use Nyxt but I could never quite get past the learning curve, and there are still key features missing) and occasionally mpv(which is barely a GUI anyway). Everything else, find a good TUI. If you can't find one, find a shitty one for emacs and bend it to your will. This keeps (auto-) defenestration at a minimum.
I face most of the same problems you do (though denied a diagnosis by the psychologist I went to) and agree 100%. I'd like to call out Firefox for really never having been a problem in this regard. I can happily use it just as I do a minimal TUI I have tuned for my exact brain. Props to their UI/UX design team for making it so accessible
To be clear, that was the culture everyone was immersed in, but that quote actually comes from[0] one of the people that got banned in the original incident[1]. Not because of the ideology expressed, of course, but because of criticism of the organization's hypocrisy.
reply