Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Scala 3.0

github.com

Post reply on HN
Print view View original

211–220 of 292 posts

Re: Scala 3.0

#211

Post by harveywi »

stock_toaster wrote: post #205
peq wrote: post #198

Earlier quoted context omitted.

Scala is one of the smallest typed languages in terms of syntax. See slide 13: https://www.slideshare.net/Odersky/preparing-for-scala-3#13 With scala 3, syntax has been simplified even more, e.g.: No more braces necessary. Top level declarations. Extension Methods.

> No more braces necessary Optional braces seems like a weird feature to me. I would prefer consistently. I think a language should either be "bracey" or not. Just pick one!

I personally wanted to be able to use underscores instead of braces.

Re: Scala 3.0

#212

Post by The_rationalist »

caoilte wrote: post #107
vips7L wrote: post #104

Earlier quoted context omitted.

I largely disagree and am not looking forward to dealing with mixed brace code at work.

Hopefully there will be a scalafmt rule that can enforce consistency.

And hopefully more than 0.1% of projects will turn the lint on..

Re: Scala 3.0

#214

Post by The_rationalist »

mwcampbell wrote: post #173
kjaer wrote: post #95

Earlier quoted context omitted.

Scala Native and GraalVM Native Image are projects with different goals, so I wouldn't say that one makes the other unnecessary. Both projects aim to compile to native code, and have use-cases for projects where the JVM startup time is too high. However, one of the main goals of Native Image is to offer as much partial evaluation (PE) at compile-time as possible. Scala Native does also seem to do some PE, but my unde…

> However, one of the main goals of Native Image is to offer as much partial evaluation (PE) at compile-time as possible. This is tangential, but I wonder if Native Image's focus on compile-time PE, and the overall design of GraalVM, would make it feasible to AOT-compile a sufficiently static subset of JavaScript to efficient native code. If so, that could influence my choice of language for new projects.

First AOT binaries are slower than JIT, there's nothing efficient about it, at least for high level languages. Second you can already make javascript binaries thanks to GraalJs. The biggest added value by far is the polyglotism/interop with the other language universes.

Re: Scala 3.0

#215

Post by The_rationalist »

maxov wrote: post #17
leroman wrote: post #4

I get paid to write TypeScript, it has come a long way to a relatively enjoyable experience compared to how expressive i feel with Scala. Looking forward to giving Scala 3 a spin to learn whats new

As someone who has spent a lot of time diving deep into Scala (I worked on compiler related semantic tooling for scalameta, worked on a experimental parallelizable Scala compiler, and even have a single commit in this release from almost four years ago LOL), and who more recently has been working with TypeScript, I find this really interesting and agree in some ways. Scala 2.x already had path-dependent types, which…

What does the typewritable type do/allow?

Re: Scala 3.0

#216

Post by halfmatthalfcat »

RhodesianHunter wrote: post #138
xfer wrote: post #79

Earlier quoted context omitted.

Kotlin doesn't sound like a good language to bet on since most suitable(for jvm) features it has will be integrated by Java now that it has picked up pace. I guess it only has decent marketshare because of google's android support(they are throwing stuff on the wall to move away from Oracle IP i guess) and Jetbrains being very popular among java devs.

Most F500's with large Java codebases including Google and Amazon are already betting big on Kotlin for server side development.

Source? Never seen or heard a major F500 pick up Kotlin as their primary backend lang over Java.

Re: Scala 3.0

#217

Post by eigenspace »

zeec123 wrote: post #161
kinjba11 wrote: post #153

Earlier quoted context omitted.

What do you mean by "not first class"? https://docs.julialang.org/en/v1/manual/functions/#man-anony...

It means I cannot fully specify the type of function my interface expects as an argument. A function is of type ‘Function’. There is no way to define it with the type of its argument or the type of what it returns.

Actually, Julia functions are all subtypes of Function. Every julia function has a unique type.

We don't parameterize a function by it's input and return types because functions are extremely polymorphic in julia. However, there's lots of tricks one can do to dispatch on whether or not a given function have methods that satisfy some sort of interface, see here: https://github.com/oxinabox/Tricks.jl#we-can-use-static_hasm...

Using this technique, you can do compile time dispatch on things like input and return types.

Re: Scala 3.0

#218

Post by saym »

jules wrote: post #97

Scala 3 + VS code + worksheets is my favourite exploratory programming environment. Its has: * Powerful functional features * Powerful OO features * Imperative features * Powerful type system * Great stdlib * Great syntax * Very fast write/test cycle with worksheets, way better than a REPL * Great IDE features such as autocomplete Scala may not be the best on any one axis, but the combination is unparalleled.

Can you talk a little more about worksheets? I'm not familiar with scala worsheets at all.

Follow-up: How do you transition to productionizing your code after iterating in them?

Re: Scala 3.0

#219

Post by Nullabillity »

kaba0 wrote: post #182
Nullabillity wrote: post #155

Earlier quoted context omitted.

Then again, considering the JVM's disastrous recent trajectory (Loom, JPMS, renewed wasted focus on Java-the-language, and so on) that doesn't seem like such a great upside anymore.

Wat? How is the recent trajectory disastrous?

To take Loom as an example..

The primary problem with threads isn't their performance, but the way that they encourage bugs and race conditions by decoupling data access from flow control.

They're fine as a low-level API for implementing a more usable API, but not as the primary API that you expect application developers to use.

Re: Scala 3.0

#220

Post by zzbzq »

jules wrote: post #97

Scala 3 + VS code + worksheets is my favourite exploratory programming environment. Its has: * Powerful functional features * Powerful OO features * Imperative features * Powerful type system * Great stdlib * Great syntax * Very fast write/test cycle with worksheets, way better than a REPL * Great IDE features such as autocomplete Scala may not be the best on any one axis, but the combination is unparalleled.

I don't know what worksheets are, but does Scala3 work with vscode now? Previously the plugins didn't do much, especially if you didn't use SBT.
Post reply on HN