mjtsai + jckarter   342

Joe Groff on Twitter: "I'd call it a bug. `lazy var` was implemented in an extremely hacky way (it really just generates a get/set), and most of its idiosyncrasies come from that… https://t.co/qFohVqGEGv"
I'd call it a bug. `lazy var` was implemented in an extremely hacky way (it really just generates a get/set), and most of its idiosyncrasies come from that

— Joe Groff (@jckarter) February 13, 2018
FavoriteTweet  jckarter 
7 days ago by mjtsai
Joe Groff on Twitter: "Well, the other way to deal with non-ideal initialization order is to use T! types, so they can initialize to nil and Swift won't bother you about really initializing them later. If anyone bugs you about it, tell them I said it was
Well, the other way to deal with non-ideal initialization order is to use T! types, so they can initialize to nil and Swift won't bother you about really initializing them later. If anyone bugs you about it, tell them I said it was OK

— Joe Groff (@jckarter) February 12, 2018
FavoriteTweet  jckarter 
8 days ago by mjtsai
Joe Groff on Twitter: "Why do we call ourselves "software engineers" and not "Knights who say NIH""
Why do we call ourselves "software engineers" and not "Knights who say NIH"

— Joe Groff (@jckarter) February 10, 2018
FavoriteTweet  jckarter 
11 days ago by mjtsai
Joe Groff on Twitter: "To be honest, our thinking was "why would anybody be using IUO *at all*". We hadn't considered the "workaround for other IUO problems" case. If your use case really is the only one, maybe we should reconsider the warning.… https:/
To be honest, our thinking was "why would anybody be using IUO *at all*". We hadn't considered the "workaround for other IUO problems" case. If your use case really is the only one, maybe we should reconsider the warning.

— Joe Groff (@jckarter) February 8, 2018
FavoriteTweet  jckarter 
13 days ago by mjtsai
Joe Groff on Twitter: "Following the 1/2/N rule, you copied and pasted the code for the first H, right… "
Following the 1/2/N rule, you copied and pasted the code for the first H, right

— Joe Groff (@jckarter) February 7, 2018
FavoriteTweet  jckarter 
14 days ago by mjtsai
Joe Groff on Twitter: "Reminder: running 32 bit processes on a 64 bit CPU for prolonged periods can lead to burn-in of the unused high bits. Degauss your CPU regularly"
Reminder: running 32 bit processes on a 64 bit CPU for prolonged periods can lead to burn-in of the unused high bits. Degauss your CPU regularly

— Joe Groff (@jckarter) January 31, 2018
FavoriteTweet  jckarter 
21 days ago by mjtsai
Joe Groff on Twitter: "IIRC one of the things that made us pick Discourse is that it was supposed to have "good" email interop for people who prefer that? No idea how to get to that point though… https://t.co/lI71n6HgcP"
IIRC one of the things that made us pick Discourse is that it was supposed to have "good" email interop for people who prefer that? No idea how to get to that point though

— Joe Groff (@jckarter) January 29, 2018
FavoriteTweet  jckarter 
22 days ago by mjtsai
Joe Groff on Twitter: "The box you get when you turn a Swift value type into an AnyObject looks for an Equatable conformance and uses that to implement -isEqual: if available.… https://t.co/Tx1tdfhxDP"
The box you get when you turn a Swift value type into an AnyObject looks for an Equatable conformance and uses that to implement -isEqual: if available.

— Joe Groff (@jckarter) January 23, 2018
FavoriteTweet  jckarter 
28 days ago by mjtsai
Joe Groff on Twitter: "@nicklockwood Everything bridges to AnyObject. That shouldn’t crash, baz should end up NSNull"
Everything bridges to AnyObject. That shouldn’t crash, baz should end up NSNull

