chris_7

33 ms·

331.
by chris_7 10y ago
Right, and that makes sense for companies, but someone should be able to make a PR against a Github project for which their wife is a maintainer.
332.
by chris_7 10y ago
It's somewhat true that lead singers and guitarists are lionized over drummers and bassists, but they're still doing relatively equal work (and in many cases the singer is also the writer). There's also the sound/lights&
333.
by chris_7 10y ago
This one: Avoid organizations becoming too central to people’s lives Seems at odds with this one: Enforce strict policies around sexual or romantic relationships within power structures Due to the use of the terms "or
334.
by chris_7 10y ago
Even if carbohydrates aren't bad, I prefer foods that are low in them when possible because other foods have disproportionate amounts. Eating a low-carb protein allows you to eat a cookie later and still hit your macro targets.
335.
by chris_7 10y ago
As a pescetarian, I find meat alternatives weird. Tofu is good. Seitan is good. Eggs are good, etc. etc. etc. I've never wanted a "something that approximates meat", I want good plant-based food, not a processed frozen puck i
336.
by chris_7 10y ago
I'd have a lot of trouble hitting my daily protein target without milk (and whey, but that's not really a drink). I also don't really see why beer is included.
337.
by chris_7 10y ago
Swift is most likely not ready for this until 3.0/SPM release, but once it'll be very competitive. Swift generics are very good and Go's are not. There's no language-level concurrency, but there's GCD and https:&#x
338.
by chris_7 10y ago
Oh, given the packing, is there any reason to use the property instead of just moving up a size?
339.
by chris_7 10y ago
Is unsigned integer support coming any time soon? Right now I'm using an integer and a computed property (Swift) to reinterpret the bit pattern as an unsigned value, which is... okay, I guess, as the field doesn't ever need to be
340.
by chris_7 10y ago
I get that it's necessary for running them on Linux, I just question the need to do that in the first place, instead of creating new, Swiftier APIs. NSURLSession's delegates have optional requirements, for example, which aren&#x27
341.
by chris_7 10y ago
> Because the flip side of monkey patching is the power to do such feats of wonder as 2.days.ago (which returns a date two days back from the current). Now you might well think that’s a bad trade. That you’d rather lose 2.days.ago if it
342.
by chris_7 10y ago
> Responder Chain Protocols, or even a superclass. > NSUndoManager Closures. Even Apple has moved away from target/selector for new APIs in favor of blocks. > Key-Value-Coding/Key-Value-Observing/Cocoa Bindings An eq
343.
by chris_7 10y ago
Other than "we want to rewrite Foundation/XCTest in Swift", why do we need XCTest or NSCoding implemented in Swift? Neither is particularly Swifty - many things in Foundation that ought to be structs are classes, for exampl
344.
by chris_7 10y ago
Long hours of software development leads to burnout and depression. People need to exercise and see their friends.
345.
by chris_7 10y ago
Not sure I see what's going on here (it's just a blog post linking to other blog posts?), but is this arguing that Apple should turn the safety of Swift back into the unsafe mess of Objective-C? Horrifying stuff like swizzling, re
346.
by chris_7 10y ago
When an app asks for a review, I typically go and leave a one star review.
347.
by chris_7 10y ago
How much of your free time do you spend recruiting?
348.
by chris_7 10y ago
The Foundation libraries provide that functionality, they're not core to the concept of a programming language, so they're not part of the minimal standard library. There are also numerous community provided implementations. One w
349.
by chris_7 10y ago
They don't have it for ivars, but that's just one potential problem.
350.
by chris_7 10y ago
Protocols and generics cover everything you need to do that. Idiomatic Swift makes little use of classes to begin with, it's mostly structs, enums, and protocols, none of which allow inheritance.
351.
by chris_7 10y ago
Idiomatic Swift shouldn't really be using inheritance though, protocols (which support associatedtype, making varying errors types not an issue) are generally preferred. Functions would be free to just "throws ErrorType" (pro
352.
by chris_7 10y ago
That is an expression that returns Void.
353.
by chris_7 10y ago
Do you mean that the committer email is used? (so, if you use your personal email on your work .gitconfig, you're fine already)
354.
by chris_7 10y ago
Errors should be Just Another Value, so the difference between untyped errors and typed errors is the same as the difference between just using Any for every parameter and return value, and using actual types. You can use Any for everythi
355.
by chris_7 10y ago
I'm not sure if the function call could be optimized out across module boundaries, that's really the only justification for this to be dedicated syntax I can see. It's somewhat obsoleted in Swift 3 regardless as SPM uses sta
356.
by chris_7 10y ago
"final" allows the compiler to strictly enforce that "don't break things" idea, instead of delegating it to fallible humans. (it also lets the compiler make your code faster) By using the tools that Swift provides -
357.
by chris_7 10y ago
If the type signature was: func throwing() throws FooError -> Int or even: func throwing() throws (FooError, BarError) -> Int to create an implicit sum type, I'd find it acceptable, but not being able to tell wh
358.
by chris_7 10y ago
Swift's error handling model essentially tosses type information out the window. I really don't understand why it was created instead of a first-party Result type.
359.
by chris_7 10y ago
Idiomatic Swift is primarily protocol-based, object-orientation is mostly used when talking to the Cocoa frameworks, which aren't idiomatic Swift code. But the main problem with subclassing is: https://en.wikipedia.org/
360.
by chris_7 10y ago
Apple's ability to release a Swift-based SDK that uses "final" and "final" being the default for classes in Swift are completely orthogonal concepts. Apple could (and should, I think) release future SDKs that use al

More ›