skysight-inc/HackerNews huggingface dataset:
> Or even better how type systems could work around data integrity errors in RAM without ECC.

You realize that you can do ECC in software too, right? You just need the statistical bound on a double fault to be similar to that of the hardware case.

Type systems can be used to do this by defining an interface for the data, letting you swap between normal datatypes and ECC ones seamlessly. (And in practice, you only need to define the base operators for your new type.) You can do this with ducktyping ECC versions of objects in say... Python. But the type system helps ensure that you've built the full set of components necessary and it properly links. You have to do this with ad hoc IDE tools in Python.

Similarly....

> The defect was as follows: a one-byte counter in a testing routine frequently overflowed; if an operator provided manual input to the machine at the precise moment that this counter overflowed, the interlock would fail.

That actually sounds like exactly the situation that a type system would be used to prevent -- partly because from a type theoretic perspective, that whole situation sounds like an obvious defect.

Further, the result was because of an obscure combination of key strokes that went untested. The use of total functions (enforced by the type system) lets you verify (by computer) that no combination of input can transition to a bad state.

So... Did you intentionally pick two cases where type systems are the obvious solution to the problem?
My guess is we'll need someone to provide OAuth tokens to spoof data for. Or at the minimum, details on what fields are required by "/oauth/token" for it to issue new ones.
Apple claims this is non-personal information:

> We may collect information such as occupation, language, zip code, area code, unique device identifier, referrer URL, location, and the time zone where an Apple product is used so that we can better understand customer behavior and improve our products, services, and advertising.

How is your occupation and exact location non-personal?
Edward Snowden: "Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say." [¹]

"When you say, ‘I have nothing to hide,’ you’re saying, ‘I don’t care about this right.’ You’re saying, ‘I don’t have this right, because I’ve got to the point where I have to justify it.’ The way rights work is, the government has to justify its intrusion into your rights."[²]

--
¹ https://www.reddit.com/r/IAmA/comments/36ru89/just_days_left...
² https://techcrunch.com/2014/10/11/edward-snowden-new-yorker-...
Same experience here, also in Texas. Nothing racist at all, just dog-got-out and other harmless posts of the like. Occasional political chatter, but not unreasonable.
Here's a use case for nullable booleans in the database, at least. Arguably this could be solved with different data modeling, but suppose you have an "Application" model/table that represents an employment or credit application. The application requires many different steps, so you want to save progress along the way. On Step 3, there are checkboxes for perhaps certifying whether or not you're a U.S. Citizen, or to check if you agree to a certain legal document. Prior to step 3, you wouldn't want to default those values to "false", as they haven't been specified yet by the user, so you leave it as "null". Once the user saves Step 3, you can now be sure that the false or true value is one that came from the user.

That being said, I challenge other developers on my team to make sure they have a very good reason for using a nullable boolean. Sloppily using nullable booleans when not needed causes queries and data understanding to be a mess (i.e. what does IsActive == null mean?!), as well as the possibility of introducing subtle bugs.

Also, I don't think "nullable boolean" as used by the parent actually should refer to the CLI/GUI, but rather that the setting of whether you've opted in or out would be null by default before the first run, and then the CLI/GUI would force a choice resulting in a non-null true or false for whether to opt-in to telemetry. That doesn't require "nullable" checkboxes, but rather a nullable boolean data field in the .NET Core settings. If you need to represent a "I'm purposefully not making a choice" null boolean value in a UI, use a radio group with 3 options.
While seen as a whole this might be true, but if you look at the major cities the story is very different.
The latest statistic from Oslo[1] shows that 32.8% are immigrants and 40% of these are from Europe. So between 15-20% of Oslo are "non-western" immigrants which I think is what you are aiming for.

I don't know what counts as homogeneous and not, but if you walk around in Oslo you see a lot more colours than white :)

[1] https://www.oslo.kommune.no/politikk-og-administrasjon/stati...
I see irony when people make these simultaneous claims:

1. This test has deep bias and flaws because it shows a difference in groups

2. I know this is true because of the results of this other test that shows equality.
The number of devs who can competently use Vim or Emacs is already on the low side. The number of non-devs that can do it is far lower. The file needs to be editable by _any_ user with a text editor, not just a developer versed in Vim/Emacs.

I know the response will be "they'll just open it in Excel anyway" which is true in most cases, but I frequently have clients that want to download an export, modify it real quick with a text editor (many use Notepad++ for this), and then reupload it. They're usually doing massive find/replaces on the data and then reuploading into the system and a simple text editor is a lot better for this than Excel.
A friend of mine has a friend who has a friend who lives in southern Portugal. I might be able to park the van there. If that doesn't work: there are guarded parking areas near airports where you can leave your van for several days. I think it's something like 5 Euros a day.

But even if I leave the van somewhere unattended: I take my laptop and wallet with me. Other than that I don't have much valuable things in my van: If someone wants to steal my underwear that I've been wearing for ten years: fine go for it.

At the end everything in my van is replaceable. Including the van itself ;)
iOS Privacy: Easily get a user's Apple ID password, just by asking
Actually, XLS is not bad to work with, if you have a library for it. And it's well defined, unlike CSV. Insofar as I know, there's no way to make a CSV file that will open and show nicely in all popular versions of excel / google docs/ open office, especially across language settings. And a well formed XLS file will just work.
Some people like to see the world burn. [insert joker meme]
Yes, but be careful:

> Personal information will only be shared by Apple to provide or improve our products, services and advertising; it will not be shared with third parties for their marketing purposes.

This goes in contrast with most tech companies such as Amazon and Google. However, Apple does have the horrible clause:

> in the event of a reorganization, merger, or sale we may transfer any and all personal information we collect to the relevant third party.

This clause should be considered the antichrist of clauses, because it just makes the entire policy void in case of a merger. Not that I see Apple being acquired by anyone soon, but still.
Irrelevant.

Even if it is declared somewhere, that would not make this behaviour legal in the EU.
All the more reason to host your own instance! However, I understand if others prefer not to go this route and thus use an alternative version control solution.
Has the BBC suddenly stopped covering men and their contributions to history? I would argue that it's just the opposite. That by finally beginning to cover women's contributions almost as much as men's they're correcting a historical pattern of (perhaps subconscious) propaganda against the concept that women are also (shock) important contributors to our society. And that you're only noticing it because you're acccustomed to news and history coverage being dominated by stories about men.
Furthermore, it is only definitive until it isn't. If we trained users to look for the github page, we'd have forked projects that point to the compromised extension, fake github clones that look like the project, fraudulent likes, and so forth.
Waybackwhen in 1998, when ICQ was a thing, I had an ICQ client on my Amiga that was scriptable. It was fairly trivial to write a quick program to tell it to change status at random times, to confuse people as to my whereabouts.
I cannot remember how often, when I worked in 'enterprise software', we were sent CSV files by companies, and they were completely broken after someone 'simply edited' them with a 'standard editor'. More than a 1000x for sure over the years.

Worse; most 'non computer people' cannot get them imported into a spreadsheet properly (for whatever reason; usually it just puts everything in one field or column, people curse and give up), so they have to edit them in Notepad or worse, in MS Word and then send them back.

Not really seeing the beauty I guess.
But that's quite circular. I have never found a cup that would overspill, if not poured to beyond its capacity.
I think I understand the sympathy you're trying to convey, and the insight that you should try to explain things to the capacity of the other people. It's a mine field of perceived ability and all, but yeah.
Of course it is illegal in the EU.
Science in America
Zero mentions of OpenStreetMap in that story. Can't be surprised I guess.
This was flagged to death but I'm vouching it because it should be addressed.

First, I'm not sure I believe your numbers to begin with. Is there a source?

