Oh, on OS X, swift works fine with PostgreSQL and ODBC datasources via Obj-C frameworks, that isn’t the challenge.
I’ve started porting both of those frameworks to Swift already. There are some ‘challenges’ that are slowing that process down, and even more so, there are some decisions to be made with regards to exception handling and optionals that I am still feeling my way through. What I’m doing is using those frameworks as a base and building one for TDS databases (Sybase/MSSQL) from the ground up. It is time consuming, and honestly, I’ve made no decision on if I’ll make the code available (as I’ll have a bit of time invested in it, and as a rule DB libraries don’t generate revenue, but sure do generate support requests!) From: Dave Fenton <sirdavidfen...@gmail.com<mailto:sirdavidfen...@gmail.com>> Date: Wednesday, January 6, 2016 at 7:59 PM To: Andy Satori <d...@druware.com<mailto:d...@druware.com>> Cc: Jens Alfke <j...@mooseyard.com<mailto:j...@mooseyard.com>>, "swift-users@swift.org<mailto:swift-users@swift.org>" <swift-users@swift.org<mailto:swift-users@swift.org>> Subject: Re: [swift-users] "business applications market" flame So far it seems to me that Swift is a powerful "c" type language that can also be used in a script-like way. Definitely a win. Hopefully as version 3 gets closer there will have emerged some useful pure swift modules for DB access (Oracle, SQL Server/MongoDB etc) as well as other middleware. I'm expecting that IBM will have some good involvement here. -Dave On Jan 6, 2016, at 7:45 PM, Dru Satori via swift-users <swift-users@swift.org<mailto:swift-users@swift.org>> wrote: I would argue that the language syntax is forgiving though, as my follow examples demonstrated. The funny thing, is that your point about minutes versus hours is the very reason BASIC came to be ( easier math language ). But I think to a degree, we are discussing semantics. It seems we agree on the principle, that Swift is good, but it isn’t there as general purpose business dev language. :) From: Jens Alfke <j...@mooseyard.com<mailto:j...@mooseyard.com>> Date: Wednesday, January 6, 2016 at 7:40 PM To: Andy Satori <d...@druware.com<mailto:d...@druware.com>> Cc: Don Wills <don.wi...@portablesoftware.com<mailto:don.wi...@portablesoftware.com>>, Donald Pinckney <djpinck...@ucdavis.edu<mailto:djpinck...@ucdavis.edu>>, "swift-users@swift.org<mailto:swift-users@swift.org>" <swift-users@swift.org<mailto:swift-users@swift.org>> Subject: Re: [swift-users] "business applications market" flame On Jan 6, 2016, at 4:27 PM, Dru Satori <d...@druware.com<mailto:d...@druware.com>> wrote: The thing that I see about Swift is that right now, today, on Linux or OS X, if Swift is installed, I can open a terminal: Touch hello.swift vim hello.swift i print("Hello Swift"); Esc :wq swift hello.swift You can do that with C too: touch hello.c vim hello.c i #include <stdio.h> int main() {printf(“Hello World!”); return 0;} Esc :wq cc hello.c && ./a.out Does that make C a scripting language? :) Having a REPL or playgrounds doesn’t really change what the language itself is; it just indicates good integration of the compiler into the development tools. To me, what defines a scripting language is a forgiving syntax that lets you bang stuff out fast without worrying about types, and super high level libraries for doing file and text manipulation and running other processes. By contrast, even if I had a C REPL and playgrounds, it would still be a pain to use C to process a directory full of text files and transform their contents and pass that to another tool. Whereas I could do it in minutes with Ruby or bash. —Jens _______________________________________________ swift-users mailing list swift-users@swift.org<mailto:swift-users@swift.org> https://lists.swift.org/mailman/listinfo/swift-users
_______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
