It's a blog. It references an interview. The post is also four month old.
"In the Pipeline" is generally a fantastic resource on the pharma industry and chemistry news.
Not really. It doesn't look like a blog, and it's not a person/org's specific blog post. It's just called "blog" in a breadcrumb somewhere, which most people won't read. It's actual a guest editorial, but still - doesn't really look like one.
Yeah, it really is, even if what's linked to is one post rather than the entire blog.
His stuff pops up here often enough. He really does blog at Science. Has for years and years.
If you have a background in chemistry, it's fairly accessible (i.e., he very rarely talks about anything in a depth that an undergrad chem major would have trouble understanding - which, given that most chemists start branching off very quickly in grad school, is roughly the appropriate depth for writing intended for a general chemistry audience, since it's the last common knowledge level).
You can type any part of the path, not just the final part - so, from `/path/to/projects/go/github.com/me/my-cool-app/src`, you could type `cool-app/src` or `proj me cool src` or `cool s`.
Interactive selection is useful partly because you can search iteratively, for less-frequently accessed locations. E.g: I might type `go fwip` because I'm looking for my go projects, and then once I see it in the list and actually remember it's called "my-radical-app", I add `rad` (or use the arrow keys to select) and hit enter.
That sounds like you've already got it pretty well figured out, then. :)
If you did want to get fuzzy-matching in your workflow, I might recommend using building a small alias/function with fzf[1], rather than using zoxide.
Something like `dst=$(cat ~/myprojectlist.txt | fzf) && cd $dst && source sourceme`. You wouldn't get the list sorted by most-frequent/recent like you do with zoxide, but it sounds like that's not what you're looking for anyways.
I'm not sure I see the problem: 'Export', and 'Export as' works as 'Save' and 'Save as'. This i like 'Export to PDF' in a word processor. If you never save in GIMP, I suppose you don't use layers?
The problem is that for those of us that used it since the beginning (1997 in my case), it's a change which broke the workflow which worked for 15 years for zero benefit for any user, old or new. I still get it wrong every time a decade on. The keyboard shortcuts are awkward, and it's all around a bad choice for usability. It has no actual benefit. Its only purpose is for the developers to force you to use XCF in a not-very-subtle manner.
I do use layers sometimes. But all of my input and output images are PNG, TIFF or JPEG and I have no use for the intermediate state. XCF is a non-standard application-specific format which has no use other than with the GIMP. It has its place, but the assumption that it is the central part of the workflow of end users is simply incorrect. It wouldn't have caused so many complaints if it was the case.
Because I'm not exporting but saving, and it doesn't work the same way as Ctrl+S should. If I have opened a file and changed it, I expect Ctrl+S(/E) to override it. What I do not want it to select a file or answer dialogs, asking me if I really want that. And when I close the app I don't want to confirm that I really don't care about xcf and yes, I want my changes "lost". And I especially don't want to lose my changes because I thought that I have pressed (Shift?)+Ctrl+E and that this warning can be disregarded.
I might be wrong in some details because it's been a long time since I last used Gimp without this plugin, but the whole process is so brain-dead that it is incomprehensible how anyone could defend it. I am guessing that if one of the core developers had to manually edit 100 PNGs they would revert their position in a blink of an eye. /rant
