WatchKit container

Our iOS App is completely built in Swift. Still early adaptor, but a great language!

Most of the app code was gradually rewritten in Swift for better performance and code maintenance.

Most of our newer apps are written completely in swift, with our older ones and some special cases using a mix of Swift and Objective-C, but with Swift 2, the language is pretty much a must-use. "guard" is <3.

iOS app

Newer apps are being written with Swift instead of Objective-C.

iOS Dev language

iOS App

For building native OS X & iOS apps on a Mac

Getting ready to move parts of the app to Swift. Love the Playground.

All "new" iOS code has been written with Swift 2.2.

iOS Development

iPhone app, a new born language, it may good but the IDE, xcode is bad compare with Visual Studio. It just like a baby. playground can only use without connect to other library...you can not do a simply refactor of renaming a variable. You can go to definition and find reference, but you can not go to implementation....I should write them on xcode not here basically it is not the fault of swift, but it tightly to it, unless you want to use a notepad to write it.

Building iOS apps

Swift is a modern language we use to build native iOS apps

Native iOS application development.

Language for IOS development

iOS apps.

Native iOS APP and Middleware with Swift Perfect.

Swift on a way to fullstack - it is moving to the backend

Flutter is coded with Swift v.2.3 and can be run with Xcode v.8.2.1. To launch in Xcode 9.3, the code needs to be migrated to Swift 4.1

Our native iOS app is built on Swift, and most of the basic function is still written in Swift

IOS applications

Fast and easy to build complex pipelines, the main component of this project.

We use Clojure mostly for its "Minority Report"-like interactive development in situations that require 'semi-automatic programming' (data inspection, admin tasks, API exploration, scrapers, etc.). We have also used Clojure successfully to build some components of our stack very quickly and reliably, in the backend and the frontend.

We are deeply invested in Clojure - all the power of Java with the simplicity of functional programming.

We use Clojure in several places, most often as a wrapper around other libraries and frameworks (e.g. Hibernate, HAPI, etc.) Our HL7 parsing workflow is heavily based on Clojure with files that look almost like configuration, but actually offer tremendous power and flexibility.

The server-side components are 100% Clojure, and the client UI and server communication logic is written in ClojureScript

The site, while running on the JVM is actually implemented in Clojure

Clojure is our main language for building out both the web service that powers the user interface of Lumanu and the web crawling that provides all of our data.

Our main machine learning service is written in Clojure.

just started learning clojure, maybe around two weeks or so. i'm addicted. this is what i want to be working with and learning for the foreseeable future. the elegance of the language is refreshing. the community is really amazing. i've finally found a language that fits my passion for programming.

Cloure is a high level language that provides access to both the JVM (for server-side development) and javascript (for client-side development) with largely the same language. This is important to limit context switching and enable code-reuse during fast product cycles. Clojure is ideal for rapid prototyping and has a strong focus on stability, correctness, and concurrency. Tools like Schema and Spec enable well-structured development and high code confidence.

To complement Java. The REPL lets me interactively exercise Java code. I can write performant and safe libraries in Java, and then use them in Clojure. I also find the data-centric aspect of Clojure (excellent build-in structures, literal syntax for easily creating those structures, functions that act well on abstractions of those structures) good for data processing.

This fits a sweet spot between Ruby and Java.

Clojure simplifies and reduces the coding efforts involved in creating CloudRepo. The fact that it runs in the JVM gives us access to all the libraries that we could ever need. Our code base is much smaller and easier to reason about than it would have been had we gone with pure Java.

Personally, I really like HAML. Not having to use open and close tags is a huge time saver. As a result, writing markup with HAML is much more pleasant. HAML essentially forces you to be very strict about spacing, organization, and structure. It also makes the markup easier to read. Protip: I use this pretty frequently: htmltohaml.com