Second, a huge issue is racism in law and police policies (not necessarily in individual cops) - crime statistics need to be taken with a grain of salt. The numbers reflect what the police and courts do, not what people do- they're related of course, but there's a bias.
Are similar services found in other more popular phones such as by Samsung or LG?
> No you are the one ignoring what I am saying, as apparently you are not doing Android development.

Great, you could’ve checked my profile, or googled who I am, but apparently you didn’t. Spoiler: I do. A lot.

> 1 - InteliJ Android plugin is not the same as Android Studio, it lags a few versions behind;

Which is irrelevant, because Android Studio itself is also splittered into several versions, and many devs simply use the beta, and others use IDEA directly, and yet others simply copied the plugin over.

The plugin in IDEA Ultimate is up-to-date with the latest stable version of Android Studio, btw.

> 2 - The free C and C++ plugins are not the same as the parts from CLion that Google integrated into Android Studio;

No, but they differ insignificantly, I’ve been using both options daily, and both work just the same and fine.

> 3 - Additionally the mixed Java/Kotlin and NDK debugging is also taken from CLion

That’s something I don’t know anything about, as I mostly use a custom solution for that purpose.
The major thing which isn't FOSS are the UI components, other than that it's the default apps, the home screen etc. And they are planning to open-source more, they effectively went bankrupt a few years back and the new investors were reluctant.
Something that bothers me about deep neural nets
"Wrong"? That URL is linked from the page I posted. Click on "France Université Numérique".
A huge desk, huge monitors, comfy executive chair, and a foot rest gives, IMHO, the best of all worlds.
So because a tool can't prevent all possible faults or problems, that tool isn't worthwhile?

I see it like this: we have a number of different tools to minimise problems (various types of testing, theorem provers, type systems etc). Non of them catch every problem and many of the tools overlap in the types of problems they do catch, but if you use many of these techniques together, then you minimise the surface area of issues that can slip through.

Very few things, in computers or "real life" are completely fool proof, but that doesn't mean that they are not worthwhile. That's a call that must be made on a case by case basis to weigh up the risk of faults, the damage done if a fault does occur, the cost of preventing said faults, your budget and time available etc...
The owner of the restaurant was clueless. That's the real news.

If he or she did not grow up in a restaurant business, then the only way for him or her to know about it enough not to lose the shirt is to go out for breakfast, lunch and dinner, daily, for twenty years.

Yes, $29 dollar chicken dish is insane outside the market such as NYC. It is definitely insane in a dump of a place pictured - yes, it is a dump if a chicken is $29. If he actually went out daily he would have known that a place with $1 cutlery can't get away with it while a place with $5 cutlery can. So buy $5 cutlery to be able to raise prices by $5 per dish, i.e. forty dollars for a two top per dinner.
Thanks for your feedback! Adding today.
Extra 10% Off Lenovo PCs and 30% Off ThinkPads
Even for people who are that isn't really "definitive proof" of anything.
ExFAT file encryption
In the US we also have an arguably poor view on what an "educated" person has to look like, and all the condescension that comes with not being "educated".

Specifically, the issue I have in mind is the commonly shitty way that trades are viewed (and trades people not seen as educated). Like plumbers, carpenters, hvac professionals, metal workers, etc.

My understanding is that there isn't as much of a divide or poor view of those paths in at least certain parts of Europe. Germany comes to mind, but I certainly could be wrong.

In many professions they also don't properly value experience (fresh graduate, with a degree), but that's another issue.
It was your tone. It reeked of "real programmers" don't use debuggers etc.
It seems I know just enough to be dangerous. Thank you for your well-written explanation.
Yacy, Decentralized Search Engine
Yeah, but I can buy a motherboard, cpu, disk and whatnot, assemble them, run Windows or Linux on it.

Of course, with phones it is more difficult to assemble stuff (everything is much smaller), but the whole concept of a standardized open platform is not there.

