aredridel

How is this better than Voiden (https://voiden.md/download)?

Yeah and the opposite politics are bad, actually.

Almost every word of this is a lie, misleading or poor framing.

Turns out the trolls have found impossible to ignore ways to interact now: they'll SWAT, Dox, and DoS you right out of your life.

Netscape 3 had so.e rudimentary dev tools, and a WYSIWYG editor that were dev tools, abd a JavaScript console.

View source has been around forever. NCSA Mosaic had it.

I did reject two particularly snarky, otherwise contentless messages today. Otherwise I've let nearly everything through.

Twitter = chance meetings as a platform.

Right parsers make this hard, since they can't tell you what they expected at a spot; only what what they parsed could fit into.

Left parsers make it easy, but aren't as powerful.

Marpa gives you everything you need for both -- a table of "what could happen here", and can parse left languages.

yacc = LALR. The tools aren't as interesting as the algorithms.

Another downside of PEGs: The language that a union of PEGs parses can reject constructs that the individual languages support.

Indeed: And most ambiguity is local, and you can apply other, perhaps more reasonable rules to resolve it than a parser forces you to make.

Indeed -- and we now end up with LL languages, which are a pretty weak grammar class. We spend a lot of time binding our minds to computer languages than computers to understand something more powerful.

Sure! All nodes will be consistent in that your balance is what they all think it is, and that the attacker's balance reflects the attack. But unless those actions are coupled in a transaction, each account may not be consistent with the other.

Maybe, yes and no, respectively.

Loathsome pop-psych, loathsome relationship pattern ... and redeemed by turning it on its head. Well played. Had me hate-reading in the middle and happy by the end.

wat

Yeah. unfortunately, people are DICKS a lot. That's what we're trying to fix.

Indeed. Any with conclusions that support dismissing women in tech?

A white man can be smart, kind, caring and sharing and have troubles of his own. But white MEN are privileged and you know it </meninblack>

THIS.

From the study abstract:

"Men and women apparently achieve similar IQ results with different brain regions, suggesting that there is no singular underlying neuroanatomical structure to general intelligence and that different types of brain designs may manifest equivalent intellectual performance."

So as always, MUCH more research needed before drawing that conclusion

You're really into protecting your rhetorical devices, aren't you?

It's not easy. Call it out. Respond to the biases that come from that position.

Yield the floor to those with less structural support when speaking. Encourage people who are ordinarily excluded. NOTICE AND CALL OUT. Use your privileged position to help where you can, and step out of the way when you can't.

It's pretty powerful when a room full of dudebros is silenced by the one guy who says "Uh ... that 'Aunt Tillie' you're designing for is actually damn smart, just hasn't used a computer yet" or "Uh, guys, you're forgetting HALF THE POPULATION". Or "That was sexist, jackass. Don't ever do that again." Or "Maybe we should acknowledge that having people who have families and would like to see them might like to participate here."

Some of these are actual statements of differing values. They are sharp instruments on wall of the bubble of the echo chamber. They're powerful.

And then, when you've women on your team, listen to them. Remember that status isn't conferred as readily on us. "She's just a junior dev" ... well, yeah, and might have been passed for a couple promotions. When you go out for an expensive meal with folks from a funding firm or industry cohorts, remember who might have had to check their bank balance before coming and may have passed. Try to include those voices. Call 'em up. Offer to pay for a meal -- or if you're in a position of company power, fix it structurally by making it not an individual problem.

And look for sources of bias and privilege. Don't just focus on women. Look for all the myriad ways that you can explain how someone ended up in the social heirarchy how they did, and think long and hard about what's fair. It won't feel nice if you came out on top by accident and you'll try to explain it away. Don't.

Even more telling is when you fail: What are the repercussions of failure for you? What might the repercussions for a woman on your team be? Are they different? That's an especially telling place to look, and it explains a lot of why women are paid less: their risks are bigger for the same gains.

Do spend your life checking it. Don't spend your entire life keeping your experiences to yourself: just be aware that your experiences aren't universal nor even prototypical. Don't be the default voice. Just a voice.

It is. You have less to lose than the average woman in the same spot.

We get fired, we get DEMOTED when asking for a raise. We have a lot less to negotiate with. So we stop when it's tolerable, because the stakes are different for us. We have to be the absolute top of our game to compete.

But a lot of us notice. A lot of us notice that it's usually 'he'. And a lot of us notice that that's not for us.

I see no problem with it. It's a word I've used my whole life...

Because it's very reasonable and not a problem.

It's a start. It costs you very little. Do it!

Posting on hacker news an starting a flame war might cost a lot though.

'they' and 'zie' are both awesome. One of those tends to garner no strange looks too.