Danke für die gute Übersicht. Ist sehr informativ. Erwähnenswert wäre noch die Visual Micro Extension für Microsoft Visual Studio (https://www.visualmicro.com). Es kann die freie Visual Studio Version (Community Edition) verwendet werden und bietet anschließend alle Annehmlichkeiten von Visual Studio auch für Arduino Entwickler. Das ganze ist aber nicht kostenlos. Es werden pro Jahr aktuell $12 fällig. Meiner Meinung ist die Visual Studio Extension aber das Geld wert. VG Marc

[Kommentar gekürzt, bitte beachten Sie die Netiquette, d. Red] Ich wüsste nicht, an welcher Stelle ich beginnen sollte, diese aus dem Himmel gegriffenen Aussagen zu demontieren. Es ist alles so was von grundfalsch, [gekürzt, d. Red.], dass ich damit erst gar nicht beginnen möchte. Es wundert mich, dass Sie so eine Bühne bekommt, um ihre programmatische Verschwörungen ans Programmiervolk zu bringen. Einfach nur mehr als eine graue Zelle aktivieren – dann ist der Spuk vorbei...

Hello! I am writing in your forum since I wasn't successful in contacting authors of this article (tried Facebook & Linked In). First of all, I want to thank you for including werf tool in this article! I am from Flant, the company behind this Open Source project and we're really happy more people will know about it! We also want to kindly clarify a few of statements mentioned in that article: werf is not in its early stage. This tool has been used in production for years by dozens of companies (at least). Different stability levels are even provided for werf releases: from alpha to stable and rock-solid. So the users can choose if they prefer new features or widely tested versions only. Of course, some specific features in werf might be new — simply due to a natural evolution of the project. That's why, for example, our GitLab CI integration has been recently heavily updated and our relevant documentation was a bit behind this overhaul. So, following the "release often" idea, we've released it without an appropriate English-language documentation and probably it has brought some confusion for those who only examine werf for the first time. Currently, the documentation is up-to-date and we've decided to avoid such practice in future (we won't publish new releases lacking appropriate English docs). I think it was the only reference to purely Russian doc we had at the project's website (and it's not an issue anymore). Considering the support of "top-10 CI systems". Werf can be already integrated with any CI system — it's just the question of how easy it is in implementation (general instructions for that are provided here). For now, we offer ready-to-use integrations and guides for two systems: GitLab CI and GitHub Actions (it was probably not published as a stable feature when you've been exploring werf, but it's ready for now — you can check it here). We plan to make similar guides for others, but yes, it takes time (and again, it doesn't mean you can't use it with other systems today). I hope these details can make your overview more correct, so more people will benefit from it. Anyway, thank you for your time! And thanks again for this article as Internet currently lacks good content on GitOps!

Visual Studio Code ist Open Source. Das mit den Binaries verstehe ich nicht – es ist klar, dass es kompiliert werden muss, wenn das gemeint ist. Aber das ist bei allen anderen wie z. B. Notepad++ genau so der Fall.

wer kann mir mitteilen bzw. aufzeigen wie man Programmierfehler mit Notepad++ nachverfolgen kann? Wp