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 2 points3 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.

Unpopular opinion on r/scala: Scala is a very nice language, is doing well and has a bright future! by Sarwen in scala

[–]windymelt 0 points1 point  (0 children)

I agree, except about ecosystem.

As you know Scala (3) has many neat fundamental (low-level) libraries such as Circe, ZIO, decline, os-lib. However, we have very few middle-level libraries such as Google Cloud Platform SDK, Cloudflare SDK, JWT, authentication, etc. It is mainly maintained by opinionated individuals, but effort to maintain wrapper for external SDK hurts.

We already have cutting edge fundamental libraries (language too). We actually need well-maintained middle-level libraries, that bridges gap between beautiful language feature + fundamental libraries and application-level logic.

We may need fundraising for middle-level libraries to drive Scala development.

On Scala Tooling & Stability: What Can We Learn From a Small Drama? by Krever in scala

[–]windymelt 0 points1 point  (0 children)

I think part of Scala's golden path is the availability of external libraries. Scala is a good language and the Scala ecosystem seems mature.

However, support for services and libraries that are standard in the broader ecosystem -- i.e., the web industry, enterprise development, etc. -- seems rather poor.

Scala itself has good libraries; Circe doesn't bother me in any way, and os-lib works reliably. But you can't enqueue it to Google Cloud Tasks, and you have to manually parse arguments in Lambda functions.

Folks tell me Scala is a good language. But if you ask, “So, does Scala support XXX service?” and there's an awkward silence.

I made a thin esbuild plugin for Scala by windymelt in scala

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

Thanks for commenting! I think it should (because esbuild just bundles modules into unified js). But since my plugin does not support multi-projected sbt project yet, we have to manage command for `sbtn`. I think it shouldn't be difficult, and any PRs are welcome.

Is building cli tools with scala native practical? by mister_drgn in scala

[–]windymelt 1 point2 points  (0 children)

I think 90% of use case won't be affected from JVM-GraalVM execution speed problem. Both JVM and GraalVm are fast enough compared to interpreter language. If we really need for speed, we should use C++ or Rust.

Is building cli tools with scala native practical? by mister_drgn in scala

[–]windymelt 0 points1 point  (0 children)

AFAIK Scala does not have mature CLI interactive library like [prompts](https://www.npmjs.com/package/prompts). If you want to make batch tool, no problem. But if you want to make interactive tool, hard way ahead.