However it is possible for the more technically minded without too much effort with an adapted "unattend.xml" file during setup. This skips TPM requirements account setup and a number of other annoyances.
I think mass hysteria is too perjorative. We have a lot of suspicious data points, but then a new data point turns up (early lights were a false alert) which suggests that the data generating process may be pretty biased.
Definitively not coincidence, but there are a lot of things that could cause a pattern of reported air lights - such as a warning to be on high alert looking for them, the autumnal equinox (nights are getting much darker very quickly in Denmark right now), etc.
Beyond the fine, the airlines will try to get their losses in millions back from someone. If it turns out to have been a private person, there will be lawsuits. In general parents are liable for their children. When a child is old enough to fly a drone on its own, I think it will also be of partial-legal age. Acceptance of manslaughter and threat to national security is not taken lightly.
Not OP. But with an unmanaged server it is on you. You are in full control and can leave it powered off if you so desire.
Monitorering is then your responsibility. They have no login/account on your host.
For any hardware issues I have had I have simply created a support ticket. They have always been really fast at responding and fixing for me. If you report a disk and serial number it gets swapped in no time.
They have managed offerings as well. I have never used those.
Hi there, I hope that it's okay that I respond here since you all mentioned Hetzner. What "clan" wrote here is correct. For our dedicated servers, which are un-managed, customers are responsible for monitoring. And naturally, if something comes up, our team will be happy to investigate it and replace the hardware (or even entire server) free of cost. It helps to speed up the process if you can document the failure as clearly as possible for our team by logging onto your account, navigating to the correct server, and opening a support ticket. You can also ask the team to run a full hardware check for you. For customers who don't want to spend as much time or effort on sysadmin, we have managed servers, where monitoring and other support is included. --Katie, Hetzner
Do you understand how flat and wartorn they were? Do you wish the same for the US?
If you are willing to take such extreme shortcuts then you can emulate the new Germany.
If not then understand that trust is a fickle thing. Quick to erode and hard to rebuild. What one administration detroys cannot simply be reinstated by the next.
Maybe 100 is a bit hyperbole. But at least 50. Being a neighbor to Germany I can assure you the reconciliation was not "quick" for us to be fully restored. And we still shiver when we follow Musks friends in Germany.
I love and is impressed with Germany and Germans. But it has not been an easy path for them.
Nothing good has ever come from Europe when we lean too far to the right. Be careful in what lessons you choose to take from us.
Exactly this. The EU has shown what happens when you let a minority run amok with the keys to the weapons locker. The scars are still plentiful and even if the last of the eyewitnesses are dying we are still steeped in the lore of the lead-up, the middle of and the aftermath of World War II. That Germany is seeing a resurgence of this is at least as scary as seeing how many other countries are easily programmed to start their march to the drumbeat of Nazi or ersatz ideology, only with slightly different scape-goats. For now it is not quite enough to tip the balance but that could happen at any moment. I hope we'll see the last of the bullet holes in the buildings patched before we start making new ones. That's the one use I have for russia right now: they seem to help us remember and it seems to serve as a uniting force.
I love the clean approach with classless. Documents do have a structure and is makes it easy to change by just swapping out the CSS without touching the document.
But could you not just add the class only when you really really need to break the structure? The middle ground for me would to do my utmost to avoid classes within reason. So as few exceptions as possible. I know this is selling elastic bands by the meter.
On the other end you have Tailwind CSS. I know many are happy with it and find it has a nice developer velocity. But I find it overly verbose and "framework of the day"-ish.
So for me it is classless until my head hurts. Then I'll sprinkle in a class to get work done.
It depends a lot on the rate of change of the document.
Documents that experience little change don't need classes because their structure is reliable.
Documents that change often have unreliable structures, and will require frequent updates to the CSS rules to match structure changes. Using classes insulates the CSS from the document structure, mitigating the need to update CSS as the document evolves.
It also depend your development strategy. If using Vue components and writing the CSS in the same file as a dedicated, small-scoped components, it's practical to update the CSS references alongside the document changes. But when there's distance between the HTML and the CSS, or there are components in use who's structures may change unpredictably (such as from 3rd party libraries), classes provide a safer reference.
There's no need to have an ideology of using classes or not using classes. The practical approach is to assess the nature of your work, the rate of change of the documents, and to adopt practices built around those assessments.
The vast majority of the time, if my document structure changes, I want the presentation to change too. It may depend some on how complex the document structure is... I usually advocate for simpler structures. I agree that one should assess and adopt practices applicable to what they are building.
My middle ground is semantic classes but also use the element names, as they are already semantic. I use IDs only for JavaScript. No hierarchical class names, no Tailwind, no code compressing, no Uglifiers. My code shall be a pleasure to read and modify.
My proposed viable middle ground approach would be to adopt markdown as an intermediate representation and use some build process to generate the final output. As long as the input is markdown, it doesn't matter if the final output from the build process maintains tight coupling between structure and styling.
That said, if the primary benefit of the no-class approach was intended to facilitate development, this method—which introduces an additional build step—would be counterproductive.
However it is possible for the more technically minded without too much effort with an adapted "unattend.xml" file during setup. This skips TPM requirements account setup and a number of other annoyances.
See: https://schneegans.de/windows/unattend-generator/
If you take the effort to do this subsequent installations will be a walk in the park.
reply