— Joe Groff (@jckarter) January 17, 2018
FavoriteTweet  jckarter 
5 weeks ago by mjtsai
Joe Groff on Twitter: "@lapcatsoftware The Swift compiler has an optimizer barrier in it for this case. If you put the result of a misannotated ObjC call directly into an Optional… https://t.co/r2jX9fBiuv"
The Swift compiler has an optimizer barrier in it for this case. If you put the result of a misannotated ObjC call directly into an Optional, it’ll handle the nil return case correctly.

— Joe Groff (@jckarter) January 13, 2018
FavoriteTweet  jckarter 
5 weeks ago by mjtsai
Joe Groff on Twitter: "@davedelong @SwiftLang Protocols with associated types are totally fixable. Just a matter of time."
Protocols with associated types are totally fixable. Just a matter of time.

— Joe Groff (@jckarter) January 12, 2018
FavoriteTweet  jckarter 
5 weeks ago by mjtsai
Joe Groff on Twitter: "Who says Swift is a static language? With @dgregor79's recent runtime improvements, (almost) any type can be dynamically formed from a strin… https://t.co/IyYBuFmk5x"
Who says Swift is a static language? With @dgregor79's recent runtime improvements, (almost) any type can be dynamically formed from a string: https://t.co/CxI2RKG6fu

— Joe Groff (@jckarter) January 10, 2018
FavoriteTweet  jckarter 
5 weeks ago by mjtsai
Joe Groff on Twitter: ""How much can one banana possibly cost?" https://t.co/daGJEICNLQ"
"How much can one banana possibly cost?" pic.twitter.com/daGJEICNLQ

— Joe Groff (@jckarter) December 20, 2017
FavoriteTweet  jckarter 
8 weeks ago by mjtsai
Joe Groff on Twitter: "It has never been easier to write calendar math bugs than in C++14 https://t.co/4dgz648pqM"
It has never been easier to write calendar math bugs than in C++14 https://t.co/4dgz648pqM

— Joe Groff (@jckarter) December 19, 2017
FavoriteTweet  jckarter 
9 weeks ago by mjtsai
Joe Groff on Twitter: "@mjtsai The bug is fixed. Radar for closed but Jira wasn’t updated to match."
The bug is fixed. Radar for closed but Jira wasn’t updated to match.

— Joe Groff (@jckarter) December 13, 2017
FavoriteTweet  jckarter 
9 weeks ago by mjtsai
Joe Groff on Twitter: "@mjtsai @lapcatsoftware @AirspeedSwift Logging with a breakpointable symbol name (something like __SWIFT_IS_BRIDGING_DICTIONARY_WITH_DUPLICATE_KEYS__) would also allow people who… https://t.co/4fdH7K1pp4"
Logging with a breakpointable symbol name (something like __SWIFT_IS_BRIDGING_DICTIONARY_WITH_DUPLICATE_KEYS__) would also allow people who want to “crash” when they’re trying to chase down the source of the collision too.

— Joe Groff (@jckarter) December 11, 2017
FavoriteTweet  jckarter 
10 weeks ago by mjtsai
Joe Groff on Twitter: "@lapcatsoftware @mjtsai In top-of-tree Swift (not sure about 4.0) you can also explicitly avoid problematic bridging if you immediately coerce an argument or return… https://t.co/DMHFwBH10F"
In top-of-tree Swift (not sure about 4.0) you can also explicitly avoid problematic bridging if you immediately coerce an argument or return value `as NSDictionary` at the call site. cc @pathofshrines

— Joe Groff (@jckarter) December 11, 2017
FavoriteTweet  jckarter 
10 weeks ago by mjtsai
Joe Groff on Twitter: "@lapcatsoftware @mjtsai Another possibility is to opt out APIs from bridging when they deal with NSStrings that may significantly differ in normalization. We alrea… https://t.co/GAXHjyBL0Z"
Another possibility is to opt out APIs from bridging when they deal with NSStrings that may significantly differ in normalization.

We already know we need an opt-out mechanism for things like Core Data NSArray/NSDictionary objects where their class-iness is part of the magic

