skysight-inc/HackerNews huggingface dataset:
What? You've been talking about (a) whether GR needs empirical observation, (b) whether things are true whether people admit them or not (i.e. Objective reality) and (c) mathematical proofs being evidence of absolute truths. Those were my three paragraphs.

How many problems have you worked through in GR? Have you gone through the proofs that GR recreates Newtonian gravity in the low-energy limit? If not, don't go around talking about how Einstein proved GR was a true description of reality with naught but mathematical proof when he didn't think he did that.

Physics has the same requirements for empiric evidence as the life sciences, it's just that we work within regimes where we can apply fundamental, empirically validated mathematical theories directly. If you don't believe me, go ask another physicist.
I loved XML and XSLT. And Internet Exporer, for all its faults, had great support for XSLT in the browser from version 5. It was quite easy to build "rich" single-page apps that get XML data from the server and build various user presentations by updating DOM with XSLT.
I have participated in privacy reviews at one of the largest tech companies and they basically boiled down to 1) are we making sure this behavior is disclosed somewhere, 2) can we get sued for this, and 3) will this enrage people so much that it's not worth the bad PR.

Those were the 3 concerns and while my personal privacy standards are a lot higher than that, these companies are targeting the mass market so I don't think this attitude should come as a surprise. While we can and should try to educate the mass market I think if you want a more private and secure product then using the same product they use will probably always leave you disappointed.
The number of steps it takes to get it "up and running" is relevant, but hardly the most important part of what makes a language/framework a pleasant experience. Also, you seem to assume I'm in react land? But I'm an angular developer. I know first hand the big problems of angular :P
Why does any programming language have infix operators? Because they make some things easier to read. Fixity and precedence are not accidental complexity. They are the essential complexity of having infix operators. In order to evaluate "3 * 4 ^ 3 ^ 2 / 4 / 2 + 5 * 8" you must define the fixity and precedence of the operators involved. You don't usually have to think about defining these things in most mainstream languages because the language defines the fixity and precedence of those operators for you to give the behavior you expect. You still have to learn it though. Do you know how Python evaluates the above expression? (Change the carets to double stars...HN didn't render double star properly.) In my first programming class long before Haskell was created, the textbook had a C operator precedence chart. The concept is not new to Haskell. Haskell has just given you control over something that has been there the whole time.

Haskell lets you make your own infix operators so that you can get the same benefits in other domains than the ones that the language designers decided to provide for you. Therefore it follows that Haskell also needs to allow you to specify the fixity and precedence so that your operators will fit together in the way that is appropriate for your domain.

> Let me explain it a bit further: to read someone's code, first I have to see what symbols they have defined and what fixity they have ascribed to each of those. Now I have to keep all that additional unnecessary cognitive load in my brain to just be able to get a hang of their code with their fixity rules associated with their symbols.

The same is true of C, Java, Python, etc. The only difference is that those languages have a closed set of operators while Haskell's is open. There is a small amount of cognitive overhead, but I think you're greatly exaggerating it. In six and a half years of professional Haskell development I can count on one hand the number of times this has been an issue. And it can be trivially resolved by adding parentheses or by decomposing the expression into separate expressions.
No, it's not. It's like blaming someone who robbed a bank and got caught.

Instead we're blaming the security cameras for revealing who robbed said bank because the bank robbers are our buddies.
This isn't even a critique/ridicule of Docker. It's an explanation of the technologies and names used in the satirical video.

The author, Ian, actually does a great job of explaining Docker and it's use in this post.
Windows 8 base design is basically Longhorn to certain extent.

They brought COM+ Runtime back from the grave, exchanged the COM type libraries for .NET metadata and renamed it WinRT.

At the same time C++/CLI syntax was repurposed for C++/CX this time doing AOT compilation to native code. Similarly, .NET went through two new AOT compilation toolchains, first the MDIL binary format used in Windows 8.x, followed by .NET Native introduced in Windows 10.

