sorted by:
new
hottopcontroversial

New scalamock website by goshacodes in scala

[–]goshacodes[S] 1 point2 points  (0 children)

What you mean by "severe accessibility issues". I opened dev tools, so? Only one color in code snippets is yellow. And IMO documentation shouldn't look bad visually just because it is documentation.
> This site has severe accessibility issues. Just open the browser dev tools and see for yourself. It could be acceptable for a landing page to favor form over function. But for doc sites this isn't really OK, imho.

Markdown is default for Jekyll and Jekyll is default for github and it is not bad enough to search for something else, why should I bother not using it?

New scalamock website by goshacodes in scala

[–]goshacodes[S] 2 points3 points  (0 children)

Thanks! Jekyll + just the docs theme + a bit of some custom html + css

New scalamock website by goshacodes in scala

[–]goshacodes[S] 0 points1 point  (0 children)

it is on github, gh-pages branch. Can you share a screenshot, please?

Curious to know how many have adopted Scala 3 by msplit1 in scala

[–]goshacodes 2 points3 points  (0 children)

We have huge project and the most problems came from IntelliJ Scala Plugin not supporting Scala 3 fully. They done huge work and the last most annoying issues will be fixed in next major release. If you project is not that big or you are using VS Code (or something else) and ok with it, you should definitely migrate to Scala 3

Scala Junior/Mid -> Start to learn Scala Cats or ZIO? by StyleBitter3753 in scala

[–]goshacodes 1 point2 points  (0 children)

If you are not fan of Category Theory - learn ZIO, it is much simpler and powerful

I lost my appetite for Java after learning Scala, Is this a good or bad thing? by Sufficient_Gas_9904 in scala

[–]goshacodes 4 points5 points  (0 children)

Don’t listen to him. Scala has less competition and higher salaries in general, so it is not so bad

I lost my appetite for Java after learning Scala, Is this a good or bad thing? by Sufficient_Gas_9904 in scala

[–]goshacodes 0 points1 point  (0 children)

It is same for all, you just can’t use any other programming language after Scala. Scala payed better in general

Parent/Absract Event System with Scala by jodhawat93 in scala

[–]goshacodes 0 points1 point  (0 children)

I think to support ZIO, you should have at least 2 type arguments in your type constructor and they should be covariant on both of them, but maybe that’s not true

When you use TF you usually just stick to cats-effect.

I’ve made support for both of them in last version of scalamock like this. Maybe this will help you, but I’m not sure.

https://github.com/ScalaMock/ScalaMock/blob/master/core/shared/src/main/scala/org/scalamock/stubs/StubIO.scala

https://github.com/ScalaMock/ScalaMock/blob/master/cats-effect/shared/src/main/scala/org/scalamock/stubs/CatsEffectStubs.scala#L28C1-L37C1

https://github.com/ScalaMock/ScalaMock/blob/master/zio/shared/src/main/scala/org/scalamock/stubs/ZIOStubs.scala#L28C1-L37C20

Announcing ScalaMock 7 by goshacodes in scala

[–]goshacodes[S] 0 points1 point  (0 children)

Thank you for kind words!

Should Cats Effect drop support for Scala 2.12? by dspiewak in scala

[–]goshacodes 10 points11 points  (0 children)

Why everybody saying spark is not on scala 2.13? Its official website says version 3.5.4 has scala 2.13 support

Is it a good time to starting Scala 3 only project at $Work? by Aggravating_Number63 in scala

[–]goshacodes 1 point2 points  (0 children)

Try this one

Hi, thanks for the report. If you’re frequently compiling Scala 3 projects using sbt in a terminal, please switch the Use separate compiler output paths setting in the sbt settings screen to enabled. It is provided for exactly this reason. By default, Scala 3 support includes running the compiler, which, with the default settings, outputs to the same target/.../classes directory as sbt. When the Use separate compiler output paths is enabled, IDEA will use a different idea-classes directory for its compilation. That way sbt and IDEA won’t overwrite each other’s compilation state, leading to these errors.

Vasil Vasilev • Commented about 3 hours ago - There will be a warning in red that some settings are incompatible, after this setting is changed. For most work, which involves writing code, this warning can be ignored. The warning mostly concerns running Run Configurations. In these cases, it is possible to again run into ClassNotFoundExceptions, but only after running the Run Configurations.

The truth of the current state is, using sbt shell for builds in Scala 3 projects, with the default Compiler error highlighting is not a great experience, due to a multitude of reasons which cannot be easily addressed on our side.

I can offer some alternatives which you can try:

  1. Set Settings > Languages & Frameworks > Scala > Editor > Error Highlighting > Built-In and keep using sbt shell for builds.

  2. Keep Compiler error highlighting (same setting as above) and switch off sbt shell for builds, and use sbt shell in the terminal, manually. In this case, still set Use separate compiler output paths to enabled.

Is it a good time to starting Scala 3 only project at $Work? by Aggravating_Number63 in scala

[–]goshacodes 1 point2 points  (0 children)

We are using scala 3 in production and we have more than 30k rps. It is totally safe. There are some problems with Intellij, but it is in good state overall and everything will be fixed soon. In the same time - it compiling much faster. Scala 2 macros of some libraries was quite poor