HNHacker News
TopNewBestAskShowJobs

okdana

235 karma · joined September 8, 2016

submissionscomments
okdana··on Why Can't the Left Win?
>Reflecting on what he called “the woke identity,” Freddie DeBoer observed a tendency among some leftists to forcefully reject the work of persuasion.... “A fundamental, structural impediment to liberal political victory is that their preferred kind of moral engagement necessarily limits the number of adherents they can win....”

The American conflation of 'liberal' with 'leftist' is infuriating.

Republicans have twisted the discourse surrounding these concepts so artfully that even many liberals earnestly believe that they're the same thing — that support for legalised cannabis or simply higher taxes makes them 'far left', that vague lip service given to the most milquetoast variety of feminism is 'radical', that subsidised university tuition is 'socialism', &c. Conversely, it's not uncommon to hear (in the context of recent university protests for example) communists and anarchists being referred to as 'liberals'.

It's politically ignorant nonsense and i think it's illustrative of the way that conservatives in the US control the parameters of any given issue. And i feel like that should be one of the biggest factors in any discussion of the prospects for 'the left'.

okdana··on How Three Kids with No Experience Beat Square and Translated Final Fantasy V
Intuitively i'd guess it's something to do with the way children are 'socialised'.

It seems very common for children living as boys to immerse themselves in video games and computers if they're dealing with social isolation or anxiety/depression. It's almost actively encouraged for them to do so — their parents and teachers treat it as normal, most of their male class mates dabble in it, and when i was growing up in the '90s at least video games and computers were depicted almost exclusively as the realm of boys. For trans people in particular i imagine the (semi-)anonymous community aspect also offers some degree of freedom of expression/identity that they often don't have in real life.

Children living as girls are not encouraged to get into games and computers to anywhere near the same degree, and for historical reasons they don't really have anyone to look to as an example or role model in that space.

I've noticed that all of the trans women i've heard of who had supportive parents and were able to start living as girls early on aren't really interested in games or computers. Admittedly, it's a very very small sample size filtered through the lens of what the mass media consider interesting — Jazz Jennings, that girl from Germany, and a few others — but it's a pattern i've seen anyway.

okdana··on Why Slack is inappropriate for open source communications
There's no talk of 'oppression' anywhere in the article.

You understand that 'discriminate' and 'privilege' are regular words with regular definitions that were used by regular people for hundreds of years before you came along with your chip on your shoulder, right?

okdana··on Optimizations in Syntax Highlighting
I can't speak to Emacs, but i know that Vim's syntax definitions are (a) not as powerful as TM's, (b) a nightmare to maintain, and (c) heavily reliant on features specific to Vim's loony regular-expression engine (like variable-width look-around).

My experience is that most syntax highlighters and their definition formats (Scintilla, nano, almost anything that's based on JavaScript) are very limited/naïve compared to TextMate's. It doesn't have to be that way -- TM can certainly be improved upon -- but it is.

okdana··on Threaded messaging comes to Slack
Some other basic issues i have with Slack:

* Spell-checking is semi-broken on macOS when you have more than one system language specified.

* A few months ago they broke the holding-Shift thing when uploading files.

* The fake Markdown is awful. Aside from the fact that the syntax is just close enough to actual Markdown to be confusing — and i realise that's probably not something they'll ever fix, due to inertia if nothing else — the parser is extremely naïve (maybe based on regular expressions?). Notably, it doesn't support escaping, and it has weird issues with certain special characters (for example, it can't render the string `a|b` as in-line code because it contains a pipe).

* The cost for the paid version is really steep if your project/organisation is on a limited budget. I wish they would introduce a lower-priced tier.

* Maybe they aren't interested in this demographic, but a lot of people really want to use Slack for non-business-related purposes, and they've done nothing really to make that easy in terms of administration/management. Many people with this use case are moving to Discord, which is a shame in my opinion because the Slack client, despite its problems, is still (for now, at least) vastly superior for text-based communication.

* I know it's kind of petty, but they haven't updated the client to support the emoji added since Unicode 8.0 in summer of 2015.

