skysight-inc/HackerNews huggingface dataset:
That actually makes the position of the US far worse. The US claims to be good in some way, to care about freedom and human rights while at the same time they couldn't care less.

China, Russia, Iran and other such countries - no matter what you may think about their policies - can at least be said to be honest.

That doesn't make them good but it does show that the US isn't better, in fact they are quite a bit worse.
well, the problem is that the mmapped file is based at a different address every time you mmap it. (in realistic situations, and the general case)

thus, every pointer dereference needs a base address. how is the support for this?
I'll gladly grant you that point: it is easier to deploy a PHP application which solely relies on the standard library. Outside of that, PHP isn't easier than more well thought-out solutions.
Great!

Is there a extension to highlight messages since last visit?

The tree is not really good on longer discussions, you did not find the new messages.
I am going to use this for epigraphs in my next ebook. This is awesome.
...invite-only? Really?
Sensor for Autonomous Cars: Camera vs. Laser
In my experience, the people forcing schemas and bloat on JSON are the same people who forced schemas and bloat on XML.
Flashback to the early days of XML: "oh god, why would anyone use something as bloated and slow as CORBA to define an interface! Look how simple XML is, and it's human readable!!"

CORBA is laughing its head off: "Who's bloated and overly complex now, eh?"

XML: "Well at least I developed an appreciation of the problem domain... Unlike those arrogant JSON kids"

CORBA: "You were the same way at their age."

XML: "Sure was, gramps!"

(Both chuckle)
There have been several JSON transformation tools, but they haven't taken off. (EDIT in general, not just for transformation,) when a task gets too complex for JSON, it's easier to switch to XML. Thus: XML protects JSON.

But I agree there is some pressure on JSON. And if someone can come up with a way to do schema and transformation that isn't complex, it will be adopted like crazy.

Counter-point: (1) all the cool kids use dynamic typing these days, and don't need schema (schema is a form of typing). (2) transformation is easy in fp (which the cool kids are also using), and don't need a separate transformation tool.
Has Facebook hit its peak?
Lets get the discussion started
One Hacker Way – Erik Meijer [video]
Or someone else has used it to solve the wrong problem.

Or your customer demands you to solve the wrong problem with XML.

A nice example:
Simple configuration files which are best described as simply option=value or maybe json if someone wants to go really wild.

A customer comes and wants configuration files to be XML. Then your sales department agrees and now you have to implement XML files. The end result: Configuration files are no longer easily editable by humans. Yay!

Another example:
Someone decided that using makefiles is too hard, so let's make the equivalent but with XML! I'm looking at you ant! Now they're still have the same problems as makefiles but they are much harder to edit.
"Watson Analytics is Now Open For Business", doesn't say open source. Also the submitted title doesn't match the linked page title.
Agreed. How much XML was used to introduce DSLs and dynamic typing into Java?
"Prof. Mazières’s research indicated some risk that consensus could fail, though we were nor certain if the required circumstances for such a failure were realistic."

I'm surprised to see the above statement in a press release; maybe it was not worded quite right. At the scale of 100s of thousands, or a millions of transactions a day, "some risk" will manifest itself on operation timescales itself. So when one is "not certain" it's always best to assume that problems will show up and it will take less time than expected.

"We are still investigating the triggers for this consensus failure, but believe it is caused by the innate weaknesses of the Ripple/Stellar consensus system outlined above compounded by the number of accounts in the network."

Also not great wording. Saying the system had "innate weaknesses" and we "believe" kind of implies engineers are still guessing on the trigger. Your building a financial corporation and if you lose you loose everything
This is not an easy way to serialize objects, it is merely a way to help virtual memory manager recognize portions of memory that can be saved to disk in the first place.

.so files are loaded through mmap, and the pointers problem is solved there through the mechanism of relocations. But please don't write raw memory objects to disk, use Google Protobuf or ASN.1
A perfect illustration of why a simple lookup table is often the better implementation. I'll stick to the knuckles method—thank you very much.
Objective facts:

* XML is complicated enough that its parsers are commonly full of obscure bugs. JSON/YAML doesn't have this problem.

* XML is complicated enough that its parsers can have security vulnerabilities (e.g. see billion laughs for just one). JSON/YAML doesn't have this problem.

* XML is complicated enough that you can create an almost-but-not-quite valid encoding. The (already complicated enough) parsers have to deal with this and the ones that don't are considered broken. JSON/YAML doesn't have this problem.

* XML's complexity does not give you any additional benefit over YAML or JSON. Serializing/deserializing dates as strings is not a problem. It never was.

XSLT is just the shitty icing on the already crappy cake. A committee created a disastrous turing complete programming language to munge this already overcomplicated data format.
The entire West is working together on intel. You can argure that Europe, Canada etc. are incompetent and weak but you can't argue that they are innocent. They are deeply complicit. But that narrative doesn't work very well.
Fidel Castro Is All Over Laura Mersini-Houghton’s Black Holes Theory
I really think that the bigger the app gets the smaller the framework should be. If it lacks functionality, it should be possible to easily add it using the frameworks core functionality.

IMHO in general the core functionality of a clientside framework is to provide a way of structuring the app and allow for communication between logical units that are nestable and modularized.

If a basic framework does that, and only that, it should be bulletproof. I admit, it took me 10 years to rethink and recode this over and over - and there is no end in sight.

I love this discussion, it reflects much of my thoughts about the issue.
You're joking, right? There are JSON libraries for every back end language and ecosystem you could imagine.
What?

Without decentralisation, Bitcoin has nothing to offer over everyone trusting some random entity offering to keep a ledger of account balances. And we already have plenty of those around.
The shuttle was a high fixed cost program, but the variable costs aka what you saved by scrapping a launch was fairly low. With 2x the budget they could have done something like 6x times as many launches and each launch could have sent 20-30 people to space. But there is simply little point in sending people to LEO which is the real issue.
"""don't use libraries, write things from scratch, the expressive power of a language is partially derived from what's in its standard library)."""

One of these things is not like the others.

He sounds like he's very charismatic and personal, and probably an ok dude to be around, but that still does not change the fact that this was a big mess of an article.
In my experience

