pluma

That was an error, thank you for catching it!

There are a few different sides you could take from this article. 1) this could improve flight experiences and help find individuals who are on the run or could cause a threat but 2) like the article discusses, it is invasive and there are no rules with regards to storing and selling bio-metrics in 99% of the states.

Interesting. It definitely didn't seem the case for web dev outside of Rails though. In the mid-2000s it felt to me like the default was Linux (because servers were running Linux) and beginners started on Windows (because that's what they already had at home). But then again web dev mostly meant LAMP (or WAMP for development, via XAMPP).

But this may be a regional thing (so selection bias again). When I was freelancing as a Python web dev, the few places that used Python usually used Plone/Zope (barely anyone used Django or Flask) and there were even fewer places using Ruby except startups. The popularity of Plone/Zope seems to be very much a German thing, just like SuSE Linux and Typo3/Drupal (instead of Wordpress). We've even had a very large Firefox marketshare until fairly recently (because of privacy concerns over Google Chrome).

That said, in European JS conferences over the past five years I'm definitely seeing more and more non-macbooks each year.

It's fine. I'm not going to engage you in an argument about whether policing tone is productive if you don't police content (or the effective politics you produce by what content you do police) but I'm mostly just annoyed that the HN blocklist extension stopped working for some reason.

HN seriously needs a way to hide (mute/block) specific users' comments rather than just relying on moderators or mob voting/flagging to decide what's "appropriate".

I'm assuming you're a native German speaker too? Must be a regional accent thing, then.

The closest I can get to ambiguity by slurring "neunhundertsechzig" is "neun oder sechzig" or "neun, neununsechzig", never "neunundsechzig", and I have to make an effort to speak faster than I normally would even if I was reading out numbers in a hurry. I've also never run into this ("hundert" and "und" being mixed up) in my daily life, so I'm surprised to hear that this is something you hear often.

Selection bias. People who go to tech conferences make up a tiny share of all the people working in the industry. Plus they're far more likely to look towards other people going to those conferences for "trends" than to the majority who don't, thus reinforcing that bias.

Even most designers I know personally don't use macOS. But if I was going by what I see at JS conferences, you'd think Apple has a 99% marketshare (although things have improved in recent years with "full stack" bringing in Linux folks and Microsoft's investment in dev tools making Windows more appealing).

This is similar to how everyone at these conferences seems to have one of the latest iPhones yet (depending on where you live) the majority of smartphone users uses Androids and those who are using iPhones generally hold onto them for years before upgrading.

Also FWIW as a long time JS dev, it seemed to me like Rails actually was one of the major contributors to the macbook monoculture because Rails (in the early days) was popular with startups who also often focused on iOS apps first, which means they had no other choice than to use macOS for development. As iOS became less of a focus than web dev, the macbooks stayed and only now seem to be slowly replaced as Microsoft is making a heavy push into web dev relations and the opinion of Apple's quality gets tarnished by dev-unfriendly decisions and hardware problems.

What you're experiencing indeed doesn't sound like burnout. It's plain old alienation. Big corporations are the prime example for this, small startups generally promise to alleviate this (though obviously this only holds true to a degree unless you hold a significant share in the company).

See also: https://en.wikipedia.org/wiki/Marx%27s_theory_of_alienation

At least having worked in Big Tech you have likely built up enough resources to be able to just do something else now, rather than being stuck in this situation until you can retire (or become physically unable to continue working).

> I come from a law enforcement family, I have many friends in local, state and federal law enforcement roles.

You didn't even have to say that, it was obvious from the lengths you go to in order to excuse the murders and brutality committed by police officers in the US.

You can talk about "but what if a polar bear attacks you" all day but that won't ever excuse why it is literally every week that new video evidence of US police officers brutalising or murdering people comes out and barely any of the officers involved ever are seriously punished for it.

If this violence was inevitable because of the gun ownership, you would see similar events in Canada or Switzerland. If this violence was necessary to protect officers from civilians, you would see vastly more stories about injured or killed police officers in the UK.

That you think your scenario of the muscular angry brute looking for "targets" is even remotely plausible should tell you something. Suspects are suspects, perps are perps, not enemy soldiers or wild animals.

Police officers in other countries are trained to deal with these situations without shooting unarmed people. How little do you think about your friends and family that you think they're incapable of learning how to do that?

Instead your peers get dehumanising pseudo-intellectualism like this: https://www.policeone.com/police-products/training-products/...

Yes, all cops.

If you think using a taser is a way to "deescalate situations", you have a very different interpretation of what a "deescalation strategy" is meant to accomplish than most.

TBH the problem seems to be that US police is often trained to "deescalate situations" by shutting them down quickly and forcefully rather than actually deescalating, i.e. carefully defusing the situation.

Tasers are violent, less-than-lethal (i.e. potentially fatal) weapons. If they're ineffective at reducing casualties and decreasing the overall use of violent force, they need to be removed.

I have no idea how this became the widely held belief about markdown. Markdown is based on Gruber's buggy Perl implementation of a rich text format that's intended to be fairly readable while editing the raw source files. Gruber had zero concerns for how other people would use it, he didn't even support standardisation efforts that tried to resolve the contradictory informal spec he had published.

I used to think that too, but the problem with gun ownership in the US tends to be more about gun culture than ownership. Other countries with high gun ownership rates don't have nearly the same problems, especially when it comes to accidental shootings.

The problem of law enforcement killing people also has little to do with gun ownership. The frequent (or at least frequent enough to be concerning) shootings of unarmed black men for example are generally excused with police officers saying they were "afraid for their lives". This can only either be explained with terrible training or plain old racism (i.e. black men seem more threatening by default to the extent that an unarmed black man is considered more threatening than an armed white man), or most likely a mixture of both.

There's a lot wrong with how police in the US is trained and held accountable. Gun ownership is the smallest contributor to that problem.