— Joe Groff (@jckarter) December 11, 2017
FavoriteTweet  jckarter 
10 weeks ago by mjtsai
Joe Groff on Twitter: "@lapcatsoftware @mjtsai Crashing is the least bad thing to do when irreconcilable inconsistencies arise. Swift imposing this added constraint on existing APIs is wo… https://t.co/dOrsQSll6s"
Crashing is the least bad thing to do when irreconcilable inconsistencies arise. Swift imposing this added constraint on existing APIs is worth challenging.

— Joe Groff (@jckarter) December 11, 2017
FavoriteTweet  jckarter 
10 weeks ago by mjtsai
Joe Groff on Twitter: "@mjtsai @lapcatsoftware It's supposed to crash if it detects a key collision introduced by the difference in equality model (theory being that keys differing only b… https://t.co/B3RWBwp4qH"
It's supposed to crash if it detects a key collision introduced by the difference in equality model (theory being that keys differing only by normalization form are almost always by mistake)

— Joe Groff (@jckarter) December 11, 2017
FavoriteTweet  jckarter 
10 weeks ago by mjtsai
Joe Groff on Twitter: "@mjtsai @lapcatsoftware It's a known problem. Eventually we want to do away with the "lazy bridging", which would allow the crash to at least happen deterministical… https://t.co/tod2eJpFAy"
It's a known problem. Eventually we want to do away with the "lazy bridging", which would allow the crash to at least happen deterministically on bridging and avoid the inconsistent view of the Dictionary.

— Joe Groff (@jckarter) December 11, 2017
FavoriteTweet  jckarter 
10 weeks ago by mjtsai
Joe Groff on Twitter: "@mpweiher @helje5 Constructors can still save references to self anywhere after self is fully initialized."
Constructors can still save references to self anywhere after self is fully initialized.

— Joe Groff (@jckarter) December 9, 2017
FavoriteTweet  jckarter 
10 weeks ago by mjtsai
Joe Groff on Twitter: "This revolutionary new device uses the power of hopes and prayers to secure your data. We call it Faith ID"
This revolutionary new device uses the power of hopes and prayers to secure your data. We call it Faith ID

— Joe Groff (@jckarter) December 4, 2017
FavoriteTweet  jckarter 
11 weeks ago by mjtsai
Joe Groff on Twitter: "@nicklockwood @SteveStreza @testable If white box tests could be written next to the implementation, they’d naturally have access to module-private things. XCTest isn’t well set… https://t.co/PvGZoZXoV3"
If white box tests could be written next to the implementation, they’d naturally have access to module-private things. XCTest isn’t well set up for that, though.

— Joe Groff (@jckarter) December 3, 2017
FavoriteTweet  jckarter 
11 weeks ago by mjtsai
Joe Groff on Twitter: "@handleym99 @JadenGeller There are still large bodies of Arabic and Indic script texts that can’t be accurately encoded in Unicode"
There are still large bodies of Arabic and Indic script texts that can’t be accurately encoded in Unicode

— Joe Groff (@jckarter) November 29, 2017
FavoriteTweet  jckarter 
11 weeks ago by mjtsai
Joe Groff on Twitter: "@handleym99 @JadenGeller There are other semantic differences in other domains that don’t get enshrined in Unicode. I think it is a bit unbalanced that math gets suc… https://t.co/wwKKgSkq5T"
There are other semantic differences in other domains that don’t get enshrined in Unicode. I think it is a bit unbalanced that math gets such in-depth distinctions

— Joe Groff (@jckarter) November 29, 2017
FavoriteTweet  jckarter 
11 weeks ago by mjtsai
Joe Groff on Twitter: "Unicode: We don't have enough encoding space, nobody would mind if we just unify Chinese, Japanese, and Korean characters Also Unicode: We m… https://t.co/rKCE8eHWpd"
Unicode: We don't have enough encoding space, nobody would mind if we just unify Chinese, Japanese, and Korean characters
Also Unicode: We must have at least 20 variations of the English alphabet pic.twitter.com/BTDgCJke3H

