Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
RFC: Discontinuing Scala.js 0.6.x?
See original GitHub issueWhat do people think about us discontinuing support for Scala.js 0.6.x? Concretely, I mean freezing the 0.6.x branch (not accepting any more PR targeting it), and declare 0.6.33 as the last 0.6.x release.
This is earlier than I would have dreamed of suggesting this, but the rate of adoption of Scala.js 1.x in the ecosystem of libraries has been extremely fast. Basically all the core libraries support Scala.js 1.x at this point. The last major milestone on that road was scalajs-react, whose version 1.7.0 was released a few days ago with Scala.js 1.x support. Laminar and Slinky have already published for 1.x; Bindings.scala has a Milestone published with 1.x support.
The above means that no one should really be blocked from upgrading to Scala.js 1.x. Therefore, any benefit to be gained from upgrading to a hypothetical 0.6.34 can also be obtained by upgrading to 1.x instead.
In addition, 0.6.x releases have already been further and further apart from each other, with less and less changes in each one, only affecting more and more obscure corner cases. The last interesting bit was js.import in 0.6.29, 8 months ago.
The benefits of discontinuing 0.6.x, for us, would be:
- Don’t wait so long for PR validation (the 1.x CI is much faster than the 0.6.x CI)
- Don’t spend time every few weeks to perform forward merges
- Get rid of the implicit constraint not to have the JDK implem diverge too much between 0.6.x and 1.x, which would make it more plausible to apply scalafmt at some point, as well as making it easier to progress towards a Scala-lib-free
javalib
The benefits for the community would be that we send a strong signal that it’s OK to drop support for 0.6.x in the libraries, freeing up all the libraries from the constraints of cross-building, both in terms of build complexity and in CI time.
What do people think?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:37
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I believe we’ve waited long enough for this, and the response has been massively positive, so let us make this official: Scala.js 0.6.x is now EOL.
Strongly agree.
In our case only two libs are still not there on 1.x but they look very close to doing that: enumeratum and play-json