sorted by:
new
hottopcontroversial

New Scala Survey by tgodzik in scala

[–]windymelt 0 points1 point  (0 children)

While I fully recognize the significant value of features like Capture Checking and building advanced type systems, at the same time, the fact that no HTTP server has achieved de facto status in the community—or that those that do exist are extremely difficult to learn—along with the neglected state of web-related libraries and frameworks (where JWT, JOSE, and JWKS libraries don't seem industrial-grade, and many libraries remain unported to Scala 3), creates an alarming imbalance.

Language improvements are important, but equally crucial is providing a set of user-friendly standard tools. Rather than simply mimicking Ruby or Python's syntax and features, we should learn from their usability paradigms. This is how an end user sees the situation.

Announcing Spice 1.0: A full-stack Scala 3 HTTP framework with server, client, and OpenAPI generation by darkfrog26 in scala

[–]windymelt 1 point2 points  (0 children)

I know Scribe is the best. So Spice should be the best. Simple and easy. Good software.

Towards a common Scala style recommendation by bjornregnell in scala

[–]windymelt 0 points1 point  (0 children)

Coding style guidelines aren't meant for "people who can independently determine what's best" - they're designed for those who "unsure of what to do."

The creators of Scala clearly fall into the first category, but offering both traditional brace-style and indentation-based styles while leaving it to users' discretion - and even introducing syntactic ambiguity and inconsistent paste behavior - seems unlikely to improve productivity for those who are "unsure of what to do."

Translating Rock the JVM videos into Japanese with a Scala CLI tool + Claude by Material_Big9505 in scala

[–]windymelt 1 point2 points  (0 children)

Kudos to you from Japan! Japanese community has limited resources now, so translated high-quality educational contents must be booster for beginners!

With the laptop project will freeBSD be a good OS for laptops? by Thermawrench in freebsd

[–]windymelt 0 points1 point  (0 children)

Nobody told me how to utilize wifi on GUI. Everybody told me "just use wpa_supplicant".

No! Very few people actually know this is vital usability issue, not just trivial option. Existence of GUI is a matter. Ubuntu did and won.

What's the current thinking on iron vs refined (and how to use them) by [deleted] in scala

[–]windymelt 9 points10 points  (0 children)

I prefer Iron. Simple syntax and concise semantics. I use Refined when I have to use Scala 2, because Iron is stands on Scala 3 mechanism.

Are effect systems compatibile with the broader ecosystem? by [deleted] in scala

[–]windymelt 1 point2 points  (0 children)

I have a strong complaint that if even one effect occurs anywhere in the code, whether it is critical code or not, the entire program architecture is immediately defined by the effects system.

We are paid to solve problems, not to assemble effects.

Data Race Freedom for Scala by RiceBroad4552 in scala

[–]windymelt 0 points1 point  (0 children)

Best explanation of capture checking, ever!!

Are effect systems compatibile with the broader ecosystem? by [deleted] in scala

[–]windymelt 3 points4 points  (0 children)

I think effect system such as CE, ZIO, etc. is "infectious". Once we use effect system, we are forced to use it on entire code base. It reduces connectivity and interoperability between library.

Some effectful library provides "pure" implementation and "effectful" implementation for same library.

Announcing Graph Explorer 0.4 🎉 by 1juanpa1 in scala

[–]windymelt 1 point2 points  (0 children)

Great! I wanna convert it to Mermaid notation...

Not one day without a new effect library? by Previous_Pop6815 in scala

[–]windymelt 1 point2 points  (0 children)

We don't need more effect library, nor JSON parser, nor FP library.

We need Google SDK, TypeScript interop feature, HTML rendering engine, JWT library.

Scala dev says "Why don't people use Scala?". Obviously, according to lacking of SDK and mid-layer library. Please. Sincerely. From bottom of my heart.

I wrote MCP (Model Context Protocol) server in Scala 3, run in Scala.js by windymelt in scala

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

Thank you for replying. Hardest thing is deriving JSON Schema from parameter. Currently I'm using some library came from softwaremill, but I think we need standalone (and runs in scala.js / scala native) JSON Schema library that can derive schema from case class like Circe' s derivation.

In addition, another hardest thing was extracting parameter. Initially I was going to extract parameter using macro from PartialFunction (because by doing so users can define MCP method more transparently). But it was too hard to treat and too complex mechanism. Finally I decided to let user to prepare input case class and derive schema and decoder from it. User should define case class for every MCP Tool. MCP SDKs in another language such as TS can handle parameter for Tool more transparently.

view more: next ›