— Joe Groff (@jckarter) November 29, 2017
FavoriteTweet  jckarter 
11 weeks ago by mjtsai
Joe Groff on Twitter: "@harlanhaskins @_cdecl @_silgen_name #dsohandle isn’t a valid handle by itself. You still need to dlopen the library. You can use dladdr to map back to a loaded dylib, or pass n… https://t.co/6pSqVPzukY"
#dsohandle isn’t a valid handle by itself. You still need to dlopen the library. You can use dladdr to map back to a loaded dylib, or pass null to dlsym to search the current process

— Joe Groff (@jckarter) November 26, 2017
FavoriteTweet  jckarter 
12 weeks ago by mjtsai
Joe Groff on Twitter: "First monad law: a monad shall not modify state, or through inaction, allow state to be modified"
First monad law: a monad shall not modify state, or through inaction, allow state to be modified

— Joe Groff (@jckarter) November 24, 2017
FavoriteTweet  jckarter 
12 weeks ago by mjtsai
Joe Groff on Twitter: "@mjtsai Turns out Ling's problem was a bug that is fixed in master SourceKit. You can remove `-v` from OTHER_SWIFT_FLAGS to work around it.… https://t.co/AIo8oHwoHe"
Turns out Ling's problem was a bug that is fixed in master SourceKit. You can remove `-v` from OTHER_SWIFT_FLAGS to work around it. https://t.co/Yljr60nI4k

— Joe Groff (@jckarter) November 10, 2017
FavoriteTweet  jckarter 
november 2017 by mjtsai
Joe Groff on Twitter: ""Smalltalk has the best syntax." huge ifTrue:"
"Smalltalk has the best syntax."
huge ifTrue:

— Joe Groff (@jckarter) November 8, 2017
FavoriteTweet  jckarter 
november 2017 by mjtsai
Joe Groff on Twitter: "@Catfish_Man CONST(PTR(FN(int, int))) p;"
CONST(PTR(FN(int, int))) p;

— Joe Groff (@jckarter) November 7, 2017
FavoriteTweet  jckarter 
november 2017 by mjtsai
Joe Groff on Twitter: "@Catfish_Man #define CONST(t) typeof(const typeof(t)) #define PTR(t) typeof(typeof(t)*) #define FN(r, ...) typeof(typeof(r) (__VA_ARGS__))"
#define CONST(t) typeof(const typeof(t))#define PTR(t) typeof(typeof(t)*)#define FN(r, ...) typeof(typeof(r) (__VA_ARGS__))

— Joe Groff (@jckarter) November 7, 2017
FavoriteTweet  jckarter 
november 2017 by mjtsai
Joe Groff on Twitter: "@lapcatsoftware You know an API is really old when its docs contain an oblique "don't poseAs: this class please" statement https://t.co/QbUM6PyAGt"
You know an API is really old when its docs contain an oblique "don't poseAs: this class please" statement pic.twitter.com/QbUM6PyAGt

— Joe Groff (@jckarter) November 7, 2017
FavoriteTweet  jckarter 
november 2017 by mjtsai
Joe Groff on Twitter: "@millenomi @jnadeau We had burner bikesheds we were willing to "lose" to make some people feel important. We got as far as this->self, constructor->init"
We had burner bikesheds we were willing to "lose" to make some people feel important. We got as far as this->self, constructor->init

— Joe Groff (@jckarter) November 6, 2017
FavoriteTweet  jckarter 
november 2017 by mjtsai
Joe Groff on Twitter: "@johnsundell The intended model is "observers are never called inside init, always called outside.""
The intended model is "observers are never called inside init, always called outside."

— Joe Groff (@jckarter) November 3, 2017
FavoriteTweet  jckarter 
november 2017 by mjtsai
IDL Skeleton on Twitter: "int *null = 0; int *nulNull = ''; int *halfNull = 1/2; int *complexNull = (int)_Complex_I; int *paddedNull = sizeof(int) % _Alignof(int);"
int *null = 0;
int *nulNull = '\0';
int *halfNull = 1/2;
int *complexNull = (int)_Complex_I;
int *paddedNull = sizeof(int) % _Alignof(int);

