HNHacker News
TopNewBestAskShowJobs

JNRowe

7,427 karma · joined February 3, 2014

username at gmail.com ; Feel free to get in touch.

[ my public key: https://keybase.io/jnrowe; my proof: https://keybase.io/jnrowe/sigs/orH3nyNqAK4vkIpcxn2HRihHPV2HX80SyDwM9cR5xnw ]

submissionscomments
JNRowe··on Standard ECMA-4 Flow Charts, 2nd Edition (1966) [pdf]
Ah, I see. That speaks to why I believe flowchart vocabulary is so common around me. I'm used to working in teams where UML would be largely unknown, whereas the flowchart(or basic BPMN¹) spans the non-compsci folk too.

¹ https://en.m.wikipedia.org/wiki/Business_Process_Model_and_N...

JNRowe··on Standard ECMA-4 Flow Charts, 2nd Edition (1966) [pdf]
Do you have other style standards for whiteboards and such? Perhaps it is the industry I'm in, but the notation in the referenced doc feels super common even if the standard name might not be. I'm thinking about whiteboard scrawls, project requirements, ASCII abominations in email, etc.
JNRowe··on Macamathehou in Lincolnshire and people named Muhammad in medieval England
I think we're in agreement, and the misunderstanding is my fault for attempting humor in my reply. I believe the linked piece is in agreement too, it even concludes with:

> this is a social game of negotiating meaning, and of noticing that language which seems so precise is often not that at all.

JNRowe··on Macamathehou in Lincolnshire and people named Muhammad in medieval England
Perhaps it was the example you were thinking of, but Christopher Danielson really brings home the extreme ambiguity of terms using vehicles and children.

I keep coming back to that every time I'm trying to have one of these conversations with people, especially when the question is deeper than whether a salad is a vehicle(as if that were possible).

https://talkingmathwithkids.com/blog/vehicle-chat-invitation...

or discussed in audio form

https://aperiodical.com/2020/08/mathematical-objects-a-vehic...

JNRowe··on The Source Code Control System (1975) [pdf]
Zeller's design seems to be addressed at least in part by darcs/pijul using the methods described in David Roundy's Theory of Patches¹. A virtual filesystem seems like an especially nice way to solve the interface issues that would arise too.

It strikes me that I treat the result of git-rerere as a ridiculously weak version of this. I'll occasionally carry an unwanted integration branch simply to handle changes that could be managed correctly if there was a better way to express relationships in my tools. Having the functionality baked in to the graph with the associated strictness, and available across clone boundaries would be great.

¹ https://www.cs.tufts.edu/~nr/cs257/archive/david-roundy/Theo...

JNRowe··on The Source Code Control System (1975) [pdf]
After seeing luckydude answer questions on the little thread the other evening, I'm wondering what other things the SCCS/BK folk think we should be doing better. What have we forgotten?

luckydude mentioned real per-file history for example¹, and that pushed me to remember per-file comments as the thing I'd want back.

Perhaps someone is listening.

¹ https://news.ycombinator.com/item?id=26207037

JNRowe··on The Source Code Control System (1975) [pdf]
Following on from some discussions about SCM history on here over the weekend I was poking around in the history of things too.

The original 1986 CVS¹ is quite interesting from a historical prospective. Given that the implementation is just a bunch of scripts on top of RCS you can see how it plumbed together really easily.

There is a note¹ on Grune's site, that explains the relationship between the scripts and the system people would more likely recognise as CVS(assuming you're old enough to recognise it at all).

¹ https://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/usenet/...

² https://dickgrune.com/Programs/CVS.orig/CVS_BB_and_GNU

Edit: And I guess you might not recognise the archives in the first footnote either. They're shar files which can be extracted using the files as a script or more simply with unshar from sharutils³.

³ http://www.gnu.org/software/sharutils/

JNRowe··on Little is a statically typed, C-like scripting language
I've been enjoying this series of "Breakfast With Forth Week", best one yet.

