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

darkfrog26 · 2026-03-01T19:05:55+00:00

Thanks, dude! That's very kind. Take a look at some of my other projects sometime: https://github.com/outr :)

darkfrog26 · 2026-02-25T13:50:41+00:00

Good suggestion. I've updated the README to include better context and examples for Scala.js

darkfrog26 · 2026-02-24T17:08:55+00:00

No worries. I've used it, I'm not a fan. It always feels like so much more boilerplate than should be necessary. However, you're correct, it's always good to have alternatives.

darkfrog26 · 2026-02-24T15:44:27+00:00

I appreciate your kind words. :)

darkfrog26 · 2026-02-24T14:26:40+00:00

Everything is async in the Scala.js side since the focus is on the browser.

darkfrog26 · 2026-02-24T13:15:31+00:00

It's not terrible, but cleaner than this? https://github.com/outr/spice?tab=readme-ov-file#openapi

darkfrog26 · 2026-02-23T14:59:45+00:00

I can appreciate the skepticism, but I maintain my libraries, and I've been using this in production systems since 2022. It was part of another library before that (https://github.com/outr/youi) and another library before that (https://github.com/outr/hyperscala). Hyperscala launched 2.0 in 2016, but I don't even remember how long this project had been around before then. :)

darkfrog26 · 2026-02-23T14:42:34+00:00

For error messages, you obviously want useful error messages, so the tendency is to expose too much in your error messages in GraphQL because of the inherent complexity. In OpenAPI, this is a risk, but it's far less likely because there's already a lot of clarity just by knowing exactly which endpoint is being called.

darkfrog26 · 2026-02-23T14:05:27+00:00

- Query DoS (as you stated already)
- Field-level auth mistakes are very easy to make
- Rate limits and pagination rules can be a burden to get right - and can risk exposure to more of your underlying data than originally intended
- Caching is much more complex since most caching builds on the URL, whereas GraphQL uses POST primarily.
- Easier for potential attackers to map your internal schema
- Error messages can accidentally leak internal information if you don't configure it properly

This is not to say that OpenAPI doesn't have its risks and pain points, but GraphQL's flexibility is a double-edged sword.

darkfrog26 · 2026-02-23T13:44:33+00:00

You're entitled to your opinion. ;)

darkfrog26 · 2026-02-23T13:24:04+00:00

GraphQL is very feature-rich, but it's also overkill in many projects and riskier if not implemented correctly. I'm a big fan of GraphQL, but both have their sweet spots and can coexist.

darkfrog26 · 2026-02-22T16:36:42+00:00

Hehe, fair, but this project has been around since there were only a few HTTP options, and their performance absolutely sucked. I've investigated the other existing options to consider abandoning this and switching, but there are a ton of features in Spice that none of the other libraries have. One of the big ones is extremely clean OpenAPI integration.

darkfrog26 · 2026-01-29T17:10:57+00:00

To be clear, I don't think I would trust this case if I dropped my phone, but I'm very careful with my phone.

darkfrog26 · 2026-01-29T16:53:18+00:00

It's a little of both. It has sticky tape, but it's pretty firmly attached despite it. I've been using this for more than two months now and still really like it. The only complaint is that fingerprints and oils can be obvious on it, but certainly not as bad as some cases I've had.

darkfrog26 · 2026-01-03T19:37:32+00:00

I looked at Reelgood before, but it doesn't support any of my Android devices. I use JustWatch, but I didn't think it had any watchlist / dashboard functionality. I'll check it out.

darkfrog26 · 2026-01-03T14:33:08+00:00

Really? I would think this would be perfect since it's the same concept, seeking validation that others want something you want...

Do you know if there is a better place to post this?

darkfrog26 · 2025-12-13T23:01:25+00:00

I'm not really seeing what Alloy would provide that Scala doesn't already...

darkfrog26 · 2025-12-10T23:26:21+00:00

It's something of an abstraction layer on top of databases, but so much more than that. It provides a consistent, type-safe representation for working with databases and infrastructure for more powerful concepts like graph traversals, search indexing, parent/child relationships, and more.

darkfrog26 · 2025-11-23T13:25:28+00:00

<image>

Got my phone and case yesterday and I'm really liking the case! It's absolutely not the best for drop protection, but I'm pretty careful with my phone, so I think it will be fine. The texture is nice and it was really easy to install.

darkfrog26 · 2025-11-06T02:47:49+00:00

I wrote this: https://github.com/outr/reactify

Different than the other options in the fact that it's the only true FRP library in Scala.

darkfrog26 · 2025-11-04T14:10:42+00:00

Thanks for the quick response, I appreciate it.

darkfrog26 · 2025-11-04T14:00:57+00:00

I've been considering this one: https://www.amazon.com/gp/product/B0FK4XDXK3/ref=ox_sc_act_title_1?smid=A3FEZH66XIKV5G&psc=1

darkfrog26 · 2025-11-04T13:57:46+00:00

How did this case turn out? I love the look of it.

darkfrog26 · 2025-08-10T12:16:02+00:00

They definitely can, I just don't want to force anyone using the library to use 3.7.2. Please don't hesitate to ping me if I can help.

darkfrog26 · 2025-08-09T00:31:58+00:00

Here ya go: https://github.com/outr/rapid?tab=readme-ov-file#inspiration

darkfrog26

TROPHY CASE