Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 13 2018 14:13
    User @SethTisue unbanned @viju0731_twitter
  • Nov 13 2018 14:11
    @SethTisue banned @viju0731_twitter
Julien Richard-Foy
@julienrf
Hello Justin! We do plan to update the Coursera courses to Scala 3 as soon as Scala 3.0.0 is released.
So, the Scala 2 versions won’t be available anymore on Coursera.
I might be able to create a private session for you, if needed, though
Justin du Coeur, AKA Mark Waks
@jducoeur
@julienrf Hmm. Okay, useful to know. How are you handling students who have already started the Scala 2 version? I expect that we're going to be starting around Jan 20th, which I suspect is before the Scala 3 release date.
Seth Tisue
@SethTisue
@julienrf is there some difficulty preventing both versions from staying active for a while? it seems desirable to me
Julien Richard-Foy
@julienrf
@jducoeur Most likely, 3.0.0 won’t be released before May. So, until that point the courses will still be based on 2.13.

@SethTisue It is not technically difficult. I thought it would be simpler to have just one place to go to learn Scala and to keep it up to date with current stable version.

But it’s true that there is an important gap between Scala 2 and Scala 3, so maybe we want to keep both versions of the courses in parallel for some time…

Seth Tisue
@SethTisue
@julienrf I wonder if it's worth doing a little survey about. the job market is going to be primarily Scala 2 for a while yet, and many people are taking these courses so they can get jobs
Justin du Coeur, AKA Mark Waks
@jducoeur
Yeah, just so. I expect us (a moderately large Scala shop) to be mostly on Scala 2 until at least the end of 2021 -- converting hundreds of repos, owned by many teams, is not a quick job. So for now, Scala 2 training is more useful. I expect some of our more serious Scala geeks (especially the ones who decide to lead the way into Scala 3) to want the new course sooner, but for most people we need to train, it really should be Scala 2.
Anyway, the key takeaway is that the Scala 2 version should be available at least through the end of April, which is what I needed to know. (And wanted to hear: it means I can okay the licenses.) Thanks!
nafg
@nafg

I thought it would be simpler to have just one place to go to learn Scala and to keep it up to date with current stable version.

@julienrf as long as you put on the scala 2 course in big, clear letters that if you're new to scala on your own then this course is superseded by the newer scala 3 course, it will not cause confusion and will be better to have both up

Justin du Coeur, AKA Mark Waks
@jducoeur
Agreed.
Julien Richard-Foy
@julienrf
I was hoping that people taking the Scala 3 course would then be able to work on Scala 2 projects (there are important changes between both versions, but I believe it’s easy to jump from one version to the other)
nafg
@nafg
yeah but in general, taking stuff on the internet offline can be annoying for people
Am I the only one that misses the old scastie?
Julien Richard-Foy
@julienrf
what do you mean by the old scastie?
nafg
@nafg
An example where they took the old offline to be replaced by the new, which at least I didn't appreciate
Justin du Coeur, AKA Mark Waks
@jducoeur
I won't know for sure until I go through it myself, but I would expect there to be a lot of friction for someone who only learns Scala 3 trying to deal with normal Scala 2. The implicits are all different, the look is very different (because of the shift to focusing on significant space) -- conceptually it's not that different, but look-and-feel is what junior developers notice most, and the look-and-feel is really, really different.
nafg
@nafg
Before the scala center scastie web 2.0+ fancy shmancy webapp with all its functionality, fancy architecture, and slowness and uptime issues, there was the old, simple scastie.org
It was a web 1.0 web page, where you pasted code into a texarea, along with some sbt notations for setting scala version and including libraries, and you pressed submit, and you got back a bookmarkable static page with the results, that you could share and would load instantly
Don't get me wrong, the new scastie has a lot of features that I appreciate. I just wish they also left the old one up too
Seth Tisue
@SethTisue
minutes from the February advisory board minutes are now here: https://scala.epfl.ch/records.html
also the previous two sets of minutes (June, October) had been missing but are also now there
June highlights: Stu finishes his 1-year stint as chair and steps down; Adriaan takes over for a year. SAP leaves the board. VirtusLab's full membership status is confirmed. SCP-024 ("Diversity initiatives") accepted.
October highlights: staffing changes. SCP-025 ("Use of Inclusive Language") accepted. Bloop discussion.
February highlights: Scala 3 progress and status. Bintray shutdown discussion.
nafg
@naftoligug:matrix.org
[m]
Seth Tisue
@SethTisue
@nafg I'd suggest opening a ticket at https://github.com/scalacenter/scaladex/issues
nafg
@naftoligug:matrix.org
[m]
@SethTisue: gladly, but it doesn't seem that other issues in the tracker have fared very well
nafg
@naftoligug:matrix.org
[m]
Could it be because my organization changed? Would that confuse it?
Even so it's way out of date
Seth Tisue
@SethTisue
I see you opened scalacenter/scaladex#657

Could it be because my organization changed? Would that confuse it?

something like that seems plausible. I speculated somewhat similarly on the ticket

it doesn't seem that other issues in the tracker have fared very well

there was a long period where Scaladex was without a maintainer, but then maintenance became more active again

Anthony Holland
@aholland
Where would I report a bug in the ch.epfl.scala sbt-scala3-migrate 0.3.0 migration tool please? It's falling over in two different ways.
Guillaume Martres
@smarter
Sébastien Doeraene
@sjrd
Yes, exactly.
Anthony Holland
@aholland
Thanks both. For the simpler bug I just created a pull request. scalacenter/scala3-migrate#175
e 🍋
@bristlycitrus_twitter
Hello! I’m looking at submitting a proposal for GSOC, specifically for one of the Metals related project ideas. This is my first GSOC, I’m looking at the Google guide for submitting a proposal and it says to check with the org about guidelines or templates. Are there any guidelines or templates you want people to follow?
Seth Tisue
@SethTisue
@bristlycitrus_twitter (perhaps someone else has better information for you, but) have you already seen https://contributors.scala-lang.org/t/google-summer-of-code-time-to-act/4940 ?
It's not wrong to ask in this room, but I'm not sure if the relevant people will see it here
e 🍋
@bristlycitrus_twitter
thank you @SethTisue ! i hadn’t seen that
Andy Nim
@tellnobody1
I'm trying to migrate project with migrate main but getting an error No such entry: plugin.properties. I've checked sbt plugins and there are no custom plugins. What this error could mean? sbt version is 1.5.0-RC2, scala version is 2.13.5.
Seth Tisue
@SethTisue
@tellnobody1 if you don't get help here, you might try opening an issue at https://github.com/scalacenter/scala3-migrate/issues
Seth Tisue
@SethTisue
Scala Center advisory board minutes for March 30: https://scala.epfl.ch/minutes/2021/03/30/march-30-2021.html
welcome new affiliate member SwissBorg!
Sébastien Doeraene
@sjrd
Thank you Seth! And welcome to SwissBorg :)
Ruurtjan
@ruurtjan
Hi there! I'm trying to migrate my codebase to 3.0.0 with https://github.com/scalacenter/scala3-migrate, but it's migrating to 3.0.0-RC3. My guess is that we need another release of the plugin now that 3.0.0 is released?
Meriam Lachkar
@mlachkar
Hello! Scala3-migrate needs in fact a new release that I started. It should be available soon!
Ruurtjan
@ruurtjan
Awesome!