It had left me wondering what had caused it. There was a thread a few weeks ago where the old guard were describing an actual attempt to game the system, and I wondered if we were seeing a version of that being played out.

https://news.ycombinator.com/item?id=25787374

JNRowe··on Little is a statically typed, C-like scripting language
Thanks, although I think you're demonstrating here and in the other comments why you should write a real history.

Was the conference recorded? I've tried searching, but I'm not turning anything up.

As an outsider you get my worthless full agreement on strictness of history, and on solving the monorepo or vendoring dilemmas. My employer at the time of the upheaval was a bitmover customer, and as we slowly switched away one repo at a time it definitely felt like a sideways step. I'd hesitate to say backwards because it did come with some big process improvements for us, but definitely not forwards.

I'd surely have been proud of solving problems with the quality that BK did too. I remember playing with a lot of the open source systems of the time¹, and none of them were in the same league. I'll make no apologies for this sounding like truly weird fan mail.

¹ I'm remembering hg, darcs, monotone, $some_implementation_of_arch, prcs, codeville but there was a lot of people in the space to some degree.

JNRowe··on Little is a statically typed, C-like scripting language
Now that all that isn't so raw, I'd love to know how you felt about the other contenders that were floating about at the time. Were any of them doing things you wanted to see in BK?

I can't be the only one who'd be interested in your views on the general developments for such important tools of our trade. Have you written about it anywhere? I'll pre-order "Larry walks us from SCCS to the git monoculture".

JNRowe··on Variable tyre pressure wheelset is a mountain biking breakthrough
Yeah. I was using a lot of hyperbole in an attempt to get my point across. However, in the time between writing my earlier comment and this I've actually been out for a lunchtime ride on my fixie. Just good fun for a Friday in February!

The response here makes me think there are others who like the idea though, so I'll try to float it in the local CC forum.

JNRowe··on Variable tyre pressure wheelset is a mountain biking breakthrough
I wasn't suggesting removing all technology, as I agree that wouldn't work even if I wanted it. I just liked idea of a parallel low technology track fighting the good fight against pointy helmet disc-wheeled ten rider weeknight TT. Something odd just for fun, like the 24 Hours of LeMons¹ on beaters from the shed.

I'm kind of aware of Keirin from watching track, but wasn't aware of the depth in the local market. That Chris Hoy video was great, thanks!

¹ https://en.m.wikipedia.org/wiki/24_Hours_of_LeMons

JNRowe··on Variable tyre pressure wheelset is a mountain biking breakthrough
At last year's UCI worlds one of the riders(I forget who) had a dropper post failure, and it was depressing watching them slowly lose rank simply because of that.

Part of me wants to see all the new advancements, but I also hate it when it ruins an otherwise good spectacle or personal ride.

We also saw it with e-shifting in road, but that seems to have largely been solved. So, perhaps any problems that should arise with this could be shaken out in a couple of seasons too? </fence>

Maybe there is a market for racing and events where you're only allowed steel-framed, canti brakes, SiS index shift monstrosities? Like one of those sub-$1k car rallies or something.

JNRowe··on Time Team: the rise and fall of a television phenomenon (2012)
As kinda mentioned in the Timesigns note in the article they're all available on All4(the new name for 4od). So UK folks, and people who ahem... have IPs that look like they are, can watch all the episodes for free.

https://www.channel4.com/programmes/time-team

JNRowe··on Parallel Shells with Xargs
Again, here we can rely on zsh having advanced globbing functionality. Instead of moving your test in to the execution block and suddenly having possibly unbalanced parallel groups you switch to something like *(.mw-1) to operate on files(the .) modified in the past week(the m[odified]w[eek]-1) or whatever. I'm choosing mtime because of your %Y, but zsh offers many other filters too. This is detailed in the glob qualifiers section of the zshexpn(1).

I'm not sure whether I'd move the actual branching in because of the balancing issue, that is point where my hairs stand up. Perhaps, this is where it all falls apart.

