HNHacker News
TopNewBestAskShowJobs

jvican

780 karma · joined March 14, 2016

submissionscomments
jvican··on Kotlin becomes second most popular language on the JVM
No, you're misreading that announcement. The Scala team is working, today, on improving Scala 2.13.x and improving the migration and tooling path to Scala 3, as I said before. The fact that 2.14.x won't be release has nothing to do with the fact that there's a team of 5 or 6 people working on Scala 2 today.
jvican··on Kotlin becomes second most popular language on the JVM
It can often give false positives, but it's mostly okay and lots of people really enjoy it. It has innovated a lot on finding better ways of showing types.

It'd be good if the OP elaborates on what "bad tooling" we have in the Scala community given that today Scala's tooling is good and on par with that of Kotlin and Java.

jvican··on Kotlin becomes second most popular language on the JVM
There's a tension between people using Scala for pure FP and people preferring to opt into pure FP whenever the model domain is needed, or that don't care about tracking every effect in their program and just focus on the 80/20. There are also those that use Scala for data science and other use cases for quick prototyping.

The interests of all of these parties are different and that's what sometimes causes tensions, but these tensions do also exist in other programming languages that aim at a broad audience. Just look at Rust. Languages that do not show these tensions are languages owned by only one party (most of the time, a company) and that are the only stewards of the project and those controlling the agenda. The good thing about Scala is that it's flexible and it allows you to use it for your use case regardless of whether the language designers want to support your use case or not.

Your claim about Scala tooling being outdated or outright abandoned is not true. There has never been as good tooling as Scala has today, with a lot of innovation happening in the field. The reality is that Scala has really good tooling, on par with that of Kotlin and Java, and sometimes even better. Just look at projects such as Metals, Scalafix, Ammonite, mill, bloop or Scala Steward to get an idea of what I'm talking about.

Also, the Scala team is not working on Scala 3, Martin Odersky's team at EPFL --LAMP-- is. The Scala team at Lightbend is working on keeping improving Scala 2 and making sure tooling is still as good as it gets for when Scala 3 is finally released.

There are lots of people in the Scala community that are not so much into "FP language theory" or category theory and just see its potential as a cross-platform language to prototype and write robust software.

jvican··on Kotlin becomes second most popular language on the JVM
What is the methodology behind these results? If it is what I read in the introduction, judging Kotlin to be more widely used than Scala based on a poll is deceiving and IMO loses any weight this report might carry.
jvican··on Kotlin becomes second most popular language on the JVM
Scala isn’t owned by a company making tools, but in the recent years it has experienced a big transformation on the tooling space with projects such as mill, Ammonite, Metals, Scalafix or Bloop. I’m obviously biased because I’ve worked on some of these tools but having worked with other programming languages lately I’d dare to say Scala tooling is solid and good. In some regards, we have better developer workflows than Kotlin and Java developers have and there’s a huge stream of innovation in this space.
jvican··on Refused U.S. visa eight times, Zoom CEO is now a billionaire
Déjà vu
jvican··on OCaml bindings for PyTorch
The Scala community has some clever techniques to ensure that those properties can be proven at compile-time, for example, https://github.com/eaplatanios/tensorflow_scala for TensorFlow and https://github.com/ctongfei/nexus
jvican··on Notion – All-in-one workspace for notes, tasks, wikis, and databases
Agreed, this would be excellent, would use it myself all the time.
jvican··on A Comparison of Functional Data Structures on the JVM
Note that Scala 2.13 (next release) includes a CHAMP hash map implementation, first contributed by the original author and then refined by several Scala contributors, most notably Jason Zaugg (@retronym) and Josh (@joshlemer)
jvican··on Requests-Scala: A Scala Port of the Popular Python Requests HTTP Client
The math doesn’t check out, rankings contradict them (check TIOBE, or google indices, or even StackOverflow rankings). It’s sad to see this kind of conclusions in HN because they are not not only incorrect but dishonest.
jvican··on Why I Don't Buy Organic, and Why You Might Not Want to Either
An interesting EU study about organic farming clarifies this further. I find this image to be a nice way to summarize the use of pesticides in organic farming. https://imgur.com/a/WjRHpk9

The EU article is called "Human health implications of organic food and organic agriculture", I recommend peeking it. http://www.europarl.europa.eu/RegData/etudes/STUD/2016/58192...

