skysight-inc/HackerNews huggingface dataset:
Unionization takes public support, it's not something done in isolation (hence why there's all sorts of articles about Kickstarter's attempt and unionizing - they need support). Public support is a zero-sum game, therefore unionization is a zero-sum game.

If I give my limited attention to this unionization effort, then I may not give it to someone else. And maybe there is a workforce who doesn't have the eye of the internet who are trying to unionize, but now kickstarter has taken all the space for that news category.
Your parent is suggesting, correctly, that the place to add housing density is inside the city (of San Francisco) itself.

It is neither noteworthy, nor harmful, that Santa Cruz maintains itself as a "bedroom community" if there is plenty of density where it belongs: in the city.
I'd argue that modern day issue of loneliness is an urban design problem way more than it is a technology problem.

The suburbs are isolating, and building strip malls instead of walkable downtowns (for both suburbs and denser areas) just adds to that. We pushed for the quiet and privacy of suburbs but took it so far that we eliminated the human interaction.

We need to start prioritizing spaces and urban design that encourage social interaction. Build walkable downtowns around commuter rail stations. More parks, coffeeshops, community spaces to suit different hobbies, etc.
The 407 is privately owned (another Conservative government debacle) and makes very little for the provincial government except maybe HST.
That is not how IP valuation works. The internal cost is not the measure; the potential or actually sales/licensing value of the IP is the measure.
And that's why I think the author is wrong about this (he is probably right about thinking (more often) about filesystems as databases, but that's somewhat orthogonal).

The approach you're describing only works for POD-style "structured data". Once you start using OOP of almost any type (though not every type), you no longer have ... well, POD that you can move to/from a storage medium. You have objects whose in-memory format IS important and compiler dependent.

There are other concerns too. His WAV example (I write pro-audio software for a living) doesn't even begin to touch on the actual complexities of dealing with substantial quantities of audio (or any other data that cannot reasonably be expected to fit into memory). Nor on the cost of changing the data ... does the entire data set need to be rewritten, or just part of it? How would you know which sections matter? Oh wait, the data fundamentally IS a byte stream, so now you have to treat it like that. If you don't care about performance (or storage overhead, but that's less and less of a concern these days), there are all kinds of ways of hiding these sorts of details. But the moment that performance starts to matter, you need to get back the bytestream level.

And so yes, there's no standard API and yes the lowest common denominator is byte streams ... because the __only__ common denominator is byte streams. Thinking about this any other way is a repeat of a somewhat typical geek dream that the world (or a representation of the world or part of it) can be completely ordered and part of a universal system.
I have to disagree.

> Some of the women even had stories about reporting the exact same manager I had reported, and had reported inappropriate interactions with him long before I had even joined the company. It became obvious that both HR and management had been lying about this being "his first offense", and it certainly wasn't his last. Within a few months, he was reported once again for inappropriate behavior, and those who reported him were told it was still his "first offense". The situation was escalated as far up the chain as it could be escalated, and still nothing was done.

Management was sexist and the structure was kept unchanged and unchecked by HR. The jackets event, in addition to others mentioned in the post, are an extension/demonstration of that behavior.
It seems like Boeing (and the FAA and the industry more broadly) have been hiding behind the veil of the "zero commercial accidents" streak for however long that was happening while aggressively trying to coverup serious problems.

It's great that everyone is finally doing a deep dive to figure out these problems. We need more of this, more critical thought and curmudgeons and people who assume the statistics are wrong.
Boeing 737 Max
I worked at a company for a while that had a pretty good take on this, IMHO.

First, the take home test was relevant to the sort of work one might actually do in a reasonable time frame. (Read a csv input file, hit an api per record in the csv, then merge that info and output an updated csv.) Could theoretically be done via shell script; my submission was ~100 lines of python.

Second, submissions were graded mostly for correctness. Style/structure and all the other stuff were nice but usually weren't deal breakers, iirc.

Third, the on-site included a session where we reviewed the submission with the candidate, asked questions, etc... This was pretty instructive, because we could point out a missed edge case or whatnot and see how they'd modify the code to handle it.

Fourth, names & personal identifiers were scrubbed from submissions, to avoid potential bias.

So, it was a better than average process, IMHO. That said, after reviewing a fair number of coding tests myself, I'd note that there are still a number of downsides to take home tests:

a) even if the instructions specify that one should take less than N hours, it's obvious that some applicants spend considerable time on them. So we'd see solutions of wildly differing quality; some with detailed unit tests, documentation, Dockerfiles, vagrant files (!), build scripts, etc... etc... some with just a single file.

