Has anyone here made a living/killing selling compiler modification services? I want to contribute to Rust/Swift/Some other language with a view of selling consulting services. Can anyone here comment about their success in this regard?
Server APIs Project
91–100 of 181 posts
Re: Server APIs Project
#92Earlier quoted context omitted.
I think most languages thatare popular today are 'best of most worlds' for their users. For example, Scala has all the features you specified and has an even larger ecosystem of libraries for the server side. I am still happy that this has been done as I know having a common API to program against does ease development and creates a great ecosystem as evidenced by node.JS.
The problem with Scala is not that it has all the features of Swift, it's that it has way more. Scala developers see this as an advantage, everybody else sees that as a liability. Swift and Kotin manage to capture the perfect amount of "a few new features but not too many" of all languages I've played with these past ten years. They are both the perfect example of languages that hit the right compromise in many dimen…
> The problem with Scala is not that it has all the features of Swift, it's that it has way more. Scala developers see this as an advantage, everybody else sees that as a liability.
Well for it's intended audience it's exactly what they want I guess, same could be said for Swift IMO. That said, Swift definitely has boarder appeal.
Re: Server APIs Project
#93Earlier quoted context omitted.
> How is the memory management? Swift has both, reference types (heap allocated, refcounted) and value types (stack allocated (mostly)). Collections are copy on write which is actually really dank. You don't really think about memory management much (compared with Obj-C). And if you do, I usually wrap it in some sort of abstraction so that I can write it and forget it. The only modern language out of the three you me…
Why is COW collection "dank"?
And is "dank" good or bad?
Re: Server APIs Project
#94Has anyone here made a living/killing selling compiler modification services? I want to contribute to Rust/Swift/Some other language with a view of selling consulting services. Can anyone here comment about their success in this regard?
http://integer32.com/ is the first Rust-focused consultancy I know of.
Re: Server APIs Project
#95Earlier quoted context omitted.
Also a significant drop in null dereferencing issues. The `if-let` syntax is brilliant.
Not as general or useful as Rust's "if let", though. Rust's "if let" affords fallible pattern matching on arbitrary types, not just on "nullable pointer types" (in Safe Rust, a "nullable pointer" is simply a regular reference wrapped in Option ).
Worth noting that we got the idea for if let from Swift :)
Re: Server APIs Project
#96Earlier quoted context omitted.
Why is COW collection "dank"?
And is "dank" good or bad?
It usually means "good", though some people use it in an ironic sense to imply something is bad. Kinda like how "bad" can also mean "good" in the right context, but in reverse.
Here I took it to mean "good."
Re: Server APIs Project
#97Having spent 10 months working in Swift, this is probably the last thing on earth I want to see right now. Pretty much every part of the entire toolchain has been a pain, from Xcode being Xcode, to compiler bugs and crashes, crappy package management and bad language design. Having built servers in Java/C#/Scala/Haskell, I'd pick Haskell over those options and Swift every single time.
What is it about Haskell? I'm currently heavily invested in Rust and have very briefly looked at Haskell, but find it to have some oddities that I can wrap my head around.
Re: Server APIs Project
#98Earlier quoted context omitted.
The problem with Scala is not that it has all the features of Swift, it's that it has way more. Scala developers see this as an advantage, everybody else sees that as a liability. Swift and Kotin manage to capture the perfect amount of "a few new features but not too many" of all languages I've played with these past ten years. They are both the perfect example of languages that hit the right compromise in many dimen…
> The problem with Scala is not that it has all the features of Swift, it's that it has way more. Scala developers see this as an advantage, everybody else sees that as a liability. Well for it's intended audience it's exactly what they want I guess, same could be said for Swift IMO. That said, Swift definitely has boarder appeal.
In which sense?
Re: Server APIs Project
#99Re: Server APIs Project
#100I wonder what happened to the rumors that Google was planning on supporting Swift on Android officially [0]. Also, are there any good tutorials/courses to get started with Swift & iOS development? (having programmed in other languages, I can pick up fast, and I've lost interest in tutorials that start out very slowly and take time to get to the point.) [0] http://thenextweb.com/dd/2016/04/07/google-facebook-uber-swi.…
I guess it would make more sense to support Kotlin officially, but then again it already works fine on Android.
As far as I understand Kotlin is reliant on Java Standard Library and is dependent on Java infrastructure(maven, jvm, xml and friends), which makes no sense for me as an iOS developer and can only benefit Java developers as it was mentioned earlier.