# Scala

Scala is a programming language that combines functional and object-oriented programming styles.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Scoverage Hardening in Scala 3: Results and Next Steps

DevFeed: [Scoverage Hardening in Scala 3: Results and Next Steps](<https://devfeed.tech/articles/scoverage-hardening-in-scala-3-results-and-next-steps-140143.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/11/17/scoverage-hardening-results.html>)

Published: 2026-11-16T23:00:00Z

Content type: article

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [future](<https://devfeed.tech/tags/future.md>), [hardening](<https://devfeed.tech/tags/hardening.md>), [results](<https://devfeed.tech/tags/results.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Scala 3 coverage testing now runs across an expanded compiler test suite and on every pull request. As of early October 2026, 7,793 of 7,828 cases passed (99.55%); the effort fixed 95 breakages and identified a systematic cause for the remaining failures as future work. Scala 3's compiler instruments code after type checking using effectful probes, while Scoverage libraries provide reports; instrumentation uses `-coverage-out:DIR` and does not require a separate compiler plugin. Because probes can change behavior if they disrupt evaluation order, the compiler must preserve that order when instrumenting expressions. Testing was expanded incrementally across language test groups, with failures tracked, investigated, and passing tests restored as regression coverage. Nightly and release builds also compile selected projects with coverage. The article says the early instrumentation phase interacts with many later compiler phases, especially capture calculus, and suggests exploring instrumentation later in the pipeline to reduce those interactions.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: Scoverage hardening. The work is coordinated by the Scala Center. Summary We've been working throughout 2026 on making Scoverage more reliable in Scala 3. As the project comes to a close, this article reports on the results. We have successfully enabled coverage testing across the wider compiler test suite, fixed breakages encountered in process achieving a 99.5% pass rate, and for the 0.5% tests not working with coverage yet, identified a systematic root cause to be resolved as future work. What is coverage? Suppose you have a function that calculates a shipping fee: def shipping(total: Int): Int = if total >= 50 then 0 else 5 And a test: assertEquals(shipping(70), 0) The test passes, but it only tests the free shipping case. The paid-shipping branch never runs. Code coverage makes such gaps visible by recording which statements and branches execute during a test run. In this example, adding assertEquals(shipping(20), 5) would test the missing branch. In Scala 3, coverage instrumentation is built directly into the compiler. You can enable it with the -coverage-out:DIR compiler option, where DIR is the directory where you'd like coverage telemetry to be recorded. The compiler writes a map of instrumented statements, and the instrumented program records which of them execute at runtime. The Scoverage plugin and reporting libraries provide the reporting and visualization of this data. In Scala 3, the instrumentation itself comes from the compiler, so a separate compiler plugin is not needed. See Code Coverage for Scala 3 for documentation. You can visualize the reports as HTML using sbt-scoverage. Interactions with the language The compiler implements coverage as a phase that rewrites the program after type checking. This phase records statement execution by injecting probes before each. Probes are effectful function calls performing the recordings. Every later compiler phase then receives t

## Scala 3.10.1 is now available!

DevFeed: [Scala 3.10.1 is now available!](<https://devfeed.tech/articles/scala-3-10-1-is-now-available-128974.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.10.1/>)

Published: 2026-11-10T23:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [releases](<https://devfeed.tech/topics/releases.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>)

Tags: [asm](<https://devfeed.tech/tags/asm.md>), [change](<https://devfeed.tech/tags/change.md>), [cli](<https://devfeed.tech/tags/cli.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [directives](<https://devfeed.tech/tags/directives.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [java-17](<https://devfeed.tech/tags/java-17.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [jdk-28](<https://devfeed.tech/tags/jdk-28.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [lock](<https://devfeed.tech/tags/lock.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [nested](<https://devfeed.tech/tags/nested.md>), [package-private](<https://devfeed.tech/tags/package-private.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [sip](<https://devfeed.tech/tags/sip.md>)

### AI overview

Scala 3.10.1 adds JDK 28 compiler and class-file support, including target version 28, which cannot exceed the JDK running the compiler. It warns about calling `synchronized` on Java value-based class instances, which JDK 28 rejects; the release recommends a dedicated lock object. The bundled Scala CLI is upgraded to 1.18.0: its JVM launcher now requires Java 17 or newer, though code can still target older JVMs with options such as `--jvm 8` or `--jvm 11`. The release also adds experimental SIP-77 method-block end markers, enabled by import or compiler option; markers must match the method name at the call site, and the feature may change or be removed. Other changes include a new broad-catch warning, REPL resource support, and fixes across compiler and tooling.

### Source excerpt

Scala 3.10.1, the first patch release in the Scala 3.10 series, is now available. Release highlights JDK 28 support (#27347) The compiler now supports JDK 28, including target version 28 for -release and -java-output-version. The target version cannot exceed the JDK version running the compiler. ASM has also been updated to 9.11.1 (#27363), enabling support for JDK 28 class files. The compiler now warns when synchronized is called on an instance of a Java value-based class (#27128). JDK 28 rejects such calls. Use a dedicated lock object instead. Upgrade to Scala CLI 1.18.0 (#27255) The bundled Scala CLI has been upgraded from 1.17.1 to 1.18.0. Highlights include: The JVM launcher no longer starts on JDK 11-16 by downloading JDK 17 and relaunching. Start it on Java 17 or newer. Your code can still be compiled and run on older JVMs, for example with --jvm 8 or --jvm 11. scala fix removes deprecated comma separators from //> using directives. Java snippets, Java source read from standard input, and Java blocks in Markdown now support enums, records, package-private classes, and JEP 512 compact source files. See the Scala CLI 1.18.0 release notes for the full list of changes. Experimental SIP-77: method block end markers (#24251) Method block end markers make it easier to see where nested argument blocks end. Experimental SIP-77 lets you close an argument block introduced by : with a named end marker. The marker must name the method as it is written at the call site, so a mismatched name is an error. This feature is experimental and may change or be removed depending on the SIP Committee's decision. We welcome feedback from users who try it. Enable it with import scala.language.experimental.methodBlockEndMarkers or -language:experimental.methodBlockEndMarkers. //> using scala 3.10.1 //> using options -language:experimental.methodBlockEndMarkers def test(name: String)(body: => Unit): Unit = println(s"Running test: $name") body def repeat(times: Int)(body: => Unit): Unit

## IntelliJ Scala Plugin 2026.3 Is Out!

DevFeed: [IntelliJ Scala Plugin 2026.3 Is Out!](<https://devfeed.tech/articles/intellij-scala-plugin-2026-3-is-out-121131.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/scala/2026/11/06/intellij-scala-plugin-2026-3-is-out/>)

Author: Dmitrii Naumenko

Published: 2026-11-06T12:15:21Z

Content type: release

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>)

Topics: [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [Syntax Highlighting](<https://devfeed.tech/topics/syntax-highlighting.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [2026-3](<https://devfeed.tech/tags/2026-3.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [build-tool](<https://devfeed.tech/tags/build-tool.md>), [code-analysis](<https://devfeed.tech/tags/code-analysis.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [framework](<https://devfeed.tech/tags/framework.md>), [highlighting](<https://devfeed.tech/tags/highlighting.md>), [idea](<https://devfeed.tech/tags/idea.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [intellij](<https://devfeed.tech/tags/intellij.md>), [intellij-idea](<https://devfeed.tech/tags/intellij-idea.md>), [news](<https://devfeed.tech/tags/news.md>), [play](<https://devfeed.tech/tags/play.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [releases](<https://devfeed.tech/tags/releases.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [scala-programming](<https://devfeed.tech/tags/scala-programming.md>), [support](<https://devfeed.tech/tags/support.md>)

### AI overview

Scala plugin 2026.3 adds support for Scala 3.10 and improves Scala 3 analysis, including extension-method resolution, contextual argument selection, and type inference. Twirl support has been architecturally rewritten, with better parsing, completion, formatting, navigation, and template renaming across Play projects. Build updates include improved sbt 2.x imports, restored dependency completion for sbt and Scala CLI, and automatic recompilation of dependents when Scala 3 macros change. Compiler-based highlighting reuses valid diagnostics and batches checks to reduce background work. Debugging and editor improvements include additional breakpoint support and smoother watch evaluation. Compatibility changes: separate sbt main and test modules are now mandatory; dedicated Ammonite assistance and Fastpass imports are removed; the standalone IntelliJ Scala Bundle is retired. Ammonite scripts can still be run externally.

### Source excerpt

Hello everyone! Scala plugin 2026.3 is here! This release brings more accurate Scala 3 code analysis, substantially reworked Twirl support for Play Framework developers, and more efficient compiler-based highlighting that reduces redundant background work. You'll also find improvements to build-tool support, debugging, and everyday editing. Let's take a closer look at what's new. Scala 3 [...]

## Scala 3.3.9 LTS is now available!

DevFeed: [Scala 3.3.9 LTS is now available!](<https://devfeed.tech/articles/scala-3-3-9-lts-is-now-available-105424.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.3.9/>)

Published: 2026-10-27T23:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [JEP-401](<https://devfeed.tech/topics/jep-401.md>)

Tags: [backports](<https://devfeed.tech/tags/backports.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [classes](<https://devfeed.tech/tags/classes.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [doc](<https://devfeed.tech/tags/doc.md>), [higher-kinded-types](<https://devfeed.tech/tags/higher-kinded-types.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [java](<https://devfeed.tech/tags/java.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [lts](<https://devfeed.tech/tags/lts.md>), [release](<https://devfeed.tech/tags/release.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [series](<https://devfeed.tech/tags/series.md>), [support](<https://devfeed.tech/tags/support.md>), [syntax](<https://devfeed.tech/tags/syntax.md>)

### AI overview

Scala 3.3.9 LTS backports most bug fixes and some improvements from Scala 3.9.0. Compatibility was checked across more than 1,500 projects in the Scala 3 Open Community Build, with the changes reported not to break binary or source compatibility. Highlights include smaller Scaladoc jars by removing custom fonts, improved Java generic signatures for higher-kinded types and value classes, exhaustiveness checking for sealed abstract Java classes, clearer missing-member diagnostics, warnings for dubious negative literal syntax, and a Scaladoc fix for an NPE on JDK 25. The 3.3.x series is planned to receive support for the next year; eligible fixes and improvements from Scala Next will continue to be backported.

### Source excerpt

Scala 3.3.9 LTS is now available! This patch release backports most of the bugfixes and some of the improvements introduced in Scala 3.9.0. All of the backported changes were proven to not break either binary or source compatibility, by testing over 1500 projects in the Scala 3 Open Community Build. Notable changes Stop using custom fonts for Scaladoc, to reduce doc jar size #26393 Improve Java generic signatures for higher-kinded types, value classes #25540 #25744 #25631 Exhaustiveness checking for sealed abstract Java classes #25788 Actionable diagnostic for missing members #23572 Warn on dubious negative literal syntax (- 42, -42.abs) #24163 Scaladoc no longer crashes with an NPE on JDK 25 #25779 For a full list of changes and contributor credits, please refer to the release notes. Scala LTS Release Notice The next planned LTS 3.3 release will include updates introduced until last Scala 3.10.x before 3.11. We'll continue to backport eligible bug fixes and improvements from the Scala Next series. Because the next LTS 3.9.0 has now been released, we will continue to support the 3.3.x series for the next year. Scala 3.x End of service 3.3.x 2027 Sep 3.9.x 2029 Sep or later 3.10.x Until 3.11.x

## Scala 3.10 released!

DevFeed: [Scala 3.10 released!](<https://devfeed.tech/articles/scala-3-10-released-85231.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.10/>)

Published: 2026-10-11T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [toolchain](<https://devfeed.tech/topics/toolchain.md>)

Tags: [announce](<https://devfeed.tech/tags/announce.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [cross-compilation](<https://devfeed.tech/tags/cross-compilation.md>), [releases](<https://devfeed.tech/tags/releases.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>)

### AI overview

Scala 3.10.0 is the first release in the Scala Next series. It stabilizes SIP-67, moves three SIPs to preview, removes deprecated syntax while preserving binary compatibility, and introduces compiler, standard library, tooling, and distribution changes. The release notes recommend Scala 3.9 LTS for projects seeking the longest support window.

### Source excerpt

Scala 3.10 released! We are happy to announce Scala 3.10.0, the first release of the new Scala Next series. This release stabilizes SIP-67, moves three SIPs into preview, and starts dropping legacy language features that have been deprecated for several minor releases. Scala 3.3 LTS and Scala 3.9 LTS put compatibility with Scala 2.13 first. Now, nearly five years after Scala 3.0, Scala 3.10 starts removing legacy syntax and features that have been deprecated for several minor releases. The standard library also starts using more Scala 3 features, such as inline and extension methods. Binary compatibility is preserved: libraries compiled with earlier Scala 3 versions keep working, including those that used features now removed. Source that still uses those features must be updated to compile with 3.10. Macros and compiler plugins may need to be adapted to changed internal representations (details below). If you publish a library and want the longest support window, Scala 3.9 LTS remains the recommended version to build against. Cross-compilation between Scala 2 and 3.10 is no longer supported because of the removed legacy features. Some libraries might remain cross-compilable, but it is expected that cross-compiled libraries will remain on Scala 3.9 LTS indefinitely. Before checking a 3.10 artifact with MiMa, upgrade to MiMa 1.2.1 or later: that release adds Scala 3.9 and 3.10 support and fixes several false positives. Highlights SIP-67: pattern matching under strictEquality no longer needs CanEqual - now stable. (But strict equality remains an opt-in feature.) Three SIPs move to preview behind -preview: @unroll, relaxed lambda syntax, and referenceable package objects. Deprecated syntax previously retained for compatibility with Scala 2, such as A with B, is now an error; see Breaking changes. The compiler reports Recursion limit exceeded instead of crashing with a StackOverflowError (details). Scala is now also distributed as .deb and .rpm packages. Breaking change

## VirtusLab assumes responsibility for Scala 2 maintenance

DevFeed: [VirtusLab assumes responsibility for Scala 2 maintenance](<https://devfeed.tech/articles/virtuslab-assumes-responsibility-for-scala-2-maintenance-66638.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/scala2-maintenance.html>)

Published: 2026-10-06T22:00:00Z

Content type: news

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [maintenance](<https://devfeed.tech/tags/maintenance.md>), [migration](<https://devfeed.tech/tags/migration.md>), [releases](<https://devfeed.tech/tags/releases.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>)

### AI overview

VirtusLab has assumed responsibility for maintaining Scala 2 in coordination with the Scala Center and Scala Core Team, which also manage Scala 3 development. It plans to maintain Scala 2.12 and 2.13 as long as necessary and continue improving migration to Scala 3. The next releases are being planned and discussed in the Scala Contributors forum.

### Source excerpt

We are happy to announce that VirtusLab has assumed responsibility for maintenance of Scala 2. This means that VirtusLab, in coordination with the Scala Center and the Scala Core Team, now manages the development of both Scala 2 and Scala 3. Former members of the Scala 2 team at Akka have joined the VirtusLab OSS team, so there will be no impact on Scala 2 maintenance or Scala 2's future. Our plans for Scala 2 maintenance have long been documented at https://www.scala-lang.org/development/#scala-2-maintenance and the wordings there have not changed. VirtusLab will maintain Scala 2.12 and 2.13 as long as necessary and will also continue to improve the Scala 2-to-3 migration story. Lukas Rytz remains on the Scala Core Team but as Scala 2 Representative, no longer as Akka Representative. We are deeply grateful to Akka for their years of support for Scala and its governance and ecosystem. If you have any questions, see https://scala-lang.org/community/ for ways to contact us. The next Scala 2.12 and 2.13 releases are being planned and discussed on these threads on the Scala Contributors forum: Scala 2.12.22: https://contributors.scala-lang.org/t/scala-2-12-22-release-planning/7309 Scala 2.13.19: https://contributors.scala-lang.org/t/scala-2-13-19-release-planning/7293

## EveryThing You Need To Know About Scala

DevFeed: [EveryThing You Need To Know About Scala](<https://devfeed.tech/articles/everything-you-need-to-know-about-scala-65415.md>)

Original publisher: [Read original article](<https://blog.devops.dev/everything-you-need-to-know-about-scala-c833fe885c44?source=rss----33f8b2d9a328---4>)

Author: Rahul Patidar

Published: 2026-10-06T13:04:28Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [class](<https://devfeed.tech/topics/class.md>), [Closure](<https://devfeed.tech/topics/closure.md>), [constructor](<https://devfeed.tech/topics/constructor.md>), [Exception](<https://devfeed.tech/topics/exception.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [superclass](<https://devfeed.tech/topics/superclass.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [block](<https://devfeed.tech/tags/block.md>), [class](<https://devfeed.tech/tags/class.md>), [classes](<https://devfeed.tech/tags/classes.md>), [closure](<https://devfeed.tech/tags/closure.md>), [design-patterns](<https://devfeed.tech/tags/design-patterns.md>), [exception](<https://devfeed.tech/tags/exception.md>), [exception-handling](<https://devfeed.tech/tags/exception-handling.md>), [factory](<https://devfeed.tech/tags/factory.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [function](<https://devfeed.tech/tags/function.md>), [functions](<https://devfeed.tech/tags/functions.md>), [monad](<https://devfeed.tech/tags/monad.md>), [none](<https://devfeed.tech/tags/none.md>), [nothing](<https://devfeed.tech/tags/nothing.md>), [null](<https://devfeed.tech/tags/null.md>), [packages](<https://devfeed.tech/tags/packages.md>), [recursion](<https://devfeed.tech/tags/recursion.md>), [scala](<https://devfeed.tech/tags/scala.md>), [syntax](<https://devfeed.tech/tags/syntax.md>)

### AI overview

The excerpt presents Scala interview topics through short explanations and code examples. It describes factory, singleton, and lazy initialization patterns; treating functions as values and higher-order functions; tail recursion, closures, placeholder syntax, partially applied functions, currying, purity, and anonymous functions. It also covers trait linearization in the diamond problem, monads, case class features, primary and auxiliary constructors, named Scala frameworks, exception handling without checked exceptions, BitSet, the App helper, package names, and Null, Nil, None, and Nothing. The supplied text ends mid-example in the factory pattern and is therefore an excerpt rather than evidence of the complete article.

### Source excerpt

Everyone who is a beginner in scala faces many problems and has many confusions while trying to understand important concepts in scala. In interviews, interviewers frequently ask about these concepts in Scala, and candidates are frequently unable to impress or explain these concepts to interviewers. So in today's post, I will be covering some important concepts in Scala, so whenever you go for your next interview, just read these concepts once and it will really help you to answer Scala Related Interview Questions. This post will cover the following topics: 1. Scala Design Patterns 2. First Class function 3. Higher-Order Functions 4. Tail Recursion in Scala. 5. Block of Code. 6. Closure 7. PlaceHolder Syntax: 8. Partially Applied Function: 9. Function Currying : 10. pure functions : 11. Anonymous Function: 12. Diamond Problem In scala: 13. traint in scala: 14. Monad in scala: 15. Case Classes In Scala. 16. constructors in Scala 17. Frameworks supported by Scala 18. Exception Handling in Scala 19. BitSet 20. app Class 21. Packages in Scala 22. Null, Nill, None, and Nothing in Scala Scala Design Patterns. Every time you develop some software, there are some common problems that everyone faces in his/her software engineering journey. To resolve these issues, we have some predefined general-purpose reusable solutions. These reusable solutions are nothing but design patterns. These are the types of templates that we can use as a solution whenever we encounter these issues. We have 3 kinds of design patterns in Scala. The factory design pattern: the main aim of the factory design pattern is to separate instance creation logic from the client. Here we implement instance creation logic in the factory class without exposing this logic to the client. It is used when we have multiple subclasses with one superclass and, based on the input, we need to return one of the inputs. Example trait Computer { def ram: String def hdd: String def cpu: String } case class PC(ram: String, h

## Top Spark Programming Question For Interview

DevFeed: [Top Spark Programming Question For Interview](<https://devfeed.tech/articles/top-spark-programming-question-for-interview-65417.md>)

Original publisher: [Read original article](<https://blog.devops.dev/top-spark-programming-question-for-interview-d5e46dca64d1?source=rss----33f8b2d9a328---4>)

Author: Rahul Patidar

Published: 2026-10-06T13:04:18Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Apache Spark](<https://devfeed.tech/topics/spark.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [big-data](<https://devfeed.tech/topics/big-data.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [big-data](<https://devfeed.tech/tags/big-data.md>), [count](<https://devfeed.tech/tags/count.md>), [custom](<https://devfeed.tech/tags/custom.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [define](<https://devfeed.tech/tags/define.md>), [example](<https://devfeed.tech/tags/example.md>), [explain](<https://devfeed.tech/tags/explain.md>), [function](<https://devfeed.tech/tags/function.md>), [functions](<https://devfeed.tech/tags/functions.md>), [groupby](<https://devfeed.tech/tags/groupby.md>), [hit](<https://devfeed.tech/tags/hit.md>), [interview](<https://devfeed.tech/tags/interview.md>), [programming](<https://devfeed.tech/tags/programming.md>), [question](<https://devfeed.tech/tags/question.md>), [scala](<https://devfeed.tech/tags/scala.md>), [spark](<https://devfeed.tech/tags/spark.md>), [sql](<https://devfeed.tech/tags/sql.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

The excerpt provides Spark interview examples for counting items across orders, cleaning special values, clickstream sessionization, UDFs, and pivoting student scores. The Scala item-count example removes brackets, splits item lists, explodes them into rows, then groups and counts. The cleaning function loops over DataFrame columns and converts listed special characters, blanks, nulls, and "NA" to null; despite the prompt mentioning uncertain column names, it applies the same value checks to every column. The sessionization examples are given in both PySpark and Scala: partition by user, order by timestamp, flag the first event or one more than 30 minutes after the prior event, then cumulatively number sessions. The stated maximum session length of two hours is not implemented in the shown logic. Other examples capitalize names with a UDF, including registration for Spark SQL, and pivot subject rows into columns using the first score.

### Source excerpt

Introduction: Hello everyone, Spark programming questions are crucial for preparing for big data interviews. In today's post, I'll cover important Spark programming questions that can help you get ready for your big data interview. Write a Spark program in Scala that takes a DataFrame with bill IDs and order names (as lists of items) and returns the count of each distinct item across all orders. import org.apache.spark.sql.SparkSession import org.apache.spark.sql.functions._ val spark = SparkSession.builder.appName("Order Count").getOrCreate() import spark.implicits._ val data = Seq( (101, "[pizza,samosa,idli]"), (102, "[kachori,sambhar,idli]"), (103, "[dosa,vada,pizza]"), (104, "[samosa,idli,chai]"), (105, "[pizza,chai,dosa]") ) val df = data.toDF("billid", "Ordername") val dfCleaned = df.withColumn("Ordername", regexp_replace(col("Ordername"), "\\[|\\]", "")) val dfSplit = dfCleaned.withColumn("Ordername", split(col("Ordername"), ",")) val dfExploded = dfSplit.withColumn("Item", explode(col("Ordername"))).select("Item") val dfCount = dfExploded.groupBy("Item").count() dfCount.show() 2. Write a Spark program in Scala with columns id, name, and salary, where the data might contain special characters, blanks, and "NA" values that should be treated as nulls. Handle the uncertainty of column names being dynamic and uncertain due to potential special characters. import org.apache.spark.sql.SparkSession import org.apache.spark.sql.functions._ val spark = SparkSession.builder.appName("Handle Special Characters and Nulls").getOrCreate() import spark.implicits._ val data = Seq( (1, "#", ""), (2, "dd", "$"), (3, "NA", "5000"), (4, "John", "NA"), (5, "", "6000") ) val df = data.toDF("id", "name", "salary") def cleanColumns(df: org.apache.spark.sql.DataFrame): org.apache.spark.sql.DataFrame = { val specialChars = List("#", "$", "%", "&", "@") val cleanedDf = df.columns.foldLeft(df)((currentDf, colName) => { currentDf.withColumn(colName, when( col(colName).isin(specialChars: _*

## Scala Days 2026 and October Scala Community Events

DevFeed: [Scala Days 2026 and October Scala Community Events](<https://devfeed.tech/articles/let-s-meet-in-october-65425.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/10/06/lets-meet-in-october.html>)

Published: 2026-10-05T22:00:00Z

Content type: news

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Developer Events](<https://devfeed.tech/topics/developer-events.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>)

Tags: [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [berlin](<https://devfeed.tech/tags/berlin.md>), [conference](<https://devfeed.tech/tags/conference.md>), [conferences](<https://devfeed.tech/tags/conferences.md>), [days](<https://devfeed.tech/tags/days.md>), [developers](<https://devfeed.tech/tags/developers.md>), [functional-programming](<https://devfeed.tech/tags/functional-programming.md>), [online](<https://devfeed.tech/tags/online.md>), [programming](<https://devfeed.tech/tags/programming.md>)

### AI overview

Scala Days 2026 will take place in Berlin on October 12-13, with workshops on October 14-15 and a EUR 15 livestream option. The article also lists Scala and functional programming events in several cities throughout October.

### Source excerpt

Scala Days 2026 is just around the corner! Next week, on 12 and 13 October, the Scala community will come together at Kulturbrauerei in Berlin for two days of learning, sharing experiences, and catching up with friends and colleagues. The program opens with a keynote by Martin Odersky. There will also be interactive labs, giving you time to explore tools and ideas with their maintainers. Whether you use Scala every day or are getting to know the ecosystem, we look forward to welcoming you. If you'd like to stay a little longer, two-day workshops follow on 14 and 15 October at Hotel Oderberger, with practical sessions on AI-assisted development and Safe Scala. Workshops require a separate ticket or a conference and workshop bundle. There are also satellite events around the conference: a guided tech walk and dinner hosted by VirtusLab on 11 October, and Typelevel Traverses Berlin (waitlist) on 14 October, hosted at Zalando. Both offer more time to meet fellow Scala developers and exchange ideas. Buy your Scala Days ticket and join us in Berlin. Join us online, or meet your local community If you can't travel to Berlin, you can still follow the conference from home. Buy a streaming ticket by choosing Livestream Access in the ticket shop. Tickets cost EUR 15 and provide access to the live conference sessions. Workshops and interactive labs are not included in the stream. You can find more details in the online attendance announcement. There are also plenty of opportunities to meet fellow Scala developers closer to home this October. Local meetups and conferences are a lovely way to exchange ideas, learn from each other, and get to know the people behind the projects you use. Scala events this October Here are some upcoming events around the Scala and functional programming communities, in date order: 7 October, London, UK: London Scala Talks, with talks on Scala 3 specialization, probability and Balatro, and suspendable query DAGs. 8 October, Prague, Czechia: Functional J

## Code Style and Quality Guide -- Formatting Guide

DevFeed: [Code Style and Quality Guide -- Formatting Guide](<https://devfeed.tech/articles/code-style-and-quality-guide-formatting-guide-48564.md>)

Original publisher: [Read original article](<https://flink.apache.org/how-to-contribute/code-style-and-quality-formatting/>)

Published: 2026-09-18T15:54:07.612713Z

Content type: tutorial

Language: en

Sources: [Apache Flink](<https://devfeed.tech/sources/apache-flink-stateful-computations-over-data-streams-on-apache-flink.md>)

Topics: [code style](<https://devfeed.tech/topics/code-style.md>), [formatting](<https://devfeed.tech/topics/formatting.md>), [Java](<https://devfeed.tech/topics/java.md>), [ide](<https://devfeed.tech/topics/ide.md>), [Scala](<https://devfeed.tech/topics/scala.md>)

Tags: [code-formatting-style](<https://devfeed.tech/tags/code-formatting-style.md>), [code-style](<https://devfeed.tech/tags/code-style.md>), [formatting](<https://devfeed.tech/tags/formatting.md>), [guide](<https://devfeed.tech/tags/guide.md>), [ide](<https://devfeed.tech/tags/ide.md>), [java](<https://devfeed.tech/tags/java.md>), [java-language](<https://devfeed.tech/tags/java-language.md>), [quality](<https://devfeed.tech/tags/quality.md>), [readability](<https://devfeed.tech/tags/readability.md>), [scala](<https://devfeed.tech/tags/scala.md>), [spaces](<https://devfeed.tech/tags/spaces.md>)

### AI overview

A formatting guide for Apache Flink contributors covering IDE setup, Spotless and Checkstyle, Apache license headers, import organization, naming conventions, whitespace, and rules for breaking long lines in Java and Scala code.

### Source excerpt

Code Style and Quality Guide -- Formatting Guide # Preamble # Pull Requests & Changes # Common Coding Guide # Java Language Guide # Scala Language Guide # Components Guide # Formatting Guide # Java Code Formatting Style # We recommend to set up the IDE to automatically check the code style. Please follow the IDE Setup Guide to set up spotless and checkstyle . License # Apache license headers.

## Code Style and Quality Guide -- Common Rules

DevFeed: [Code Style and Quality Guide -- Common Rules](<https://devfeed.tech/articles/code-style-and-quality-guide-common-rules-48562.md>)

Original publisher: [Read original article](<https://flink.apache.org/how-to-contribute/code-style-and-quality-common/>)

Published: 2026-09-18T15:54:07.612713Z

Content type: tutorial

Language: en

Sources: [Apache Flink](<https://devfeed.tech/sources/apache-flink-stateful-computations-over-data-streams-on-apache-flink.md>)

Topics: [code style](<https://devfeed.tech/topics/code-style.md>), [Java](<https://devfeed.tech/topics/java.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [code-style](<https://devfeed.tech/tags/code-style.md>), [guide](<https://devfeed.tech/tags/guide.md>), [java](<https://devfeed.tech/tags/java.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [quality](<https://devfeed.tech/tags/quality.md>), [scala](<https://devfeed.tech/tags/scala.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

A common code style and quality guide for Apache Flink contributors, covering pull requests, IDE tooling, compiler warnings, comments, code readability, nesting, design, and immutability across Java and Scala code.

### Source excerpt

Code Style and Quality Guide -- Common Rules # Preamble # Pull Requests & Changes # Common Coding Guide # Java Language Guide # Scala Language Guide # Components Guide # Formatting Guide # 1. Copyright # Each file must include the Apache license information as a header. /* * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding copyright ownership.

## Code Style and Quality Guide -- Components Guide

DevFeed: [Code Style and Quality Guide -- Components Guide](<https://devfeed.tech/articles/code-style-and-quality-guide-components-guide-48563.md>)

Original publisher: [Read original article](<https://flink.apache.org/how-to-contribute/code-style-and-quality-components/>)

Published: 2026-09-18T15:54:07.612713Z

Content type: tutorial

Language: en

Sources: [Apache Flink](<https://devfeed.tech/sources/apache-flink-stateful-computations-over-data-streams-on-apache-flink.md>)

Topics: [Apache Flink](<https://devfeed.tech/topics/apache-flink.md>), [stream-processing](<https://devfeed.tech/topics/stream-processing.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [YAML](<https://devfeed.tech/topics/yaml.md>), [Java](<https://devfeed.tech/topics/java.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [code-style](<https://devfeed.tech/tags/code-style.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [guide](<https://devfeed.tech/tags/guide.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [quality](<https://devfeed.tech/tags/quality.md>), [yaml](<https://devfeed.tech/tags/yaml.md>)

### AI overview

A guide to code style and quality practices for Apache Flink components. It covers pull requests, Java and Scala conventions, configuration placement and naming, connector design, concurrency and checkpointing considerations, and standards for useful examples.

### Source excerpt

Code Style and Quality Guide -- Components Guide # Preamble # Pull Requests & Changes # Common Coding Guide # Java Language Guide # Scala Language Guide # Components Guide # Formatting Guide # Component Specific Guidelines # Additional guidelines about changes in specific components. Configuration Changes # Where should the config option go? 'flink-conf.yaml': All configuration that pertains to execution behavior that one may want to standardize across jobs.

## sbt 2.1.0 Beta: Rebuilding the sbt Plugin Ecosystem

DevFeed: [sbt 2.1.0 Beta: Rebuilding the sbt Plugin Ecosystem](<https://devfeed.tech/articles/reforesting-the-sbt-plugin-ecosystem-and-sbt-2-1-0-beta-55203.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/09/16/sbt-plugin-updates.html>)

Published: 2026-09-15T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [beta](<https://devfeed.tech/tags/beta.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [github](<https://devfeed.tech/tags/github.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [migration](<https://devfeed.tech/tags/migration.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [release](<https://devfeed.tech/tags/release.md>), [scala](<https://devfeed.tech/tags/scala.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

The Scala Center describes work to support the sbt 2.x plugin ecosystem, including migration tooling, ABI stabilization, compatibility support, and plugin updates. As of September 2026, Scaladex lists 172 plugins available for sbt 2.x.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: sbt 2 Stable Release and Maintenance. The work is coordinated by the Scala Center. Plugin as an ecosystem Out of the box, sbt handles basic functionality like building and testing Scala code. Once you get used to the basics, the build can be extended further by using community plugins. Plugins range from simple utilities to support for new programming languages. One aspect of a plugin project is that it can be created and developed without waiting for a release of sbt, so it's a great way to try new ideas or collaborate across the community. If you want to discover plugins two sources are: Community Plugins page Scaladex Preparing for reforestation Since the ecosystem is an essential element of the user experience, the health of the plugin ecosystem is always our concern. This is especially so when we release a new major version, which burns the old forest. All plugins need to be cross built, and re-published, like new saplings springing from the ash. There are several strategies we adopted to aid the reforestation. Over the years, we have centralized major plugins to GitHub sbt organization. This lets us add new maintainers to the plugin who can review the PRs. Created the sbt 2.x plugin migration wiki page to coordinate the migration effort. We locked down the ABI for 2.x with 2.0.0-RC1, which was released in August 2025. This gave a head start for the plugin authors to cross publish before sbt 2.0 came out. In March 2026, Anatolii Kmetiuk (Scala Center) created sbt2-compat plugin, which adds a compatibility layer so that the same plugin can target both sbt 1 and sbt 2. Beyond tooling, we've actively sent pull requests to migrate the plugins. I'm happy to report that as of this writing (September 2026), Scaladex lists 172 plugins available for sbt 2.x. Many thanks for the community effort by volunteers like Kenji Yoshida and many others. In this post, I'd like to highlight some of the mo

## Co-Create: Building GitLab with our users

DevFeed: [Co-Create: Building GitLab with our users](<https://devfeed.tech/articles/co-create-building-gitlab-with-our-users-86.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/co-create-h1-2026/>)

Author: Isa Huerga

Published: 2026-09-10T00:00:00Z

Content type: article

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Application Security](<https://devfeed.tech/topics/application-security.md>), [Cloud APIs](<https://devfeed.tech/topics/cloud-apis.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [co-created](<https://devfeed.tech/tags/co-created.md>), [community](<https://devfeed.tech/tags/community.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [duo](<https://devfeed.tech/tags/duo.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [scala](<https://devfeed.tech/tags/scala.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

GitLab users collaborated through the Co-Create program on product improvements delivered in the first half of 2026, including API extensions, CI/CD capabilities, Scala support for AI-powered code understanding, security controls, and integration flexibility.

### Source excerpt

GitLab users bring firsthand experience of the workflows they want to improve. Through our Co-Create program, they collaborate directly with us to design, build, and deliver product improvements that benefit more teams. In the first half of 2026, our users helped us extend APIs, add CI/CD capabilities, expand language support for AI-powered code understanding, strengthen security controls, increase the flexibility of integrations, and make GitLab easier to use and understand. Co-Create gives customers a direct path from a real-world challenge to a product improvement. Customers collaborate with us on the problem and solution, and help deliver the change. Unlike a feedback-only model, this puts real workflow context into the product development process. It creates a shorter path from need to value while helping us validate improvements in real conditions and extend their benefits to more GitLab users. "Over ten years ago, we set out to build code.siemens.com, our internal coding platform based on GitLab, which today serves close to 100,000 people. We've run and scaled the platform with a tiny team, guided by a 'for developers, from developers' philosophy. We co-created hundreds of features such as x509/gpg signed commits, protected container/packages, and project and social features such as follow users, allowing us to strengthen the security and collaboration culture at the scale of Siemens." -- Roger Meier, Distinguished Engineer, Siemens From a specific need to a shared improvement Some of the best product improvements start with a specific, real-world need. GitLab contributors helped us address the following needs: Making Scala codebases understandable to Orbit and GitLab Duo Giving security administrators a way to enforce Secret Push Protection across an entire instance Letting high-throughput teams configure merge train pipeline limits Showing the platforms supported by multi-architecture images Providing screen reader users with more context on documentation pa

## Scala 3.9 LTS released!

DevFeed: [Scala 3.9 LTS released!](<https://devfeed.tech/articles/scala-3-9-lts-released-43575.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.9/>)

Published: 2026-09-02T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [version](<https://devfeed.tech/topics/version.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>), [maintenance](<https://devfeed.tech/topics/maintenance.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [compiler](<https://devfeed.tech/tags/compiler.md>), [lts](<https://devfeed.tech/tags/lts.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>)

### AI overview

Scala 3.9.0 opens a new Long Term Support line, succeeding Scala 3.3 LTS as the recommended baseline for library authors and conservative production users. The announcement explains the LTS and Scala Next release models, compatibility considerations, backports, and the continued maintenance of Scala 3.3 LTS.

### Source excerpt

Scala 3.9 LTS released! We are happy to announce Scala 3.9.0, opening the new Long Term Support line for Scala 3. It succeeds Scala 3.3 LTS as the recommended baseline for library authors and conservative production users, while keeping the Scala Next line available for teams that want the latest language work as soon as it is released. What does LTS mean? Scala 3 follows the Scala LTS and Scala Next model. Scala Next receives regular minor releases with new language features, tooling work, and ecosystem changes. Scala LTS receives patch releases focused on bug fixes, diagnostics, tooling improvements, and carefully selected quality-of-life changes that are also subject to the compatibility guarantees of the LTS line. Libraries published with Scala 3.9 LTS can be consumed by later 3.9 patch releases and by Scala Next. The 3.9 line is expected to receive patches and backports for an extended period. Library maintainers: artifacts built with Scala 3.9 cannot be consumed by Scala 3.3 projects, so treat the move from Scala 3.3 LTS to Scala 3.9 LTS as a minor-version publishing decision for your own libraries. Looking back at Scala 3.3 LTS Scala 3.3.0 was released in May 2023 and became the first Scala 3 LTS. It carried the ecosystem through more than three years of Scala 3 development while Scala Next delivered new syntax, new standard-library work, new tooling integration, and deeper compatibility testing. The 3.3 LTS line was not a frozen branch. As I write this, 1,420 of 2,380 pull requests merged into the main Scala 3 compiler branch since 3.4.0 were also backported to Scala 3.3 LTS. That's almost 43% of all changes! That work kept 3.3 useful as a publishing target while still protecting the compatibility expectations that made it attractive in the first place. The result of this decision is visible in the ecosystem - roughly 56% of Scala 3 libraries are currently published using Scala 3.3 LTS. What's more, the next patch release - Scala 3.3.9 - is planned within th

## Creator of Scala: Comparing Languages And How AI Will Impact Them | Martin Odersky

DevFeed: [Creator of Scala: Comparing Languages And How AI Will Impact Them | Martin Odersky](<https://devfeed.tech/articles/creator-of-scala-comparing-languages-and-how-ai-will-impact-them-martin-odersky-18089.md>)

Original publisher: [Read original article](<https://www.developing.dev/p/creator-of-scala-comparing-languages>)

Author: Ryan Peterman

Published: 2026-08-31T13:05:35Z

Content type: opinion

Language: en

Sources: [The Developing Dev](<https://devfeed.tech/sources/the-developing-dev.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Programming language](<https://devfeed.tech/topics/programming-language.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [functional-programming](<https://devfeed.tech/tags/functional-programming.md>), [languages](<https://devfeed.tech/tags/languages.md>), [llms](<https://devfeed.tech/tags/llms.md>), [scala](<https://devfeed.tech/tags/scala.md>)

### AI overview

An interview with Martin Odersky, creator of Scala, compares Rust, Zig, Python, and Scala and discusses how AI may affect programming-language ecosystems. Odersky also explains functional programming as a style based on values and functions, with minimal mutable state and side effects.

### Source excerpt

There are so many choices every programming language creator makes while navigating engineering tradeoffs in building one.

## AWS Glue 6.0 now available with 30% lower price and full Apache Iceberg v3 support

DevFeed: [AWS Glue 6.0 now available with 30% lower price and full Apache Iceberg v3 support](<https://devfeed.tech/articles/aws-glue-6-0-now-available-with-30-lower-price-and-full-apache-iceberg-v3-support-4608.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/aws/aws-glue-6-0-now-available-with-30-lower-price-and-full-apache-iceberg-v3-support/>)

Author: Channy Yun (윤석찬)

Published: 2026-08-21T18:53:26Z

Content type: release

Language: en

Sources: [AWS News Blog](<https://devfeed.tech/sources/aws-news-blog.md>)

Topics: [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Apache Spark](<https://devfeed.tech/topics/spark.md>), [Python](<https://devfeed.tech/topics/python.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [Geographic Information System](<https://devfeed.tech/topics/gis.md>), [Internet of things](<https://devfeed.tech/topics/iot.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [launch](<https://devfeed.tech/tags/launch.md>), [news](<https://devfeed.tech/tags/news.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [python-3-13](<https://devfeed.tech/tags/python-3-13.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [release](<https://devfeed.tech/tags/release.md>), [scala](<https://devfeed.tech/tags/scala.md>), [spark](<https://devfeed.tech/tags/spark.md>), [streaming](<https://devfeed.tech/tags/streaming.md>)

### AI overview

AWS Glue 6.0 is generally available with 30% lower pricing, a modernized Spark 4.1 runtime, Python 3.13 and Scala 2.13 support, and full Apache Iceberg v3 support. The release adds improved handling of semi-structured data, declarative ETL pipelines, faster PySpark execution, and real-time streaming with single-digit millisecond latency.

### Source excerpt

AWS Glue 6.0 is built on a fully modernized runtime, Apache Spark 4.1, Python 3.13, and Scala 2.13, delivering 30% lower pricing than previous AWS Glue versions.

## Fixing a remote execution vulnerability in sbt

DevFeed: [Fixing a remote execution vulnerability in sbt](<https://devfeed.tech/articles/fixing-a-remote-execution-vulnerability-in-sbt-43569.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/08/10/sbt-remote-tcp-advisory.html>)

Published: 2026-08-09T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Security](<https://devfeed.tech/topics/security.md>), [bug](<https://devfeed.tech/topics/bug.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>), [Scala](<https://devfeed.tech/topics/scala.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [bug](<https://devfeed.tech/tags/bug.md>), [execution](<https://devfeed.tech/tags/execution.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [rpc](<https://devfeed.tech/tags/rpc.md>), [scala](<https://devfeed.tech/tags/scala.md>), [security](<https://devfeed.tech/tags/security.md>), [server](<https://devfeed.tech/tags/server.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The post describes a vulnerability in sbt that enables remote code execution when TCP server communication is enabled. It explains the access-control issue, affected sbt versions, and recommends removing the TCP setting or upgrading to sbt 1.12.15 or 2.0.6 and later.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: sbt 2 Stable Release and Maintenance. The work is coordinated by the Scala Center. TL;DR Only builds that explicitly set serverConnectionType are affected. You can remove the setting from your build, or upgrade to sbt 1.12.15 / sbt 2.0.6 or later by putting the following in project/build.properties: sbt.version=1.12.15 Note that installing a new sbt command does not affect the sbt version used by each individual build. The vulnerability As part of our ongoing work on the sbt 2 release, we've been reviewing bug reports and pull requests. Recently we received a security report GHSA-m2pw-22cj-jq4v from Arpit Jain that an attacker is able to execute arbitrary code remotely via the sbt server when the serverConnectionType is set to ConnectionType.Tcp. By default, sbt uses UNIX domain sockets on Linux and macOS, and named pipes on Windows, but this can be changed to TCP using the following setting: Global / serverConnectionType := ConnectionType.Tcp This will use a TCP port that can be calculated deterministically from the working directory, e.g. 5001, for the sbt server communication. An attacker can then craft a JSON-RPC message, masquerading as an sbt client. In a normal sequence, using TCP would go through a token authentication so only the local user can use the sbt server; however, there were several endpoints that were not protected by the access control, which allowed improper escalation. This is a form of CWE-425: Direct Request. The vulnerability has existed since sbt 1.1.0 and affects both the sbt 1.x and sbt 2.x series. The fix The primary fix was to make sure all LSP-like endpoints are protected behind authorization when using TCP. The fix is available in sbt 1.12.15 and 2.0.6. The remediation was implemented by Eugene and Anatolii using GitHub's private fork feature. The full advisory is available as GHSA-m2pw-22cj-jq4v. We recommend removing the serverConnectionType setting from y

## Using generative AI and human review to improve Scala API documentation

DevFeed: [Using generative AI and human review to improve Scala API documentation](<https://devfeed.tech/articles/coaxing-quality-output-from-generative-ai-43568.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/07/06/quality-from-genai.html>)

Author: About the author

Published: 2026-07-05T22:00:00Z

Content type: opinion

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Generative AI](<https://devfeed.tech/topics/generative-ai.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [iteration](<https://devfeed.tech/topics/iteration.md>), [Code](<https://devfeed.tech/topics/code.md>), [Prompt Engineering](<https://devfeed.tech/topics/prompt-engineering.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [code](<https://devfeed.tech/tags/code.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [human-review](<https://devfeed.tech/tags/human-review.md>), [iteration](<https://devfeed.tech/tags/iteration.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-as-a-judge](<https://devfeed.tech/tags/llm-as-a-judge.md>), [prompting](<https://devfeed.tech/tags/prompting.md>), [scala](<https://devfeed.tech/tags/scala.md>)

### AI overview

This report describes an approach to improving Scala standard-library API documentation with generative AI. It addresses output quality and human review capacity through iteration, LLM-based judging, deterministic code, orchestration harnesses, and scripts.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment. The work is coordinated by the Scala Center. The work described in this post was done by Bill Venners and Chua Chee Seng of Artima. One of the tasks funded under the STA project is to improve Scala's API documentation. Such a task looks like a natural fit for generative AI, because the work is repetitive and the code to document is nearby in the source. But handing the work to an AI raises two challenges. The first is quality: an AI model will readily produce documentation, but it may be mediocre or wrong. The second challenge is managing human review time: someone will have to check all that output. This post is a report on how we approached these problems when using AI to improve API documention of Scala's standard library: what we tried and how it worked out. Quality writing requires iteration. You write a draft, review it (or have someone else review it), then improve it. You repeat this process until you're happy with the quality. One way to achieve quality with generative AI, therefore, is to delegate the writing part to the AI model and review it yourself, but this doesn't scale. An AI model can generate content at a much greater rate than you can review it. Because of this, we decided to use the "LLM as a judge" technique in an attempt to raise the quality of the output as high as possible prior to asking humans to review it. Another way we tried to raise the quality of the AI output prior to human review is to use harnesses to orchestrate the AI work. First, we wrote a todo-writer application that reformatted doc comments for consistency and inserted text markers in the standard library source to precisely indicate where we wanted an AI to insert focused documentation. Then we created a script to drive the filling-in process. Finally, we attempted to keep the review tasks for humans to a reasonable size. The rest of this post describes five techniques that formed our overall approach. Tech

## sbt 2 is now available!

DevFeed: [sbt 2 is now available!](<https://devfeed.tech/articles/sbt-2-is-now-available-43567.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/06/29/sbt2.html>)

Published: 2026-06-28T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [migration](<https://devfeed.tech/topics/migration.md>), [test](<https://devfeed.tech/topics/test.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [client](<https://devfeed.tech/topics/client.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2025](<https://devfeed.tech/tags/2025.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [development](<https://devfeed.tech/tags/development.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [migration](<https://devfeed.tech/tags/migration.md>), [release](<https://devfeed.tech/tags/release.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

The Scala community has released sbt 2 after five years of development. The new build tool version uses Scala 3.8.4 and requires JDK 17, adds a native-image client, incremental testing, Bazel-compatible local and remote caching, project matrices, client-side commands, and updated documentation.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: sbt 2 Stable Release and Maintenance. The work is coordinated by the Scala Center. After five years of development, sbt 2 is out. Since the experimental sudori part 1 blog post in 2021, more than 82 people have contributed to the project. We would like to thank community and corporate contributors, Scala Center, and Sovereign Tech Fund for their support. What's new in sbt 2? sbt 2 is a new version of sbt. If you're familiar with sbt 1.x, hopefully the jump is not too far, but we have pushed sbt to the modern standard. The headline features are: sbt 2.x uses Scala 3.8.4 for build definitions and plugins (Both sbt 1.x and 2.x are capable of building Scala 2.x and 3.x), which requires minimum JDK 17 Uses sbtn (native-image client) for faster startup. test changed to incremental test. Local/remote cache system that is Bazel-compatible. compile and test are both rewritten to be cachable tasks. Project matrix, which was available via plugin in sbt 1.x, is in-sourced in sbt 2.x. Client-side run. Client-side console. New documentation. For more details, please check out sbt 2.0 changes summary and the Scala Days 2025 talk sbt 2.0: go big from 2025. How do I get started with sbt 2? The sbt version used for your build is upgraded by putting the following in project/build.properties: sbt.version=2.0.1 This mechanism allows that sbt 2.0.1 is used only for the builds that you want. Download the official sbt runner from SDKMAN, or download from https://github.com/sbt/sbt/releases/tag/v2.0.1 to upgrade the sbt shell script, sbtn, and the launcher. Repopulating the plugin ecosystem Major plugins are already available on sbt 2.x. Under the sbt 2 workstream, Anatolii from Scala Center has created the sbt2-compat plugin, which bridges the source-level differences between sbt 1.x and 2.x. This allows cross-building of a plugin, aiding the migration process. Also under the STA workstream, Rikito Taniguchi from

## Scala 3.3.8 LTS is now available!

DevFeed: [Scala 3.3.8 LTS is now available!](<https://devfeed.tech/articles/scala-3-3-8-lts-is-now-available-43571.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.3.8/>)

Published: 2026-06-09T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [releases](<https://devfeed.tech/topics/releases.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>)

Tags: [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [lts](<https://devfeed.tech/tags/lts.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Scala 3.3.8 LTS is a patch release that backports bug fixes and improvements from the Scala Next series. The release adds JDK 26 support, improves coverage support, introduces the @uncheckedOverride annotation, updates REPL Ctrl-C handling, and includes linting, presentation compiler, and lazy val implementation improvements. The changes were tested for binary and source compatibility across more than 1,500 projects.

### Source excerpt

Scala 3.3.8 LTS is now available! This patch release backports most of the bugfixes and some of the improvements introduced in the Scala Next series to the Scala 3.8.4 release. All of the backported changes were proven to not break either binary or source compatibility, by testing over 1500 projects in the Scala 3 Open Community Build. Notable changes Support for JDK 26 #24430 Multiple coverage improvement to make it on par with Scala 2 support including // $COVERAGE-OFF$ and // $COVERAGE-ON$ markers New @uncheckedOverride annotation for definitions that may override. #24545 Trap Ctrl-C in the REPL: if no command is running clear the prompt, if some command is running ask for confirmation before exiting. #24127 Numerous linting and presentation compiler improvements and fixes. New -Yfuture-lazy-vals options that allows to compile with new lazy val implementation compatible with all JDK 9+ #637 For a full list of changes and contributor credits, please refer to the release notes. Scala LTS Release Notice The next planned LTS 3.3 release will include updates introduced until last Scala 3.9.x before 3.10. Scala 3.9.x will also be a new LTS release. We'll continue to backport bug fixes and improvements from the Scala Next series to the 3.3.x series for the next year after the release 3.9.0.

## Improving Scala's docs and website

DevFeed: [Improving Scala's docs and website](<https://devfeed.tech/articles/improving-scala-s-docs-and-website-43566.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/06/09/sovereign-doc-project.html>)

Published: 2026-06-08T22:00:00Z

Content type: article

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [Scala](<https://devfeed.tech/topics/scala.md>), [Website](<https://devfeed.tech/topics/website.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [API](<https://devfeed.tech/topics/api.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [api-documentation](<https://devfeed.tech/tags/api-documentation.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [scala](<https://devfeed.tech/tags/scala.md>), [standard-library](<https://devfeed.tech/tags/standard-library.md>), [tools](<https://devfeed.tech/tags/tools.md>), [website](<https://devfeed.tech/tags/website.md>)

### AI overview

The Scala Center is coordinating a Sovereign Tech Fund-supported project to improve outdated, incomplete, poor-quality, or missing documentation for Scala. The work focuses primarily on Scala 3 Scaladoc and the Scala website, with some important Scala 2 improvements also included.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment. The work is coordinated by the Scala Center. We have collected possible documentation tasks from three sources: Tasks in the original proposal we made to the Sovereign Tech Agency Tasks collected in internal discussions since then Tasks from community suggestions on this Contributors forum thread This blog post summarizes what we have collected, identifies tasks that we have chosen to tackle, and describes work that is already underway. Project goals We aim to identify documentation, both API documentation (Scaladoc) and the docs on the Scala website, that is: Outdated, or Incomplete or poor quality, or Missing entirely And we want to address those shortcomings, to aid both: New users coming to Scala Existing users of Scala Project scope A major focus will be on the Scaladoc for the standard library. We will update and expand it. Along the way, if we find that limitations of the Scala 3 Scaladoc tool are causing quality issues in the doc, improving the tool is in scope. The project scope also includes the documentation on our website such as the Scala language specification, getting-started docs, language tour, features guides, Scala Toolkit documentation, and so forth. Scala 3 is the primary focus, but we can also make especially important improvements on the Scala 2 side. What's not in scope? Third-party tools, libraries, and publications are not in scope. That said, it is sometimes appropriate for our website and docs to describe and link to third-party documentation and resources. Examples of such documentation that is in scope for improvement include: the Scala community page, the Scala IDEs page, the Scala Toolkit documentation (because the Toolkit includes third-party libraries), and the Scala books page. What did we initially propose? In the Center's original proposal we identified the following areas or "work packages". Any work we do must fit in at least one of these areas, and we must do

## Scala 3.8.4 is now available!

DevFeed: [Scala 3.8.4 is now available!](<https://devfeed.tech/articles/scala-3-8-4-is-now-available-43574.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/news/3.8.4/>)

Published: 2026-06-04T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Security](<https://devfeed.tech/topics/security.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Parsing](<https://devfeed.tech/topics/parsing.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [parsing](<https://devfeed.tech/tags/parsing.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Scala 3.8.4 is a release focused on security audit fixes, including hardened TASTy parsing, a stored XSS fix in Scaladoc, improved process-parser error handling, and a JAR-walking fix. It also expands compiler-setting help and upgrades the bundled Scala CLI to 1.14.0.

### Source excerpt

Release highlights Security audit fixes Scala 3.8.4 includes improvements and fixes for issues discovered during the Scala codebase security audit carried out in collaboration with the Open Source Technology Improvement Fund and Quarkslab. Notable fixes in this release include: Hardened TASTy parsing to prevent infinite loops on maliciously crafted files (#25676) Fixed a stored XSS vulnerability in Scaladoc (#25681) Improved error handling in scala.sys.process.Parser.tokenize (#25675) Fixed TastyPrinter's JAR-walking logic to include subdirectories (#25678) :help syntax for all compiler settings (#26052) You can now append :help to any compiler setting to see its documentation -- not just a fixed subset as before. This works wherever you pass compiler options, making it easier to discover available flags without leaving your workflow. With the Scala runner, add :help to a flag on the command line when running a script or project: > scala test.scala -Xkind-projector:help -Xkind-projector Allow `*` as type lambda placeholder to be compatible with kind projector. When invoked as -Xkind-projector:underscores will repurpose `_` to be a type parameter placeholder, this will disable usage of underscore as a wildcard. Default disable Choices: disable, , underscores In the REPL, pass the same flag through :settings: scala> :settings -Wunused:help -Wunused Enable or disable specific `unused` warnings Choices: - nowarn, - all, - imports : Warn if an import selector is not referenced., - privates : Warn if a private member is unused, - locals : Warn if a local definition is unused, - explicits : Warn if an explicit parameter is unused, - implicits : Warn if an implicit parameter is unused, - params : Enable -Wunused:explicits,implicits, - patvars : Warn if a variable bound in a pattern is unused, - linted : Enable -Wunused:imports,privates,locals,implicits Upgrade to Scala CLI 1.14.0 The bundled Scala CLI has been upgraded from 1.11.x through 1.12.5, 1.13.0, to 1.14.0. Notable a

## Scala Codebase Security Audit Complete

DevFeed: [Scala Codebase Security Audit Complete](<https://devfeed.tech/articles/scala-codebase-security-audit-complete-43565.md>)

Original publisher: [Read original article](<https://www.scala-lang.org/blog/2026/06/01/first-part-security-audit.html>)

Published: 2026-05-31T22:00:00Z

Content type: release

Language: en

Sources: [The Scala Programming Language](<https://devfeed.tech/sources/the-scala-programming-language.md>)

Topics: [Scala](<https://devfeed.tech/topics/scala.md>), [Security](<https://devfeed.tech/topics/security.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [audit](<https://devfeed.tech/topics/audit.md>), [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [library](<https://devfeed.tech/tags/library.md>), [lts](<https://devfeed.tech/tags/lts.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [scala](<https://devfeed.tech/tags/scala.md>), [scala-3](<https://devfeed.tech/tags/scala-3.md>), [security](<https://devfeed.tech/tags/security.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

The Scala Center reports the first results of a security audit covering the Scala 3 compiler and standard library. The audit found five medium-severity issues, one low-severity issue, and two informational findings; all were addressed in the Scala 3.3 LTS and 3.8 branches. Most findings affected scenarios where the compiler processes untrusted input as a service.

### Source excerpt

This post covers work done under the Sovereign Tech Fund investment umbrella: Maintenance of the Standard Library/Core Library Modules and APIs. The work is coordinated by the Scala Center. The Scala Center is proud to share the first results of the security audit of Scala carried out in collaboration with Open Source Technology Improvement Fund and the security researchers at Quarkslab. The audit was divided into two major parts: an assessment of the Scala 3 compiler and Scala standard library codebases, and a separate review of Scala's supply-chain security. This first publication focuses on the compiler and standard library audit. Since many reported security issues in Scala ecosystems involve the standard library, the audit aimed to strengthen the security and robustness of Scala's core components through a combination of manual code review and automated tooling, including fuzzing and Java deserialization gadget finders. Results Read the full report here. No critical or major security issues were identified during the audit. However, the review uncovered 5 medium severity issues, 1 low severity issue, and 2 informational findings, all of which have since been addressed by the Scala maintainers. All of these issues are fixed as of the date of this blog post, both for the 3.3 LTS branch and for the main 3.8 branch. Importantly, these issues do not affect typical users compiling Scala code locally or through continuous integration pipelines. Most findings were only relevant in scenarios where the Scala compiler is exposed as a service and processes untrusted input, where they could potentially lead to denial-of-service-type behavior. Fixes All reported issues were present in 3.8-RC1 and fixed before the publication of this blog post, both in the Scala 3.3 LTS branch and in the main Scala 3.8 development branch. One example was a medium severity issue in the compiler's handling of TASTy files. The compiler did not validate that certain offsets were nonnegative, whic

[Next page](<https://devfeed.tech/topics/scala.md?cursor=WyIyMDI2LTA1LTMxVDIyOjAwOjAwKzAwOjAwIiwgImE5MzEzYTE0LTZkNGMtNDlhNS1hMjZmLWQyZWFlNjkwNTVlZSJd>)