b) Even though the primary criteria was correctness, there was some room for assessment of code quality, and subjective bias of the reviewer was undoubtedly a factor. A solution that missed an edge case but which was well structured would generally be fine, but "well structured" is obviously subjective. Or, although applicants could use "the language of their choice," those selecting, say, Java, were at a disadvantage. Most of us were Python/PHP/Ruby folks and the Java submissions looked generally bloated in comparison, and seemed to be graded more harshly.

Not sure what a perfect solution would look like. To resolve issue a) one could impose a strict time limit or use HackerRank or whatnot, but that would create time pressure and up the anxiety. For b) one could rely on purely objective criteria, though that may create other unforseen problems.
GitHub: Increased Error Rates
You can't use rand() to compress a file
Nah, I still can't set up a linux that's both graphical and feels snappy to this day.
Sure, I understand why people want to. I just think it's a futile effort. In order to determine whether bankrupting 1000 people is worse than killing 1 person you have to quantify all those variables, including the value of a human life (an actuary will gladly do that for you). By some measures, say economic impact, killing a single person may not matter at all, depending on who they are. What people want is to quantify morality. Good luck.

However what we do see that correlates to some "badness" metric is the punishment we mete out for crimes. Years of imprisonment is a simple, linear measure that can be used to measure crimes against one another.

You see it all the time. So and so killed a person and got X years in prison, but this other guy ran a Ponzi scheme and got Y years in prison. Whether X is greater than Y, and your viewpoint, will determine if you think that's fair or not. But my original point is I think it's a rather pointless determination to begin with because it isn't really telling you anything. It doesn't answer the question of whether one crime is worse than another because that's fundamentally a philosophical question that I don't think can be measured.
Surfly Now Available for Nice InContact CXone
Luckily Germans like paperwork and statistics:

https://de.statista.com/statistik/daten/studie/76211/umfrage...

Can't speak for US / world. But I assume it's very similar.
I completely agree, I'm never setting my feet on a new Boing again. The certification they receive is mostly done by themselves anyway.

I might have been lenient if it was one issue but it issue after issue and it's not just design of the plane, it seems the whole company is rotten to the core.
That may have been true circa 2010, but in the past decade we've seen rich settings menus and compact, information dense interfaces stripped away in favor of "mobile first" designs.

Typically, whenever a website / program I use gets a UI update, the only change is that all padding on buttons, text, etc. has been increased by 50% meaning I need to scroll in order to see a 5-item list! Windows 10 control panel is an example of this phenomenon.
The general value of typed functional programming lies in leaving no edge cases
> and white men in particular

It's difficult for a man to experience sexism at the level a woman does for the same reason that it's nearly impossible for a white person to experience racism.

Going this out of your way to "defend" white men is in direct opposition to the cause of feminism and fighting racism for a simple reason: centrism favors the status quo, and the status quo is still in 2020 that a baby born in America white and male is among the luckiest babies in history. They don't need defenders like you. They're good.

> I know HN is filled with white knights that are ridiculously enough are okay with sexism against men so let the downvotes rain upon me.

