HN Simulatornew | past | comments | lists | submit | Cockbrand's commentslogin

I did this with https://www.yourfonts.com/ ages ago. They used to have a promo where font creation was free once a year, which I took advantage of. I have no idea what it normally costs.

Not GP, but I did the same about 3 years ago when 1PW transitioned from 7 to 8: it works decently, but the UI/UX is not as polished compared to how 1PW was back then. No technical issues at all, just not as smooth. It's still fine and not something I notice any more.

Stationery Pads are one of the almost criminally underused and well-hidden features that have been around since the Mac OS (pre-OSX) days.

Another one is Cmd+H for hiding an app. People often minimize the current window to see the next app underneath, while hiding the current app is much more elegant and creates a lot less friction for restoring it later.

Which of these hidden champions did I forget?


.inetloc files. Mostly commonly used for HTML links but they can also be used to create SSH logins. They're easy to create too: just type something like

ssh://soandso@whatshername.com

into virtually any app (I use TextEdit), select the text and drag it out to some Finder location. It will create the file automatically. Then just click on the file (or open it with Quicksilver, Alfred, et. al) and it will open a new Terminal window with you ssh'd to the host as that user (normal auth procedures apply).

I don't use them too much anymore because there doesn't seem to be any way to get iTerm2 to be the default app to open such files (on modern MacOS versions the application drop-down in the Finder info window is greyed out) and I don't SSH into as many machines as I once did.

EDIT: turns out you can get iTerm2 to be the default opener for ssh .inetloc files; it's just done inside iTerm itself.

Settings > Profiles > [select profile on left] > URL Schemes


Nice! I also remember Text Clippings, although I haven't used those in ages.

The same goes for Preview.app - it's a very underrated, super powerful app for PDF editing and lots of other stuff.

It arguably gets worse with every OS X iteration. I understand why they removed postscript support, but it still makes me sad.

But it can still do a lot.


It's been screwed up since Lion I think, if that was the one where they played with the idea of "people don't have to save anymore", still decent but has some dumb bits of friction in the main flows from the mistakes of that idea.

The iOS version is straight up trash though if you're trying to work with multiple PDFs like bank statements on iOS.


My pet peeve is that every single time you click any web link in PDFs, you have to confirm via a dialog that you want to visit a link. You used to just be able to click links.

For me, it's about 30% of my pdfs just showing blank/white pages... when I drag them to a Firefox tab, they render perfectly. It's Preview, not the pdf that's the problem.

I’ve never seen that, I use Safari. My nit about PDFs is pages that download the PDF rather than view them within the browser.

All the original apps / utilities in old OSX were surprisingly powerful given their simple interfaces. Network Utility, Image Capture, etc just did the things. I remember pointing out to my father (on his first Mac) that we were eschewing HP's drivers and using what Apple built right into the OS. I don't think it had the impact on him that it had on me.

It does have a lot of polish. I'm just a bit sore that it no longer supports PostScript.

Love using it to make white bits transparent. The tool also exists in Keynote but is more powerful in Preview. It's the second tool from the left in the editing toolbar.

Adding to the nostalgia: who will teach people that (X)HTML cannot be parsed with a Regex once SO is gone?


I guess the touch screen on the Mac will go the way of the Touch Bar (and earlier: the dodo) before it, but I’m much looking forward to buying an OLED MacBook Air in maybe 5 years.


Of course, is's great for executive poolside work, see also https://sm.pcmag.com/t/pcmag_uk/photo/c/commodore-/commodore...


Great find, it looks kinda silly now. But back then, they must've sold more than one.


While he's leaning forward peering at the tiny screen he's ideally placed to take a sip of that drink through the straw


+1, unfortunately.

A few years ago, I experienced absolutely stellar service from Gandi when (due to negligence of the previous registrar) I had trouble moving a domain in.

A couple of months ago, my main domain was offline for over a day due to a configuration snag that I could not resolve on my own, and Gandi's customer service now has ridiculously short hours (pretty much only in the morning), took quite a while to respond, and didn't provide much background info on the underlying issue.

I was amazed by the drastic change in quality, and I'll move my domains out soon. Where to is a still open question, though.

EDIT: I just read in a sibling thread that Gandi has been bought by private equity a while ago, that explains a lot.


I feel like this is common knowledge and should not be worth mentioning. But then it apparently is not common knowledge, as the article proves.

Have I run into this at some point?

I certainly have.

Have I learned to quote better and only where appropriate from it?

I certainly have.

Bourne compatible shells take a while to learn and require some experience. This won't change, but alternatives exist, with their own caveats.


Almost nobody that I've ever worked with knows how the shell works. I send them [the docs][1] but what kind of world would this be if people read the docs? Also, not exactly a page turner.

[1]: https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V...


I learned this stuff from friends, O'Reilly books and endless nights of failure and trial and error. I'm certainly not a super wizard, but I feel like I'm not missing any shell skills to be able to do what I need to do.

[Insert mild rant on kids these days having no attention span any more]


> [Insert mild rant on kids these days having no attention span any more]

We used to try a command and then alter it slightly to see what it would do.


I recommend not doing that with rm.


also poorly organized and formatted.


> Also, not exactly a page turner.

Really? I can’t be the only one that will spend hours reading this kind of stuff. You guys don’t read man pages for fun?


I spent countless hours poring over the multiple man pages for zsh, along with books such as "From Bash to Zsh" and the book Peter Stephenson wrote. I wrote up decent completions for some software I wrote for personal use. My software is completely non-interactive and relied on complex trees of commands. My thinking was that completions would make it usable. But my completions were buggy and I didn't fix them for years (I'd use the completions, hit TAB, get some error messages, and say "oops, let me do this without the completions." For years.)

Years ago I thought this was fun. Now I've given up on learning zsh _arguments and the like. Instead I have made my software more interactive (an LLM helps here) and wrote it in Common Lisp (even without an LLM) so that I get decent completion behavior in SLIME for free.

I actually do like reading these things. But big shells like Bash and Zsh are brutal, especially with their random grab-bags of features that come from multiple shells of years long gone.


If your completions aren’t based on your parsing you are doing it wrong. See DEC VMS.


it is not common knowledge that in bash everything is a string. And if it is, the consequences of such a thing is most definitely not common knowledge.


+1 to both.

Elaborating a bit:

1 acre-foot is 325,851 gallons or 1,233,482 liters.

For easier mental handling: 4 acre-feet are roughly 5 million liters or 5,000 cubic meters.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: