phpnode

Presumably in this model the dev wouldn't push their branch until the merge is actually complete, and there's presumably a convention like prepending `[CONFLICT]` to those commits to discourage people from checking them out directly.

Why not both?

TOGAF - The Open Group Architecture Framework [0] for anyone else wondering

[0] https://en.wikipedia.org/wiki/The_Open_Group_Architecture_Fr...

I wonder if there's a name for this phenomenon, where a small group emerge from a userbase, gain control of the platform and start applying their preferences to the detriment of the average user. It strikes me as very similar to the problems stack overflow faces.

> "we have enough cash to run this service until everyone currently alive is dead"

They might have the money but why should they give it away? They are not a charity.

> it would make room for better search engines to emerge

How would those search engines fund themselves? what would their business model be?

Of course, hence the focus on server-side rendering. It is quite difficult to do properly though. Facebook itself is not a single page application.

Take something like Google Search, a service that is ad-supported but is free to use and produces an enormous amount of value for virtually everyone on the internet. What is their business model in a post-adwords world, where they've been forced to adapt? Presumably they'd have to charge for it, which means that the poorest people on the internet would not have access to this amazing tool that we take utterly for granted now. No one likes (poorly targeted, invasive) ads, but is that world preferable?

Isn't android effectively that?

The insistence that Linux be called GNU/Linux when even Linus calls it Linux is exactly the kind of behaviour that alienates people who would otherwise align with them.

There is also no requirement that a Linux distribution includes any GNU software at all, should we refer to them as e.g Busybox/Linux?

Traceur has been around for years, much longer than Babel, it's a Google project but afaik it's mostly the work of one person

In the mean time, Talk Talk advise their customers that there is "no need" to change their passwords: http://www.bbc.co.uk/news/technology-38223805

It's common to sanitize a commit history before making code public. Old commits can contain potentially sensitive information, like certs committed by mistake and later removed, db dumps used for testing that contain unsanitized data, commit messages could be some value of unprofessional that you don't want to share with the world, that kind of thing.

This looks like a nice idea but it's a bit unfortunate about the name clash with https://github.com/rpominov/static-land

Edit: Dear downvoters, normally it'd be unlikely for the name clash to matter, but because these are both JS libraries, both available on npm, it's the difference between `npm install static-land` and `npm install staticland` which would be an easy mistake for anyone to make.

It's an out and out money laundering service. It exists for no other reason, there are no legitimate circumstances where someone would want or need to sell amazon gift cards at less than their face value. It is straight up money laundering and it's frankly incredible that it's lasted as long as it has.

How would that work?

Is that processor more or less powerful than the processor in this laptop?

even if you live in a terminal all day 1280 x 720 is just too small to be practical.

edit - I too once basked in the warm rays of a 320x200 CRT, it's OK at the time if that's all you've ever experienced, but it's hard to go back to that from 4k.

Yes, I noted that in the PR. It's easy to fix it, why don't you try?

Here's a PR that fixes this issue - https://github.com/threepointone/markdown-in-js/pull/2

Presumably they've thought this through before announcing it.

These are closure type annotations - https://github.com/google/closure-compiler/wiki/Annotating-J...

Unfortunately your example won't work. You can't use a primitive value as a key in a weak map, which negates many of their possible use cases.

That's a grossly unfair mischaracterisation of the piece, did you actually read it?

This project is something that people spent a long time creating, they put in a lot of hard work and they offered it to you for free. They obviously do care a lot about accessiblity, it's evident from their website. If you found a problem with a particular screen reader, did you open a github issue? What was the name of the software? Did you follow all of the accessibility guidelines? Did you engage with the authors and ask them for help? Or did you simply register a new HN account with which to insult and diminish the hard work that these people gave to you in good faith and for free?

This isn't a very helpful comment, what do you mean?

The milkman is still a thing in the UK at least, but certainly dwindling.

GP is making the point that not all CPUs have a cache.

I like that the punishment for Man who stole coffee and spanners from Poundland was that he had to stay in court until 5pm that day. Truly that is justice.

> I find it very interesting that commenters from countries where cycling is decidedly unsafe are going to lecture those from countries where the predominant mode of transportation is the bicycle on safe cycling practices

This is exactly the point though. The guidelines that apply in the Netherlands are different to the guidelines in, say, the UK, precisely because the two countries have very different attitudes towards cycling. In the Netherlands you have an environment where cycling is extremely common, motorists are very used to sharing the roads and in fact most motorists are also cyclists themselves. This dramatically reduces the sort of us vs them conflicts between cyclists and motorists that seem so common in other countries. Different types of road user are seen more or less equally and show each other a level of respect that is just about unheard of elsewhere. In such an environment, hogging the lane seems unnecessarily aggressive because you simply don't need to do it.

In the UK, USA and just about everywhere else motorists are simply not used to driving close to cyclists. They don't know how much space to leave, they don't know how to pass them safely, it's actually socially acceptable to be aggressive towards cyclists but most of all, motorists are not on the lookout for cyclists, they are not expecting them. In this kind of environment the cyclist's number one priority is to make themselves seen and that's why being assertive is so important.

If you're in the middle of the lane by default the car behind you might be annoyed but at least they are likely to see you, and when you've been seen you can then move closer to the kerb to allow them to pass you safely. This puts the cyclist in control in a situation where they'd normally be at the mercy of motorists.