Which begs the question if the Dev and Windows devisions weren't so busy fighting each other, maybe just maybe, Longhorn would have had the UWP application model instead of Windows having gone through all these releases until they had settled their differences.

Now it still remains to be seen how much it will eventually matter.

This was just an example, there are others regarding other technologies, for example Symbolics had quite a few internal fights.

http://danluu.com/symbolics-lisp-machines/
If this technology's been around for so long, I wonder who's been suppressing it?
I feel the same way.

As history has shown, when presented with an existential threat to the group, humans are often willing to drop their immediate plans and sign up to fight. Perhaps we're wired that way.

Bring on UBI. And bring on a global 'war economy' to transition us to a zero carbon energy infrastructure.
How do you fix a bug you can't replicate?
There are many flavors of XML and JSON out there now. I think for many developers JSON started to "look good" when the number of standards that started stacking up against XML (and XML-ish/SGML-ish/HTML-ish based formats) started to make people go insane. In the healthcare world we typically had to deal with a never ending set of "format standards" that kept integrating themselves together. I guess originally that may have been the beauty of XML... we started with XML RPC, moving on to SOAP 1.0, SOAP 1.1 introduced new ways to send headers. At some point however it just went crazy.. I think kinda when the enterprise-level people got their hands on things, they started porting all of their non-standard wack-job features into XML.

WS-Addressing - ok seems simple, but now your SOAP stack has to support async processing.
WS-Trust - OK Let's add a simple feature that lets you put "some tokens" in the request and response for security, auditing, non-repudiation - good ideas sure.
WS-Eventing - Let's add enterprise queuing to XML and soap and require stacks to support that, let the users of the stack figure out a way to connect that to the queues.

Anyway the list goes on, and you can read about it here:
https://en.wikipedia.org/wiki/List_of_web_service_specificat...

Suffice it to say, but XML died because the developer now had to learn all of these, how they worked because one tiny industry body starts to adopt 1% of each, requiring implementors to learn 99% of all. It basically just made JSON attractive, a reset if you will.

XML won't go away. HTML will continue forever (it crosses a developer-designer "human line" that makes it kinda permanent) Developers adapt to future technologies a lot faster than designers and other's dabbling in HTML.

Now all this being said, you can see the list of standards piling up against JSON. There's really no critical mass ready replacement though, so JSON will be safe for quite a while longer. JSON will only be replaced in various "areas" like YAML for config, binary JSON-compatible representations for wire and/or storage.

I'm not biased against XML for data transfer, but if someone asked me to create a SOAP 1.1 service with WS-Trust, SAML tokens, etc... I'd also argue for a more industry accepted REST service with OAuth tokens, simply because it would be like introducing the Hummer all over again in age where Tesla's are everywhere. - everyone would hate us.
> Why is the ID, clearly always an integer in every sample of hundreds I see, represented as a string

Becase XML is a text-based markup. If you truly want binary data you need to encode it and use CDATA sections.
From the article:

> People are not robots. Sex happens in a context. It is about power. Southern African girls and young women are infected by men who are much older than themselves. It’s about poverty. It’s also about a culture of machismo.

As I understand it, older men target girls and young women in order to reduce their own risk of infection. But many of those older men are already infected, and are either asymptomatic or in denial.
I've never played regular Werewolf, unless you are referring to what I know of as the informal party game Mafia (several nights, one killer, several townspeople, maybe one or two additional roles who get special abilities).

In that case, yes much better:

- Everyone is involved start to finish, and a free phone app serves as the emcee.

- People receive cards with (usually) unique roles that furnish them some special information in their own way. I think some Mafia variants have minor special roles, but the makers of ONUW really did a good job thinking of creative ones.

- Many roles involve moving cards around at night, so when you wake up you usually don't know for sure whether you're still the role you thought you were, or whether a card you saw at night is still where it was when you saw it.
Well, why can't they?

(That's not rhetorical.)
Exactly. It is victim blaming. But there is no need to bring in such a vision. When I come to this site I expect people to argue about macro politics, building scalable architectures and education. I dont expect to see an offhand comment relating an act on the political scale to someone being physically and emotionally abused.
I didn't get from dang that HN is going to require Facebook auth or anything else to make it more difficult to create pseudonymous accounts. Dang simply discourages creating unnecessary new pseudonyms because the community benefits with consistent pseudonyms. If you need a new pseudonym to protect your identity, that's a necessary pseudonym: have at it.
So this is an interesting thought -- will the general public even be able to own their own self driving car? Or will self-driving functionality be locked down with DRM to such a degree, will the developers of the technology hoard it / control it to the point that they are the ultimate arbiters of what you can even do with a self driving car?

What scares me is that there is absolutely precedence for companies to act like this, and I can even imagine legal arguments about the hardware requiring certain oversight and maintenance to allow self-drive to be enabled. Kind of like John Deere exerting control over their tractors but even worse.

So to your point, in such a world, no one could go out and buy a self-driving car, and certainly not a fleet of them, and then just try to independently run this service. If you want the car to drive you from Point A to Point B you would be signing a TOS saying it was for personal use, yadda yadda, and all the APIs would be completely locked down like a walled garden preventing people from taking the self-driving platform and building on top of it. This would all be in the name of safety and limiting liability, of course....
There will still be organziations and managers and Q&A and R&D! We'll just starve them all of resources and wonder why we're being out-competed by corporations who use different economic models and structures.

That's not an abstract hypothesis. That's what happened to the Yellow Cab Co-op in SF.

Vanguard is a decent example, but it's in a unique market where information is shared very widely and customers are extremely sensitive to price. And nothing other than price relative to returns.
As a developer I'm not quite happy with a single-letter names. Of course it's ok for minor local things to be named 'x' but for more important values and functions there is no problem these days to have a readable names just like in software. So you could actually read of a paper without guessing and searching those epsilons, lambdas and cappas and cryptic symbols. Use expectation(x) instead of e(x), use mean(y) instead of \hat y and so on.
I don't think they will have free circulation so I think that the "best case" will be worse (than Norway & Switzerland).
I once got an XML file from an integration partner where the whole thing was XML escaped (all the tags looked like &lt;node&gt;value&lt;/node&gt;) because they had embedded it within an outer "envelope" XML file. They saw nothing wrong with this and argued when I questioned it. I wonder how they were planning to express escape sequences within the inner XML document that was already escaped...
Yeah, because eating less is easy. If only overweight people knew that it would have a small impact on global warming, I'm sure they'd suddenly be able to cut back, even though personal health, physical attractiveness, and day to day comfort haven't been enough to get them to eat less. But yeah, a small potential impact on global warming will probably do it.
If you want to create your own personal echo chamber, so be it. But I'll still be here to occasionally hold you accountable.

Also new account, since you prevented the other one from posting. :^)
For those looking for a fully native experience, give https://interceptapp.xyz a try. Currently in alpha. Feedback is welcome and appreciated.

Disclosure: I'm the developer.
> In this emerging model, Twitter could have adopted a
> protocol-based approach and issued a crypto-token,
> Twokens, that users could earn from things like amassing
> followers, reporting abuse, etc. Twokens could also be sold
> by the Twitter founding team to finance their operations.
> Crypto-exchanges could make a market in Twokens so that
> anyone who wanted to speculate on the future value of the
> Twitter protocol could do so.

I don't understand this line of thought. A Twoken would be a sort of irredeemable financial instrument, which Twitter would issue hoping that speculators would mistakenly value these tokens based on the value of Twitter, as a company?

Common stock in Twitter is a financial instrument that gives you part ownership of Twitter. It has value because Twitter, as a company, has value. Twokens would be a financial instrument that gives you nothing, except the hope that other people will misunderstand this fact and buy them, pushing up the (offer) price. Great for speculators, useless for everyone else.
Basic Income Guarantee?
Right, so it would actually have been hard to mess that up.