JNRowe··on Parallel Shells with Xargs
This feels like exactly the reason I prefer using zsh's zargs command for these things. In part because you can use all the extended globbing functionality zsh provides. Something like the following [untested] rework of your pipeline:

    zargs -P $(nproc) -i ***(#i).(pdf|azw3) -- calibre-convert \{\} \{\}.epub
We're firing up nproc tasks, matching case-insensitive .pdf or and .azw3 at any depth, and then batch processing them. zargs is documented in zshcontrib(1).

It doesn't feel that different to your imagined syntax to me, quite whether that matches your mental model better is for you to decide though.

JNRowe··on Coq 8.13
I fear I may have phrased my question poorly. I can understand why you'd gravitate toward there now, I'm more generally curious about how that specialisation came to be in the first place. Was there a specific catalyst? A person or event perhaps.

For example, from my Wikipedia trail I see Maurice Nivat come up in the adviser camp for a few of the more current names.

JNRowe··on Zsh Tricks to Blow Your Mind
Hmm, if you mean the C-g behaviour then you need to set $NNN_TMPFILE:

    nnn() {
      declare -x +g NNN_TMPFILE=$(mktemp --tmpdir $0.XXXX)
      trap "rm -f $NNN_TMPFILE" EXIT
      =nnn $@
      [ -s $NNN_TMPFILE ] && source $NNN_TMPFILE
    }
You can use a static file if you're sure you'll never be running more than one instance.

I'd prefer something like:

    nnn() {
      local tmp=$(mktemp --tmpdir $0.XXXX)
      trap "rm -f $tmp" EXIT
      =nnn -p $tmp $@
      [ -s $tmp ] && cd ${"$(< $tmp)":h}
    }
That will cd to the selected file's directory with enter/right, or do nothing if you simply quit. I guess it depends if you use it for browsing a lot or simply picking a file.
JNRowe··on Zsh Tricks to Blow Your Mind
From the man page:

> The following is a list of all the standard widgets, and their default bindings in emacs mode, vi command mode and vi insert mode (the `emacs', `vicmd' and `viins' keymaps, respectively).

What that means is that if you issue 'bindkey -e' from a bare .zshrc it will enable the emacs bindings and C-q will work. The other two unbound entries state that it isn't enabled by default if you want to use vi-style editing.

The KEYMAPS section in the man page has a full explanation. The easy way to play with it is to start an extra zsh with "zsh -f" so it ignores your configs, call "bindkey" to see what the default bindings are like, then "bindkey -e; bindkey" to see all the goodies that are enabled in emacs mode for example.

JNRowe··on Coq 8.13
Somewhat off-topic, but does anyone know the reason Inria seems to have developed such a specialisation around these types of tools? I get why you'd be there today, but is there a common link/person when that started? If so, I'd love a little nudge about where to find out more.

Edit: Thanks for responses. And a warning to others: don't start following links to advisers and students in Wikipedia, it never finishes.

JNRowe··on Zsh Tricks to Blow Your Mind
You can also operate on the stack of pending commands programatically using the read and print builtins along with the common to both -z option. It can be a really nice way to build up or edit complex commands/variables in combination with expansion flags and such. 'print -z goodbye; print -z hello' for the five second example of what happens.
JNRowe··on Zsh Tricks to Blow Your Mind
You're right, all it requires is a call to compinit from base zsh: `autoload -Uz compinit; compinit` And compinstall can be used to configure things like the case-sensitivity or amount of ambiguity accepted in matches using a nice menu system.
JNRowe··on Who did the Anglo-Saxons think they were?
In last summer's heatwave I was walking home along the old roman routes in Anglia after having a problem with my bike, and with the full-on scorch we'd had all manner of encampments become visible in fields. I found the whole experience of walking in the shadows of people gone for thousands of years quite calming somehow, despite realising I was having to ration fluids and food given any shops you might have found were closed for lockdown.

Just south of Cambridge is the intersection between Icknield Way¹ and Ermine Street², and you hardly seem to be able to stick a trowel in the ground without finding a coin hoard in these parts. You can still walk large parts of it on footpaths and bridleways. Not as pretty as Wales, but nice nonetheless.

¹ https://en.m.wikipedia.org/wiki/Icknield_Way

² https://en.m.wikipedia.org/wiki/Ermine_Street

JNRowe··on Building Replica Amigas to Preserve Digital Artwork
My assumption on bending is no, but I'm assuming that only because I'm sure we would have seen tonnes of stories posted about doing just that if it worked. The retro gamers love curved old screens and love posting weekend makes, so that seems like a valid assumption to me.

I'll also add a reminder to check back here in a few days to see how you've fared :)

