SShortSingh.
Back to feed

Automattic's Harper Offers Fast, Private Grammar Checking Built in Rust

0
·17 views

Harper is a new open-source grammar checking tool developed by Automattic and built using the Rust programming language. It is designed to analyze documents in milliseconds while consuming less than one-fiftieth of the memory used by LanguageTool. Unlike cloud-based alternatives, Harper runs entirely locally, ensuring user data is never sent to external servers. The tool supports WebAssembly, enabling it to run across multiple platforms, and can be installed via extension stores for browsers, Visual Studio Code, and Obsidian. Full documentation is available at writewithharper.com for users on other platforms.

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
ProgrammingDEV Community ·

FBI Warns of North Korean 'FaceStealer' Scheme Using Fake Video Calls to Steal Crypto

The FBI reports that North Korean state-sponsored hackers are using compromised accounts and secretly recorded webcam footage to lure victims into fake video conferences. Participants are tricked into running commands or scripts under the pretext of fixing audio or connection problems, which installs malware that steals cookies, credentials, and cryptocurrency. The agency says more than $400 million was taken over the preceding 18 months and that over 900 webcam recordings were seized, though recordings do not equate to verified victims. Attackers reportedly reuse stolen contacts and footage for follow-on attacks, including an attempted compromise of a JavaScript library maintainer that was caught early. The FBI also notes other attempts targeting npm and Rust package maintainers, with no confirmed success.

0
ProgrammingDEV Community ·

ElevenLabs and Murf.ai Compared for Enterprise Voice AI in 2026

An engineering analysis compares ElevenLabs, a research-driven platform focused on neural audio synthesis, low-latency streaming, and voice cloning, with Murf.ai, a studio-style tool built for voiceover production and localization. The review examines each platform's architecture, pricing structure, learning curve, API capabilities, integrations, and security certifications. ElevenLabs is presented as better suited to real-time conversational agents, developer-driven pipelines, and very low-latency streaming, while Murf.ai is positioned for corporate video, e-learning, and marketing content managed by non-technical teams. Both platforms are reported to hold SOC 2 Type II and GDPR compliance, though their approaches to commercial indemnification and voice watermarking differ. The author frames the choice as depending on whether a team prioritizes API throughput and latency or a timeline-based editing workflow.

0
ProgrammingDEV Community ·

Solo-Developed Megabonk Sells Over One Million Copies in Two Weeks Using Unity

Megabonk, a 3D survivors-style game built by solo developer Vedinad in Unity, launched on Windows and Linux in September 2025. The title reportedly sold over one million copies within two weeks and peaked at 117,336 concurrent players on Steam. The article argues that Unity suited the game's 3D movement, procedurally generated maps, and large volume of characters and items. Compared with Vampire Survivors, which had to be ported to Unity later, Megabonk started on the engine, avoiding a costly rewrite. The developer also withdrew the game from a Game Awards nomination, though the article notes that rough visuals drew some early criticism.

0
ProgrammingDEV Community ·

Automating Breach Notifications to Meet Fixed Regulatory Deadlines

Breach notification is framed as a race against a statutory clock, with Singapore PDPA guidance and GDPR Article 33 both requiring assessment and regulator notice within a set window. The article argues that automation only succeeds if the pipeline is built before an incident, since the clock begins at discovery rather than when a team convenes. It recommends that each case be created automatically from a monitoring alert, with the deadline calculated from the discovery timestamp and stored directly in the case record. The pipeline moves through four stages, from capturing the discovery event to scoping, dossier assembly, and dispatch, with human decisions limited to binary gates that fall back to predefined defaults when a time limit expires. Each stage is meant to produce signed, timestamped artifacts so that notification timelines can be verified during audits, and the author recommends tracking latency, gate timeouts, regulator rejections, and rework while running quarterly drills.