okdana··on Show HN: Zazu App – An OSS app launcher, similar to Alfred
I tried switching from QS to Alfred ages ago, since Quicksilver development has been stagnant for over 5 years (it's still being updated, but just barely — mostly just compatibility-related improvements).

So obviously you can deduce from my last sentence that the biggest advantage Alfred offers is that it's actually under active development. New features are added pretty regularly. Just last month they added some new stuff. Nothing game-changing IMO, but it's a massive difference from Quicksilver. (New features occasionally appear in the QS change log, but they're almost universally trivial — for example, in the latest release they made it prompt you for what to do when there's a file-rename conflict. That's the level of 'feature addition' you can expect from QS.)

As a result of this active development, Alfred has a vibrant community. Their developers are easy to reach via social media and e-mail, they have a forum, a blog, tech support people, &c. They have lots of users who like to share their work-flows and settings. Quicksilver's community was once like that, but it hasn't been for many years. I don't think most people even realise it's still around. The Web-site design/structure hasn't been updated since ~2010, giving the impression that the project is abandoned. Much of its extended functionality is buried in esoteric third-party plug-ins, and documentation is often out-of-date or simply non-existent.

Alfred is much prettier by default, its configuration interface is so much more elegant and intuitive, and it's a lot more dynamic in the sense that the UI can be moulded to better suit certain features (for example, the music-player feature adds media control buttons to the interface). The Quicksilver interface is pretty much static no matter what you're doing, and it's honestly not suited for a lot of the functionality people have tried to inject into it (like clipboard management).

Alfred is also vastly more stable and reliable. Hard lock-ups and silent crashes are an almost weekly occurrence for me on Quicksilver, and the auto-updater seems to break periodically, so that every 3 to 6 months i have to go manually download the latest version from the Web site.

With all of that said, i'm still using Quicksilver, and the #1 reason for that is the fact that it handles its own catalogue index. Quicksilver has very powerful custom file-indexing options, so that for example you can control exactly what types of files it catalogues under what directories, how many levels deep it goes, &c. Alfred, meanwhile, uses Spotlight, and only provides global (as opposed to per-directory) toggles for a few basic file types like 'folders' and 'images'. As a result, finding things in git repository directories and similar complex file structures can be very tedious.

The other main advantage QS has over Alfred is that it's free and open-source, which is important to some people... but it's not to me. If it weren't for my very particular file-indexing needs, i would definitely switch to Alfred.

okdana··on Kaspersky: SSL interception differentiates certificates with a 32bit hash
I'm not familiar with WFP (or Windows in general really), so i can't comment on the use of that particular technology, but the fundamental idea here is to man-in-the-middle the user's TLS connections so that the product can inspect or manipulate the data within. Presumably in this case it's for anti-virus purposes, but the same technology is used by schools and businesses to filter pornography, piracy, gaming, phishing, and other 'undesirable' Web sites, to shape bandwidth, and to log Web activity.

The firewall/software generates a root certificate so that it can sign and serve 'fake' leaf (site) certificates on the fly. Because the root certificate is self-signed, however, most browsers/whatever won't automatically trust it, which is why the user/admin has to add the root certificate to each affected machine's browser or OS certificate trust store.

okdana··on Exploring CLI Best Practices
Yes, that's what i was getting at. The use of `cat` isn't useless (for once) — the use of `ls` and `xargs` is.
okdana··on Exploring CLI Best Practices
>`ls | xargs cat | my-util`

lol, this is really turning the whole 'useless use of cat' thing on its head.

okdana··on Exploring CLI Best Practices
POSIX talks about it a little bit: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_...

Some argument-handling libraries like Python's argparse and PHP's Symfony Console generate usage help for you, and they all use a relatively similar formatting that i think was inspired by the formatting of man pages: http://man7.org/linux/man-pages/man7/man-pages.7.html

docopt (http://docopt.org/) is an attempt to standardise it from the other way around — instead of you defining the options in the code and it generating the usage help for you, you write the usage help and it generates the code to define the options. But i don't know that it's super widely used.

okdana··on Exploring CLI Best Practices
Well the argument parser knows that `-u` must take a value, and the only way it can really associate it with its value is positionally (i.e., the value is the stuff that immediately follows it). So it could force you to make the value a separate argument, but that would be a purely arbitrary restriction — it couldn't allow anything but the value to follow, so it'd just have to return an error for the sake of it.

This behaviour is defined in POSIX, btw:

>If the SYNOPSIS of a standard utility shows an option with a mandatory option-argument (as with [-c option_argument] in the example), a conforming application shall use separate arguments for that option and its option-argument. However, a conforming implementation shall also permit applications to specify the option and option-argument in the same argument string without intervening <blank> characters.

okdana··on Exploring CLI Best Practices
>Provide long, readable option names with short aliases.

It's unnecessary, and potentially even burdensome, to provide short aliases for less commonly used options. `ls --quoting-style` doesn't need a short option — you're almost never going to need it.

>Provide a version command that can be accessed by version, --version or -v.

Don't use `-v` for that. It's true that some utilities do, but i think even more use `-V` — including most GNU tools, Python, PostgreSQL, cURL, OpenSSH, iptables, iproute2, procps-ng, just about any Symfony Console app, &c. Even if you don't need a verbosity option right now, you might some day, and it's best to have that work as expected.

>Sometimes your script will take longer to execute than people expect. Outputting something like ’Processing…’ can go a long way toward reassuring the user that their command went through.

If you do print status messages like that, make sure to send them to STDERR if your utility outputs any actual data (like a report or file listing). Same for progress meters.

>Conversely, don’t exit with a nonzero status code if your CLI didn’t encounter an error. Your cleverness will end up confusing and frustrating your users, especially if -e is set.

Using `set -e` is the 'cleverness' here. It's a bad idea in all but a few cases. Also, i'm not sure what qualifies as 'encountering an error', but i think it's perfectly reasonable to return a non-zero status in certain non-error conditions, like when `grep` doesn't find a match, or in other cases where output is valid but empty.

← PreviousPage 2 of 2