It means manufacturers are now eyeing linux as a viable marketable product. If they can pocket the difference between the windows license no matter how cheap, you bet they would do it

For Proxy specifically, that is how vue ref is actually implemented. By making a proxy so you get reactivity.

Alternatively, just do it sqlite style. Open source, closed development

If you don't need the rich presence features, the browser should handle everything. The desktop version is just a web wrapper anyway and ships its own browser that may have bugs (to support native binding)

Yeah, they need another revenue stream first before they can retire that IP I guess which does make sense and I wish more games adapt this strategy for their EOL

From their FAQ

Q: Is the game “Open Source” now?

A: Open Source refers to the Open Source Initiative’s definition, which the current non-commercial license doesn’t meet. Ideally, once we finish another game and are hopefully able to re-acquire certain rights, we’d like to re-license the U3 SDK under the MIT License.

Absolute bangers! Must read for every dev and demistifies the stigma about rolling your own auth! Authz is where things get hard

In sampling and statistics, I'm pretty sure there are terms for that. To account for the fact that not 100% of the population are being sampled. Hmmm, I wonder what that term is.

What do you mean by "install aur"?

I ask the inverse. Why should you demand that every project that uses x.y.z versioning be a semver? A widely held standard only applies if you actually want to follow it in the first place. You know HTTP spec didn't mention anything about the body in GET requests and so almost every web server just ignores body on GET? Yeah, some software decided to use that. And guess what? That software? It was Elasticsearch. People are free to do whatever they want with their software. If they decided to publish something non standard and you decided to use it, you can ask them nicely to follow standard, or make an adapter for it.

Whoa. Thanks a lot for the in depth explanation! I really appreciate it. I do come from a time when HTML didn't even have a semantic tag and CSS was still having difficulty of styling combo box across browser. Good ol times of PHP "SSR" as the modern development calls it. I moved to more backend development stuff with occasional hardware/firmware so that's why I am so rusty when it comes to web front end stuff. However, I am now opening my own company and I want to understand the technology that I will actually use even if I will hand it off to a front end person eventually.

Thanks a lot. One follow up tho if I may. How do you determine the markup and styling if the layout changes significantly from browser to desktop? Do you ship 2 different versions of the HTML and style them accordingly? My struggle is often about how to make the HTML and CSS so I don't repeat anything if possible. One example is having a list of navigation links in HTML once should be enough and show correctly on desktop and mobile via CSS only. But that is how a lot of UI frameworks usually do it. They have 2 different navigation markup. One for mobile as a drawer and one for desktop as a navbar. Only one is active at a time. The navigation link list is usually defined as a JS object but I don't feel like that's the way to do it properly.