4 ms·

I care very little about the App store. In my world the iOS app is a small part of our ecosystem. What I care about is getting charged for a developer licence

by worik 5y ago

I care very little about the App store. In my world the iOS app is a small part of our ecosystem. What I care about is getting charged for a developer licence that was never delivered. Needing a licence to use hardware I paid money for. Without the licence I cannot put apps on the iPad I own connected to the Mac I own, apps I write on said Mac. Buggy developer tools that they will not fix. Xcode (and its Swift ecosystem) work well for a small project, really great. Until you realise that the debugger is lying about the state of your variables. Get to 100,000+ lines of code (or whatever measure of size you like, big) Xcode stops working, the tools to navigate your code start getting flaky, the editor with its slick features gets very slow.... And the debugger: It tells lies - but the worst, the very worst, is that in Swift, on iOs comparing a optional to `nil` is unreliable. No shit, this is needed: if foo == nil { if let _ = nil { // foo is not really nil About 1% of nil comparisons fail... A trillion dollar company built off the work of developers and the tools are like this? They take money for access? Times like this I am glad I am on a salary...

Grustaf 5y ago
Optionals are of course 100% reliable. What are you actually trying to do? "if let _ = nil" makes no sense and doesn't compile.
- worik 5y ago
  Duh! if the_variable_that_might_be_nil == nil { if let _ = the_variable_that_might_be_nil // Nope not really nil I have counted: A bit less than 1% of the time at a certain point in our code. I have seen it, measured it... The Swift ecosystem has important bugs in some corner cases. Fact.
  - Grustaf 5y ago
    This is different from what you wrote the first time though. This time it makes sense syntactically and compiles, but why would you write it? It makes no logical sense, the inner block would never be executed. If the inner block is actually called, that's an extremely serious bug. I know people in the Swift core team, can you share a code sample with me the exposes the bug and I will bring it up?
    - worik 5y ago
      The inner block is, roughly 1% of the time (in the code base this is from) executed. This is my point: The flagship development system of the most valuable company in the world is buggy. It is one example, but I have several examples of flaws like this.

by worik 5y ago

Grustaf 5y ago

Optionals are of course 100% reliable. What are you actually trying to do? "if let _ = nil" makes no sense and doesn't compile.

worik 5y ago
Duh! if the_variable_that_might_be_nil == nil { if let _ = the_variable_that_might_be_nil // Nope not really nil I have counted: A bit less than 1% of the time at a certain point in our code. I have seen it, measured it... The Swift ecosystem has important bugs in some corner cases. Fact.
- Grustaf 5y ago
  This is different from what you wrote the first time though. This time it makes sense syntactically and compiles, but why would you write it? It makes no logical sense, the inner block would never be executed. If the inner block is actually called, that's an extremely serious bug. I know people in the Swift core team, can you share a code sample with me the exposes the bug and I will bring it up?
  - worik 5y ago
    The inner block is, roughly 1% of the time (in the code base this is from) executed. This is my point: The flagship development system of the most valuable company in the world is buggy. It is one example, but I have several examples of flaws like this.