lparry's comments

“Give me directions to foo” - gives directions to foo in apple maps

“Give me directions to foo using Waze” - gives directions to do using Waze

This might be new, but it definitely works on the iOS 13 beta, although I’m pretty sure it worked on iOS 12. It would still be nicer if we could just set default apps

Im two years in and I hate the keyboard. I actually didn’t hate it to start with because the bigger keys felt nice and I figured my accuracy would return after I got used to it, but it’s been literally years and I still make constant typos on this thing. I recently started using an external old-Mac-style keyboard and suddenly I can type without mistakes again, it’s honestly bizarre. Muscle memory wouldn’t last this long, there’s something about the newer design that just doesn’t work for me

> If I'm listening to a podcast on my phone, I'm going to have my phone on me. I'm not going to walk away from it because then I couldn't control the playback.

Every set of wireless headphones I’ve owned have let me control play/pause/skip from them, which makes up 95% of the playback controls I ever use. The last 5% I can do from my watch. Roaming about the house listening to stuff without a care where my phone is seems totally normal to me these days. I would never go back to wires now I’ve lived with the benefits of wireless.

FTR I was equally skeptic before I bought some cheap $10 Bluetooth earbuds to try running without wires tugging with every stride, and found myself wanting to use them all the time in spite of their awful sound quality so I bit the bullet and got some decent ones

A long press wouldn’t suffice, since you’d still need the second gesture (more pressure with the 3D Touch implementation) to switch from moving around a cursor to select mode (ie. moving around the second cursor). Not claiming 3D Touch is the only way it could be done, but a long press seems like it could only support a subset of apples cursor mode.

You must be fun at parties!

> Frontenders can write their frontend code in whatever they see fit. REST is a contract on data and format of the data between frontend and backend.

Oh, it’s a contract? Amazing, I guess that means you can just update the contract and nobody is stuck doing busywork anymore. Nope? I guess then either your frontenders need to learn your backend stack, lest they be stuck waiting for someone to do the busywork for them. I feel like I’m repeating myself, because I am. Please don’t quote out of context

> Now tell me: > - what will you do when your glorious ad hoc GraphQL query ands up bringing the database to its knees? > - what will happen when your glorious GraphQL schema doesn't have all the data the frontend needs?

Sound like interesting, challenging, and satisfying problems for the backenders to work on. Certainly more so than adding/removing fields from serialisers. These also seem like much more rare problems than the small data requirement changes that are the backbone of frontend work.

I’d rather work on speeding up the things that slow down development and deal with performance when it becomes a problem. I dunno, maybe our experience differ, and in you world your app is relatively static and performance is crucial, but the world I exist in involves stakeholders constantly wanting minor changes, performance has never been a problem, and development is constantly blocking because of frontend/backend blockers on our “rest” api and capacity on either side being wasted at various times because of that blocking.

Sure, sometime someone’s going to write a horrendous graphQL query where the answer is going to be “sorry, we can’t make that perfomant so we have to disallow it”, but that’s a: solvable and b: going to happen a lot less often than your frontend is going to need an extra field (or no longer need a field, but since nothing breaks these change requests rarely come through and your backend is eternally querying and sending unused data over the wire)

Because in rest, urls are supposed to specify a resource, but now your response is a resource and some other resources too.

Not saying that being pure to rest ideology is a good thing. I think it’s a terrible fit for most applications more complex than a demo todo app

And now your frontenders need to know how to write code in whatever your backend is written in, lest every new change be bottlenecked waiting for someone to build them new endpoints. Also, your backend guys are tied up constantly doing stupid endpoint changes, and both teams are wasting time messing around with extra effort to allow one side to be deployed before the other, instead of working on actual functionality work. Doing this in REST is a genuinely unpleasant experience, well deserving of being called hacky

Apple has never sold updates for iPhones. What you’re misremembering is them selling updates for iPod touches back at iOS 2 because of some perceived accounting issue, and the cost was pretty token, something like $5-10 IIRC correctly. Hardly a cash cow that would have had them making more optimisations then they do today

> the convenience of Apple Pay seems to be moving backward as I'm forced to use my PIN and sign in all sorts of places I used to be able to just wave my phone at.

This is a rant against how you imagine things work, instead of how they actually work. I put my watch on in the morning and it is automatically unlocked the next time I unlock my phone with touch id. From this point on, the pin is never required. Apple Pay is just a double click on the long button, no pin entry as you've imagined if the watch is unlocked, which is true unless you've only just put on the watch.

waiting for the face to light up however, is a legit complaint. It really sucks that there's not even an option for "always on" that you could use while working out, as it's a pain in the ass to be running and want to check your current pace and find that wrist-flick detection failed so you're staring at an off instead of getting the data you wanted and getting back to looking where you're going quickly again.

I can't speak for the other commenters, but for me it's because my browsing style was formed back in the days of dialup in Australia. You'd click a link and wait 30+ seconds to have the page load, so instead of staring a loading page you'd open anything that looked interesting in a new tab and continue on the current page, so all the interesting links would be there ready to read without waiting. invariably you wouldn't end up having enough time to read them all, but they piqued your interest enough to open them, so you'd keep them around in the hope that some time later you would. Rinse, lather, repeat, and add in persistent browser sessions between restarts and suddenly you've got 100+ tabs open.

The internet is much faster these days, but I still open way more links than I actually have time to read because they sound interesting

Even if it's not an instance method you can write the first as

  validated_items = items.select(&method(:is_validated?))

(Typed on my phone but I'm pretty sure that's the right syntax)

Won't the binding then be your monkey patched debug method on kernel instead of where you called it from?

If that driver with a criminal record keeps their rating high enough to keep driving, what's the problem? A reformed criminal who drives safely and is pleasant to their passengers would be better than half the taxi drivers I've ever had the displeasure of dealing with

Properly learning any editor is like learning an instrument. Once you're comfortable with one, you're going to be more comfortable with that one than the others.

Likewise, some editors are similar enough that you can chop and change quickly, others not so easily. Atom and sublime are like members of the guitar family, while vim is like a piano. They can all produce lovely text files in the hands of a skilled musician

complete stab in the dark here, but perhaps however you're getting your work onto master is rewriting timestamps (NFI if the graph goes off authored or commited dates).

Maybe try 'git checkout master && git merge --no-ff feature-branch' and see if that helps

I can't if you're being sarcastic, or just exhibit some really strange driving behaviours

Too small? Logitech makes a keyboard cover for the mini [1], they'll surely do one for the ipad air

[1] http://www.logitech.com/en-us/product/ultrathin-keyboard-min...

I'm pretty certain you're completely screwed if that happens. I don't think it's worth that level of risk to not know the password for your 1Password vault

Wow, you're either one of those incredibly rare ruby devs who actually run windows, or you're going to switch your entire environment in order to switch frameworks. Something doesn't smell right