I downvoted because of this bad faith portion of the comment. I'll eye roll whenever someone says some shit about white men being, lol, oppressed, but on this forum there's an expectation of actual good faith conversation. It's obvious from this portion of your comment that you're not looking for that. It seems to me you threw yourself into the midst of a relatively socially liberal forum, found a pole to climb, and are now trying to martyr yourself up there.
"I disagree with how it works" ≠ "It's a bug"
Agreed. If you account for second-order effects, the result could look pretty grim. That's why I'm of the opinion that some white-collar crimes can absolutely be worse than violent ones - including murder - and that they should be punished accordingly.
> For example, in this very thread

Can you provide quotes and/or links to examples?
I read it. The article is superficial and one-sided. And there is nothing wrong with companies building their own tools. There are many such companies, including SAP, Microsoft and Google.
> - Why Canadians keep the Ford family in power

The rest of Canada is not keeping the Fords in power.
Here's a local example from Waterloo Region— Feb 2017, cyclist killed by motorist exiting the highway:

https://kitchener.ctvnews.ca/cyclist-dies-after-being-hit-fr...

A year later, all charges dropped on account of an apparently burned out streetlamp. The lawyer called it "happenchance":

https://www.therecord.com/news-story/8354441-charges-dropped...
The sexism I see in her post: Upon joining, her manager sexually propositioned her; a subsequent manager sabotaged her performance reviews and attempts at transferring to keep a woman on his team; they gave leather jackets to SREs as a gift, but would only get jackets made for men (I think this is what you refer to as "the shirts"); she recalls many emails that she does not describe; HR claims she is the problem in all of her claims; she was threatened with firing over her claims of sexual harassment, and they backed off when she pointed out that was illegal.

Those are the instances. What that tells me is that it was a deeply sexist system.

See: https://www.susanjfowler.com/blog/2017/2/19/reflecting-on-on...
As a huge fan of Starcraft, Warcraft and C&C franchises I was pretty excited when it was announced
(as the classical RTS genre was clearly on life support if not already dead at that point), but frankly it turned out to be a terrible RTS that’s not worth anyone’s time.
I built a lot of applications like this in Clipper back in the day. With the extended linker they ran light lightning. I have one still in use today.
>In an emailed statement, Ontario's government says it "consulted with key stakeholders to test the readability, reflectivity and functionality of the new high definition plate design. Ontario's new high definition licence plates were tested using advanced plate reader technology under multiple visibility conditions, and plates were successfully read under those conditions."

>But it acknowledged that "some Ontarians are reporting concerns with readability to the naked-eye under certain light conditions," and says it is looking into the issue.

---

In the aftermath Ontario brags about how they tested it with stakeholders and super advance ai enhanced plate readers... They don't admit there is a problem, just that some people report there is a problem.

This is what happens when you put too much faith in the fact you tested.

The "older" scanners that the police have should have been tested, visibility of people with multiple color sight profiles (think: the dress) and eye sight distance (ie: other then 20/20) should have been tested.

Not to mention that I can almost guarantee there is some scientific research into visibility and colors that would have predicted this just based off of color palette alone.
Nim has an automated generator for C/C++ wrappers or translating from C.

Also there are very easy ways to create Python modules in Nim:

https://robert-mcdermott.gitlab.io/posts/speeding-up-python-...

https://github.com/yglukhov/nimpy
Why do (standard) plates have to be fancy? If you want to sell fancy plates for more money, and people are okay with that, then do it, but make the standard ones cheap, boring and easy to read.
You seem to be arguing with something I didn't say.

I definitely agree that Google should prune their portfolio using rigorous standards. I'm just saying that if one judges the whole effort by typical established-business standards, you're going to get typical results. Some things need more time to prove viability. Since Google a) will be around a long time, and b) is currently dependent on a single cash cow, they can (and should!) take long-term risks with long-term payoffs.

> It's not obvious why it ever was expected to be so.

This is a very bad way to look at long-term research. Or any novel venture, really. You want to be a pundit with a great track record on startups? Just say each one will fail. You'll be right 90% of the time with very little effort.

But it's even easier to wait until something fails and say, "It's not obvious why it was ever expected to work." Of course! If it were obvious that something was going to work, it wouldn't need to be done as a startup. And once it has actually failed, hindsight bias lets us paint it as an inevitable failure. E.g., if SpaceX had had less money and a couple more explosions, it could easily have gone under, and then all of its detractors could have done the "we told you it would never work" routine.
> Maybe the HN crowd can but not your average or median computer users

The median computer user and use cases from 1983 to 2020 are very different.
Suit yourself, but I’d rather fly on a plane that had problems found, scrutinized, and fixed rather than a plane that may or may not have problems but nobody actually knows because they weren’t pressured to look hard enough.

Re: other manufacturers, if the regulatory environment is one in which Boeing can get by with cutting corners, that means it’s an environment in which other manufacturers can cut corners as well. That, combined with the inherent characteristic of for-profit companies doing what they do, I have no reason to believe that Airbus et al are not doing the same. Hell, the first A320 was infamous for a software issue causing it to crash, too, complete with regulators and Airbus involved in controversy afterwards for trying to alter the results of the investigation.
https://churchillnavigation.com/
yes did you see the uncle bob video about programming future? before 11 years. --> it happing today
Amazon workers have died in Amazon warehouses. Seems like that "factoid" might be more relevant than you want it to be.

I still don't understand why you are arguing that unions aren't effective. What skin do you have in the management game?
This aphorism that HR is there to protect the company -- I hear it all the time and it's terribly cynical, while also probably true. Why must it be this way; asked another way, why do we accept that it must be this way, that every time we engage HR it must be with the understanding that they are the adversary. Why go to HR at all, why even have HR, why not fold it all in the legal counsel's office? Why can't HR be what they purportedly say they are, with all the videos and the role-playing and the seminars that everyone hate-attends yearly?

Back to the article - I'm always sad and surprised that there are women doing the work of defending bad actors by attacking the whistle-blowing women. From the article:

> "One woman called Fowler, claiming to be a PI working on a case against Uber; when Fowler got off the phone, she discovered the firm the woman worked for pretty much exclusively helped companies discredit people who’d been sexually harassed or assaulted."

cf. Lisa Bloom in the Harvey Weinstein case, it's damning as Bloom vociferous claims to be on the side that believes and defends the women accusers.
If anyone thinks this is hyperbole, there is a CBC interview with Doug where he claims Trump "took a page out of their book" and not the other way around. There are other occasions where he has spoken about his admiration for Trump, and opted to stay at Trump's hotel while on a diplomatic visit.

Edit: Since this is drawing some ire I thought I would clarify that this is no remark on either politician in itself. They are Doug Ford's words.

The interview: https://www.youtube.com/watch?v=BROa5f9Dnrw

And more recently: https://www.theglobeandmail.com/canada/article-doug-ford-cri...
Show HN: Hyvor Talk – a better way to add comments to blogs
Hello HN!

I'm Supun from Hyvor Talk ( https://talk.hyvor.com ), a commenting platform for websites.

First, to be clear, Hyvor is the startup I'm building and Hyvor Talk is the first product of it.

Here's how it started. I'm a PHP dev and I did a blog a little while ago. When it came to adding comments I didn't like the options available there for three reasons.

1. Some were not privacy-focused. They collected a bunch of user's data and placed ads on users' sites.

2. Most of them were not modern-looking.

3. Most of them were expensive.

So, I created my own commenting system for my website with only comments and replies. After a few weeks, I thought it would be better if I could allow others to use this and solve the above 3 problems. So, in December 2019, I started working on this full time. Since then, I have developed many features (most of them are based on suggestions I got through our Discord server).

Here are some features/facts about it.

* It does not collect users' data. * It's fast because of no third party code, ads, etc.

* It has a powerful AJAX-based moderation console. * It's completely free up to 40,000 page views per month.

