steipete

#define PSPDF_EMPTY_ASSERTING_INIT() \
_Pragma("clang diagnostic push") \
_Pragma("clang diagnostic ignored \"-Wobjc-designated-initializers\"") \
- (instancetype)init \
{ \
NSAssert(NO, @"Use the designated initializer to create an instance of this object."); \
return nil; \
} \
_Pragma("clang diagnostic pop")

imjasonh

* {
    font-size: 12pt;
    font-family: monospace;
    font-weight: normal;
    font-style: normal;
    text-decoration: none;
    color: black;
    cursor: default;
}

iraycd

Interestingly Apple doesn't even use Storyboards in their recently open-sourced ResearchKit as [Peter Steinberger has noticed][1] (under the subheading "Interface Builder").

As expected, Apple keeps improving Storyboards and Xcode. Some of the points that applied to iOS 7 and below don't apply to iOS 8 anymore (and are now marked as such). So while Storyboards inherently still have flaws, I revise my advice from don't use to selectively use where it makes sense.

Even now that iOS 7 is out, I would advise against to use caution when deciding whether to use Storyboards. Here are my reasons:

• Storyboards fail at runtime, not at compile time: You have a typo in a segue name or connected it wrong in your storyboard? It will blow up at runtime. You use a custom UIViewController subclass that doesn't exist anymore in your storyboard? It will blow up at runtime. If you do such things in code, you will catch them early on, during compile time. Update: My new tool **[StoryboardLin

ryanflorence

Turning Off Github Issues

My friend Michael Jackson turned off github issues on one of his smaller projects. It got me thinking...

Maintainers getting burned out is a problem. Not just for the users of a project but the mental health of the maintainer. It's a big deal for both parties. Consumers want great tools, maintainers want to create them, but maintainers don't want to be L1 tech support, that's why they

0xced

{
  "People" : [
    {
      "Symbol" : "😀",
      "Name" : "GRINNING FACE"
    },
    {
      "Symbol" : "😬",
      "Name" : "GRIMACING FACE"
    },

zwaldowski

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<!-- iOS 10, macOS Sierra, and friends bring a new logging subsystem that's
supposed to scale from the kernel, up to frameworks, and up to apps. It defaults
to a more regimented, privacy-focused approach that large apps and complex
systems need.

It, along with Activity Tracing introduced in iOS 8 and macOS Yosemite and the
Console app in macOS Sierra, hope to help you graduate from caveman debugging to

mludi

#! /bin/bash
cd ~
sudo apt-get update -y
sudo apt-get install clang libicu-dev binutils git -y
sudo apt-get install libcurl4-openssl-dev -y
sudo apt-get install libpython2.7 libpython2.7-dev -y
sudo apt-get install libmysqlclient-dev -y
wget https://swift.org/builds/swift-3.0-release/ubuntu1510/swift-3.0-RELEASE/swift-3.0-RELEASE-ubuntu15.10.tar.gz
tar zxf swift-3.0-RELEASE-ubuntu15.10.tar.gz
sudo mv swift-3.0-RELEASE-ubuntu15.10 /swift-3.0

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

JohnSundell

target 'MyTarget' do
    use_frameworks!

    # Post installation script that enables the Swift 4.2 compiler's
    # legacy 4.1 mode for 4.2-incompatible pods
    post_install do |installer|
      incompatiblePods = ['PodA', 'PodB']

      installer.pods_project.targets.each do |target|
          if incompatiblePods.include? target.name

verebes1

import RealmSwift
import Realm

protocol CascadeDeleting {
    func delete<S: Sequence>(_ objects: S, cascading: Bool) where S.Iterator.Element: Object
    func delete<Entity: Object>(_ entity: Entity, cascading: Bool)
}

extension Realm: CascadeDeleting {
    func delete<S: Sequence>(_ objects: S, cascading: Bool) where S.Iterator.Element: Object {