adambrenecki's comments

IIRC, because the payment terminals have their own power source, previous iPhone generations lacked the induction coils necessary to support passive NFC tags. Presumably they were added to the iPhone 7?

Don't forget, it's not just about consumer applications. Anywhere you might use a QR code or traditional barcode, but you don't want to have to worry about the barcode becoming obscured or worn with use. I know we've thought about using them to track vehicles and some kinds of parts in the automotive retail company I work for, and there's probably plenty of other industrial applications for them.

Pricing is €1,499, according to http://bgr.com/2017/02/28/sony-xperia-touch-release-date-pri...

This would be awesome if it weren't for that price.

...is this a parody?

This is how they want you to use it:

> Trademarks are proper adjectives and should be followed by the generic terms they describe.

> Correct: The image was manipulated using Adobe® Photoshop® software.

> Incorrect: The image was manipulated using Photoshop.

Adobe's own marketing pages consistently use the ostensibly "incorrect" usage though: http://www.adobe.com/au/products/photoshop.html

Photoshop is a verb.

Adobe's trademark lawyers would very much like it to not be a verb, but it is. They've lost that battle long ago.

As someone who has Coeliac disease: shhhhhhh! /s

When I was first diagnosed, you couldn't buy groceries or eat out _anywhere_. Now, pretty much every restaurant has gluten free options marked on their menu; every supermarket has a wide range of bread, flour, cake mixes, biscuits, and so on; and manufacturers of packaged food are swapping out incidental gluten-free ingredients like wheat starch for gluten-free alternatives. You can bet that's because of people that think gluten-free food is "good for you", rather than the much smaller group of Coeliacs ourselves.

I can't vouch for it myself, but the Django Girls tutorial [1] is the resource I hear recommended most often for learning Django without any prior programming experience.

[1]: https://tutorial.djangogirls.org/en/

Yeah, QF has already done this (for their domestic flights at least, as of last August) and they had motorised overhead monitors that folded down for the safety video.

To be honest, the author of that blog post seems like he's kinda being a bit of a dick.

> I submitted several lint cleanup pull requests. Getting each one accepted was a challenge. Primarily because the project owner isn’t really interested in having lint clean code.

Having read through the PRs he filed[1], the "challenge" the author faced was to do with his needlessly changing things around to match Google style guide, which the project doesn't actually observe. (There's a lot of comments of the form "as a former Google employee, my shit doesn't stink" in there, as it happens.) In fact, most of them were merged straight away except his last one[2], where he'd changed existing code away from the project's preferred style, been asked not to, then threw a tanty and closed the issue.

> for d in filter(os.path.isdir, path):

This and the other example he gives are both from that last issue, which leads me to think this blog post was part of the aforementioned tanty. (It was published on the same day, too.) Let's be honest, if the worst issue you can find with a codebase is that it uses filter() instead of a generator expression, it's probably a pretty good codebase.

> All you have to do is Google “python map filter deprecated”.

Yes, do, and you'll find they aren't. The BDFL doesn't like them, but that's not the same thing.

> I noticed that the directions for running the unit tests did not test the code in my local git repository — it tested the code installed by pip. ... Anthony told me he wrote the directions to specifically test the installed code, not the code in his git repository and he didn’t understand why anyone would test their uncommitted code.

I can't find the issue where he raises this, or where the maintainer says that. Perhaps the author isn't familiar with `pip install -e`? All of the other issues in that first 'P.S.' paragraph appear to be fixed, some by him even.

tl;dr This doesn't seem like a damning criticism of fundamental project management issues so much as a tantrum being thrown by someone because they couldn't walk in to a project and impose their stylistic preferences on everyone else.

[1]: https://github.com/xonsh/xonsh/search?utf8=%E2%9C%93&q=is%3A... [2]: https://github.com/xonsh/xonsh/pull/512

> in connection with our provision of the Service.

This is pretty much boilerplate legalese that's generally intended to mean "you can't upload a file to your public folder, then sue us for copyright infringement because that file is in a public folder".

Lawyers seem like to cover their clients' asses as much as possible, but for a service like this that's designed for privacy-conscious people it'd do them well to step back and think about how the license comes across to privacy-conscious laypeople.

