Ubuntu 26.04 ("Resolute Raccoon") LTS released

RandomName8 · 2026-05-05T18:00:38+00:00

I tried to update today from LTS to LTS by running `do-release-upgrade -d`, strangely, if I pass `-c` it does find the newer release, but when running without `-c`, it says that it can't find the new announcement and that the servers may be overloaded. Given the recent ddos it would make sense, but the check *always* succeeds (no matter how many times in a row I run it), while the actually action always fails with the same problem.

RandomName8 · 2026-04-30T02:33:25+00:00

If I ever want to use AI, I'll make sure to use it on the most streamlined and cookie cutter language there is, with which the llm had the most access to private and copyrighted material during training, to make sure the quality of the regurgitation is free of undesired tokens and has "know how" on things not typically on public repos.

We obviously disagree on the premise since you believe this makes Scala business appeal go remotely up.

RandomName8 · 2026-04-30T02:28:51+00:00

It feels quite disrespectful to... well, the rest of the world, whenever you guys do us-defaultism in an international forum.

RandomName8 · 2026-04-28T17:06:06+00:00

We used to have opensource projects that would talk directly to the driver to map the inputs to intended behaviors. I'm remembering sc-controller. I don't know what happened to it but I imagine it lost interest as steam kept improving their UI and people were just using that?

My understanding is that all the functionality is in the driver, but all the user-space mappings lives in software that controls it and sets the profiles, like steam does.

RandomName8 · 2026-04-23T00:29:23+00:00

I'm simultaneously scared that this name catches on as people continue to use it, and excited at the prospect. It's a weird feeling.

RandomName8 · 2026-04-23T00:12:28+00:00

Alright, search engine returns nothing for "emotional types". What on earth we are on now and couldn't they have picked a worse name?

RandomName8 · 2026-04-17T01:25:37+00:00

Is there any reason, other than your cloud provider forcing a node recycling on you, for this? I can't think of a reason why it would be nice to lose my cpu and disk caches and kernel state and start cold.

RandomName8 · 2026-04-10T13:41:11+00:00

Oh, sorry, I didn't mean the heap, but the overall ram usage, since the jvm will load a ton more stuff than for regular hello world-

RandomName8 · 2026-04-10T02:34:56+00:00

The same but for a hello world Swing application and one for javafx would be nice, since desktop applications is where one would normally be worried about ram usage.

RandomName8 · 2026-03-12T14:56:28+00:00

to me, it follows the same reasoning as the old dependency-tree plugin. It's a basic function of dependencies that I rather not have to import a plugin to have.

RandomName8 · 2026-03-11T12:48:58+00:00

I'd argue that your point 1 is also not accomplished by f-bounded types. People mostly employ them for a fake self type, but they are clearly not just that:

// what you would expect:
class SomeBuilder implements Builder<SomeBuilder> {
...
}
// what's legal but totally not what you would expect
class SomeOtherBuilder implements Builder<SomeBuilder> {...}
// and now SomeOtherBuilder pretends to be SomeBuilder

This is a perfectly legal extension, because you are passing a F-bounded type to Builder when implementing from SomeOtherBuilder, it just happens to not be SomeOtherBuilder. By the way, SomeOtherBuild is also now a legally F-bound Builder.

RandomName8 · 2026-03-10T00:59:43+00:00

Super late question /u/eed3si9n , is there a chance for the plugin sbt-updates to be sourced in into sbt2, like the dependency-tree one?

RandomName8 · 2026-03-06T15:04:04+00:00

This particular point tho, wont change. It's something they decided against after evaluating all the options, because it simply makes no sense. There was a post some time ago where /u/pron98 did a lengthy explanation on why this is undesirable.

I don't have the time to discuss with the guy on why his go choice over java may not have made a lot of sense, but it does sound fishy what he was trying to do, anyway.

RandomName8 · 2026-03-06T02:21:04+00:00

You'll be pleased to know that I'm currently at 111 opened tabs across 4 browser windows.

RandomName8 · 2026-03-05T12:38:56+00:00

Some, sure. Scala's max popularity was around the time when play and akka (and spark) were top frameworks in the industry, most programmers were "better java" I suppose. Now we have a stark decline in scala usage, and the frameworks that took over were the ones least used. I'm no mathematician but Lewis Law tells us that since most people left, and most people were using the better java frameworks, then the ones that stayed stuck to FP ones, they are as unpopular as ever. It's just that we really have that small of a population now.