The only platform where Firefox has limited ASLR is Linux, where PIE is disabled, due to issues with some desktop managers not detecting PIE executables are executable. So the default builds disable it for maximum compatibility. Distros like Debian and Fedora have fixed the bug on their side though, and just ship PIE Firefox executables.

The graph mentions Safari, so you'd think Mac OS X. But AFAIK the ASLR implementation just works on Mac OS X?

So I have no idea what the graph is supposed to mean.
Thanks for the kind words.

> When do you kick back and put out low quality, lowbrow work?

I have gobs of "low quality, lowbrow work" which I don't publish. Too embarrassing.

But I kick back a lot. Lisp is a huge lever that allows me to appear a lot more productive than I really am :-)
C would never had taken over the computing world if AT&T had the freedom to sell UNIX and did so at the same price levels as the other OSes, instead of giving almost for free to universities as they decided to do.

Same thing with Java, it was available for free, just download and install with a JDK that was "batteries included" versus the chaos of trying to write portable code in C or C++ in the mid-90's.
Because the commercial food business is all-powerful in Washington.
Every computer already defines the domain "localhost" for this purpose, which never expires and can't be hijacked. Why would someone want to use this risky alternative?

Also, localhost will work if your machine is disconnected from the internet, while local.computer, which relies on a remote DNS server, will not.
... And much of the rest of the code written these days: https://github.com/blog/2047-language-trends-on-github

If we're talking about the JVM, we must also include Clojure, Scala, Groovy, and any other JVM language code that would be killed if the JVM died.

If we're talking about the language, then the majority of Android and its app ecosystem are included.

Most importantly, don't forget that Java the specification is an open standard with dozens of runtime implementations and 7 compilers (not counting Google's). And the primary compiler, Sun's javac is GPL.

https://en.wikipedia.org/wiki/List_of_Java_virtual_machines
https://en.wikipedia.org/wiki/List_of_compilers#Java_compile...
XML could be fairly lightweight also. It was all the enterprisey-standard formats that were hideous.

E.g.

{"name":"John","age":42}

vs.

<person name="John" age="42" />
Even if you hear somebody shouting a secret across the room, you can choose not to rebroadcast that information.
A tree view of the bazillion files in the typical Java project. (of course, if the project wasn't organized as one file per "design pattern" + domain part, each file of which has 1 or 2 executable lines nested within the required ritual...)

As well as a tree view of the properties and methods of the handful of "god classes" within said projects.

But seriously, on the plus side, IntelliJ is actually fairly usable in that you can quickly toggle on and off the supplemental info panels and just use the "distraction free" editor panel, particularly with the vim (key map) plugin (don't know if there's an emacs plugin).

I think Steve Yegge had a comment in one of his rants that IDEs have better support for languages that require IDEs :-)
It is a red herring.

It reminds me how soda companies shift blame on their customers: "exercise more, don't blame our sugar water". Actually, what and how much you eat/drink is much more important than the exercise, to fight obesity.

Another (BS) example: "shower less to save water" -- compare the agricultural water consumption (giant) vs. the household needs (negligible by comparison).

If a corporation destroys the planet; its products should include the price today (e.g., via a tax): the problem fixes itself.
>And bring on a global 'war economy' to transition us to a zero carbon energy infrastructure.

yes, this is what is needed. unfortunately, the imaginations of our "leaders" are far too small-- too small to see beyond the horizon of their next election.

if we want to continue existing, they've gotta go.
That was not quite my point.

Why pretend it is a string at all?

<Task>
<ID>3</ID>
</Task>

I should have been more clear. Sometimes you have these argument type deals <Task ID="3"> where I would at least hope for <Task ID=3> or the monstrosity above (I assume ID=3 is not valid in hindsight, I am getting tired just writing this all on the second pass even!). And I see all different variations in the same XML file! There is no logical consistency, not even in the same config for the same function of this multi-stage system.