* Configuration files are best made with YAML (it's the most human readable).

* APIs / other forms of serialization/deserialization over a network are best done with JSON (chop it in half and it will fail fast unlike yaml. still fairly readable tho).

* Programming languages (like ant) should not be written in either one ever (fortunately I've never heard of a YAML or JSON based language).

* XML does a bad to terrible job of all three.
<Blink> more
With plenty of respect to the conclusion (stock options to pay CEOs are wildly exploited) I'm not sure how that's supposed to be a failure of the idea that "companies exist merely to generate economic returns to their owners". It sounds more like a failure of a common mechanism used to seek that goal.
>There have been several JSON transformation tools, but they haven't taken off. When a task gets too complex for JSON, it's easier to switch to XML. Thus: XML protects JSON.

Uh, no. In general if you're sensible enough to use JSON as a data interchange format, you're probably sensible enough to use a real programming language to do transformation.
Mobile Health, HIPAA and Health Technology Predictions for 2015
Hy, Get some Lisp flavor
Well it was to be expected, Ripple scammed thousands of users with similar promises

They re-branded as "Stellar" + somehow got Stripe to give them a mention and the scam repeats
7 Entrepreneur Traits That Let You Soar with Angels
Well WebKit is C++, but the UI is probably Obj-C.
"Eyes on the scoreboard, not on the ball." It's not hard to see where problems could come from. Quarter-driven management, etc.
I am new to Lisps but i did some programming with Haskell and i have understanding of functional programming. I am very excited by the language and i could get my hands on it fast. It is a charm since it compiles down to python and i can see what is going on. I think Hy makes it easy to learn Clojure for Pythonistas as well.
i was looking at rabbitmq - do you recommend a MQ that isnt a SaaS?
Ask HN: How I stay motivated when learning foreign language(english)?
I don't have a friend outside my country I live in third world. I like written books or articles

in English to share my ideas to the world.

Help me please.
> Growing up in a secular society ancient religions can seem awful strange: why did people worship stone statues and sacrifice to them? Did they really believe all that effort did anything?

I don't know, do you really believe there is anything that suggests mathematics exists in reality outside of the maintenance of symbols, structure, and meaning in the mind of man?

Some things exist to teach patterns, to maintain a style of thinking. There are tons of things we don't understand about culture socially - in maintaining peace, individuality AND unity with ourselves as individuals and ourselves in society, that might have been intelligently dealt with in a very real way in cultures you consider primitive, intelligible, irrational, unscientific, archaic, and non-secular.

You can't judge a book by it's cover, so to speak. The superficial observation of ritual does not mean it serves no purpose. The meaning of things change over time, as these things are interpreted and understood by different cultures that come from different backgrounds with different ways of representing and interpreting information about the world. Math does not always represent what it says it represents. Neither do dancing statues. There are certainly TONS of things people rely on, things they assume about how existence functions, that we can't even begin to touch the tip of, because we are blinded by the complexity of our own minds.
Install visual studio. Click new Project. Start writing code.

Install linqpad, start writing code.

Install intellij/pycharm/rubymine. Click new project. Start writing code.
Generating Fields Using Discrete Math (Part 1: Prime Fields)
Given the revelations about the NSA,

Is it not possible to trace these emails to their source?
Maybe legality is a bit of a red herring anyway. A spy agency has to do things that would be normally illegal, and needs to maintains secrecy that would make proper investigation by the police impossible. In the absence of facts the public tend to judge things on how "tasteful" they find an action rather than something more concrete. A lot of people simply don;t have a problem with spys watching web cam footage or monitoring SMS. It takes a certain understanding to realise how wrong the spying is.
It's a critique of a movement not an idea.

I would argue executives should receive stock with long vesting schedules (as in 30 years) not options. However, options are nominally cheap up front so they tend to look more appealing for boards.
The next systemd hackfest is on Jan 30th:

https://plus.google.com/events/c56kbn26s6g01n6m4tj2nmdgnfc

If someone could fix docker so that projects like this are not required:

https://github.com/ibuildthecloud/systemd-docker

...that would be great!
דער מענטש טראַכט און גאָט לאַכט.
There is a lot of confusion between typing systems, metatyping systems (that can implement arbitrary type systems) and the transport representation of such systems.

I agree with your counterpoints, but the cool kids are still having issues with transport representation of arbitrary types. Sure (eg Ruby) can use Kernel dump and load to marshall arbitrary types, but what happens when the other end doesn't have the type loaded or available?

Ouch, maybe we should invite Java Enterprise Beans to the party to comment on the semantics of distributed types?

JSON is currently deceptively simple precisely because its wire representation (with simple types) is equivalent to its type definition which can be directly evaled in js to produce a memory instantiation. But none of that holds in the general case... Try for example marshalling a JSON object with a tree structure.

Maybe we end up going in Alan Kay's direction, where we stop trying to send representations across the wire and just send code... But that too was tried in the past. It has other limitations.

It's complicated.
Since two years I am working full time on a website which gets rendered via XSLT (via Apache Cocoon). When I joined, it was kind of a mess and I had a hard time understanding XSLT and the templates written.

Just recently I had the chance to do a rewrite. What I did is I created "my own HTML". Basically every module of Twitter Bootstrap has it's own XSLT template. That means you have a very easy XML "HTML" syntax, but the output is Twitter Bootstrap. And every piece of output HTML is defined just once in the whole application so it's easy to maintain.

With the help of XSLT you can abstract a lot of things. One example: I have an element called <colgroup/>. It can contain up to 12 <col/> elements. if I set the @size attribute to one of the columns, the @size attribute for the others will be calculated automatically and the output matches the Twitter Bootstrap CSS classes.

I have to say, I love it. I can't imaging writing the whole mess of Twitter Bootstrap plain HTML in a template anymore.
I was thinking that too, until I remember that current flows from the negative terminal. Electrons have a negative charge. Because when Ben Franklin was deciding what to call things, and made a guess about which way it flowed, he guessed wrong.
>The problems that XML and XSLT address have not gone away. It saddens me when the XML-hating JSON community starts reinventing solutions that have all the same issues of bloat and complexity (see JSON schema, Collection+JSON, Siren, etc).

JSON schema:

Validing schemas is not as nearly important for JSON as it is for XML. JSON's relative simplicity the problem of "almost-but-not-quite" valid encoding mostly goes away.

As a result, not many people use JSON schema.

Even when I work with XML I very rarely come across code that performed actual XML validation. Most people would just wing it and hope nothing broke. That's the first dirty secret of XML validation.

The second dirty secret is that if you are consuming an API that provides invalid XML (a common occurrence), you just deal with it and try to make it work. XML validity be damned.

Collection+JSON:

Literally never heard of this. Don't need it either. Once the JSON is deserialized you can use the language's own tools (and a combination of lists/arrays + maps). So what's the point? I don't miss XPath or XQuery.

Siren:

An solution attempting to solve a non-problem copied from a solution from the XML world that didn't solve a problem either.
Fortunately they're usually ignored.
Tell any lisp programmer he doesn't get first-class functions and has to use nothing but macros, and he'll run screaming in horror.
That link is on the page ;)
There have been great legal barriers erected to protect management from shareholders. Without restrictions on hostile or silent(unannounced) takeovers, management would not be able to employ tactics like overloading with debt or emergency stock repurchase (effectively harming the company to prevent being taken over).

http://en.wikipedia.org/wiki/Shareholder_rights_plan

http://www.investopedia.com/terms/s/sharkrepellent.asp
but the more simpler you get the less there is that end up biting you

And increasing the probability that you invent the wheel, badly. I have been using libxml and libxslt for years and as far as I remember I never encountered a bug. Both projects have been developed for years and is used by a gazillion other projects.

It is many times more likely that you will be bitten by a bug in your own custom configuration file parser than e.g. in libxml2.

I am not arguing for or against XML, but code reuse. Simplicity also means not reinventing the wheel and keeping your own projects simple by leveraging existing, good, libraries.
That actually looks pretty nice.
If you refresh HN regularly, you will see that really often.
People are just gaming the community for a few upvotes or views as far as I can tell.

I see this timeline all the time:
1. User posts article about xyz technology
2. User posts article negating post 1
3. Most boring shitstorm every occurs
4. karma karma karma
Give me an input, the expected output, and I will show you I can do a more readable shorter and easier version of the transofrmation with jquery. The XSLT is so unreadable it requires comments.

I did once a less than 2k library in js that loaded the TTML markup in an hidden div and would show it on an HTML 5 video player with extra formatting.

Why would someone need XSLT in 2014? It was a failure in 2000.
On the systems I've seen, brk makes a lazy allocation, i.e. it doesn't allocate physical memory until you write to a page.
I'm from abroad. What's this "cashback" thing that I keep reading about? They give you money back onto your credit card, after you paid? Why don't they just give you the discount right away? And what do credit card companies have to do with grocery stores?
The nature of ownership has shifted from a long term shared investment in an enterprise, to a short-term investment expecting immediate returns in the next quarter.
HMRC will tell you whether in their opinion you are caught by IR35. However, it is important to understand that they are not a neutral advisor, and just because someone at HMRC thinks you are caught, that does not mean the actual decision-making process if they challenge your status will lead to the same conclusion. In reality, they have a record of chasing not very many people under IR35 in the first place and then winning only a fraction of those cases when someone has put up a fight.

To be clear, I'm not arguing that this is necessarily due to any ill intent on their part. It's just that even if HMRC people are trying to help when you call them, they can still fail to understand what the tax rules actually say and they can give incorrect advice as a result. When that happens, they seem to err on the side of saying you're caught by whatever it is you're asking about and should pay the extra tax.

If I'd taken them at their word the last couple of times I called, my companies would have paid far more tax than we really owed. (To be clear again, I'm not talking about any funny tax avoidance measures here, just applying the normal but somewhat complicated rules for things like international sales.) Fortunately, we also spoke with some accountants who could explain why the first advice was wrong, which in fact they did by citing parts of HMRC's own written guidance that HMRC's own people had overlooked.
Reminds me of the person (people, team, etc) who decided it was a good idea to code websites in XML + XSLT. Because XHTML is just not good enough. The most prominent of these (I'm shocked it's still this way) is http://www.skechers.com/
You rarely see uninitialized pointers or off-by-one array bounds errors? I wish that was true for my colleagues.
YAML allows deserialization into arbitrary native types, which most definitely is [1] an issue (see: the flood of Rails/YAML vulns a while back)

[1] http://blogs.teamb.com/craigstuntz/2013/02/04/38738/
"That's actually the biggest problem with wind power; when you have excess power, you can't do anything with it except curtail your production and lock your turbines so they can't spin."

There seems like countless ways a society could use "excess energy". What this article talks about is more like time-shifting the energy it's captured. But if excess energy were a problem, wouldn't you be able to store it in batteries, or apply it towards desalinization or other net positive activities rather than just locking the turbines?
I don't follow your question. A right-handed helix remains so regardless of its orientation, just like how I wouldn't become left-handed if I were suspended upside-down.
"The journalist was slacking some here, The Nexus 5 (and, the LGs and Motorola this last year) are the closest / only competitors to the iPhone that cost $300."

The comparable phones (current flagship Samsung, HTC, LG etc.) are priced at around the same level. Apple has chosen not to participate in the "cheap phone" market, whereas Android has no choice being "open".

Apple very arguably provides additional value in security, privacy and a better user experience due to higher quality software and UI design.

Have some more sour grapes, Zuck... ;-)
Agreed, it's a very shallow take on the matter. It treats "shareholder value" and "short-term expectations tunnel vision" as synonymous, but I don't think that is the case.

Even if it were, it's still not a good argument: even if shareholder value necessarily imposes (opportunity) costs in terms of profitable projects not taken (what's the difference between the lost returns and the second-best choice, anyway? probably negligible), you have to compare this to the costs of alternatives. Countries with "stakeholder" involvement in the governance system tend to have marginal q < 1, i.e. they undertake negative NPV projects, destroying capital.
If we eliminated everything where implementations have had obscure bugs or security vulnerabilities, there would literally be nothing left.

XML's complexity does not give you any additional benefit over YAML or JSON.

This is so incredibly wrong, on every level, that it belies belief and reads like something you would come across on a "beginning programmers" forum. As others have said, JSON/YAML thus far have seen limited usage (no, that configuration file on your app is not a complex example). But as it grows people are starting to ask questions like "Gosh, wouldn't it be nice if my perimeter or the source system via a metadata file could validate the JSON passed to us". "Wouldn't it be nice to be able to convert from one JSON form to another."

And the exact same complexity is arising...poorly, and with the same hiccups that the XML system went through.

I mean some of the comments are incredible. Like "JSON is simple enough that errors aren't big" -> Hey, sorry that those bank transfer got lost, but it turns out that we mistyped the account number field name and the destination system just ate it. Json.

¯\(°_o)/¯

Sorry that the dates are completely wrong, but all of those years of discovery about time zones and regional settings...just make it some sort of string and they'll figure it out.

¯\(°_o)/¯