psquid

The evidence that they didn't review it, is that a million line rewrite was merged 8 days after it began being written. It's simply not possible for a team that size to review that much code in that little time.

As far as testing - yes, they do have a test suite that it was checked against during the rewrite, but that still means that any behaviour that wasn't strictly tested for by that suite could have changed and it would still pass.

Same reasons that IE versions only support certain versions of Windows:

- they want to be able to switch to newer APIs when the underlying OS adds them (though in Edge's case it's more likely it was written from the ground up using newer APIs)

- they quite possibly want to use "you can get the new browser only if you upgrade" as a carrot for OS upgrades (they explicitly did with IE, I haven't seen anything explicit for Edge but it wouldn't surprise me if they're still taking that approach)

The lack of subscription and signup, combined with the pricing, suggest that this is aiming at people who almost never send a fax, and would spend significantly more buying and maintaining a fax machine, compared to a couple dollars on this service.

I do hope you find a service that fits your need, but this is very likely not intending to be it.

it works. doesn't feel very native, but then neither do a lot of the big names in chat right now

it's US english, they're referring to Lego the product as a whole, rather than individual Lego pieces (the meaning ends up basically the same, but the distinction does change the grammar)

Exactly so. It's not strictly correct modern English as far as I know, but it's quite a common slip amongst French speakers (from their names I would strongly suspect at least one of the core Pijul folks fits that category) for whom the native word is indeed "edition".

I've never really gotten into absolute line numbers, but relative ones are a godsend for me since I use <num>j, <num>d, et al a lot but can't really eyeball how many lines away something is once it gets to be more than 2 or 3.

The crucial distinction as far as the OP is using the term seems to be that such a datastore does not require the user's hosting provider to give them an instance of any of the common DB servers, which typically needs a more expensive plan than the usual baseline of "disk space and an httpd [that supports calling out to one or two scripting languages]".

(Basically it should run on anything more complex than a static site host. Though it's also true that sqlite would probably be a cleaner choice for the datastore without losing any of that benefit.)

or V for Vendetta

That link seems to be about Windows Server (no version stated, but given it's upcoming, presumably 2016), did you mean to post a different one?

Assuming I'm reading the parent post correctly, neither of those links actually do what they would've been hoping for when moving browsers, even if they certainly get closer than nothing.

Firefox Sync only syncs with versions of Firefox, and Chrome's sync only syncs with versions of Chrome, so they'd have to switch mobile browsers too just because they switched desktop browser (and unlike on desktop, I've found Firefox for Android to generally be clunkier to use than Chrome for Android).

And that second link is about Chromecasting from Firefox for Android, not the desktop browser. Being able to send stuff from desktop Chrome is definitely a convenience someone could get accustomed to.

There's various ways:

Some rely on the device itself to enforce it, but that's obviously fragile if you can bring your own device.

Some check the TTL of your packets when they enter the carrier's network, because tethering is at least one more hop and so even if your computer's OS and phone's OS agree on what TTL starts at, the TTL will still be different than expected for your device's platform. Obviously this can still be mitigated by adjusting your TTL, but outside of software that'll handle this for them, that's already beyond a lot of customers.

Some even take the route of only checking HTTP traffic, and detecting tethering based on User-Agent, but I think a lot have abandoned that because it doesn't catch other protocols, and is easily bypassed even on HTTP.

However, that still makes it a conscious choice to engage with the service that way - the default way is still checking back, and that shapes the general usage patterns of the site, even if some people have concluded it benefits them more to modify their experience.

Unfortunately, I suspect you overestimate the obfuscating power of dynamic content when the number of users is sufficiently large.

A certain MMO I play recently had a limited-time event built around figuring out the meaning of different clues (locations to go to for the actual meat of the event), and despite a fairly large number of variations, people had collectively figured out just about every possible clue->location mapping within a matter of hours.

That's not to say you can't prevent cheating, but that even with relatively little incentive (that whole clues thing gave only a single cosmetic item, and anecdotally I've seen very few people actually use theirs) users can and most likely will outpace any attempt to prevent it by means of varying the problem.