ここでScalaJSの名前を聞くとは・・・ｗ #orestudy

Doing some ScalaJS UI work. Felt pretty cool searching the web for docs from several different angles

Cats-Actors 2.1.0 is out 🎉 — now with Scala Native Scala.js support! Ring benchmark across JVM/Native, live browser demo, and new samples to get you started. Blog post 👉 cloudmark.github.io/Cats-Act… Thanks to rlavolee and Voltir! #Scala #ScalaNative #ScalaJS #CatsEffect

These remind me of the early scalajs scastie days

Project 4: Chattie This is a full-stack Scala application, and you'll learn - using databases - exposing web servers - frontend with ScalaJS - sharing domain model - websockets

Clojure is done. Rich is 65 and retired. He is no longer hungry, he’s already declared victory, he’s exited the game. David is talking about how ClojureScript is jquery. If he had said that was his mission in 2011 I would be a ScalaJS programmer today. Alex is making weasel worded cope statements on HN that Clojure is growing a little bit and survey numbers are down because it runs at different times each year and with varying marketing. “Groups never admit defeat, you get a schism instead.” Electric is Clojure’s last stand. If we fail to create a breakout technology with clear and compelling differentiation, it’s over. And if we succeed, we will be dragging Rich kicking and screaming. Did you know he has rejected Electric talks three years in a row now? He has surrounded himself by obedient subordinates who implement his vision unquestioningly. When I asked him what he thought about Hyperfiddle in 2019 or so, one of a few short things he said, this is an exact quote, “it’s not ours.”

I value the Alex's opinion but I'd like to offer several additions, clarifications and/or counterpoints: 1. Realistically speaking gears not supporting scalajs platform is not a huge problem exactly because it will support wasm. Thus the only runtime where it could matter is the js in the browser (because for lambdas we can use native!) where <checks notes> react is the premiere solution. React doesn't care about effects and neither does any other popular UI library. To make things even more interesting, I am under the impression that the most popular scalajs library is currently Laminar, which also doesn't care about how you deal with asynchonicity and has its own reactive programming library - airstream. I therefore reject the notion that gears being based on continuations is incredibly limiting - it works with jvm, wasm and native and in these platforms we still have the opportunity for growth. Scala on android or on iOS is probably not happening, that ship has sailed ages ago and both of these platforms have a corporate backer that has an interest in keeping things under control. Regarding VT runtime not being able to be tuned - a quick glance at the Loom's mailing list reveals that there's an open discussion about custom schedulers already and some Java projects are experimenting with this idea (link in reply below). It seems possible to me we will be able to use CE or Kyo's scheduler with Loom to manage carrier threads in the future. 2. Ox is also based on Virtual Threads of project Loom, just as Gears is. It's not a library for "blocking threads", it's a complete structured concurrency toolkit that will be able to benefit from Caprese's improvements in the future and offers massive ergonomics improvement over whatever lands in Java. Regarding the problem of other platforms - on this year's Scalar @WojciechM_dev spoke about his prototype of virtual threads for Scala Native IIRC. This however forces me to talk about the elephant in the room - there's a lot of wonderful stuff to be done in the context of Scala Native and a lot of incredible stuff is already happening there like the absolutely mind blowing things done by @velvetbaldmime or @gabro27 (the latter recently ported JDBC to Scala Native and proved that it works with Magnum for sqlite at least!). All of that work is being done by VL or by open source contributors without any commercial backing and this seems to be the crux of the problem - I haven't seen any real interest in Scala Native from our customers. It's a bit surprising to me but that's how things are - multithreading being available did not change this. I hope TL stack being usable on SN will bring in some interest but given how things are right now it's hard to convince anyone to allocate more resources for a project without business traction. Maybe the jvm is just Good Enough? Any feedback about what would make The Business consider Scala-Native would be massively helpful. 3. regarding Kotlin - it is still just grandpa's async/await. If anything is driving the adoption of Effect.ts, it's Promise/async/await and Alex seems to be well aware of that. With Loom and Caprese we have no need for traverse or sequence, no need to treat higher order functions in any special way. Kotlin will get better immutability? Cool, we'll get rust-style safe mutability. Either way, with things like Caprese and Kyo we're still well ahead of the competition and if anyone is interested in pushing the monadic syntax improvements - SIPs are open to anyone.

Tu Nguyen just published awesome looking Laminar bindings for the WebAwesome (Shoelace.js 3.0) web components library: > github.com/nguyenyou/webawes… > webawesome-laminar.vercel.ap… You can now easily use even more professionally made web components in #ScalaJS!

Haven’t used elm, but comparing Tyrian to React or even scalajs-react (which makes impressive strides toward safety) have to agree TEA is the way to go.

I certainly can't think of any value proposition Scala as a language has that OCaml (and, by extension, F#) don't. You could say "Scala ran on the JVM," but that's backing into a value proposition based on its runtime, not what the language is (which, to be clear, is at least in part a good thing: Scala on the JVM lasted long enough that there's now Scala Native and ScalaJS, too, so the runtime reach has grown, rather than shrunk). And it turns out this doesn't matter much... or, maybe, the growth of these languages laid the groundwork for the acceptance of Rust, which is nominally "an alternative to C ," but has practically all of the language features of ~OCaml/F#/Scala as well, leading to its acceptance far outside the "systems programming" domain.

Also, we have a ticket to provide a TS interface via ScalaJS. It’d be great to collaborate if you’re interested! github.com/getkyo/kyo/issues…

It's been a while since I touched scalajs but nothing changed: it's as fun as it is annoying. Feels a bit like a toxic girlfriend. Or any girlfriend actually?

ScalaJSもCoffeeScriptももう懐かしい… #TSKaigi #TSKaigi_toggle

Find out a practical way to learn full stack Scala 3 with ZIO & related libraries. If you’re interested in real life settings of ZIO stack, Laminar, & ScalaJS, this is the workshop for you! More on Real-World ZIO workshop by @rockthejvm is coming soon to scaladays.org/workshops

TS の、他の AltJS に対する優位性って、「その言語の標準ライブラリ」という存在が無いことなのでは 今はどうか知らんけど、一昔前の KotlinJS や ScalaJS はバンドルサイズがクソデカかったイメージ

ScalaのJsonSchemaのライブラリ、scalajsで動かないよ〜

That's a great ambition... Someone mentioned SBT as a pain. I tend to agree, but in some ways I've also gotten used to it. Perhaps some common tasks need more attention: IDEA integration, multimodule/project setup - especially ScalaJS with Scala backend (I use cask and upickle)

Released scala-uri 4.2.0, now with Scala Native 0.5 support: github.com/indoorvivants/sca… The native part currently depends on libidn2, but I'm working on a pure Scala Punycode implementation, to remove dependency on scalajs-dom (and browser) in Scala.js as well.

Scala is a great tool for JVM users to develop projects using a single language on both the server side (Play Framework) and the client side (Scalajs). Scala Native is another option for creating binaries using the same language. Scala itself is a suitable Java alternative.

I’ve been using sonnet-3.5 Cursor and it works well for front end stuff (ScalaJS, CSS, etc). I suspect the smaller training set is offset somewhat by the compiler error messages: Cursor’s agent mode will keep trying to fix stuff until it compiles.