— IDL Skeleton (@jckarter) October 29, 2017
FavoriteTweet  jckarter 
october 2017 by mjtsai
IDL Skeleton on Twitter: "@olebegemann @mjtsai @SAKrisT These sorts of performance differences are bugs. We’d appreciate it if you report them when you observe them"
These sorts of performance differences are bugs. We’d appreciate it if you report them when you observe them

— IDL Skeleton (@jckarter) October 27, 2017
FavoriteTweet  jckarter 
october 2017 by mjtsai
[joe groff]; on Twitter: "@iljawascoding @steipete @internetofshit Toothbrush…toilet brush…internet communicator. Are you getting it? They’re all one device!"
Toothbrush…toilet brush…internet communicator. Are you getting it? They’re all one device!

— [joe groff]; (@jckarter) October 5, 2017
FavoriteTweet  jckarter 
october 2017 by mjtsai
Joe Groff on Twitter: "@owensd I’m glad my job involves easy fluff like compilers and optimization and not hard problems like getting css to work across browsers"
I’m glad my job involves easy fluff like compilers and optimization and not hard problems like getting css to work across browsers

— Joe Groff (@jckarter) September 23, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "@gregtitus @harlanhaskins Sure, once we can decorate methods as taking self +1 we could make most nonmutating operations modify in-place too."
Sure, once we can decorate methods as taking self +1 we could make most nonmutating operations modify in-place too.

— Joe Groff (@jckarter) September 22, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "@cocoaphony @mjtsai @UINT_MIN That's the way we generally go with all public stuff. When a library writer ships a mistake, they can't fix it."
That's the way we generally go with all public stuff. When a library writer ships a mistake, they can't fix it.

— Joe Groff (@jckarter) September 22, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "@nicklockwood @zats Apple’s guidelines for property-hood have only concerned lack of side effects, which is what the swift stdlib also follows"
Apple’s guidelines for property-hood have only concerned lack of side effects, which is what the swift stdlib also follows

— Joe Groff (@jckarter) September 21, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "Face ID checks for your attention to prevent in-nap purchases"
Face ID checks for your attention to prevent in-nap purchases

— Joe Groff (@jckarter) September 13, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "@owensd Another linked list variant is a contiguous array of (value, next index) pairs, so you get locality and can efficiently insert by appending"
Another linked list variant is a contiguous array of (value, next index) pairs, so you get locality and can efficiently insert by appending

— Joe Groff (@jckarter) September 6, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "@mjtsai I forget details, but exclusivity enforcement for passing pointers to ivars was relaxed to accommodate this kind of use. cc @pathofshrines"
I forget details, but exclusivity enforcement for passing pointers to ivars was relaxed to accommodate this kind of use. cc @pathofshrines

— Joe Groff (@jckarter) September 6, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "@mjtsai That use case should work with the latest Xcode 9 betas."
That use case should work with the latest Xcode 9 betas.

— Joe Groff (@jckarter) September 6, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "@mjtsai @owensd If you're seeing protocol overhead it's probably also failing to specialize something."
If you're seeing protocol overhead it's probably also failing to specialize something.

— Joe Groff (@jckarter) September 6, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "@mjtsai @owensd The optimizer is also not great at telling that insert/append-type operations maintain uniqueness so it can leave out checks."
The optimizer is also not great at telling that insert/append-type operations maintain uniqueness so it can leave out checks.

— Joe Groff (@jckarter) September 6, 2017
FavoriteTweet  jckarter 
september 2017 by mjtsai
Joe Groff on Twitter: "@lapcatsoftware I got asked once to implement sort() in Python. I said to use the standard library sort() because rewriting it is bad. I still got the job"
I got asked once to implement sort() in Python. I said to use the standard library sort() because rewriting it is bad. I still got the job

