Articles

WordPress 6.0 has been released, and another niche jazz musician will be enjoying extra Spotify royalties next month.

WordPress 6, named for latin-jazz musician Arturo O’Farrill, is the realization of a change of direction the WordPress Foundation adopted several years ago.

All versions of WordPress now power around 42% of the web. That’s approximately 810,000,000 sites. If you looked at each site for a single second, without pausing to blink, it would take you over 25 years to see the home page of each one — of course, if you factor in how long a typical WordPress site takes to load it would take well over a century.

Some people (i.e., me) have been predicting the decline of WordPress for so long that sooner or later, we were bound to be correct. And, despite its astonishing reach, there are some signs that its market share may now be in decline. Even the W3C abandoned it in favor of Craft.

Of the 1,930,000,000 sites that currently make up the web, only around 400,000,000 are active. WordPress’s long-term dominance, coupled with a stalling market share, means that a disproportionate number of abandoned sites are WordPress. With site builders like Wix, Squarespace, and Shopify taking huge chunks of WordPress’ share of new sites, WordPress is facing something of a cliff edge.

What the ill-informed naysayers (i.e., me) hadn’t counted on was that WordPress had already seen the writing on the wall and formulated a plan…

WordPress’s problem has always been its legacy code; supporting out-of-date ideas and a spaghetti-like codebase has meant a great deal of work to do anything new. As a result, the last few releases have seen great ideas stifled by labored implementation. Even the most loyal WordPress user has to admit that Gutenberg, while filled with potential, doesn’t work the way it should. However, with WordPress 6, all the work may be starting to pay off.

With version 6, the block editor in WordPress is starting to feel like a design tool that, if not perfect, is at least usable. Editing content no longer feels like you’re fighting against the UI. Most importantly, the bar for creating a site is much, much lower. WordPress 6 also offers improved performance and accessibility, both areas that have traditionally been lacking. Security is still something of an issue, but that is mainly due to the ROI for hackers that massive market shares generate.

WordPress, it seems, has arrived at two conclusions: its main competition isn’t other CMS but other site builders. To maintain its market dominance, it needs to cater not to professionals but to amateurs.

Don’t get me wrong; the WordPress ecosystem will benefit from WordPress 6, at least reputationally. New sites run by amateurs eventually become established sites run by, if not professionals, then at least knowledgeable amateurs.

OK, so WordPress probably isn’t a good choice for enterprise sites. And there are certainly better options for ecommerce. And as for SEO, well, probably best not mentioned.

But in WordPress 6, we have a free, open-source site builder that lowers the bar for making a new site. It’s a credit to the community that has persevered to produce it.

Source

The post WordPress 6.0 Lives Up To The Hype first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

As I’m becoming a senior developer in terms of age, I’ve transitioned from one language to another. One of my main interests has always been clean, easy-to-understand UIs (User Interface). That journey started for me with Director (to create multimedia CD-ROMs), Flash website animation, and Flex Rich Internet Applications (= « Flash on steroids »). When I started developing with Java over 10 years ago, we had some projects with the early versions of Vaadin and JavaFX. As I went on with serverside applications, I only continued with JavaFX for some personal and side projects and loved the way you can create a UI both with XML (FXML actually) and code, exactly the same approach I loved with Flex. Since then, my love for Java and JavaFX only grew and it’s still my major programming environment.

But JavaFX has one missing piece: running it in the browser… Yes, JPRO can do this, but it needs a license and a dedicated server. And yes, there are some projects ongoing to bring JavaFX fully to the browser, but they are ongoing and not mature yet… Let’s look at another approach: Vaadin Flow and run it on a Raspberry Pi to control a LED and show the state of a button.

Source de l’article sur DZONE

We tend not to think about it, but the Internet has a physical dimension. It’s a complex network of wires, cables, servers, and technical odds and ends — if you really want to, you can track it down; doing so is particularly easy on small islands because there tends to be a single cable tethering the region to the wider world.

Those physical cables run all the way to your building, and although an ISP manages them, they are normally rented from public bodies as part of your national infrastructure.

Beyond the physical, international bodies govern protocols like ARP, IEEE, HTTP, NTP, FTP, and others, which control how data is transmitted through the network and keep everything playing nice.

Then, at the other end of the equation, there’s your device. It may be a phone, a tablet, a notebook, a desktop. It’s probably several of these. And because it’s your device, everything on it feels like yours. We tend to think of it as our method of accessing the Internet instead of being part of the Internet — in reality, it’s both.

On your device, the software you use to access the Internet is your browser. For 65% of people, that’s Chrome. Even if you’re reading this on Edge, it’s created with the Blink engine, an extension of Chromium, which is the basis for Chrome. In fact, almost every browser is built using a variation of Chromium, except those on Apple devices that require Apple’s own WebKit to be used instead.

Chromium is ostensibly open-source. WebKit is not, but both are geared towards their primary contributors’ business goals; neither Chromium nor WebKit will make a change that negatively impacts Alphabet or Apple.

Your browser is just a copy of a pre-compiled set of source files sat in a Git repo somewhere. You may have installed a few plugins in your browser. You may have bookmarked a few pages. You’ve probably moved it to your dock or your home screen. Those features are just nice add-ons for the GUI; what really matters is what decisions are made about how to render web technologies.

Imagine a world in which every single car used the same mid-range Ford engine. Add in a stereo, and paint it any color you like, you can even pick your own tires, but under the hood, it has to be that mid-range Ford engine. And the only justification is that it’s too much work to create an alternative.

The 2020s are going to be a time of enormous change. You can smell the panic in traditional banking sectors every time Cryptocurrency is mentioned. Real estate billionaires are desperately trying to get us back into offices we don’t want to return to. And yes, I’m sorry, but the climate crisis is looming, and it will force our hand. The values of a whole generation have been rapidly reassessed. Innovation and the potential for innovation are rife, except, ironically, on the Internet, where we’re still chugging away with the mid-range Ford engine under the hood.

The web has reached the point at which the browser engines we choose define real-world infrastructure. There’s a fork in the road: either browser engines are part of an infrastructure that should be rationalized into a single browser protocol, or alternative browser engines need to be nurtured, encouraged, and accessible by choice.

Featured image via Pexels.

Source

The post Poll: Is It Time to Merge Browser Engines Into a Browser Protocol? first appeared on Webdesigner Depot.


Source de l’article sur Webdesignerdepot