abbot2

Yes, bluetooth has plenty of unfortunate limitations. For example, there is no standard high-quality bidi audio codec in bluetooth spec (see https://www.ipetitions.com/petition/duplex-high-quality-audi... for detailed explanation).

ASN.1 is extremely complicated and hard to implement correctly. All ASN.1 implementations I've seen are either specialized (know how to work only with a very specific message), or slow, buggy and expose equally complicated APIs. Modern systems like protobufs tend to use much simpler encodings & specs which are easier to understand and implement correctly.

Take the state of the project as a market fit test of the idea?

This already exists: https://ubuntu-touch.io/

Not available in the UK. Online movie distribution they said.

Try staying on the page for a while and scroll around. Pretend to read it. Triggers for me on mobile chrome browser.

evil, adj.: morally bad, cruel, or very unpleasant

I totally get the frustration and such, and not trying to protect Amazon, but: author's web site intercepting browser history to trigger "checkout this content before you leave" when back navigation is clicked is outright evil. Just don't do that, be kind to visitors.

Edit:

1. Dictionary: evil, adj.: morally bad, cruel, or very unpleasant

2. To get the prompt you need to stay around on the page for a while, scroll around, pretend to read it. Triggers at least in mobile chrome browser.

I find it amusing that the advice in the style guide gives a good example contradicting another good example, and contains a subtle bug.

In the "Reduce Scope of Variables", second good example leaks an open file when WriteString fails, because it doesn't follow the own advice of "Defer to Clean Up" if you are curious.

(Handling that properly with a defer is a bit more tricky - something like https://play.golang.org/p/l1PeWM3Tisg).

Update: style guide was fixed after this report :) It was this if you wonder: https://github.com/uber-go/guide/blob/a53ee0bef8c0b11b52340d...

I'm fine with paywalled content overall. I'm not fine with paywalled content on the front page of hn, because it reduces hn utility: I can't see the content.

Wired web site displays annoying "pay us now" banner over half of the page on a phone browser, which cannot be removed, probably due to JavaScript bug. Can't help, but flag this.

1. Force everyone to register to get access to content. 2. Leak that data. 3. ... 4. Profit. Not sure how this part works though.

I hope lesson should be learned: don't force users to register just because you can

I never claimed this design to be Russian ;) I only said it is very popular there.

Suprisingly enough, this collection doesn't seem have the design most common & popular in Russia, roughly this: https://www.youtube.com/watch?v=mrsxMqvHXkw.

It's England. You don't tip here.

May be in reading it wrong, but that page contains another video, couple example snapshots and "why we built this". I still have no idea what all the fuzz is about, and I'm not wasting my time on videos.

I wonder, is there a quick way to learn what's that all about without watching a video? As usual, seems like good old text reading/writing skills are ignored...

A friend of mine who used to work at McDonalds, told that "custom" burgers are always made to order, so he advised that if you want a fresh hamburger, order a cheeseburger with no cheese - you'll get a fresh made to order hamburger and cheese on the side.

The most hard part of PKI is omitted completely in the article: how to deal with revocations (CRLs, OCSP and such). Hope that's not because they "forgot" to do that in their actual infrastructure.

Everyone. You are not buying "5 grams of golden earrings", you are buying earrings which fit you, hence the volume.

I've been using Jawbone 24, and after it broke down (button stopped working) decided to switch to Fitbit Flex (thought, software will be better). I've been using both devices with Android phone. Its terrible for either of them. In fact, Fitbit one has even more critical quirks than Jawbone (e.g. unreliable alarm synchronization). Hardware is great for both devices. Software is just pure disaster.

Seriously? I don't consider myself poor by any standard, but I'll also think 5 times before buying a 1500 sofa. It's just stupidly expensive.

A better question would be "why the poor buy a $1500 sofa"?

Your API sucks and is not as idiomatic as you think if you can't use curl as a client.

Don't get me wrong, I perfectly understand what interface{} is and why someone is tempted to use it. It just kills the type checking and converts your golang code to a compiled python, without all those nice static analysis things. Yes, API would be larger, but it would be compile time type-checked and you wouldn't depend on things like "well, it will most probably crash very early enough".

When I read things like "func Get(pattern interface{}, handler interface{})" I start questioning why this whole thing is ever written in Go at all? This kind of ditches half of Go's benefits by moving all type checks to run time.

Am I the only person who thinks that relying on client behaviour for "security" is, well, a bit naive?

Watched 40 seconds. Don't have sound. Understood nothing.