I am not even a novice programmer, and I find the variation annoying, and sometimes hard to reason about when I want to know what the hell the programer was thinking.

The valid part for the CDATA portion has changed several times in minor releases, so when our server team upgrades, I get to figure out the new syntax.

I thought XML was proposed to avoid these things! Haha. Again, tools in the hands of "wise men" like me are dangerous. I am probably as ignorant as them, I just think I know better!
Six-figure is really not that many figures in the Bay Area, for instance. I have a friend who makes six figures in SF and just rents a room.
I think if you're marking up text, you really want to be using markdown one of the other wiki like formats. For writing you're much more likely to run into non-technical people who will be severely impacted by syntax errors.
Some of us can be unproductive, Lisp or not.

Despite all the jokes I can profer on HN in this trendy topic, some of us are destined to suck at programming, from Assemly to PHP to Datalog to J!
Yes we could also create N! districts, where N is the number of languages spoken in the EU...

On a more practical level, I and my wife already speak English fluently, I have two remote teams composed with people from three different nations with whom I speak English, and having to learn eg German would make me need to use 3 different languages (4 for my wife, who is Russian). Seriously, the only shot we have at a European lingua franca at the moment is English.

Well, maybe I'll just have to move to Ireland or Canada if I actually move.
> AIDS is somewhat preventable (for people who already have HIV),

I think he means, much more simply, that HIV is preventable by avoiding risky behaviors. Which may well be the case in countries where AIDS/HIV prevalence is small and restricted to specific demographics, but much harder in poor areas where 10% of adults have HIV. It's going to be hard to convince one in five couples in sub-Saharian Africa not to have children.
I like IntelliJ, but I still spend time here and there window-shopping the settings and plugins. That seems to be the nature of things, regardless of the tool.
GitHub/Google/Microsoft/Blizzard/Heroku have "recovery" or "backup" codes which you are supposed to keep in a safe place (perhaps even a physical safe) and can be used when the phone is not available(lost, locked, erased, whatever).

They are one-time only (that's why you get 10), but are not time sensitive (like those generated by app/token) so they are longer.
Any chance to inject a rape metaphor?
Please don't take already-flammable threads straight into flamewar hell.

We detached this subthread from https://news.ycombinator.com/item?id=12197796 and marked it off-topic.
This article in some ways describes the delta from HTML development to XML development. In the early/mid 2000s, XML was cargo-culted through the tech world on a massive scale; typically being adopted by web developers who proceeded to apply the same habits and tools for XML as they'd been using for HTML. Which of course resulted in many of the issues mentioned.
But isn't the complaint more akin to complaining that the bank revealed the individual account balance for its customers? It shouldn't be necessary to do that to prove the bank was robbed.
We detached this subthread from https://news.ycombinator.com/item?id=12195922 and marked it off-topic.
The whole point is that those personal details had nothing to do with the robbery, and leaking them had nothing to do with revealing the robbery.
A comment that begins "hahahaha another apologist" is a bad comment for HN. Please post civilly and substantively, or not at all. Especially on inflammatory and divisive subjects.

We detached this comment from https://news.ycombinator.com/item?id=12195604 and marked it off-topic.
Ember PostgREST Dynamic UI: An Approach to Flexible and Easy-To-maintain UIs
This is an experiment of dynamic UIs (forms atm) using Ember & PostgREST
Must not be that remarkable if it wasn't even worth recording in 720p or better.
Repeat from above: The whole point is that those personal details had nothing to do with the robbery, and leaking them had nothing to do with revealing the robbery.
Clozure CL's IDE basically is a clone of Emacs/Slime though -- you even send sexps from the Emacs-style editor to the repl via C-x C-e. Not that I mind it myself, but people who don't like Emacs wouldn't like it, I'd imagine.