From what I've seen of Keybase, from back when they were just an alternative to the PGP Web of Trust to now, I don't think they're genuinely planning anything nefarious (but they'd still do well to have a ToS that reflects that).

There's a bunch of other tools[1][2] that do this sort of thing already, although all the ones I've seen display file size as a sort of flame graph/pie chart hybrid (imagine a flame graph wrapped around a circle).

This flat representation is probably better because it doesn't exaggerate the size of deeply nested files, but I find the example in the article a bit harder to read.

[1]: https://daisydiskapp.com/ [2]: http://www.jgoodies.com/freeware/jdiskreport/

This is a neat idea; it's sort of an entity-relationship diagram or class diagram for API resources.

In fact, if your audience is familiar with these sorts of diagrams, I wonder if it'd be more readily scannable if you denoted the cardinality of the relationships with the sort of notation you'd see in ERDs or CDs? (Personally, I'm a big fan of Crow's Foot.)

By the sounds of it, you'd use this as an overview and use something like Swagger for the actual details of each endpoint.

(For that matter, if you output the diagram in a format that supports hyperlinks like SVG or PDF, you could link from the diagram directly into Swagger.)

I kind of wish there was a ALGPL; a license that works like the AGPL in terms of access over a network being considered use, but could be used unmodified as a library in non-GPL-compatible software like LGPL libraries can.

Sadly, I doubt the FSF will ever write such a license, given how they discourage use of even the LGPL unless absolutely necessary.

> red tape

...

> Such technology is illegal because jammers are likely to affect wider areas and other frequencies than those they are intended for. They can also result in the disruption of emergency and rescue radio services in the public area.

Oh fuck off. This isn't red tape, this is the law doing exactly what it's supposed to: protecting public safety and people's access to an essential service.

I'd love to see this principal bleating about "red tape" to the coroner after one of her students is hit by a car out the front of the school, and dies because nobody can call an ambulance.

(Well, no, I'm glad that this nonsense is being nipped in the bud before something awful like that happens, but that's exactly the scenario this idiot is setting herself up for.)

Existing certs (those with a notBefore date before Oct 21 [0]) are still trusted by Firefox. New certificates are not.

(WoSign could theoretically backdate the notBefore date on new certs to make them look like existing certs, but Mozilla have said that if they catch WoSign doing this they'll distrust their root totally.)

Other browsers are taking similar measures, but I'm not sure on the details.

[0]: https://blog.mozilla.org/security/2016/10/24/distrusting-new...

The closest the industry came to what you're describing, unfortunately, was Pebble. They were cheap (IIRC the OG Pebble was around $99); while they didn't last _multiple_ weeks you could get 7-10 days out of a charge depending on model.

I use my Pebble Time Steel pretty much exactly how you're describing; to glance at the time, weather, and notifications, so I can keep my phone on silent in my pocket.

Apparently nobody except you and I want that, though :(

This is really sad; Pebble had probably the best products on the smartwatch market, and I'll be disappointed to see them go.

They were the only smartwatch manufacturer that could claim anything close to 10 days of battery life. They were the only smartwatch manufacturer that made devices that were water resistant and really meant it. (That is, they're all rated to 3-5 ATM and tested the same way regular watches are, you can actually use them in chlorinated or salt water, and they didn't try to claim that your "water resistant" device's warranty was void if you got it wet.) They were the only smartwatch manufacturer that made devices that had an always-on display that's actually any good (with the possible exception of the just-released Gear S3; I've yet to see one in person but it sounds like Samsung are getting there). It's a small thing, but they were also the only smartwatch manufacturer that didn't take themselves too seriously, filling their UI with cute icons and animations that made the watch fun to use. All that, and their products were significantly more affordable than some of their competition.

Oh God, that sounds an awful lot like two more Australian systems: the Queensland Health payroll debacle, where a bunch of health workers were paid incorrectly or not at all. Or the National Disability Insurance Scheme debacle, where healthcare providers haven't been paid, resulting in small business owners having to take out huge amounts of personal debt just to pay their employees, and sole traders unable to provide services their clients need to live day to day while still keeping a roof over their own heads. (They're both IBM projects too.)