mdoc
Typechecked markdown documentation for Scala (by scalameta)
sbt-native-packager
sbt Native Packager (by sbt)
Our great sponsors
mdoc | sbt-native-packager | |
---|---|---|
4 | 5 | |
386 | 1,581 | |
0.8% | -0.1% | |
8.4 | 6.8 | |
7 days ago | 9 days ago | |
Scala | Scala | |
Apache License 2.0 | BSD 2-clause "Simplified" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mdoc
Posts with mentions or reviews of mdoc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-04-20.
- Optimal decision-making with examples built using scala
-
Friction-less scala - Tell us what is causing friction in your day-to-day life with Scala
Literally what scaladoc is, it comes with sbt. Although, it's better when enhanced with mdoc so that you get the standard microsite template like these. It would be nice to have an sbt serveDocs and if everyone would host their docs for external linking, but javadoc doesn't do that either.
-
A Scala rant
The good news is that scaladoc is produced by default by sbt and published by default. So you can often pull it from the same repository your library jar came from, extract it with zip, and read the docs. But that's also totally unnecessary - javadoc.io allows you to put in your module info and serves the docs for you, so if there's an older version you can access the documentation this way. Rely on the type signatures, since they can't lie, whilst comments (including scaladoc comments) can. Honestly, library authors should be using mdoc and including examples on every public method, and that type of documentation is something you can almost always contribute to a project for a quick pr kudos.
-
The future of Scaladoc
I know it's not new but the "Snippet validation and results (mdoc)" features in mdoc are so cool. Really takes some of the tedium out of working with documentation since you can know that as you evolve your code the compiler will make sure you keep the docs in sync. Whole new level of Readme-Driven Development
sbt-native-packager
Posts with mentions or reviews of sbt-native-packager.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-11.
-
I had a great experience with Scala and hopefully it will get more popular
once you outgrow scala-cli, you should know sbt has a lot of plugins ( some might say it's ecosystem is the only thing keeping it relevant....) like sbt-native-packager which again does the heavy lifting for you
-
Asking for help to improve codepreview
So far, we have been working mainly with projects that use https://github.com/sbt/sbt-native-packager, still, projects building fat jars should also work smoothly.
-
I removed sbt-assembly and sbt-buildinfo from my project.
You should use sbt-jib. (You shouldn't use sbt-native-packager either, it doesn't work well in this regard: [1], [2].)
-
Why Scala is way slower than python ... and than Java too in leetcode?
As others have stated, this is mainly due to the nature of the JVM. You can try using GraalVM however, which basically complies JVM bytecode to native-code avoiding startup time issues, sbt-native-packager lets you do this quite easily.
-
SBT error when running package application: java.lang.RuntimeException: No main class detected.
IMO don't take any of this advice and use https://github.com/sbt/sbt-native-packager
What are some alternatives?
When comparing mdoc and sbt-native-packager you can also consider the following projects:
sbt-unidoc - sbt plugin to create a unified Scaladoc or Javadoc API document across multiple subprojects.
sbt-assembly - Deploy über-JARs. Restart processes. (port of codahale/assembly-sbt)
sbt-mima-plugin - A tool for catching binary incompatibility in Scala
sbt-pack - A sbt plugin for creating distributable Scala packages.
sbt-revolver - An SBT plugin for dangerously fast development turnaround in Scala
sbt-native-image - Plugin to generate native-image binaries with sbt
coursier - Pure Scala Artifact Fetching
xsbt-web-plugin - Servlet support for sbt
sbt-updates - sbt plugin that can check Maven and Ivy repositories for dependency updates
sbt-release - A release plugin for sbt
mdoc vs sbt-unidoc
sbt-native-packager vs sbt-assembly
mdoc vs sbt-mima-plugin
sbt-native-packager vs sbt-pack
mdoc vs sbt-revolver
sbt-native-packager vs sbt-native-image
mdoc vs sbt-pack
sbt-native-packager vs coursier
mdoc vs coursier
sbt-native-packager vs xsbt-web-plugin
mdoc vs sbt-updates
sbt-native-packager vs sbt-release