21–30 of 90 posts
As someone who doesn't really know anything about scala, why is this a cool thing? While such an early release is definitely aimed at scala enthusiast, I'd still like a sales pitch for the rest of us.
Nowadays you can even run sliced bread on Javascript... though, wouldn't it be better to focus on developing languages on top of asm.js or PNacl so we wouldn't rely on JS?
Fun stuff, but again, doesn't come with any tools. Microsoft Typescript is much better on that matter. What javascript universe needs right now is not some more of syntactic sugar clusterfuck followed by debugging nightmare, but real tools, static code analysis. I don't want to waste my precious time dealing with closure compiler+scala something combo. It's fun from programmers POV, but still it won't make me pay my…
- Integrated with sbt (including support for dependency management and incremental compilation)
- Can be used with your favorite IDE for Scala
- Generates Source Maps for a smooth debugging experience (step through your Scala code from within your browser supporting source maps)
I remember how years ago I complained about how Javascript was the only language aviable for the web. Nowadays you can even run sliced bread on Javascript... though, wouldn't it be better to focus on developing languages on top of asm.js or PNacl so we wouldn't rely on JS?
Earlier quoted context omitted.
Parsing JSON in Scala is very easy with lift-json: https://github.com/lift/lift/tree/master/framework/lift-base...
There's also Play-Json, Spray-Json, various wrappers for Jackson and a few others I don't remember. We use Play-Json and its macros a lot at the company I work for and I contributed a performance fix for it a while back. I wouldn't consider Play's JSON inception to be "pretty involved" at all if you're using case classes. http://www.playframework.com/documentation/2.2.x/ScalaJson https://github.com/spray/spray-json
As someone who doesn't really know anything about scala, why is this a cool thing? While such an early release is definitely aimed at scala enthusiast, I'd still like a sales pitch for the rest of us.
Earlier quoted context omitted.
Given that it uses reflect I bet your library very slow. I wonder how it compares to parsing JSON in Python or node.js. > except for null/undefined, That's not a small issue. Not only do JSON responses for API's vary a great deal from request to request, some handle errors without HTTP response code's. So the JSON you get back can be very different then you might expect otherwise.
> Given that it uses reflect I bet your library very slow. Look carefully - what I wrote is not a library; it's a standalone binary. It's run exactly once, when you write the code, so speed isn't an issue. > That's not a small issue. Depends on the language. In Go, it's very easy to allow a JSON value to be null and/or undefined by making the value it unmarshals to a pointer (which you should be doing already anyway)…
Oh missed that.
> This is an issue no matter what language you use.
It's a lot bigger issue when you have to define classes for each type of possible response.
Anyone know how the compilation times compare with regular Scala?
I've been investing a lot of time in learning Scala because I think that it's at the head of the vanguard of a software engineering revolution, but with some of its ergonomic issues, I can't help thinking it's eventually going to lose out to something that's more elegant from a design standpoint and has better tooling.