The weird thing is their web version / chrome app never has the state problems for me. But the mobile version on iOS screw s up regularly. I'll reach the end of my feed with the "all done" screen and upon refresh all the stuff I just read pops back as unread. Really annoying.
The stack trace contains the stacks of all the goroutines. The running goroutine which caused the panic is printed first, so it should be pretty easy to find the source of the problem. At least I haven't had any issues in debugging complicated apps with thousands of goroutines...
Ideally by the time we get to that point of surveillance we'll have sufficiently advanced self-driving vehicles such that driving infractions will no longer be a thing.
Most financial transactions that hit the banking system at some point can already be tracked and audited. Arguably many people who elude that are basically ripping off the rest of society. As far as banks cheating people, maybe that kind of surveillance could help curb that?
Definitely would need to be careful about how far it pervades in to private life. Maybe it's impossible to limit, in which case it's probably a bad idea.
"This may seem confusing at first, but makes sense since TLS is just a minor update to SSL 3.0. Subsequent versions of TLS have followed this pattern. Since TLS is an evolution of the SSL protocol, people still use the terms TLS and SSL somewhat interchangeably."
Yeah, but it's one I found I often neglected in the past. I ended up buying a Roomba since it was on sale and it's worked out quite well. It's not perfect at vacuuming but on average the floor is a lot cleaner when I can run the Roomba every couple of days while I go out for lunch versus me getting around to vacuuming every few weeks.
$99? That's well in to "shut up and take my money!" territory. I've long wanted to buy a GoPro for the occasional kayaking / climbing / skiing footage but there was no way I could justify the price tag. $99 (+$40 waterproof kit) really changes the equation for casual shooters like myself.
Car2go also has a $14.99 / hour maximum, so you could potentially drive it a lot more and for multiple stops. No way you could hire an UberX to drive you around the city for an hour for that price.
Why would you send a string which is not valid utf8 over the wire in your system? That's the kind of validation that should probably be done prior to that. Or if it hasn't, you can do the validation manually on the receiver. There's no reason to incur the cost on each transmission.
You're comparing apples to automobiles. The documentation and video accompanying the Swift announcement was the official promotional materials and guides. The document linked here is a development proposal sent by a developer to the golang-dev mailing list outlining his intentions to work on a feature for the next release.
That's not been my experience, often it helps to add more context to errors as they propagate through the layers. Unless you control the entire stack of function calls top to bottom as part of your application, I think it's ogyrn bad form for one library to bubble up another library's errors directly. It's effectively leaking implementation details and it means the clients of your library may also have to import your dependencies to handle the errors.
Isn't someone going by the handle "rubyn00bie" criticizing an article with "call me maybe" in the title as being juvenile something akin to the pot calling the kettle black?
"Enhanced application development, delivery, portability and isolation through Linux Containers, including Docker, across physical, virtual, and cloud deployments as well as development, test and production environments."
What's even weirder is that with the Apple Store app you can scan your own items and just walk out of the store. Haven't tried it with anything really expensive, but I bought an iPad case for around $80 and just scanned it with my iPhone and left. I was half expecting someone to run down the street to catch me as I walked away.
As a user with an account, I also struggle with linking to tweets. The process right now is something like this:
1. See tweet in timeline, click the "expand" link in the lower left, or just some other blank spot in the tweet.
2. Hunt around until I see the non-obvious de-emphasized "details" link in light grey next to the date.
3. Click the "details" link and load the full page for the tweet.
4. Copy the link from the browser URL bar.
I don't know why they make it so hard and require me to load a whole other page and interrupt my timeline browsing flow. Annoyingly there's a "more" link on each tweet which I always end up checking anyway, and it doesn't have an option to copy a link to the tweet! You can "share via email" or "embed tweet" but neither of those gives you a useful URL you can just paste somewhere. The UI is a train wreck.
> Working at POF is like working at McDonalds. It's temporary. Pay is anemic for even the people who control the site, so they'll bounce once something better comes along.
I don't think that's necessarily correct. I know people who have been working there for quite some time and enjoy it.