jvican··on When Is Haskell More Useful Than R or Python in Data Science?
Yes, it’s heavily used in this area.
jvican··on Announcing the Build Server Protocol v1.0.0
FWIW, this has nothing to do with BSP and it's also not true technical wise.
jvican··on Elixir at PagerDuty
Lisp doesn't have any way to define those FP constructs and it's one of the first functional programming languages ever. I think you're being misled by Haskell.
jvican··on Elixir at PagerDuty
Productivity is defined in subjective terms. I know several success stories of companies that use Scala as a better Java and find themselves more productive. That doesn't mean they don't do any functional programming -- it just means they don't need to use Scalaz/cats to be happy Scala developers. The OP is mostly concerned about Scala being a language that encourages the use of monad transformers and catamorphisms all over the place. What I'm trying to illustrate is that nothing could be farther from the truth.
jvican··on Elixir at PagerDuty
I work for the Scala Center and I'd like to comment on some of the points you make to hopefully explain how I see things from my side. You can expect my opinion to be biased but I'll try to stick to the facts.

> Haskell influence on the language, especially early on, encouraged the omission of dots and parentheses wherever possible.

This is considered an anti-pattern in the Scala community. The last library that used this at large scala was sbt, Scala's build tool, and now everyone discourages the use of infix operators.

> Haskell influence on the community encourages category theory solutions to all problems.

This is simply not true. First, there is no Haskell influence on the language. Scala is a functional programming language, all similarities between the two are just fundamental to how their type systems work and the foundations of the paradigm. Second, I contest heavily that the Community encourages category theory to solve all the problems. There are many subcommunities in Scala and many styles, but if you talked to some Scala developers nobody would agree that category theory should be applied to all code. In fact, most people don't. They just use Scala because it's a better Java that boosts their productivity.

> Scala's rich OO system (classes, interfaces, traits, singletons, case classes, implicits, etc) results in frequent design paralysis, not to mention taking a while to learn.

Absolutely agree that for someone not experienced, it may be difficult to know what's the best way to design libraries (this is more of a problem with libraries than applications). This is a big problem of Scala that I think we're solving by making the language more opinionated and being more open about what's encouraged and discouraged.

If you ask for my opinion, I think we also need to make a better job at communicating all this knowledge that advanced Scala developers learn but that is usually kept to closed circles.

jvican··on Elixir at PagerDuty
I don't know what he meant by that either, but it's important to mention that `Scala != Scalaz` and that sbt is not the only build tool used in the community (and it's certainly not built by academics!).
jvican··on Speeding Up Compilation Time with Scalac-profiling
No, non-cached whitebox macros are.
jvican··on Speeding Up Compilation Time with Scalac-profiling
Happy to take any questions, by the way!
jvican··on Towards Scala 3
Not really. https://github.com/random-maven/scalor-maven-plugin
jvican··on Towards Scala 3
At the Scala Center we’re working on addressing these problems. We now have working groups devoted to ease coding in Scala and make it easier for any dev to use any build tool.
jvican··on Towards Scala 3
> which has the potential to achieve better accuracy

The quality of the used names extraction affects accuracy, but not compile speed. I must say, Dotty and Scala are extracting about the same amount of dependencies, with some corner cases being covered better in Dotty (for example, changes in constant values).

I don't see a way Dotty can become a faster incremental compiler that doesn't involve adding the incrementality in the compiler.

jvican··on Towards Scala 3
I challenge the fact that Rust and Kotlin are improving faster than Scala. Scala is not only more stable, but is under active development and there are lots of discussions to improve the language over time (check our SIP meetings).

Kotlin doesn't even get closer to what Scala is, and Rust is for those folks with the mentality that memory management is something worth keeping track of.

jvican··on Towards Scala 3
> However, it supports more aggressive incremental compilation than Scala 2

I'm not sure what you mean here... but Scala 2 and Dotty have the same incremental compiler, and their independent bridges feature overall the same quality (which is high and heavily battle tested, for those interested).

jvican··on Thoughts on Rust, a few thousand lines in
I think the standard compilation speed of Scala is around 3000 loc/s. https://developer.lightbend.com/blog/2017-06-12-faster-scala...

Your Rust example compiles at about 180loc/s.

jvican··on Tail calls, tailrec and trampolines (2009)
Note that there is a compiler plugin for mutual recursion in Scala. https://github.com/wheaties/TwoTails/blob/master/README.md
jvican··on Complexity Theory, Game Theory, and Economics
Any idea how I can get an ePub or MoBi version of this?
jvican··on Our Approach to Privacy
Sounds about what I was looking for. Thanks!
jvican··on Our Approach to Privacy
After reading this, I have two questions:

1. Are there any statistics showing the ratio of security issues between Android and iOS?

2. What's the most common phone among security researchers?

To be honest, I'm wary of believing this, but I own a Nexus and if I had to give the benefit of the doubt to either Google or Apple, it would most certainly be Apple because they don't make business out of my data (or, not as much as Google, at least).

jvican··on Scala 2.12.3 Released
I think it has very much changed. In any case, open source tools are there to be improved by the community. If you feel sbt is not solving your problems in the right way or could be improved, please get in touch with us. We're always happy to make the tool easier to use, at all levels.
← PreviousPage 4 of 5Next →