JNRowe··on Building Replica Amigas to Preserve Digital Artwork
> faux CRTs sitting atop the non-Amigas. ... in the end, they decided to use a standard LCD behind a milled acrylic lens

Hmm, I'd never considered that. I keep seeing people talking about buying really expensive 90s Sony TVs for retro gaming or resorting to iffy display filters in their emulator, but a clip-on lens could be nice. And frankly, I'm not sure my desk or tables would support one of those 90s monsters anyway.

I'm imagining one of those odd "anti-radiation filters" that were all the rage in the CRT days. Have to remember to check back in a few days to see if any commenters there have posted a workable home solution.

JNRowe··on Zsh Tricks to Blow Your Mind
'bindkey "${key[Up]}" up-line-or-search' is probably the incantation you're looking for if you don't want to use oh-my-zsh or whatever. The $key hashmap is generated by zsh's zkbd so that your config can be terminal independent, but you can insert the actual key if you prefer not to use zkbd or only use one terminal type.

There are a bunch of other search types available, zshzle(1) has all the gory details.

JNRowe··on Zsh Tricks to Blow Your Mind
It isn't shown in TFA, but the zcalc keymap is bindable in the line editor so not only can you use it like qalc/irb/luap/whatever you can also take advantage of any other functionality of zsh within it. Admittedly, you could do some of that with some magic $if/$endif guards in your ~/.inputrc if your REPL uses readline, but the integration is nice functionality if you're a heavy zsh user. I think of it more like the expression register in vim or eval-print-expression in emacs.
JNRowe··on Zsh Tricks to Blow Your Mind
I'd guess that xorcist added a space at the end of the function name because zsh uses =( to specify one type of process substitution. Without the space or an escape for = zsh will error on alpaca128's definition believing you wanted something else entirely.

To that point zsh has some excellent additions for process substitution beyond bash's <(list), but it also makes for yet more weird incompatibilities for when that matters. I only looked at this to start with because I assumed the space was because =() would have been treated as the full path modifier for a command called (), because it would mean that with any other character including other bracket types. TIL.

JNRowe··on Zsh Tricks to Blow Your Mind
I'm a zsh user, and I disagree on it not being much of an issue. It is very easy to inadvertently rely on all manner of zsh-specific behaviour in scripts. Short form logic syntax, builtins with different arguments, internal stat/attr/datetime/etc manipulation, my personal favourite $RANDOM behaves differently to bash in subshells, and much more.

zsh does have the emulate builtin available to help with some basic things, but it is still easy to produce scripts littered with zsh'isms.

However, I do use zsh for personal scripts. In fact, I go so heavy on zsh'isms I know I'd need to rewrite things to share them if non-zsh users are an issue. It is easier to keep track of things that way, instead of tripping over the little easily forgotten quirks.

JNRowe··on Zsh Tricks to Blow Your Mind
If you're looking to go full rabbit hole, the zsh native scripting handbook is good for a few examples. Easy to end up in linenoise if you're not careful though. A fair few really nice zsh things in zdharma's GitHub repos too.

https://zdharma.org/Zsh-100-Commits-Club/Zsh-Native-Scriptin...

← PreviousPage 13 of 21Next →