Actually ACL on Windows is very bad. Recursively changing owner of directory can take minutes, same operation on any UNIX-like OS takes seconds.
Yup, if you have SSH service open on port 22, you're automatically spammed by bots trying to brute force their way onto the system.
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.
Heck, I would just ask him about his take on the world, humanity, philosophy. His art and engineering has been studied already, and in 1 hour you would barely scratch the surface of the iceberg, but just how he viewed world, considering he was ahead of his times would be really interesting.
You can run some Photoshop versions on Linux, but I would just seek alternatives. I've been using Krita for ages. It's not Photoshop, but it has non-destructive editing unlike GIMP.
Software engineering nowadays is really complex. There is no way you're going to know what's going on, nobody is.
It's just the more experience you have, the easier it is to figure out what's going on. If you want to learn coding, just start coding.
I will start from something no one mentioned - start with Linux. Windows has its own very "special" ways of compiling stuff, while Linux is very simple. If you start on Windows, you'll probably use IDE which will set up everything for you (cause setting up thing in Windows is messed up), and it will still be a black magic for you how the code transforms into binary.
Many people recommend python, but I would start with C (not C++, C++ sucks). It will give you the understanding of basic concepts like memory management.
Then start using something like javascript, which will get you wide range of libraries, which you can use to build anything.
Then at the end learn how infrastructure works, how are services communicating with each other, how to put your server to the public, learn Docker, set up reverse proxy, run stuff in cloud.
@gornius
@lemmy.world