— Joe Groff (@jckarter) August 30, 2017
FavoriteTweet  jckarter 
august 2017 by mjtsai
Joe Groff on Twitter: "@stroughtonsmith I don't know what tools the iOS 10 App Store was built with, but iOS 11's will be built with sticks and stones"
I don't know what tools the iOS 10 App Store was built with, but iOS 11's will be built with sticks and stones

— Joe Groff (@jckarter) August 14, 2017
FavoriteTweet  jckarter 
august 2017 by mjtsai
Joe Groff on Twitter: "@owensd @mjtsai People can, and should, still discuss ideas before implementing them. Implementation is only necessary for review."
People can, and should, still discuss ideas before implementing them. Implementation is only necessary for review.

— Joe Groff (@jckarter) August 10, 2017
FavoriteTweet  jckarter 
august 2017 by mjtsai
Joe Groff on Twitter: "ME: Show me statements in the order they will execute COMPILER: That's too hard. Here are some abstractions I think are good. Do you like th"
ME: Show me statements in the order they will execute
COMPILER: That's too hard. Here are some abstractions I think are good. Do you like th

— Joe Groff (@jckarter) July 28, 2017
FavoriteTweet  jckarter 
july 2017 by mjtsai
Joe Groff on Twitter: "@UINT_MIN @owensd Does anyone use those constructors in practice, though? They don't fulfill any protocol, and it's easier to write literal 0/false"
Does anyone use those constructors in practice, though? They don't fulfill any protocol, and it's easier to write literal 0/false

— Joe Groff (@jckarter) July 17, 2017
FavoriteTweet  jckarter 
july 2017 by mjtsai
Joe Groff on Twitter: "https://t.co/0EchbA0a4l"
pic.twitter.com/0EchbA0a4l

— Joe Groff (@jckarter) July 17, 2017
FavoriteTweet  jckarter 
july 2017 by mjtsai
Joe Groff on Twitter: "@mikeash @itaiferber It seems fine to me. If you change your struct layout, the CodingKey gives you flexibility to maintain the same serialization format"
It seems fine to me. If you change your struct layout, the CodingKey gives you flexibility to maintain the same serialization format

— Joe Groff (@jckarter) June 12, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "@mikeash cc @itaiferber . I believe it uses the CodingKey's declaration order, so you can reorder if necessary."
cc @itaiferber . I believe it uses the CodingKey's declaration order, so you can reorder if necessary.

— Joe Groff (@jckarter) June 12, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "@pilky Yeah I'm hoping one day we get something like type providers that could import resources from your Xcode project directly as typed objects"
Yeah I'm hoping one day we get something like type providers that could import resources from your Xcode project directly as typed objects

— Joe Groff (@jckarter) June 9, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "@pilky Intended pattern there is to declare constants: let MyNib = https://t.co/Emw5ev3ikW("MyNib") let Cell = NSUIIId("Cell")"
Intended pattern there is to declare constants:
let MyNib = https://t.co/Emw5ev3ikW("MyNib")
let Cell = NSUIIId("Cell")

— Joe Groff (@jckarter) June 9, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "@timburks You can form key paths into structs, and there's Go-ish automatic decoding/encoding."
You can form key paths into structs, and there's Go-ish automatic decoding/encoding.

— Joe Groff (@jckarter) June 9, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "There's no http:// before com dot apple dot dt dot Xcode. Thanks Twitter"
There's no http:// before com dot apple dot dt dot Xcode. Thanks Twitter

— Joe Groff (@jckarter) June 8, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "@NSExceptional @JordanMorgan10 Yeah, key paths are hopefully the first step toward a more comprehensive reflection and dynamicity story."
Yeah, key paths are hopefully the first step toward a more comprehensive reflection and dynamicity story.

— Joe Groff (@jckarter) June 6, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "@owensd It's derived from the iOS playgrounds editor, which had strict performance constraints to begin with, so that probably helped"
It's derived from the iOS playgrounds editor, which had strict performance constraints to begin with, so that probably helped

