skysight-inc/HackerNews huggingface dataset:
I got your point and said it’s irrelevant nitpicking that completely ignores the definition I linked to in my first post.

Sure, it might be a bit clickbaity but this trend of “I didn’t bother to read the article so I’m going to bitch and moan about the title instead” I’ve seen on HN is way worse than the title in question.
And I for one am tired of it!

How much would it cost me to have a phone with all trackers turned off? (Or, perhaps, routed through a core application that requires whitelisting?)
>Assange offered to try to crack a computer password for Manning

>“Cracking the password would have allowed Manning to log onto the computers using a username that did not belong to her,” the indictment says. “Such a measure would have made it more difficult for investigators to identify Manning as the source of disclosures of classified information.”

It's up for a trial to determine how much / if any of that happened, but if it did it seems well outside the boundaries of what a journalist should do.

I don't expect a journalist to be assisting someone in accessing information illegally. If the journalist is just given it fine they should be protected, but this seems a good step beyond that.

The article talks about how it would have helped protect that source but it's clear it also would have provided more information / assisted in that process.

Let alone a concern I would have if I were a journalist (I'm not) that providing my source with some cover of another real world person could seriously harm that other person.
While I think it is important to recognize that Jobs/Musk/Bezos all had large organizations working on things they are often credited with, I think it is more reasonable to credit them in this way because they were explicitly the leaders and founders of their companies. They envisioned, created, and led the organizations that produced all those products.

I don't think that is an apples-to-apples comparison with this story. The Event Horizon Telescope (EHT) is a collaboration between numerous organizations (see https://en.wikipedia.org/wiki/Event_Horizon_Telescope#Collab...) and it does have a leadership team (see https://eventhorizontelescope.org/organization). But in this story, we did not discuss the leaders of this effort. We discussed one contributing engineer/scientist who was elevated above the rest, when her algorithm was not even used in the production of the final image (which is the underlying scientific milestone that is being recognized here).

I find it bizarre because from all that I've seen, Bouman was not in a leadership position but was a peer-contributor alongside many others. Her contributions matter, and are important (as credited by Andrew Chael), but it is bizarre to recognize her alone and not everyone else who is on equal footing in terms of their contribution (or even greater footing, for those who came up with the algorithms that were used for the final image).
What we tend to forget in this debate is, human readability doesn't only mean "read and understand", but "read, understand and mentally validate". Now I'm not so sure that for example YAML is as easily validatable as JSON.

To me the simplest and the easiest to validate used to be the old good INI but unfortunately it never got its chance to be strictly standardized to support nested structures. JSON is the next readable/validatable but it is slightly worse in all respects.
Agreed. I feel like everyone uses YAML, I hate it.

YAML feels like 10 steps back; no parser I've ever used has been able to accurately give me a line number for an error, white space issues make it impossible to work with without special editor features, and some of the types are just cryptic. I spend most of my time that's spent editing configs in vim over SSH and it can be challenging at times.

TOML resolves a lot of these issues in my experience but I'd still argue that by virtue of its capability, is still quite complex when trying to define configs for new applications.
I've read the following in a newspaper article:

"[...]30 of the 200 scientists were responsible for the image processing. There were four algorithms developed in parallel to transform the telescope data into pictures, one of them developed by Bouman during her Phd at MIT[...]"

The gist was that she's a great researcher, but not a hero or the face of the project, as she was presented.

Frankly, it looks like the media screwed up in their attempt to transform her into the face of women in science and turned her into a target of harassment. I've seen e.g. an article from a major publication titled "Without this woman, there would be no picture of the black hole".
She seems to be a very competent researcher and had an important contribution. Saying that would have been accurate, fairer and would have prevented the malicious gossip, I assume.
At least a year before that we all got together in that conference room off the building 40 cafeteria and watched the vision demo of making every management action in MMC translate to script. I don't recall Snover being in the picture at that point. Could be wrong. I got the impression he was brought in to solve a problem that was already distinctly on the radar.
So. Mind you I haven't really followed what Assange did or didn't do. But it seems like a lot of people are angry at him because they think he is responsible for having Trump becoming president. Before that, the same people seemed pretty supportive of him.
With Eurowings or Ryanair that flight would be 100 €.

Sadly I am yet to know a company that actually gets Bahncard for their employees. I have known a couple that expect people to use Bahncards. though.
Because i read the indictment.

https://www.justice.gov/usao-edva/press-release/file/1153481...

Line 25 under "Acts in Furtherance of the Conspiracy" - by both his requesting more information about the password and his statement that he had "no luck so far" he indicated that he had been attempting to crack the password.
The Case for Spaced Repetition
> I mean, do people consider Apache config files -- which extensively use comments -- to be a shining example of clarity? Hundreds of lines long, impossible to parse manually.

You're conflating two things, the readability of very large config files, and the readability of config files that allow comments.

> Good luck finding those 3 lines you need.

Personally, since I live in a world where searching text in a file is commonplace and trivial, additional text to match, possibly even comments that note where the config differs from the stock one that ships, are useful.
That's a good point. I guess I'm luckier than many in this respect.

I can't even imagine working in such an organization and staying sane.
”Config files are usually pretty self explanatory”

In the universe where I live, most settings in a config file are pretty explanatory, but also, almost every config file has at least one setting that isn’t.

Also, even if I clearly understand the configuration file I’m reading, figuring out how I can change it often isn’t clear at all:

- If a json attribute contains a file path, can it be a URL or S3 object reference, too?

- does that path to a .gz file in an attribute mean input must be gzipped, or does the program look at the extension? If the latter, what compression methods are supported?

- If I don’t want to write that second output file, do I leave out the ‘extraOutput: foo.txt’ path setting, set it to null, set it to an empty string, or add an optional attribute ‘produceExtraOutput: false’ that defaults to ‘true’?

- what is the range of acceptable values for that ‘foo’ attribute that has a value of 42 in the config file I’m reading?

- is that ‘progressInterval’ value measured in bytes read, input lines, records processed, lines written, or wall time seconds?

- what other options that aren’t in this config file might I want to set in mine?

Yes, all of that could be in the documentation, but it’s easier for me if the config file contains comments describing that, and, in my experience, it also is easier for programmers writing the code to add such comments to the sample config file than to keep a documentation page in sync with the code and the sample config file.

Finally, some things cannot be in the documentation of the tool because they are local changes. For example, logging config could deviate from company standard for a reason.
No, it's not, which is largely the fault of moron doctors and the government who are idiotically conducting a campaign against vaporization.

The primary health risk of cigarette smoking comes from the products of incomplete hydrocarbon combustion. These cause inflammation (leading to chronic lung disease) and many are carcinogenic.

An intelligent realist understands that most people are ignorant and prone to addictive behaviors, and will intervene where possible to substitute a lower-risk behaviour for a higher-risk one.

Instead, stupid doctors have refocussed their (otherwise appropriate) campaign against smoking on vaporization, and the government has moronically banned it in all the same places as smoking.

This stupidity has spilled over into marijuana legalization, causing vaporization liquids to remain illegal and denying users access to a relatively safe, measured, convenient dosage format with a long shelf life.

Patients taking marijuana for medical reasons are thereby screwed.

I despise stupid people making decisions in large groups. What a clusterfuck.
Some valid points, but the only one that pains me are comments, the rest is fine.

I don’t want to program my config files, it goes against the whole idea of configuring stuff.

JSON being JSON makes it language agnostic and easily shared (via APIs and whatnot).

And as for the changes argument - try inline commit log in a file editor (eg GitLens in VS Code). Not perfect, but it does give you some history at a glance.

(The point above is weakened by JSON’s lack of dangling comma support, so one-line changes often affect two lines).
It’s a bit lesser known but I’m a fan of HOCON (human optimised config object notation). https://github.com/lightbend/config/blob/master/HOCON.md

If that’s not an option I’d prefer xml (with some sadness). JSON is a bad idea for the reasons described in the article, and YAML is too clever for its own good and is definitely a loaded foot-gun.
> taxes being approximately the same percentage of GDP

This would astound me. I wonder how you square this belief with, e.g. reports like these: https://itep.org/notadime/
Yes devaluing currency is much less painful. But it creates risk for traders which the monetary union removes. Removing that risk may not be a great idea since one region is bound by a different political structure that is bound to play a role.
A few issues:

• The description is a bit vague, but the article seems to describe a model of a stack of resolvers, each resolver asking the next one in turn, the last resolver getting an answer, and the answer being then passed down the chain again. But this is not how it works. For a normal DNS query, there is ever only one resolver involved. This one resolver is the single thing asking many authoritative servers the same question, each time getting names of servers who might know the answer, and ultimately getting an actual answer. There is no stack of resolvers.

• The article completely conflates the process of a cached record expiring due to TTL expiration, with the process of an updated zone with a new serial number being transferred to slave servers. These two things have virtually nothing in common.

I also found the illustrations too detailed (i.e. confusing for non-experts). There are a lot of options to "dig" which could have been used to cut down on the extraneous output when illustrating a particular point.

The zone file was especially confusing, in that none of it was explained, and the nature of the DNS data model would have been much better illustrated with an object diagram of some kind.
I love taking the IC Bus + ICE from Eindhoven to Stuttgart. Takes me ~6.5 hours door-to-door, for c.a 140-150 euros round trip (with Bahncard 50). I could do this by car in roughly the same time and cost but then I couldn't work (at ca. 300kph no less!).

Flying would be silly too: much less (environmentally) friendly with lines and security checks, which also leaves less time to work.
I even have decent internet access the whole time, for free, which I would not have in an airplane.
HSON ( https://hjson.org/ ) addresses a lot of this. Just allowing trailing commas and adding comments reduces 90% of the friction involved.
Norway: 50% of food, 77% of energy in waste, and 97% of toxic waste is recycled.
https://translate.googleusercontent.com/translate_c?depth=1&...

We are also rebuilding some of our plants to sort waste with machine learning. The initial tests are really promising.
Several of them are already sorting out most plastic using spectrometer-sensors, so we don’t need to do it manually. In combination with the machine learning the tests get it up to 99.9% or higher.
https://translate.googleusercontent.com/translate_c?depth=1&...
I had been using Google Contacts with a minor "hack" of using the "file as" field as a three digit priority field, but still with the person's name and leading zeros. So a contact record looks like this "095. John Smith". Then when I come across a contact record I change that number, almost whimsically which makes it kind of like a bubble sort. As the same time, I made effective use of labels (tags). I have, however, recently switched to Nimble which I like, but am still getting used to. Syncing with Google Contacts is a mandatory feature for me, and Nimble allows 2000 syncs without additional charge via a third party.
Mondragon

Also read stuff by David Ellerman
Switch your parsers to HJSON, and never look back :)
We have no high speed rails, are finally privatizing some trains and it's for good. The quality of service is finally going up even in the state run train company.

The competition works differently. Our country wants train that will run from A to B, X times a day and companies will present their offers. Who has the best offer will run this route for Z years.

Nationalization was tried and doesn't work. It has to be supervised by state, but not run by them, that will lead to inferior service.
Fact-finding is not misogyny. And the facts in this case are that Bouman's algorithm was not used in the black hole image that is being hailed as a scientific milestone. She had other contributions here (see https://twitter.com/thisgreyspirit/status/111651854732747571... which credits her with writing the testing framework), but what was pitched in news headlines about her role/contributions was explicitly false. Pointing out the truth is not misogyny.
Next to the fact that flights always have more time overhead and train stations are almost always central.

I regularly drive from Bern to Salzburg (Austria). To lazy to Google but AFAIK there are no more direct flights, the last I know of was about 400 dollars and with check in and getting to and from the airport did take about 4 hours. Using a nearby airport gets this to 5 hour or more.

Some cities are well and cheap connected per flight. Most however aren't
Worth mentioning that VS Code also lets you map any filename glob to a JSON schema. [1]

1: https://code.visualstudio.com/docs/languages/json
One Man vs. McKinsey: Billionaire Says Consultancy Rigged the Bankruptcy System
- parsing xml may cause random random network requests (firewall issues)

- xml contain comments, sooner or later someone will try to add data to comments, but you already have the thing for data, the format itself, adding data to comments is stupid

- unlike js, in json someone finally said "Enough! There will be only one type of quotes", it makes parser simpler
> For most people, the time gained by taking the high speed train is not worth the extra cost.

Citation needed. I'm just a single data point but I'd gladly pay more to be home w/ family a few minutes/hour earlier and considering how jam packed the ICEs often are I would say others share a similar sentiment (maybe for other reasons).

Most arguments in this article are based on price which to me is similar to people arguing over benchmarks in software/hardware products (i.e. performance of a product) while there are tens of other factors to consider, performance being just one of them.

I for one don't consider price at all (within reason, for me that means when the difference between choices is ~200-300€) when travelling on business (and the older I get for private travel as well). I favor comfort, speed, reliability of connections etc.

I basically disagree with almost everything in that article - but similar to his viewpoint mine is very subjective.
My guess is that what most people are instinctively turned off by is the clickbaity element that they see as implicitly in play when a headline reads "meet the woman behind X" instead of something more generic like "meet the researcher behind X." In the former case, the headline writer is going beyond the standard obnoxious media spin that likes to oversimplify the research process and also apparently hitching their wagon onto the "women in STEM" angle to get more clicks. It's just even more over-the-top than normal, and people are put in an especially critical, even dismissive, frame of mind right off the bat.

That said, I think it's fairly uncharitable to read the headline that way, and we shouldn't jump to conclusions about the author's intent when it's so ambiguous. But it's also uncharitable to read some kind of sinister latent misogyny into HN reactions critical of the headline.
AWS CDK: https://github.com/awslabs/aws-cdk
And I would even say that’s not true most of the time. Why is the update button slow?

- Is your customer in Asia and your servers are in us-east-1? Do we need a multi master database one in each region? Can we make even that faster by doing an eventually consistent write?

- do we really need a synchronous update process or can we use queues to make it more consistent?

- is our web server slow? Should we scale horizontally or vertically? Should we use autoscaling and if so which metric should we use? What should our cooldown time be between autoscaling events? Do we need to autoscale across regions? Where is our traffic coming from?

- is our database indexed properly? Did we look at our slow query logs? Did someone do something stupid like have triggers on our database unnecessarily? Is an RDMS the right choice? Do we need to denormalize the table?

- or is it our code?

This is the thought process my manager was looking for when he interviewed me. Not the best way to traverse a tree.
Could this have been avoided if the suspect himself had the same access to his own sensor data? Like an alibi? I read this whole thing as the technology is there to prevent innocent people to jail, and the processes haven't caught up.
Faced with a nationwide backlash, Amazon pulls back cashless stores. For now.
But do they feed it back to the fabricants already ?
Besides being more feature complete, I'd love to see a way to import transactions from banks/credit card companies.
Matrix.org Homeserver Breach
> It was reported that Assange had a “panic button”. The report said that he had directly threatened the government of Ecuador with with retaliation if anything happened to him. I don’t have a link handy, but it shouldn’t be hard to find.

If Assange has a panic button rather than a dead man switch, he is much dumber than he is portrayed at which point most of the claims that are dismissed as ridiculous (i.e. a smart man would not do X) become not only plausible but likely.
there are portions of rural oregon that have been continually sued to reverse the laws, and there is a list of parts of oregon that have disallowed sale: https://www.oregon.gov/olcc/marijuana/documents/cities_count...

for the most part, those are rural communities - i suspect there would be shops there if they were allowed.
YAML I think is too full featured. It does way too much for a config file format. INI and TOML have the advantage of being simple and focused. My only issue with INI is that different parsers aren't always entirely compatible with one another. But that's mostly only a problem for edge cases.
He said so himself. Please read the indictment.
Agreed completely, the current state is like using a language with no debugger, no modern knowledge of code reuse, no real IDE integration, Terraform is especially poor on a large project since it’s parser doesn’t report line numbers on errors and it has no forward references or ways to resolve interdependence between objects and leaves that up to the user to manually converge its state, not to mention you have to rewrite everything for every cloud and it’s riddled with bugs for common uses.

Pulumi is going down a better route in that they’re using a normal programing language with a normal tool set, however I’m skeptical of how their engine is designed with RPC calls for language bindings, since again it makes debugging more complex as opposed to just a normal sdk. They also don’t have debugging enabled yet.
I’ll do my usual plug and mention that Chrome DevTools (which I write the docs for) can help with contrast ratio (CR).

Inspect CR of a single node with color picker: https://developers.google.com/web/updates/2018/01/devtools#c...

Run an audit and check the accessibility category to find all nodes with insufficient CR: https://developers.google.com/web/tools/lighthouse/#devtools
The parent commenter was comparing the bad UI of NoScript to the bad UI of Gmail. Seems fair comparison to me if the UIs are similar. What does JavaScript have to do with it? People are quite capable of creating bad UIs with or without JavaScript.
Previous topics:

https://news.ycombinator.com/item?id=19636858 (2 days ago)

https://news.ycombinator.com/item?id=19634169 (2 days ago)

https://news.ycombinator.com/item?id=19632890 (2 days ago)
Learning Clojure opened my eyes big time. Since I have done that I can pick up other languages much more easily than before. The only problem I got is with Java, I could never grasp the different concepts of OOP but I do not actually mind that.
It's not possible. Even a wired landline phone generates data that the telecom companies take advantage of.

The closest you could get would be to buy burner phones with cash.
Try clustering similar languages into groups centered around shared features, then try to come up with high-level statements which hold true for all the languages in a group. Then try to derive the individual differences within the group from these statements. Use mnemonic techniques as required and prepare cheatsheets if needed.

One thing to realize, though, is that syntax - outside of a few special cases - is the most trivial part of any language. It's 100% acceptable to forget the syntax of a `for` loop in one language, as long as you still know that, in that language, the `for` loop is actually a for-each construct working on sequences of some types and additionally it's an expression which returns a sequence of results, making it equivalent to `map` higher-order function. Now, I described the `for` loop of (for example) Elixir, CoffeeScript, Racket, Common Lisp (`loop` with `collect`) and F# and Scala (with `yield`). As long as I know that a language I'm using right now belongs to this group, I can plan my implementation around the semantics outlined above. Then, when it comes to writing the code, I can just look up the syntax, or more commonly - just make my editor autocomplete and snippet-insert the relevant bits for me.

So, my advice would be to first learn and understand as many programming language features as possible, focus on their semantics, and then group the languages you know around the features. The syntax is really a trivial matter, and "mastering it" (ie. having the whole grammar constantly in your head) is not actually necessary in my experience.
Here's the chat excerpt:

https://twitter.com/kpoulsen/status/1116341065416462336
And just look at the black cabs. Currently excempt from the ULEZ with their old diesel engines running all day because..? Oh, money.