SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Chrome to stop applying XSLT on 17 November 2026; sites advised to transform XML on the server

0
·4 views

Google Chrome will stop applying XSL stylesheets to XML from 17 November 2026, which affects sites that rely on client-side XSLT. The article recommends running the transformation on the server with PHP, Python or Node.js and sending plain HTML to the browser as the most durable fix. Sites in Chrome's origin trial or under enterprise policy keep XSLT until Chrome 176 in August 2027, and a polyfill remains an option for those who cannot change their server. The author stresses that XML sitemaps should stay in XML, since search engines and feed readers require it, and that a separate HTML copy can be published for human readers. The piece includes worked examples of building a readable sitemap page while keeping the original XML in place.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Payments Canada Launches Real-Time Rail, a 24/7 National Payment System

Payments Canada has announced the launch of Real-Time Rail (RTR), a new payment infrastructure intended to operate around the clock across the country. The system is designed to support faster, always-available payments for individuals and businesses. The announcement points to a broader goal of modernizing Canada's national payment network. The source material provides limited detail beyond the announcement itself, so specifics such as the exact launch date and participating institutions are not confirmed here.

0 comments Read more at Hacker News
0
ProgrammingDEV Community ·

Benchmarking Six Inference Engines for Gemma 4 E2B on a Single Cloud TPU v5e Chip

A developer compared six inference serving engines running Gemma 4 E2B on one Cloud TPU v5e chip, including vLLM, SGLang-JAX, a pure-JAX engine, and TorchTPU variants. Each engine ran alone on an identical flex-start v5litepod-1 instance using the same chat prompts, load sweeps, and 1,319 GSM8K questions. Answer quality was broadly similar across engines, with SGLang-JAX scoring slightly ahead of vLLM. For single requests, SGLang-JAX delivered the highest throughput at about 160 tokens per second, while TorchTPU trailed significantly. Under heavy load, patched SGLang-JAX reached 4,249 tokens per second at 64 requests, about 2.5 times vLLM's throughput, though vLLM remained the engine that works with Gemma 4 E2B as shipped.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Plain-English Beginner's Guide Explains Cloud Computing and the Work of Cloud Engineers

An introductory guide aims to demystify cloud computing, describing it as renting computing power from large data-centre operators over the internet and paying only for what is used. The author compares this model to buying electricity from a grid instead of running private generators. It contrasts the older approach of purchasing and maintaining physical servers with today's ability to scale resources up or down within minutes. The piece also outlines the role of a cloud engineer, who plans, builds and maintains systems in the cloud, and offers a realistic starting path for newcomers.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Shopify Developer Rates in 2026 Range Widely, and Why Fixed Quotes Often Work Better

Shopify developer hourly rates vary from about $15 to $200, reflecting the difference between entry-level theme work and senior platform engineering. Upwork's published figures run from $15 per hour for beginners to $95 for experts, though its averages are pulled down by lower-cost regions. Across countries, North America and Western Europe typically charge two to four times more than South Asia and Latin America, a gap that narrows at the senior level. The author argues that the real cost is rate multiplied by hours, and that a cheaper hourly rate can end up costing more when a developer takes longer. For projects with a defined endpoint, the author recommends a written scope and a fixed price, since that shifts overrun risk onto the developer.

0 comments Read more at DEV Community