![]() |
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
The TC39 committee, which oversees JavaScript standards, advanced three JavaScript proposals to Stage 4 at its February meeting. Evolving to stage four means the proposals are ready to become part of the ECMAScript standard, which is the standard for JavaScript.
Sarah Gooding, head of content marketing at Socket, reported the JavaScript updates on the software security company’s blog. Advancing to stage four were the following proposals:
Large language models are good at discussing Kotlin and can answer questions about it, but their knowledge is incomplete and can even be outdated, warns a recent analysis of AI and Kotlin.
As if that weren’t problematic enough, artificial intelligence is also prone to typical large language model errors such as miscounting or losing context, writes software developer Vera Kudrevskaia on JetBrains’ Kotlin blog.
JetBrains Research tested commonly used AI model, including DeepSeek-R1, OpenAI 01 and OpenAI 03-mini, using a new benchmark the team created for evaluating Kotlin-related questions.
“We looked at how they perform overall, ranked them based on their results, and examined some of DeepSeek’s answers to real Kotlin problems in order to give you a clearer picture of what these models can and can’t do,” Kudrevskaia said. ”Our evaluation showed that the latest OpenAI models and DeepSeek-R1 are the best at working with Kotlin code, with DeepSeek-R1 having an advantage in open-ended questions and reasoning.”
The research team also did a code test of DeepSeek that’s worth reviewing.
Overall, the results show that a model can be more adept at a language than other, similar models. But there are other factors that come into play, such as a model’s speed.
So, programmer beware.
Those who have found incorrect or surprising LLM responses are invited to share them in the Kotlin public slack or post to the blog’s comments section.
OpenAI released a research preview of GPT-4.5, which the company calls its largest and best model for chat.
“GPT‑4.5 is a step forward in scaling up pre-training and post-training,” the company said in a blog post introducing the new model. “By scaling unsupervised learning, GPT‑4.5 improves its ability to recognize patterns, draw connections, and generate creative insights without reasoning.”
It’s broader knowledge base, improved ability to understand user intent and a greater “EQ” (emotional quotient) makes it better at writing, programming and solving practical problems, the company claimed. GPT-4.5 will engage in warmer, more intuitive and natural flowing conversations, they added.
Perhaps more significantly, the team said it may hallucinate less. Regardless, the research preview will help OpenAI better understand its strengths and limitations.
“We’re still exploring what it’s capable of and are eager to see how people use it in ways we might not have expected,” the team wrote.”
In addition to the blog post, there’s an approximately 13-minute video introduction to GPT-4.5.
Next.js 15.2 released Wednesday with updates for redesigned debugging experience, metadata and TurboPack.
In essence, the Next.js 15.2 team has redesigned its error UI and improved stack traces to improve the debugging experience.
Also with this release, async metadata will no longer block page rendering or client-side page transitions, thanks to the introduction of streaming metadata.
Thanks to Turbopack performance improvements, users should also experience faster compile times and reduced memory usage. Early adopters have reported up to 57.6% faster compile times when accessing routes compared to Next.js 15.1, the team noted. Vercel also saw a 30% decrease in memory usage during local development.
“With these improvements, Turbopack should now be faster than Webpack in virtually all cases,” the team noted. “If you encounter a scenario where this isn’t true for your application, please reach out — we want to investigate these.”
Finally, Next.js 15.2 introduces experimental support for React’s new View Transitions API and the Node.js runtime in middleware.