You're talking about assembly in a thread about OOP...

That's like saying the source code of a binary is a bunch of hexadecimal numbers. You can use a hex editor to look at the "source" of every binary but it's not human readable...

Yes, the model can be published without the dataset - that makes it, by definition, freeware (free to distribute). It can even be free for commercial use. That doesn't make it open source.

At best, the tools to generate a model may be open source, but, by definition, the model itself can never be considered open-source unless the training data and the tools are both open-source.

Gee, you sure put a lot of effort into supporting your argument in this comment.

Joplin itself is AGPL. Unfortunately, Joplin Server is under "JOPLIN SERVER PERSONAL USE LICENSE".

While I really like Joplin, I'm thinking of making the switch to something fully open source.

About 30 PLN for a standard seat in Poland, but that's not really going to tell the whole story without looking at things like the median income, average prices of other goods etc.

For some reference, that's the price for a month of standard Netflix over here.

It's no more a risk than throwing more developers at it when they're not needed.

“Too many devs“ can, and often is, a significant bottleneck in and of itself. The codebase may simply not be big enough to fit more.

Besides, I still don't see what all those additional engineers would actually be doing. "Responding to incidents" presupposes a large number of incidents. In other words, the assumption is that the application will be buggy, or insecure enough, that 30 engineers will not be enough to apply the duct tape. I stand by the claim that an application adhering to modern standards and practices will not have as many bugs or security breaches, and therefore 30 engineers sounds like a completely reasonable amount.

This sounds like the devs are personally, sword and shield in hand, defending the application from attacks, instead of just writing software which adheres to modern security practices, listening to the Security Officer and occasionally doing an audit.

Regarding mutation testing, you don't write any "tests for your test". Rather, a mutation testing tool automatically modifies ("mutates") your production code to see if the modification will be caught by any of your tests.

That way you can see how well your tests are written and how well-tested parts of your application are in general. Its extremely useful.

Ah yes, advocating for basic human dignity is now "not understanding basic ideas about economics", and none of the SIX different solutions I provided (which I didn't invent myself, btw) could ever work in any capacity.

I won't be continuing this conversation, as it is clearly not productive.

I'm sorry, but you won't be able to convince me that allowing a single company to own hundreds of apartments is a good idea that won't contribute negatively to housing prices.

Some ideas could include, but are not limited to:

• ban companies from buying housing properties
• introduce a fairly high tax on every second (or at least third, progressively higher with each) property to deter buying up properties to rent
• perhaps introduce another tax on properties which have been vacant for X months/years
• introduce rent control
• perhaps even introduce some form house price control (per square meter, tied to median wage, perhaps)
• make the government build some housing

You can debate how well each of these would work, but there are many ways to bring prices down without making it less pleasant to live in those houses. I'm most partial to a progressive property tax, rent control and government housing, myself.