Salam: New Programming Language Supports English, Persian, and Arabic Coding

·2 views

Salam is a newly introduced general-purpose programming language designed to be accessible, fast, and easy to read. It uniquely supports coding in three languages — English, Persian, and Arabic — aiming to remove traditional language barriers in software development. The language can be used to build native applications and websites, and includes built-in layout tools for web creation. Developers can try Salam instantly via a browser-based playground or install an official Visual Studio Code extension for local development. The project is community-driven, with collaboration channels available on GitHub, Discord, and Telegram.

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)

How Modern Browsers Track You in 2026 and What You Can Do About It

Contemporary web browsers, including Chrome, Safari, Edge, and even privacy-focused alternatives, are built with data collection mechanisms that go far beyond traditional cookies. Google's Chrome, which powers about 65% of web traffic, uses its dominance to shape privacy standards while profiting from user data through tools like the Topics API, which lets the browser itself categorize users into interest groups for advertisers. Apple's Safari and Microsoft's Edge similarly blend privacy-friendly branding with ad measurement systems and AI features that read user activity. Techniques such as browser fingerprinting and CNAME cloaking allow trackers to identify users persistently, even across private browsing sessions and despite ad blockers. The article argues that no mainstream browser is truly free of commercial data interests, and that users who do not pay for a product are effectively the product being monetized.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

GitHub Actions workflow can automatically block blog PRs with SEO errors

A GitHub Actions workflow described on the Lyra blog automatically checks every blog pull request for four common SEO issues before allowing a merge. The four automated jobs validate external links, meta and canonical tags, JSON-LD structured data, and a Lighthouse performance budget. SEO errors like broken canonicals, malformed structured data, and oversized images typically go undetected during standard code review and only surface weeks later via Google Search Console. The workflow triggers only when files in the blog content directory are changed, keeping it targeted and efficient. By keeping the merge button locked until all checks pass, teams can prevent silent SEO regressions from reaching production.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Research Tool Uncovers Potential Hidden Bias in Goldbach's Conjecture Analysis

A developer directed an AI-powered research engine at Goldbach's Conjecture, one of mathematics' oldest unsolved problems, in 2026. The AI tool surfaced what the researcher describes as a hidden bias related to the conjecture. The finding was shared on DEV Community as a short technical post tagged under math, primes, and AI. Goldbach's Conjecture, which posits that every even integer greater than two is the sum of two primes, has remained unproven for centuries. The post does not provide a formal proof but highlights an analytical observation made possible through AI-assisted research.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Scheduled Email Smoke Tests on Staging Catch Delivery Failures Early

Many release pipelines pass CI and health checks yet still fail at email delivery, with messages arriving late, duplicated, or pointing to the wrong environment. A lightweight approach treats email verification as a scheduled smoke test rather than a full end-to-end suite, running a narrow check every few hours on staging instead of on every pull request. The method relies on isolated, disposable inboxes so each test run receives exactly one fresh message, making it easy to assert the subject, recipient, call-to-action link, and send timestamp without ambiguity from prior runs. Keeping the implementation small and repeatable builds a month-long history that can reveal patterns like post-deployment slowdowns or provider delays that ad-hoc testing would miss. The core principle is optimizing for repeatability first, using throwaway mailboxes as a clean boundary for non-production checks.

0 comments Read more at DEV Community