I’m sorry, but have you ever needed to manage some certificates for a legacy system or something that isn’t just a simple public facing webserver?
Automation becomes complicated very quickly. And you don’t want to give DNS mutation access to all those systems to renew with DNS-01.
I do not agree. Very often, when using libraries for example, you need some extra custom handling on types and data. So the easy way is to inherit and extend to a custom type while keeping the original functionality intact. The alternative is to place the new functionality in some unrelated place or create non-obvious related methods somewhere else. Which makes everything unnecessary complex.
And I think the trait system (in Rust for example) creates so much duplicate or boilerplate code. And in Rust this is then solved by an even more complex macro system. But my Rust knowledge might just nog be mature enough, feel free to correct me if I’m wrong…
As a life-long developer in OOP languages (C++, Java, C#, among others) I still think OOP is quite good when used with discipline. And it pains me that there is so much misunderstood hate towards it nowdays.
Most often novice programmers try to abuse the inheritence for inpropper avoiding of duplicate code, and write themself into a horrible sphagetti of dependencies. So having a good base or design beforehand helps a lot. But building the code out of logical units with fenced responisbilities is in my opinion a good way to structure code.
Currently I’m doing a (hobby) project in Rust to get some feeling for it. And I have a hard time to wrap my mind around some design choices in the language that would have been very easily solved with a more OOP like structure. Without sacrificing the safety guarantees. But I think they’ve deliberatly avoided going in that direction. Ofcourse, my understanding of Rust is far from complete so it is probably that I missed some nuance… But still I wonder. It is a good learning experience though, a new way to look at things.
The article was not very readable on mobile for me but the examples seemed a bit contrived…
We call that percussive maintenance… the brick is optional.
That’s good advice, we will. Thank you.
Thankfully Microsoft is a thrustworthy partner with the users best interests in mind. /s
At home Proxmox works reall well. When our VMWare licenses expire we’ll certainly evaluate that as option.
Wasn’t really aimed at you but from the things I’ve seen I am afraid not all Windows administrators might realize that.
And probably as a security update as well.
Installing Word, on a server, running as administrator, forecefully linked to some MS account for activation… Is that really a reasonable solution in a Microsoft world? Smh.
If documentation comes as Word document there is no documentation and a huge red flag for the software.
I’m sorry, you’re arguing in bad faith or have a huge case of Stockholm Syndrome.
But, just look at their Troubleshooting documentation where they tell you to drop to the terminal.
My point is that Microsoft has stopped making new buttons and dropdowns and refer you to new Powershell incantations for most new settings. Just look at how many options the new “Settings” app offers compared to the deprecated Control Panel.
Ha, then stay on Windows 7/10 or you’ll lose your control panel soon…
I have heard this argument for over 20 years… “You have to use the terminal in Linux, so user hostile”.
Well, try to do ANY windows sysadmin tasks without Powershell… See how far that gets you. Need to manage Exchange? Powershell. Need to change some network settings? Powershell… It is even getting more and more unavoidable. Now Powershell doesn’t even have a good terminal environment, sane parameters or good usability. And a general lack of documentation for all the obscure incantations.
In the meantime KDE on Linux is wonderful, fully integrated with the system, easy software maintenance (on Kubuntu for example) and with a sane settings menu… You hardly need a terminal at all. Try to find that in Windows.
So sorry, this argument is either invalid, out of date or Microsoft is even worse.
Strangly this UI always reminds me of the hospital scene from Idiocracy… Click the icon for where it hurts
As others have said: it depends on your technical expertise… But a nice and cheap solution is hosting a static blog build with Jekyll on Gitlab pages.
Yes, and that is where we enter the complicated territories…