Searched for "May 14, 2019" in this user's bookmarks. Found 66 results

« earlier   

Twitter
Google has been advertising Pixel on its search page for years.

Sales of ~4m fire sale Pixels just show how ineffective Google’s ads are.

Apple sells 215M ~$750 iPhones each year. And it also makes money on secondary sales of refurbs. But yeah, pretty much the same isn’t it?

— Daniel Eran Insider (@DanielEran) May 14, 2019
FavoriteTweet  DanielEran 
3 days ago by mjtsai
Twitter
They’re still there. So that’s not what happened.

Bindings has some technical issues that still exist so many years later. Poor KVO support for the controllers, bugs that are more than 10 years old. The binders should have been public.

I’m surprised people still use them.

— Scott Anguish (@sanguish) May 14, 2019
FavoriteTweet  sanguish 
4 days ago by mjtsai
Twitter
TIL: “defaults find NSUserKeyEquivalents” - I've never known about the “find” variant of defaults. Plus that means changing command keys can easily be done via script, which you would think I would know.

— Peter N Lewis (@peternlewis) May 14, 2019
FavoriteTweet  peternlewis 
4 days ago by mjtsai
Twitter
If anybody has tried playing music videos in Apple Music, they won't be at all surprised by this. https://t.co/ZNB4EUIAyW pic.twitter.com/o9Xd0qv3wf

— Dan Masters – OhMDee.com (@OhMDee) May 14, 2019
FavoriteTweet  OhMDee 
4 days ago by mjtsai
Twitter
This has saved my bacon many times.

(And before the don't use CoreData rabble rousing, I've yet to see another database framework handle threading any better than CoreData. At least CoreData has a way to catch the issues.) https://t.co/SH3QVZ4eGy

— Colin Cornaby (@colincornaby) May 14, 2019
FavoriteTweet  colincornaby 
4 days ago by mjtsai
Twitter
I tried Lightroom for several months but canceled the subscription because I didn't feel like I was getting good enough value. Seems that things are only worse now. https://t.co/mGlFahbKii

— Greg Hurrell (@wincent) May 14, 2019
FavoriteTweet  wincent 
4 days ago by mjtsai
Twitter
Yep. AnyHashable only helps if you have two Hashables and they may or may not be the same type. Doesn't help if you have two not-Hashables of some kind

— Tanner B (@NSExceptional) May 14, 2019
FavoriteTweet  NSExceptional 
4 days ago by mjtsai
Twitter
@benthompson How can you say “making tech policy according to a 40-year old case about brick manufacturers is stupid” while wishing the precedent was upheld?

(I had a hard time following the writing, I’m not trying to argue, but understand.)

— Ryan Jones (@rjonesy) May 14, 2019
FavoriteTweet  rjonesy 
4 days ago by mjtsai
Twitter
Yeah, once you’ve received something as an Any, it’s too late to turn it into an AnyHashable, right?

— Michael Tsai (@mjtsai) May 14, 2019
mjtsai  Twitter 
4 days ago by mjtsai
Twitter
So ideally, everything would (or could) automatically conform to RuntimeEquatable, and RuntimeEquatable itself could conform to Equatable.

This seems like a really flexible solution to me, someone poke some holes in it

— Tanner B (@NSExceptional) May 14, 2019
FavoriteTweet  NSExceptional 
4 days ago by mjtsai
Twitter
For sure. Which is why it should be opt-in, either by something like adding Equatable conformance to Any by hand, or by adding another protocol, RuntimeEquatable or something, which synthesizes conformance just like Equatable but includes that boilerplate type-checking

— Tanner B (@NSExceptional) May 14, 2019
FavoriteTweet  NSExceptional 
4 days ago by mjtsai
Twitter
Function equality is undefined because it depends on optimizations. But also what if the function value is a closure with captures?

— Slava Pestov (@slava_pestov) May 14, 2019
FavoriteTweet  slava_pestov 
4 days ago by mjtsai
Twitter
This seemed like the obvious solution to me, so I assume there’s something I’m missing.

— Michael Tsai (@mjtsai) May 14, 2019
mjtsai  Twitter 
4 days ago by mjtsai
Twitter
I guess there’s a small performance win because you statically know that the types are the same, so you can avoid that check.

— Michael Tsai (@mjtsai) May 14, 2019
mjtsai  Twitter 
4 days ago by mjtsai
Twitter
Annnnnnd there’s the gotcha I expected google to force: Alexa and Assistant can’t both be active at the same time because politics pic.twitter.com/kOle1kBY9f

— Owen Williams ⚡ (@ow) May 14, 2019
FavoriteTweet  ow 
4 days ago by mjtsai
Twitter
One big theme with AppKit is it is insanely faster at building applications driven by data. Not only do you get things like bindings and passive formatters, but you also get multicolumn/resortable/reorderable tables and token fields. AppKit is just a monster at these tasks.

— Colin Cornaby (@colincornaby) May 14, 2019
FavoriteTweet  colincornaby 
4 days ago by mjtsai
Twitter
That comes down to the same problem, but with Hashable instead of Equatable. Both have "self or associated type requirements," which means I can't use them for anything meaningful since they can't be used as generic constraints

— Tanner B (@NSExceptional) May 14, 2019
FavoriteTweet  NSExceptional 
4 days ago by mjtsai
Twitter
Yeah, this is really annoying. Is there an advantage to the Self requirement other than making it more concise to implement == by avoiding manual type-checks? Seems like there sould be a way to separate those issues.

— Michael Tsai (@mjtsai) May 14, 2019
mjtsai  Twitter 
4 days ago by mjtsai
Twitter
But also, I usually want the type-check. Just like in Objc land.

Maybe another Equatable sort of protocol would be more appropriate for that. Unfortunately I can't make my own that behaves just like Equatable, because it gets compiler help synthesizing conformances.

— Tanner B (@NSExceptional) May 14, 2019
FavoriteTweet  NSExceptional 
4 days ago by mjtsai
Twitter
Posts updated today:

Collision Coursehttps://t.co/GgBFu3BxZq

New Mac Pro Won’t Arrive Until 2019https://t.co/wO8uIsHAXW

The Unofficial Guide to xcconfig Fileshttps://t.co/7KTbH0IhRj#mjtsaiblog

— Michael Tsai (@mjtsai) May 14, 2019
mjtsai  Twitter 
4 days ago by mjtsai

« earlier   

Copy this bookmark:



description:


tags:



Copy this bookmark:



description:


tags: