Ah yes I've seen it in those kind of contexts too. Thanks everyone this has really clicked in to place for me :)
HN user
soupshield
E.g. to rm file named “-f”:
I've defintely had this sort of problem in the past :)
Thank you for this brilliant explanation (complete with interactive example :) I completely get it now.
What do we call the "--" part in a command like this:
git checkout HEAD -- <filename>
I find it hard to remember things unless I understand their purpose. It looks like it's specifying an argument but without an argument name (e.g. --verbose), unless it's similar to a pipe | symbol and <filename> is being passed to the checkout command as some special kind of argument?We have extension methods; I would like extension properties.
Can you share how it's doing cpu/memory wise and his it's holding up in general under what I assume I heavy load from HN?
I find it a bit strange that in this system my identity is conflated with my wallet.
My heart is with vim but I switched to emacs as I love orgmode too much for note taking. I tried a few vim orgmode plugins but they seemed quite flakey even though I only really use orgmode for outlining. Excuse my ignorance but could all this LSP/Lua stuff allow neovim to take over from emacs?
MST3K's Tom Servo bears a striking resemblance to the Quasar Klatu robot:
When I switched to Firefox I also switched to bitwarden for password management. Auto-filling is still in beta but I don't miss it. The Firefox extension is fast and simple to use.
Pinboard archives it with wget: https://pinboard.in/faq/
Have you ever had any false alarms with this?
I seen an issue on github[0] which mentions that a lot of development time is still spent on version 3, which is slowing down progress on version 4. I suppose future versions might take longer to roll out if they're supporting the previous version at the same time.
Found some info on this:
0.37.8 is actually a 1.0.1 version of Atom so it's not THAT old. The only difference between 0.37.8 and 1.0.0 release is the remove of deprecated API that were not flagged as such in 0.37.8 release. Reason why Atom only incrementally updates electron is to minimize application breakage due to Atom project's size. [0]
We decide to update to a new version of Electron when there is an enhancement or bug fix that version would enable that would benefit Atom users. Because updating to a new version of Electron is non-trivial, sometimes we skip versions until there is a clear benefit that justifies the cost. [1]
[0] https://github.com/atom/atom/issues/11967#issuecomment-22550...
[1] https://github.com/atom/design-decisions/blob/master/electro...
I almost didn't watch this because it's over my head, but the speaker was enthusiastic and made it fun. It's a shame there wasn't time for questions. I'm now going to watch the original Larry Hastings GIL talk: https://www.youtube.com/watch?v=4zeHStBowEk