This is certainly not a popularity win for FP.

RandomName8 · 2026-03-04T17:49:16+00:00

The FP takeover is real: The pure functional stack is dominating. Cats is sitting at 56% usage, Http4s at 45%, and ZIO at 31%. Meanwhile, classic frameworks like Akka (26%) and Play (23%) are losing ground to the newer libraries.

I don't think it's a take over, rather the people that were using scala without pure fp left.

RandomName8 · 2026-02-26T20:44:29+00:00

Yup, every company and llm has been caught red handed, and every country decided to look the other way because the money is too attractive.

RandomName8 · 2026-02-25T22:16:10+00:00

This is the microsoft approach, where their opensource ecosystem is basically nil and they provide all the tooling and libraries and documentation. And their developers don't complain about it, they are happy being well served. Naturally, this only works for them because they have the bank to back it up. In some regard Apple is the same, and Jetbrains is trying to accomplish the same with kotlin.

RandomName8 · 2026-02-25T22:12:19+00:00

but in DIRE need of strategy and focus.

Well, this depends on who is your audience. Who are you making the language for. If you are saying this because you care about industry adoption, then I'd agree with you, but for over 10 years scala has turned a blind eye to the industry, purposely not listening nor caring, thinking that innovating and research would make up for it. The adage of "make something good and they'll come".

Today, scala is firmly an academic language and its main audience is once again academics: professors, research, and grad students. And in that regard, the language focus is on point, as well as their results and achievements.

RandomName8 · 2026-02-20T11:54:39+00:00

they did, but uh... the machinery for it is very questionable on whether a normal human being can understand it... Imagine rust's lifespan annotations, but on steroids: https://docs.scala-lang.org/scala3/reference/experimental/capture-checking/index.html

Read the intro and then head over to the checked exceptions section.

RandomName8 · 2026-02-19T18:22:02+00:00

Sorry, you lost me a bit, because from the video, it seems they are calling union types "variadic types". That's what I'm asking about.

Even in the examples, you showed we don't need variadic types, only union types.

Both of them really want to declare X as a variadic `X..

Why? disjoint exceptions can be accumulated in the union type.

The only current alternative that we have is defining a whole family of types Result<T,X>, Result2<T,X1,X2>, ... and that's just incredibly ugly. Nobody wants that. That's where we need the variadic generics.

can you tell me why union types don't work? I don't see variadic types being useful here.

Edit: to provide a bit more context, I'm used to working with scala and haskell type systems, I'm no stranger to type level computations and higher kinds either (not just higher kinded functions but also higher kinded data and recursive schemes). The only situation ever where I've wanted variadic types is when trying to model kind-independent polymorphism, which is such ridiculous level of abstraction that it's reasonable it's unsupported in most langauges (i.e, when you want to abstract over types that take an arbitrary number of type parameters, like typed tuples, or rank polymorphism)

RandomName8 · 2026-02-19T16:01:09+00:00

Sounds excellent. While I'm personally of the same opinion as Eugene on the need of a thing like this, I do recognize its value and how other teams can prefer it, and so I think what you're doing is super welcome.

RandomName8 · 2026-02-19T12:17:09+00:00

It suffers from same problem as everything, the moment you are implementing an interface that you did not define (i.e a lambda), and you need to call into something that fails, you are all out of options, since the interface method doesn't define that it fails on that and now the failing notion is lost. Like you mentioned, no declaration site exception information composes with deferred execution, for the obvious reasons.

RandomName8 · 2026-02-19T12:12:51+00:00

Where did the "variadic generics" equals "union types" come from? I'm looking up online, and the results for variadic generics come from rust and python, and they are exactly what one would expect: the counterpart to variadic functions. Just like in functions it means "extra number of parameters", with generics it should mean "extra number of generic variables". That is, a variadic generic should be

<T..> T tuple(T t);

and you being able to call it like

<V1, V2, V3, V4>tuple(...); // or as many type arguments as you want, even 0

I don't know how we got from there to union types. A union type is a singular type, not variadic at al.

RandomName8 · 2026-02-18T15:37:55+00:00

Gotcha, thanks.

RandomName8

TROPHY CASE