— Joe Groff (@jckarter) June 6, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "@lapcatsoftware We can hope the iMac Pro project attracts all the thinness engineers so they leave the Mac Pro people alone"
We can hope the iMac Pro project attracts all the thinness engineers so they leave the Mac Pro people alone

— Joe Groff (@jckarter) June 6, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "Includes a look at some of the Foundation team's awesome new Swift features like coding and key paths! https://t.co/fDpTZdiAnc"
Includes a look at some of the Foundation team's awesome new Swift features like coding and key paths! https://t.co/fDpTZdiAnc

— Joe Groff (@jckarter) June 5, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "At last, a place for apps,"
At last, a place for apps,

— Joe Groff (@jckarter) June 5, 2017
FavoriteTweet  jckarter 
june 2017 by mjtsai
Joe Groff on Twitter: "@steipete @defer Just sayin', we have taken ObjC features from external contributors before, like @(value) boxing for structs"
Just sayin', we have taken ObjC features from external contributors before, like @(value) boxing for structs

— Joe Groff (@jckarter) May 31, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
Joe Groff on Twitter: "A nice thing you can do with key paths: Declare type schema once, and build default implementations on top of it https://t.co/XCH7o2lczD"
A nice thing you can do with key paths: Declare type schema once, and build default implementations on top of it https://t.co/XCH7o2lczD

— Joe Groff (@jckarter) May 26, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
Joe Groff on Twitter: "@lapcatsoftware May 2017: "It breathes naturally like a living thing" August 2017: Tim and Jony order AC units for their offices"
@lapcatsoftware May 2017: "It breathes naturally like a living thing"
August 2017: Tim and Jony order AC units for their offices

— Joe Groff (@jckarter) May 19, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
Joe Groff on Twitter: "@colincornaby In our large mixed projects it turned out not to be, and the savings in removing unused entry points was significant. Not the case for you?"
@colincornaby In our large mixed projects it turned out not to be, and the savings in removing unused entry points was significant. Not the case for you?

— Joe Groff (@jckarter) May 17, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
Joe Groff on Twitter: "@mpweiher @benjaminencz @simjp And I think it's a given that you'd need to build your own data structure for max performance in either case."
@mpweiher @benjaminencz @simjp And I think it's a given that you'd need to build your own data structure for max performance in either case.

— Joe Groff (@jckarter) May 12, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
Joe Groff on Twitter: "@mpweiher @benjaminencz @simjp How is that different from the UndoManager situation? In that case too, it's only as fast as the actions you feed it."
@mpweiher @benjaminencz @simjp How is that different from the UndoManager situation? In that case too, it's only as fast as the actions you feed it.

— Joe Groff (@jckarter) May 12, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
Joe Groff on Twitter: "@owensd Swift is a research platform for discovering new forms of access control"
@owensd Swift is a research platform for discovering new forms of access control

— Joe Groff (@jckarter) May 10, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
Joe Groff on Twitter: "@owensd Especially with concurrency, a big problem is complex semantics without enforcement. Correct user code shouldn't care about the "magic""
@owensd Especially with concurrency, a big problem is complex semantics without enforcement. Correct user code shouldn't care about the "magic"

— Joe Groff (@jckarter) May 10, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
Joe Groff on Twitter: "I got a brand new computer. Now how do I put antivirus on this thing https://t.co/t3V0QFo5Ur"
I got a brand new computer. Now how do I put antivirus on this thing pic.twitter.com/t3V0QFo5Ur

— Joe Groff (@jckarter) May 6, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
Joe Groff on Twitter: "@mjtsai The laptop form factor is a compromise for an integrated system that isn't really ergonomic for any task."
@mjtsai The laptop form factor is a compromise for an integrated system that isn't really ergonomic for any task.

— Joe Groff (@jckarter) May 6, 2017
FavoriteTweet  jckarter 
may 2017 by mjtsai
« earlier      
per page:    204080120160

Copy this bookmark:



description:


tags: