All of these functionalities can be provided by a simple WebSocket + REST server. The car connects to the WebSocket, and you can access these functionalities from your phone either with WebSockets or regular HTTP requests.

Cheapest servers with backend written in JS can easily handle thousands of WebSocket connections, and written in Go tens of thousands WebSocket connections. They would not ever need like over 100 of these servers GLOBALLY, which would cost them around $3000 monthly.

That’s the price of 60 subscriptions, which is freaking ridiculous.

You realize that maintaining a server that would allow that costs pennies?

You wouldn’t pay $150 for a lollipop, but somehow people think this is ok.

This problem exists exactly because of people like you, thinking it’s OK to pay for the features you already paid for.

Ah yes, perfect data format, where markup takes more space than the actual data.

And as always, DRMs fuck only legitimate customers, and pirates can watch anywhere at full quality.

That’s one of the reasons I don’t feel bad about pirating any more. Not even the cost, but the fact that if you pay you’re going to have a worse experience.

https://www.oracle.com/cloud/free/

There are tutorials on youtube on how to create a VM and set up a firewall for external access.

If you’re lucky enough to successfully create an account on Oracle Cloud, you can also try Oracle Cloud Free Tier. You can have free ARM64 x4 CPU and 24 GiB RAM totally free of charge. There might be problems with availability during VM registration, but there are scripts that automate spamming for checking every 80 seconds.

I’ve been using it for 2 years and it’s great. However be aware that your VM might get erased if you have a free account. That too can be remedied if you update to a premium subscription (You still get Free Tier resources without a charge). Nobody has reported an erased VM on a premium plan yet.

Still, I am pretty sure they can erase it if you do illegal stuff with it. I’ve been using it only to host Minecraft Server, as well as other services using Docker. So far so good.

If you’re trying to self-host http service, you can use cloudflare tunnels.

I mean, GPL guarantees code remains open and free. If they release an app based on the source code licensed under GPL, they have to give a source code along with essential build instructions to anyone who is using it, and then you can do anything with that code, including sharing, compiling, and distributing that app, provided it’s under GPL license.

Edit: I see it’s licensed under GPL 3.0, so no worries.

General rule of thumb: Comments say why is it here, not what it does. Code itself should describe what it does.

I actually had to refactor configuration module some time ago. These really came in handy. But was it worth it? Well… it saved some time, the time that could be used to debug problems manually, but it made me a lot more confident that the functionality that worked before, worked after.

95%? More like 99.999%, considering how many Wordpress sites are there.

And in many of these 0.001% cases, simple horizontal scaling would do the trick.

And if you need more than that, just use something that can work on the edge.

The thing is, they look like too much for a simple app with near none interactive elements.

But once app starts growing, concepts like reusable components, reactivity and state management become such an important tool.

Imagine tracking shopping cart’s total value. With these frameworks it’s just one store containing total value, exposing the value as reactive state. Once the value changes, all components using directly or indirectly that value update immediately. In vanilla you would have to keep track of every instance where that value is used manually.

Additionally, if you decide keeping total value of cart in frontend is stupid (because it is), you just modify your store to provide only readonly value, and create setters that require you to pass item or item id. Then that setter would hit up backend keeping your cart’s total value, add an item, and backend would return new total, which would now be set as that store’s new total value.

These frameworks are kind of SOLID principles applied to chaotic world of user interfaces.

I tried to learn React, but it was unnatural for me, but then senior front dev at my workplace suggested Vue. I remember Vue’s options api being too weird to even try it.

Then I discovered there’s composition api and fell in love with it. React’s flow without its weird quirks.

I think Svelte is next step towards feeling as natural as possible.

ZZ will save file though, the others won’t. You meant ZQ.

If you’re using Excel so much to the point that certain things can only be done in Excel on Windows, just learn Python.

It is better than in most languages with exceptions, except from languages like Java, that require you to declare that certain method throws certain error.

It’s more tedious in Go, but at the end of the day it’s the same thing.

When I use someone else’s code I want to be sure if that thing can throw an error so I can decide what to do with it.

What’s wrong with Docker?

Actually ACL on Windows is very bad. Recursively changing owner of directory can take minutes, same operation on any UNIX-like OS takes seconds.

Have you even made a production grade front end project?

You can’t use “pure” HTML solutions because every browser can display these differently. You have to use CSS to make a website look and behave modern. “Pure” center tag is clunky and doesn’t work everywhere and that’s “by design” (That behavior is defined in specification, and we can’t change specification to meet today’s standards because that would make it non backwards compatible). Additionaly you need to make your website scale to wide range of devices. And sometimes you need to even add JS to fix some of the issues if you don’t want the developer to implement a non-maintainable solution taking him 5 hours, if he could do that in JS in 5 minutes.

Look CSS is not perfect. It’s hacky solution to a problem, but news flash: most software engineering is. And it’s proved to be working.

“But what if in the future…” - address future problems in the future. As soon as they appear - not before or after that.

That’s the stupidest thing I’ve read today. I hope you’re not any kind of engineer. There are some situations where it might not be worth it to future-proof something, but if you apply that to everything you end up needing a full rewrite instead of just adding a feature.

To add to an answer, caddy is better fit for reverse proxy in my opinion. It’s like easier to configure version of nginx. With nginx proxy_pass you also have to configure other headers like x_forwarded_to, and you will also need to do some magic to get websockets working.

And also caddy automatically generates certs using ACME, by default.