Already, there’s a lot of buzz about React 19. FreeCodeCamp has a breakdown of the new features by self-described frontend ninja Neha Sharma.
One major issue that React 19 will tackle is the issue of excessive re-rendering, Sharma noted.
“Developers have historically spent countless hours addressing this problem, which often leads to performance issues,” Sharma wrote. “The constant hunt for code causing re-rendering and the subsequent optimization efforts have been a recurring task for engineers. But with React 19, this concern will be alleviated. The framework will handle re-rendering automatically, streamlining the development process.”
Sharma provides an analysis of each of the new features React 19 plans to have, complete with code samples in her GitHub.
Among the new features she examines are:
Nuxt 3.11 boasts better logging, a preview mode and server pages, according to Nuxt maintainer and core team leader Daniel Roe. This is the last minor release before Nuxt version 4 releases.
The better logging means that when developers have server logs associated with a request, they will now be bundled up, passed to the client and displayed in the browser console on refresh. Previously, the logs were not displayed in the browser console, which made it more difficult to debug, Roe noted. The plan is to add support of streaming of subsequent logs to the Nuxt DevTools in the future, he added.
Nuxt also introduced a preview mode.
“A new usePreviewMode composable aims to make it simple to use preview mode in your Nuxt app,” he wrote. “When preview mode is enabled, all your data fetching composables, like useAsyncData and useFetch, will rerun, meaning any cached data in the payload will be bypassed.”
Other new changes in this release:
The full release notes are available on GitHub.
Last week, Roe and Sébastien Chopin, author of Nuxt.js, also wrote a “looking forward” blog post that introduces some of the concepts Nuxt will be pursuing in the future, including its commitment to Baseline Compatibility, which relates to identifying web platform features that work across browsers. (“Baseline helps you decide when to use a feature by telling you when it is less likely to cause compatibility problems for your site’s visitors,” according to Mozilla).
The two outlined some of the strategies they use to pursue new features while prioritizing stability for existing users, such as making it possible to disable testing new modules or experimental features and using the ecosystem-ci pattern of validating that code changes don’t inadvertently break downstream projects.
PySimpleSoft released PySimple GUI 5 as a commercial software product this week. The move to a commercial software license is an effort to support the company’s sustainability and future software development efforts, the company’s chief marketing officer, Monty Hagler, said in a press release.
PySimple GUI 5 allows developers to create user interfaces. A free 30-day trial is available, after which a perpetual license costs $99. Hobbyists can still use it at no cost. The GUI was originally released in 2018 to enable Python programmers to create GUIs.
The new release adds improved security, cryptographically strong tamper protection, updated documentation, and other features, the company said in a press release.
WordPress 6.5 is “almost ready,” according to a recent WordPress team blog post, which means it’s time to start planning the 6.6 release cycle.
This new cycle will feature smaller squad sizes in an attempt to mitigate the “bystander effect” the core team has seen with larger squads, which created “the sometimes false feeling that somebody else must be working on things, resulting in unclear direction,” wrote core team member Héctor Prieto.
“With this smaller release squad, release leads should have proven experience and good availability during the release cycle,” Prieto wrote. “Less experienced folks and newcomers are still welcome to join as a cohort.”
Interested volunteers are encouraged to comment on the post.
Tabnine, which offers an AI coding assistant, will now allow developers to select the underlying large language model that powers Tabnine Chat, its software development chat tool.
Engineering teams can now select from a catalog of models to use the one best suited to their situation, and can switch between them at will, the company noted.
The available models are:
Providing options for the underlying LLM is in part to accommodate how rapidly LLMs are changing, the company noted.
“Historically, engineering teams had to choose both the AI coding assistant and its underlying models,” the company noted. “However, this approach leaves little room for teams to benefit from advancements from different LLMs without having to install, integrate, deploy, and train their users on a different AI coding assistant.”
Tabnine Chat was announced last June and is now generally available. It allows developers to interact with Tabnine AI models using natural language.
