MySqlConnector VS WordPress

MySqlConnector (the most popular .NET library for MySQL, and the one that I authored) has supported protocol compression for many years: https://github.com/mysql-net/MySqlConnector/issues/31.

> I kept technical notes about the protocol, to serve as a future reference for myself and for other developers.

As someone who's written a MySQL client (in C#: https://github.com/mysql-net/MySqlConnector), I'd be very interested to see your notes. Are they available anywhere, or were they the confidential IP of your client?

> Unsurprisingly, bugs were uncovered every time a new client was added.

I've faced the same thing, from a client perspective. Every time a new server is tested (MySQL, MariaDB, Amazon Aurora, Azure Database for MySQL, etc.), I find slightly different interpretations of the protocol and have to accommodate them.

I have had the pleasure of contributing to a couple different networked drivers with very talented maintainers that I like to use as references.

One supports a wide array of Framework versions and has both Sync and Async I/O, as it must to implement the ADO.NET database driver interfaces. Reading the internals really highlight the way that .NET has evolved over the years and what must be done in each target version to maximize performance:

https://github.com/mysql-net/MySqlConnector

The other supports .NET 6 only with Async I/O only. This support policy seems to be the way that "modern" .NET development is headed, as .NET 6 will be the floor for LTS .NET (formerly .NET Core) releases in a few months. Async APIs only greatly simplify development, and make it simpler to remain performant when targeting WASM.

https://github.com/Cysharp/AlterNats

As a library maintainer, one thing I often wonder about is how to indicate .NET version support. One option would be for the major version of the library to track the major version of .NET, so if I were to publish a new library today then start with .NET 6 support and start with version number 6.0.0 instead of 1.0.0. This would limit the library to only making breaking changes when the .NET version changes though.

Use the MySqlConnector to load the data into a temp table using the bulk copy API. Both of my libraries implement the IDataReader (DbDataReader) interface, so they can be directly used with the bulk copy APIs. Then insert into the final table from the temp table filtering out rows that are already in the final table.

I'm the author of what you might call the "new" MySQL ADO.NET library: https://github.com/mysql-net/MySqlConnector

I agree with your impression that developers of the other library don't seem to be "plugged in to" the .NET ecosystem. As an independent developer (not affiliated with Oracle or Microsoft), I've been able to influence GitHub PRs that shape the ADO.NET API for .NET 6.0, just by showing up and contributing; I haven't seen anyone from the Oracle MySQL team participating. Meanwhile, they violate basic principles of the .NET Framework Design Guidelines that have been around for over a decade (https://docs.microsoft.com/en-us/dotnet/standard/design-guid...), which makes their library feel alien to a .NET programmer (regardless of the quality issues it might have).

e.g. this community effort of a MySQL ADO.NET provider is miles ahead of Oracle's driver.

Creating a high-performance website is essential in today’s digital age. Speed, efficiency, and a seamless user experience are the cornerstones of successful web development. This article explores how combining Next.js with WordPress can achieve these goals, providing a robust solution for developers looking to elevate their web projects.

WordPress as the backend headless CMS, offering a versatile content management foundation.

Open source CMS WordPress and Drupal introduced WYSIWYG editors and template customization to empower independent publishing but page building was still largely code-driven.

While specific CMS platforms were not directly listed in the sources as explicitly supporting Behat, it’s widely known in the development community that Behat can be integrated with several PHP-based CMS platforms. Drupal and _WordPress _are notable examples of PHP CMSs that support Behat testing, thanks to their flexible architecture and the availability of various plugins or modules that facilitate integration with Behat. For instance:

WordPress is the most popular CMS(Content Management System) among bloggers. The same fact has made WordPress more vulnerable to attacks by hackers. Especially for authentication vulnerabilities such as brute-force attacks.

I recent WordFence scan identified the plugin reCaptcha by BestWebSoft as a "critical" vulnerability adding that it has been removed from wordpress.org. Where can I find information as to why it was removed from wordpress.org or why it is a critical security vulnerability?

The Genshine Impact database site looks pretty custom, can't tell if there is any CMS involved. You could start with the tried and tested WordPress. I built my gaming site on WordPress, it's not as fancy as the site you linked but it has plenty of options and flexibility to build all sorts of sites.

Almost every host has one-click WordPress installs these days using either cPanel's WP Toolkit or Softaculous, so that should be a non-issue. You never have to visit wordpress.org if you go that route; the host is handling that for you. Watch Ferdy Korpershoek's videos on YouTube for tutorials on getting started with WordPress. Personally, I would not go with his hosting recommendations, however. I like iWebFusion, but there are other good recommendations over at /r/webhosting

I am on wordpress (commerce plan ) £55pm. wordpress.com is what I am using, however I have heard of wordpress.org also which requires more technical knolwedge which I am willing to invest in over the next 12 months.

wordpress.org requires that user input should be sanitized and validated, and output should be escaped, to prevent mischief by bad actors. This mantra is embedded in current wordpress.org plugin guidelines. Unfortunately older plugins may not comply, leaving them vulnerable. They always were vulnerable, but what's changed is the light has been shone on the issue by Patchman and others. Publicly available code can be scanned by both good and bad actors to detect where malware can be injected.