* It's fully customizable (colors, fonts, texts) - You can see some customized pages in our landing page.

* It has a built-in spam detector.

* I and my girlfriend (a graphic designer) worked hard to make the system as much as user-friendly and attractive.

At the moment, I'm happy to say, 20+ websites use this commenting system actively. More than 1000 users have signed up as commenters.

Thank you for checking this out! I'd love to hear your feedback.
Hasn't the world population of humans been increasing exponentially? And consuming, well, not all matter but still quite a lot?
Once we have the technology (and will) to mine asteroids that'll even get worse.
January 2012 for me (Chicago).
> The reason you don't actually hit 1 Gbit/s in practice is due to other overheads such as the interframe gaps, preambles, FCS, etc.

Actually Gigabit Ethernet is highly efficient; it can actually give you 98-99 % of line rate as the payload rate.
Are you trolling or are you unaware of the thousands of years of men and institutions treating women as property, as objects of desire or status, as cheap labor, and the fact that these attitudes are still very much in place?

Cry me a river, women's rights movements and feminist culture push back against this millennia-long oppression and some men don't like losing their right to treat women like sh*t.

Show me the 80% of corporations where most of the top earners and decision-makers are women, where women speak 80% or more of the time and where men earn 75c on the dollar women earn. Along with governments consisting of female lawmakers legislating men's reproductive health and not vice versa.

Until then sexism stands for institutionalized and cultural oppression of women.
What's the best IDE for javascript? What helps you be the most productive?
Well F# is based on OCaml, and it have been recognized for some time that C# is adopting more and more features from F#. As the article alludes to, this is not without controversy. Some feel that C# is becoming too bloated, and if you want to program in a functional style, you could just use F# in the first place. C# is much more widespread though, so this makes functional idioms more broadly available.

On the other hand, C# have also gotten deeper support for pass-by-reference and stack allocation which I consider more low level features. So I don't think the development is purely in functional direction.
[Eloquent Javascript](https://eloquentjavascript.net/) -- A general intro to JS/Programming.

[Javascript: The Good Parts](http://shop.oreilly.com/product/9780596517748.do) -- Once something makes it into Javascript, it's there forever. While this book only covers up to ES5, it creates a good foundation for things to use and things to avoid. This is especially relevant if you wind up working with older codebases.

[Exploring ES6](https://exploringjs.com/es6/) -- This book will take you from the ES5 land into the world of ES6 (ES 2015). It does NOT cover newer features from ES2016-ES2019, but only a couple of those are major updates.

[Javascript Allonge](https://leanpub.com/javascriptallongesix/read) -- A nice, soft introduction to functional JS concepts.

[You don't know JS](https://github.com/getify/You-Dont-Know-JS/blob/2nd-ed/READM...) -- an overview of the language feature by feature. I feel it's a bit too advanced for an introduction on quite a few things though.

I'd avoid Javascript: The Definitive Guide. It doesn't do a great job of distinguishing between the good and bad parts of the language and some examples aren't best practice anymore. Maybe they'll get around to creating a 7th edition one day that'll be worth reading. Likewise, I'd avoid reading the spec until you've worked with the language for a while. It's not light reading. I'd start with the 5.1 edition because it's much easier to approach (and much smaller at only around 250 pages). Once you've read that, it'll make reading the newer specs much easier (ES2019 spec is over 3x as long).
https://www.manning.com/books/nim-in-action - from one of the core developers.
It has great GR reviews, thanks for the rec
In theory, there doesn't have to be a power differential between the average car owner and the average aircraft owner. In practice, there is.

This is sousveillance, not surveillance.
You’re missing the other half of your logic though, which is that due to knowing that this plane has an issue, you also know that the issue will be resolved, so you actually know that this plane does not have the issue. For other planes, as you said, it is unknown if they have the issue or not. I’d rather fly on the plane that I know for sure has had the issue addressed.