[1] https://blogs.msdn.microsoft.com/dotnet/2016/06/27/announcin...
In case you want to investigate some:
- https://www.playframework.com
- http://projects.spring.io/spring-boot
It has static typing, limited type inference (function parameters need their types declared - by design - will infer otherwise), no JVM, and has several web frameworks. Not sure if any of them would be considered "good" by your definition, but check it out: https://github.com/flosse/rust-web-framework-comparison
I've already decided my next service/api will be in Rust.
Still is early days, but there's a lot of stuff too. Excited to see it develop further.
It's a functional, pure and statically typed language inspired by Haskell. It claims that programs that compile successfully cannot:
- Suffer from any kinds of code-injection attacks
- Return invalid HTML
- Contain dead intra-application links
- Have mismatches between HTML forms and the fields expected by their handlers
- Include client-side code that makes incorrect assumptions about the "AJAX"-style services that the remote web server provides
- Attempt invalid SQL queries
- Use improper marshaling or unmarshaling in communication with SQL databases or between
- Static typing
- Type inference (and pattern matching)
- No dependency on JVM, .NET, or BEAM
But the number of web frameworks, etc. for Rust sucks compared to that of older languages like Go. Go 1.0 was released in early 2012 and Rust 1.0 in May 2015.
Rust is more verbose than Go, but Go's FFI to functions written in C isn't as efficient and since "cgo isn't go", I'm not sure cgo covered by Go 1.0 compatibility guarantee.
On the other hand, Go has tons of "batteries included" plus web frameworks so that is pretty awesome to have on stable platforms (I don't consider Windows a stable platform for Go and got burned several times, but Go works great on FreeBSD & Ubuntu.)
I suspect Go & Swift won't have robust reliability on Windows (compared to other platforms) but they'll be rock solid on the ones they favor. Rust may have better prospects regarding this, but Rust still too new this year for web server language -- wait until MIR is integrated and a couple more releases after that.
In the meantime, I'm more actively working on Ponyo for Standard ML right now. Take a look at the ponyo.org server[0] for a brief glance at what it can do today.
Check out the /r/sml wiki if you are trying to get started. And please join #sml on Freenode if you have any questions!
[0] https://github.com/eatonphil/ponyo/blob/master/site/server/s...
Anyway: What about kotlin [0]?
* 100% java compatible * can compile to the JVM and javascript, so you should be able to run it with node.
Googling found this: https://jonninja.github.io/node.kt/
If you use Kotlin, use the JVM - at least for now.
- Static typing -- Type hints enable restriction of the dynamic typing behavior of default Python to mimic static types
- Type inference -- Not familiar with the particular behavior of type inference of Haskell, but yes.
- No JVM -- Definitely no JVM, but not particularly high performance so...there is that.
- Good pre-made web framework -- Lots of good ones, Python ecosystem is fairly rich in general, but ones I have used: Django, Pyramid, Flask, etc.
- Static typing -- I want to eliminate as many runtime bugs as I can
- Type inference -- Like in SML and Haskell
- No JVM -- Personal preference, but I'd rather not pull in this monster if I don't have to.
- Good pre-made web framework -- I've briefly looked at OCaml but the web frameworks seem disappointing. Tell me if I'm wrong!