Somebody should define the "PC Phone", and declare it an open standard.
It was kind of crazy how many times people on San Diego (of all places!) NextDoor would talk about how they "caught" a "hispanic male" looking in cars, or some other offense. This in a place where people with an appearance common to folks from Mexico and central America (note that "hispanic" isn't an appearance, but whatever) make up a huge percentage of the general population.
The current state of software safety discussion resembles the state of medical safety discussion 2, 3 decades ago (yeah, software is really really behind time).

Back then, too, the thoughts on medical safety also were divided into 2 schools: the professionalism and the process oriented. The former school argues more or less what Uncle Bob argues: blame the damned and * who made the mistakes; be more careful, damn it.

But of course, that stupidity fell out of favor. After all, when mistakes kill, people are serious about it. After a while, serious people realize that blaming and clamoring for care backfires big time. That's when they applied, you know, science and statistic to safety.

So, tools are upgraded: better color coded medicine boxes, for example, or checklists in surgery. But it's more. They figured out what trainings and processes provide high impacts and do them rigorously. Nurses are taught (I am not kidding you) how to question doctors when weird things happen; identity verification (ever notice why nurses ask your birthday like a thousand times a day?) got extremely serious; etc.

My take: give it a few more years, and software, too, probably will follow the same path. We needs more data, though.
I had the exact same problem re: uBlock Origin. I even set up a quick site[1] a couple referrals ago just so I could have a place to easily point someone to.

[1] https://getublock.com/
I left Kentucky for California in my early 20's. I've been making > 100k per year since then and living as cheaply as possible to hold on to it despite the cost of rent. Most of my friends back home make 20-30k a year.

The tradeoff is that quality of life is terrible. The cities are full of petty bug people. And COL makes living standards precarious for all but the wealthy and the extremely poor (government programs). The precariousness also inhibits the formation of stable IRL (as opposed to chat group based) friend groups.

That said, after half a decade of this I've saved enough money to go back home and use stocks, real estate, and side hustles to put down roots with a decent quality of life.

Sometimes I feel like Odysseus on Ogygia. It's easy to be trapped in one of these hubs so long that you miss out on the chance to exit young-adulthood gracefully. (Very sad the number of friends I have who decided to start a family too late and couldn't quite make it work out).
> You are trying to tell me that the phrase is supposed to make me think in racist terms, right?

No, "dog-whistle" terms seem mundane and can be played off as having the dictionary definition, but to certain people they have a very specific meaning. Your neighbor might say he wants to keep "thugs" out of your neighborhood, which you can naively infer to mean "violent criminals," but to other racists it's a synonym for "niggers." Or maybe you do know what he means, so you call him on it... and he asserts that it just means "violent criminals." That's what makes a dog-whistle.
> Type systems to me seem to be (I'm not exaggerating) the answer to all software reliability problems (barring social ones). If you want a property to uphold, formulate it as a type. The compiler verifies.

I'm a massive Haskell proponent and I'm calling you out because you're doing typed programming a massive injustice with this kind of overinflated claim. There is no known type system that can get anywhere near solving "all software reliability problems". Flexible type systems like Haskell's are really useful. Don't overpromise.
-> magically get stupider

Anyway, it's actually more than magic at work; kids in grades 3-8 and 11 in 2016 are not the same set of people as kids in grades 3-8 and 11 in 2017.
I took several deep dives into a project that he apparently wrote a good bunch of code for, the test automation framework FitNesse. Besides having major conceptual and architectural shortcomings, this piece of software was also easily among the biggest piles of crap I have ever seen, code-quality-wise. Granted, this was 5 or 6 years ago, and it seems to have improved since then, but I still consider it sub-par.

So whatever's coming from this guy, I now immediately see this ugly, unreadable code in front of my mental eye when I just hear his name. Quite a fail, considering he called his company "Clean Coders".
Any idea why property crime is so high? Is it because SV is wealthy (on average) so more attractive for non-local thieves?
I directly skipped to finding a solution to that "problem". I literally found myself browsing amazon for monitor stands that can be folded and easily mounted in a van. What happens if I break hard? Hmm... I came up with requirements for a monitor stand suitable for use in a van. For a moment, I remember being depressed about the zero number of perfect solutions for this "basic" use-case.

Now I'm convinced that I'd never give-up my home-office for a van-office until serious advancements are made in the monitor-stand industry.
Because you to some extent is one of those "random dudes", and Uncle Bob is not? He is even family ;)
> That is why we, coders, are different from other 99,99% of population of the Earth.

