dev_null

Yeah, the environmental issues that are orders of magnitude less problematic than literally pumping the toxic chemicals into the atmosphere like with fossil fuels, vs comparatively miniscule amount of solid waste to store inert.

Fair enough. Yeah, I never thought of open and closed source as two exclusive options, but two of many.

I myself publish an application which isn't open source, but I publish the source code, as I believe my users have the right to know what runs on their computer, and have the freedom to audit, modify, and compile their own builds if they so wish. But I don't want someone to take and resell my application. I have yet to encounter someone calling my app closed source, but I can see how someone could.

I am not in the US. But the purpose is gaining credit score and rewards, at no cost.

Agree 100%

To make it more specific I guess, what's the problem with that? It's like having a "people living on boats" and "people with no long term address". You could include the former in the latter, but then you are just conveying less information.

I use my credit card all the time, and it's set to auto pay off all of it every month, so there is never any interest charged. It basically delays the time my money leaves my bank account from the time of purchase to up to a month later, with no downside, while building credit history. The interest may be 300%, I don't care because I'm never charged it.

I am not aware of any definition of closed source published by OSI.

Closed source (or proprietary software) means computer programs whose source code is not published.

It's not closed source, since the source is publicly published. It's source available.

Micronaut and Vert.X also work, and with Kotlin you unlock that ecosystem as well, for example Ktor. One could argue whether Spring is still a modern framework. It works very well, but there is a lot of "magic" and hard to understand annotations with Spring that make it harder to learn and debug than it could be.

Of course the reality in enterprise environments is that change is often very difficult and such changes are a hard sell when you already have millions of lines of Spring code.

But if you are not locked to Spring, there are better options. DI being build in is another negative to me. Spring does everything, and any project using it becomes a "Spring project". Which robs you of any choice. If you use Ktor for example, it's only a library, not a framework, and only does the web component. You choose your own DI library that works for you, you choose your own serialization, you choose your own persistence/database solutions, and you can replace Ktor with something else 3 years down the line, if needed, without touching any of the other parts if the project.

I use IntelliJ Idea. The free Community Edition is all you need.

He can't pretend to save the world if the world isn't ending.

I said Vivaldi is not open source a 2 comments ago. I said I recommend Firefox and derivatives, including Librewolf, I said Brave may be more secure, but shouldn't be used for reason that have nothing to do with it. Since you are not reading my comments anyway, I won't spend the time.