WP Provider
WP Provider
151 Google recensies
Inge Scholman
17/08/2023
Snelle en goede service! Kan altijd op WP-provider rekenen!
Colin Harzing
27/07/2023
Fijne hosting partner. Altijd snel en responsief. Neemt al je zorgen uit handen omtrent hosting. Echt een aanrader!
Jan Hartog
27/07/2023
Supr snelle en vakkundige service! Heel fijn bedrijf!
Philippe Neven
03/07/2023
Fijne partner om mee samen te werken. Ontzorgen je volledig op hosting gebied en zijn gespecialiseerd in WordPress. Wanneer er iets is, ontvangen wij altijd snel en persoonlijk een reactie en worden onze vragen ook snel opgelost. Kortom, wij worden goed geholpen en ontzorgd!
Steven E.
30/06/2023
WP Provider has gone above and beyond to surpass my expectations. Their customer support is exceptional, and their performance is reliable, making them a true gem in the Wordpress hosting industry
Marijnke Vincent
28/06/2023
Super snel en fijne service en klantcommunicatie!
Max van Velsen
22/06/2023
Fijne, professionele en vooral snelle service! Krijg altijd snel en concreet antwoord op mijn vragen. Niks slechts op aan te merken.
EMQ
21/06/2023
Wat een fijne partij! Goed bereikbaar, meteen hulpvaardig. Wij zijn heel tevreden.
Raymond Ros
19/06/2023
Zeer tevreden, aftersales dik in orde bij WP Provider!
John Gruter
13/06/2023
Wat een topservice leveren zij. Altijd snel een oplossing als er wat is. Als iemand een website wilt laten maken of beheren, bent u hier aan het goede adres, tegen normale prijzen. Blije Voeteb

Matt Mullenweg speaks out against automatic WebP conversion in WordPress 6.1

In recent months, the question of whether WordPress should convert uploaded JPEG files to WebP files by default has often been raised in the WordPress developer community. Thoughts went so far that this feature should be implemented by default in WordPress 6.0.

WordPress 6.0 should integrate WebP even more strongly

However, the proposal was rejected rather quickly.

With the upcoming WordPress version 6.1, however, the question resurfaced, and now Matt Mullenweg seems to have put his foot down:

I went through all the conversations and issues here. I’m interested in supporting new formats and improving performance, but I think this change sent to users by default when upgrading to 6.1 is too much for now, especially because of operating systems’ clunky interactions with webp (and HEIC!) files.

I am glad that support for webp and HEIC files remains in the core, as we should be generous in what we accept and work with, but not with the change to convert everything to webp when JPEGs are uploaded.

This is excellent territory for a plugin that is the norm, a concept that I think every Make team should explore much more as a place to experiment and add functionality, just as we have done in the past with MP6 and Gutenberg. I think the plugin directory needs more collaborative, community developed and non-commercial or no-upgrade plugins that do something right, and Make-teams are the perfect groups to develop and maintain those. It is the ethos and process of the core that is applied to plugins so that we can officially recommend them and present them in the plugin directory, and that also gives us time to mature the environment around something (like WebP). Source : https://make.wordpress.org/core/2022/09/11/webp-in-core-for-6-1/

Matt Mullenweg suggests instead making the functionality of automatically converting JPEG images to WebP available with a plugin, as was the case for Gutenberg before its implementation in WordPress core.

General support for the WebP format remains, of course. This has been around since WordPress 5.8: WebP will soon make WordPress even faster

At the same time, Matt Mullenweg points out the importance and significance of plugins in general in another article. He also discusses how WordPress development teams can develop new features with less pressure but with less revision effort by taking a plugin-first approach. And he immediately gives some ideas on how to do this.

Delen:

Picture of admin

admin

Laatste berichten

Follow us