Not sure if that's coders or autistics (to be clear: NOFI).
> There has to be something I'm missing...

Some of your replies have already touched on a few points, so I'll add a new one: type systems can be more than a lot of work, they can be wrong. You do allude to "formulating the type is too laborious", but it's more than that.

For example, let's take the perennial question of object-relational mapping frameworks. "Object" isn't a great name for it because the real goal is usually a specific syntax (method calls) and type-safety features (make getID return an Integer, not a String). But there's a problem. "ID" is not the name of an attribute. It's a token in a SQL query. In the database, "ID" can be an Integer today, a nullable String tomorrow, and deleted next week. The type of the underlying data comes from the schema, not the application code. So there is inevitably a mismatch. Unless you understand there is some dynamism there and model the code that way.

The same thing goes for strongly typed HTTP or SOAP clients. Also anything that parses input on the fly.

There are absolutely places where the application can decide something has been validated and then apply that information to some data with a strong type, but there's a tradeoff there, too. You end up requiring that sort of validation-and-tagging in all sorts of places where it's irrelevant. Compare creating an XML DOM with using xpath, xquery, etc. You could create a giant graph of all the nodes in your XML document. Or you could just provide an expression that does pattern matching. There are places where either is handy, but the latter is almost always more flexible.

Now, there are limits. Generally, well-typed data is easier for compilers to understand and optimized. That is, strongly typed data structures are important. But, honestly, most code isn't brand new data structures.

Anyway, there's certainly balance to everything, but people need to keep in mind that type systems are a hammer like anything else. They can be misapplied harmfully, too.

Caveat: It's possible to use generic programming and higher kinded types to work around many of these limitations, but I'm writing this blurb to people who are "application developers" or otherwise are big on object-oriented programming. If people are interested in how type systems can be more flexible, we can talk about that too. My point is that they overwhelmingly aren't used that way.
Slightly off-topic, but maybe we need a fully standardized and unambiguous CSV dialect with its own file extension. Or maybe just use SQLite tables or Parquet?

Some things I dislike about CSV:

* No distinction between categorical data and strings. R thinks your strings are categories, and Pandas thinks your categories are strings.

* I'm not a fan of the empty field. Pandas thinks it's a floating point NaN, while R doesn't. So is it a NaN? Is it an empty string? Does it mean Not Applicable? Does it mean Don't Know? Maybe it should be removed altogether.

* No agreement about escape characters.

* No agreement about separator characters.

* No agreement about line endings.

* No agreement about encoding. Is it ASCII, or UTF-8, or UTF-16, or Latin-whatever?

* None of the choices above are made explicit in the file itself. They all have the same extension "CSV".

These use up a bit of time whenever I get a CSV from a colleague, or even when I change operating system. Sometimes I end up clobbering the file itself.

Good things:
* Human readable.
* Simple.

I think the addition of some rules, and a standard interpretation of them, could go some way to improving the format.
Perhaps it is because all it takes to "be a Christian" is to say "I believe in Jesus", or at least that is how it has been predominately defined by the religious authorities over the past 2,000 years. From then on it is supposed you will go to Heaven no matter what sins you commit
This is non sense, the life for the rich is far better than for the poor. If you don't believe that is true, then you haven't been exposed to it enough. Having high status in any society can have massive advantages. More leisure time, better mates, ability to purchase expensive health care and therapy, organic food, the freedom to go anywhere in the world, the list goes on and on