> It doesn't need a blocker for third-party scripting, service workers ... because the browser's technology simply doesn't recognise these page components
I'd never thought about it like that, but it's a nice side-effect. You don't have to worry about obtrusive JS, if your browser doesn't know what JS is. :D
It's worse than that[0] - Lynx statically renders the page at load time which means any "dynamic" updates just can't happen. I did have a bash at integrating the Mozilla JS engine but gave up after realising that anything more than just `document.write("flange")` handled at load time would need the entire inner engine rewriting and that was/is far beyond me[1].
[0] This is based off my memories of the Lynx source back in the Olden Times, ~1995-2000ish.
[1] But I did do the original cookie jar and colour styles (as seen in the screenshots) work (`lynx.lss` is all my fault, sorry)
> There are plentiful capable US engineers available to be hired
An anecdote, for what it's worth:
My brother graduated from Berkeley last year (CS/Math), and has absolutely struggled to find jobs. His friends have struggled; everyone he's talked to has struggled.
Meanwhile, job postings in the Indian job market (we're both Americans, but are Indian by origin so we tend to keep up with things there) are damn-near overflowing. It's a frustrating position to be in, and it doesn't look like the current administration is going to fix anything.
> job postings in the Indian job market (we're both Americans, but are Indian by origin so we tend to keep up with things there) are damn-near overflowing
The wild part is there is a market between Indian wages and American wages for the H-1Bs.
India has 1.4bn people. It is honestly weird they are not dominating in more sports. Once they really move out of being a developing nation and spend more on frivolous pursuits like Olympic medals I bet they will do just that.
The comparison to street photography is very apt. My blogs are usually a snapshot of how I feel at a given moment in time. Even if they're just technical posts, they often reflect my understanding when I wrote them.
It's also fun to go back a year later to see how stupid/naive/ignorant I was 'back then'.
What if you had constraints on the CSV files? Suppose you knew that they don't contain spaces, for example. In that case, I don't see the problem with using UNIX tools.
Then you're not actually processing the CSV format, you're processing a subset of it. You'll also likely bake that assumption into your system and forget about it, and then potentially violate it later.
Well-defined structured data formats, formal grammars, and parsers exist for a reason. Unix explicitly eschews that in favor of the fiction of "plain text", which is not a format for structured data by definition.
reply