Kissaki

we’ve made the decision to cancel the Runtime Fee for our games customers, effective immediately. Non-gaming Industry customers are not impacted by this modification.

Unity Personal: […] Unity Personal will remain free, and we’ll be doubling the current revenue and funding ceiling from $100,000 to $200,000 USD. […] The Made with Unity splash screen will become optional for Unity Personal games made with Unity 6 when it launches later this year.

at its heart, it must be a partnership built on trust

well… as much trust as you can get back after such activities.

I recently watched a presentation (on YouTube from a conference/offline presentation) about Systemd which also went into its focus/baseline of Linux, not Unix, and how NT supported a stronger service concept from the beginning. It was quite interesting to learn about the differences and the presenter's assessment and reasoning of the necessity of Systemd or something else that replaces or extends init and rc.d.

• The Tragedy of Systemd

Somehow it’s clunky to use.

huh?

I find developing GitHub CI in YAML clunky.

I don't find configuring a simple service via YAML config, with a preset showing me and explaining what I can do clunky.

The server sidebar has an uptime stat. Could also have a simple monthly costs covered percent stat.

with this in mind

With what in mind? Evading NULL?

Languages that make use of references rather than pointers don't have this Dualism. C# has nullable references and nullability analysis, and null as a keyword.

What does your reasoning mean in that context?

The items don't seem concise and always clear. But seems like a good, inspiring resource for things to consider.

If it is expected that a method might fail, then it should fail, either by throwing an Exception or, if not - it should return a special case None/Null type object of the desired class (following the Null Object Pattern), not null itself.

I've never heard of evading null with a Null object. Seems like a bad idea to me. Maybe it could work in some language, but generally I would say prefer result typing. Introducing a result type wrapping or extending the result value type is complexity I would be very evasive to introduce if the language doesn't already support result wrapper/state types.

It’s an operating system that demands more of you than does the commercial offerings from Microsoft and Apple.

Does it?

It's different, but I imagine they're not fundamentally different if you exclude established knowledge/already being used to something.

Normal office use for non-techy people is launching apps, editing documents, and surfing the web. That doesn't work much differently, not fundamentally different, and not fundamentally more difficult.

I wish standards were always open access. Not behind a 600 dollar paywall.

When it is paywalled I'm irritated it's even called a standard.

TOML instead of YAML or JSON for configuration.

YAML is complex and has security concerns most people are not aware of.

JSON works, but the block quoting and indenting is a lot of noise for a simple category key value format.

This is not my experience at all.

It seems we search for and look at different kinds of questions.

At least that's a testament to neutrality - in a shitty way.

fake internet points

Your take is a valid one, but not very fair.

Points are a reputation system. People who are contribute and provide quality get increased trust and power.

It's not "fake". It's a designed system of points with meaning.

A casual surfer not being able to vote is by design. Which has a cost of missing out on valid votes, but the benefit of evading trolls and misuse.