Urgent.News

What's breaking now, across thousands of outlets.

Tech

Merriam-Webster adds 1,400 words and definitions, from vibe coding to Sunday scaries

Merriam-Webster added 1,400 words and definitions, including vibe coding, Rickroll, looksmaxxing, and Sunday scaries. Here’s what made the cut.

Merriam-Webster adds 1,400 words and definitions, from vibe coding to Sunday scaries

Merriam-Webster has expanded its dictionary with 1,400 new words and definitions, covering a wide range of topics from social media to pop culture. The update includes terms like "Sunday scaries," which describes the anxiety felt as the weekend ends, and "cuffing season," referring to the colder months when people seek short-term relationships.

The dictionary also adds tech-related terms such as "vibe-coding," which is the practice of using AI to generate computer code, and "AGI" for artificial general intelligence. Food terms like "superfood," "cake pop," "bao bun," and "chili crisp" have also been included. Additionally, the dictionary recognizes the Mandela Effect, a phenomenon where people collectively misremember details, and "rickroll," a prank involving a bait-and-switch link leading to Rick Astley's song.

While some of these terms may seem recent, Merriam-Webster notes that they have been in use for a long time based on evidence from their editors. The publisher emphasizes their mission to document the rapidly changing English language, capturing the evolution of language in areas such as software development and daily experiences.

Written by urgent.news from Mashable's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at mashable.com →

More in Tech

Node.js SaaS Job Retries — Simple Queues, Delayed Backoff, and Dead Letters

Short answer: use an at-least-once message queue with delayed retries, an idempotent Node.js worker, and a dead-letter queue for failed SaaS jobs; use cron only to trigger work that is then drained by…

  • Node.js SaaS jobs require at-least-once message queue with delayed retries and dead-letter queue
  • Idempotent workers and unique job IDs ensure exactly-once execution despite at-most-once delivery
  • Operational choice depends on existing platform decisions and team's skills

More from Wednesday 16 September →