Skip to content
Frontend Feeds
  • Today
  • Archive
  • Sources
  • Categories
    • The Giants6 Sources
    • Multi Author Blogs18 Sources
    • Top Front-end Bloggers25 Sources
    • More Front-end Bloggers77 Sources
    • Browsers, engines, etc.11 Sources
    • Libraries, Frameworks, etc.12 Sources
    • Company/Startup Blogs12 Sources
    • Developer/Designer News4 Sources
    • YouTube Channels13 Sources
    • Podcasts7 Sources

Today

Front-end, in one read.

The latest from the sources worth following, newest first.

Thursday, 5 November 2026

  • Web Tools WeeklyMulti Author Blogsread at source

    Web Tools Weekly Issue #694

    React Tools, AI Tools, Text Editors

Wednesday, 4 November 2026

  • DEV CommunityThe Giantsread at source

    Two coroutines, one journal: a Restate restart demo

    Both preparation steps had finished when I stopped the Node process. The Restate server stayed running. After I started the service again, the pending invocation returned ["A", "B"] , and the preparation writes were still present only once each. This is the small recovery demo I wanted for Restate's new durable coroutines: two routines with their own steps, an interruption in the middle, and a file that makes the executed effects easy to inspect. There is no language model in this example. Diagram of the completed restart trial. The spacing is schematic, not a latency measurement. Image by the author. Put the work inside the routines Restate's announcement describes generator-based coroutines that let its scheduler control when routines advance. Their I/O can overlap while completion order is recorded for recovery. [1] I used Restate Server 1.8.1 , Node 22.22.1 , and both JavaScript packages at 1.18.2 . The service writes a short line during preparation, waits on a durable timer, then writes a finish line. A returned value travels through the generator's local variable into the final result. In a new package with "type": "module" , install the matching dependencies: npm install --save-exact @restatedev/restate-sdk@1.18.2 @restatedev/restate-sdk-gen@1.18.2 Save the service as service.mjs : import { createServer } from " node:http2 " ; import { appendFileSync } from " node:fs " ; import * as restate from " @restatedev/restate-sdk " ; import { gen , execute , run , sleep , spawn , all } from " @restatedev/restate-sdk-gen " ; function lane ( name ) { return gen ( function * () { const value = yield * run ( async () => { appendFileSync ( " effects.log " , `prepare- ${ name } \n` ); return name . toUpperCase (); }, { name : `prepare- ${ name } ` }); console . log ( `prepared- ${ name } ` ); yield * sleep ( 8000 ); yield * run ( async () => { appendFileSync ( " effects.log " , `finish- ${ name } \n` ); return true ; }, { name : `finish- ${ name } ` }); return value ; }); } const demo = restate . service ({ name : " CoroutineDemo " , handlers : { run : async ( ctx ) => execute ( ctx , gen ( function * () { const a = spawn ( lane ( " a " )); const b = spawn ( lane ( " b " )); return yield * all ([ a , b ]); })), }, }); const endpoint = restate . endpoint (). bind ( demo ); createServer ( endpoint . http2Handler ()). listen ( 12880 , " 127.0.0.1 " ); The timer is set to 8,000 milliseconds to leave a clear interruption window. It is a demo setting, not a measured overhead result. gen() receives a generator factory. spawn() registers a routine and gives back a task handle; the scheduler advances it when the current routine yields. all() waits for both handles and returns their values in input order. The package's own README distinguishes these operations and notes that spawned work can be abandoned when the main operation exits; explicitly joining the tasks avoids relying on fire-and-forget behavior. [2] Keep the journal outside the worker process The service is only one part of the setup. It needs a running Restate server and a registered deployment. I used this local server configuration, saved as restate.toml : disable-telemetry = true bind-address = "127.0.0.1:15122" advertised-address = "http://127.0.0.1:15122" rocksdb-total-memory-size = "256 MiB" default-num-partitions = 1 [ admin ] bind-address = "127.0.0.1:19070" [ ingress ] bind-address = "127.0.0.1:18080" After installing Server 1.8.1 from its official release, I started it with this configuration and its own data directory, then registered http://127.0.0.1:12880 through the admin API at http://127.0.0.1:19070/deployments . The service itself starts with node service.mjs . [3] The invocation goes through the server's ingress at http://127.0.0.1:18080/CoroutineDemo/run , with a JSON null body. Calling the Node endpoint directly would skip the server that owns this journal. I first let an invocation finish without interruption. It returned ["A", "B"] and wrote each preparation and finish line once. That was the control before introducing a restart. For the restart trial, I waited until both prepared-... messages appeared. These messages come after the corresponding yield* run(...) has resolved. I then killed only the Node service process, started it again on the same port, and left the original request waiting for its response. Read the effects, not just the replay messages The restarted worker logged that it was replaying the invocation. It also printed prepared-b and prepared-a again: those diagnostic statements are outside the durable closures, so seeing them again is expected. The file tells a more specific story. Immediately before the crash it held: prepare-b prepare-a After recovery and completion it held: prepare-b prepare-a finish-b finish-a The response was ["A", "B"] . The order of returned values follows all([a, b]) ; it need not be the order in which the effects finish. In the uninterrupted control, the finish lines appeared in the opposite order. That is the useful division in this example: normal JavaScript flow is reconstructed, while acknowledged durable steps supply their recorded results. The local value variable is rebuilt through replay; it is not a heap snapshot copied out of the crashed process. There is still a boundary around external side effects. This trial interrupted the worker after the preparation results had resolved. It did not kill the process between a file append and acknowledgement of that step. The append itself has no idempotency key, so I would not infer exactly-once writes for every possible crash point. The Diagrid team's explanation of at-least-once workflow execution describes that effect-before-recording window in Dapr. [4] It is a useful question to bring to any recovery demo: which side of the acknowledgement did the failure happen on? Here, the server was never restarted, no remote tool or LLM was called, and no throughput benchmark was run. The completed check is service-process recovery with two joined coroutines and inspectable effects. References and resources Igal Shilman, Stephan Ewen and Giselle van Dongen, Durable Coroutines for TypeScript . Restate contributors, generator SDK package and API documentation . Restate contributors, Restate Server 1.8.1 . Diagrid, Understanding At-Least-Once Execution and Why It Matters for Workflow & Agent Developers . Asset credits Original recovery diagram based on the executed local service and its effect files. The service example is original; Restate dependencies retain their upstream licences. AI disclosure AI was used to draft the article.

  • DEV CommunityThe Giantsread at source

    Why Pay for the Smartest Model Every Time?

    Originally published on wrightfunctions.com , where the demos are live. A restaurant doesn't send every order to the head chef. Toast goes to the line cook. The head chef gets the dish that can go wrong. Plenty of AI apps do the opposite: every request, from "what's your refund policy?" to a thorny legal question, goes to the same big, expensive model. The price gap is large. As of September 2026, Anthropic's cheapest current model, Claude Haiku 4.5, costs $1 per million input tokens, and its priciest, Claude Fable 5.1, costs $10 ( pricing page ). That's ten times the price for questions the small one could often answer just as well. This post covers the four common ways to stop overpaying, and the one thing that keeps them honest. Routing: decide before you ask Model routing puts a quick decision in front of your models. A small, fast classifier reads each request and picks who answers: the cheap model, the expensive one, or a person. That classifier can be a decision model like Jev , which TypeSafe documents for exactly this . It works at scale. When OpenAI launched GPT-5 in August 2025, it described it as fast and deeper-thinking models behind "a real-time router that quickly decides which to use" . Researchers at UC Berkeley and Anyscale built routers that learn from human preference data. Their RouteLLM project reported costs cut by more than 85% on one benchmark while keeping 95% of GPT-4's quality. AWS offers a managed router in Bedrock and claims it can cut costs by up to 30% . Cascades: try cheap, escalate when unsure A cascade skips the upfront guess. The small model answers every request and says how sure it is. Below a confidence threshold, the request goes up to the big model. The 2023 FrugalGPT paper chained models into a cascade, with a small scoring model judging each answer, and matched the best single model "with up to 98% cost reduction" on its tests. The catch is that escalated requests pay twice, and the whole thing rests on calibration: a small model that's confidently wrong never escalates. On the original post, you can drag the threshold. ▶ Interactive demo: try it on the original post Set it too low and wrong answers slip through cheaply. Set it too high and you're paying for both models on most requests. The sweet spot is where quality stops rising, and you find it by measuring. Distillation: teach the small model your job If the small model is almost good enough, make it better at your specific task. Distillation trains a small model on a big model's answers. The name comes from Hinton and colleagues in 2015 , who built on earlier work squeezing big models into small ones. A famous early result, DistilBERT , came out 40% smaller and 60% faster while keeping 97% of its teacher's language understanding. In January 2025, DeepSeek released six smaller models, from 1.5 to 70 billion weights, distilled from its R1 reasoning model . For your own app, it's the same move: log what the big model answers on your real traffic, then use fine-tuning to train a small model on those answers. Your cascade then escalates less often. Caching: the cheapest answer is one you already gave Plenty of requests repeat. A semantic cache stores answers and returns one when a new question means the same thing as an old one, matching them by embeddings rather than exact text. Open-source tools like GPTCache do this. Providers also offer prompt caching for the part of a prompt that never changes, like a long system prompt or a reference document. On Anthropic's API, a cache hit on most models costs a tenth of the normal input price . Caching stacks with everything above. Keeping it honest Every one of these trades a little quality risk for a lot of money, so the only safe way to run them is with measurement. Keep a test set of real requests with known good answers. Run it against the cheap path and the expensive path before any change to thresholds, routes or distilled models goes out. That's the eval gate from the first post in this series , applied to cost: a change ships only if quality holds. Then watch it in production, because routing failures are silent: a misrouted hard question gets a confident, wrong, cheap answer, and nothing crashes. Traffic also drifts: a new product launch fills your stream with questions the small model has never seen, and quality slides a percent at a time. Sample escalations and non-escalations, grade them, and track the numbers like any other SLO. So why pay for the smartest model every time? You shouldn't: most of your traffic is toast. Let a line cook handle it, send the hard dishes to the head chef, reuse what you've already cooked, and train the line cook on the chef's recipes. Along with quantization and decision models , it's one of the big levers on the AI bill. The one rule is that you can't cut the cost of quality you aren't measuring. References & further reading Claude pricing (Anthropic · as of September 2026). Haiku 4.5 at $1 / $5 per million input / output tokens, Fable 5.1 at $10 / $50. Intent Routing (TypeSafe AI · docs). A decision model classifies each request and sends it to fixed logic, a specialist LLM or a human. Introducing GPT-5 (OpenAI · August 2025). A fast model, a deeper reasoning model, and "a real-time router that quickly decides which to use." RouteLLM: An Open-Source Framework for Cost-Effective LLM Routing (LMSYS · July 2024). Routers trained on preference data cut costs by over 85% on MT Bench while keeping 95% of GPT-4's performance. Paper at arXiv 2406.18665. Amazon Bedrock Intelligent Prompt Routing (AWS). Routes within one model family and claims up to 30% lower costs without losing accuracy. FrugalGPT: How to Use Large Language Models While Reducing Cost and Improving Performance (Chen, Zaharia & Zou · 2023). Learned cascades, with a small DistilBERT scoring each answer, matched GPT-4 with up to 98% cost reduction, or beat it by 4% at the same cost. Distilling the Knowledge in a Neural Network (Hinton, Vinyals & Dean · 2015). Names distillation and builds on Caruana's earlier work compressing an ensemble into a single model that's much easier to deploy. DistilBERT, a distilled version of BERT: smaller, faster, cheaper and lighter (Sanh et al. · Hugging Face · 2019). 40% smaller, 60% faster, 97% of the language understanding. DeepSeek-R1: Incentivizing Reasoning Capability in LLMs via Reinforcement Learning (DeepSeek-AI · January 2025). Six dense models from 1.5B to 70B, distilled from R1 on top of Qwen and Llama. GPTCache (Zilliz · GitHub). An open-source semantic cache that matches new questions to past ones by embedding similarity. Prompt caching (Anthropic · docs). Cache reads cost 10% of the base input price on most models, even less on a few. AI-assisted: I write these with help from AI tools.

  • DEV CommunityThe Giantsread at source

    7 B2B SaaS Market Trends for 2026: What Buyers Are Actually Doing

    The State of SaaS 2026 is best understood through several overlapping evidence sets rather than one unsupported market total. Public-cloud forecasts measure more than SaaS, vendor reports describe their own customers, and buyer surveys reflect specific samples. Here are the seven trends that matter. 1. Cloud spending is context, not a SaaS market total Gartner's public-cloud forecast covers multiple service categories. It is relevant to the environment in which SaaS operates, but it is broader than subscription application software. Infrastructure, platforms, services, and application software grow for different reasons — combining them produces an impressive number but a weak answer about SaaS vendors, customer adoption, or software budgets. 2. Buying decisions are becoming more deliberate G2's 2025 Buyer Behavior Report shows buyers need clearer proof of fit, security, integration, and measurable operating value. For vendors, that raises the importance of transparent documentation, implementation requirements, and pricing boundaries. For buyers, it strengthens the case for trials using representative data and workflows instead of relying on category grids alone. 3. SaaS operations move beyond license counting Zylo's 2026 SaaS Management Index shows the operational work created by application portfolios: discovery, ownership, renewals, utilization, access, and spend governance. A useful operating model assigns an owner to each application, records the business purpose, tracks renewal terms, reviews access, and defines the system of record for important data. 4. AI changes product expectations AI is now evaluated as part of software capability, but adoption statistics vary widely because surveys use different definitions. Some count any AI-assisted feature; others measure regular organizational use or scaled deployment. Buyers should examine data handling, model providers, permissions, retention, evaluation, and human review. 5. Security and resilience remain buying criteria IBM's Cost of a Data Breach Report and CrowdStrike's 2026 Global Threat Report reinforce why SaaS evaluation includes identity, logging, incident response, data location, vendor access, and recovery planning. A certification badge alone does not explain tenant configuration, customer responsibilities, or incident procedures. 6. Platforms and specialized products will coexist Consolidated platforms may reduce vendor management and integration work. Specialized products may offer deeper workflows for a particular team or industry. Neither approach is automatically cheaper or safer — compare the complete workflow, migration effort, integration ownership, data portability, and the consequences of vendor dependency. 7. What to watch through 2026 Whether vendors disclose AI functionality and data practices with greater precision. How buyers measure adoption and business outcomes after purchase. Whether SaaS-management programs improve ownership and renewal decisions. How security, resilience, and regulatory requirements influence vendor selection. The full report, with each source's scope explained, is on SaaSStatsHub: https://saasstatshub.com/analytics/state-of-saas-2026-annual-report/ Originally published with full sources at SaaSStatsHub. Free calculators for MRR, churn, CAC and LTV: https://saasstatshub.com/tools/

  • DEV CommunityThe Giantsread at source

    zk-barter: Exploring Zero-Knowledge Proofs for Trustless Digital Barter | Rushidev Ukalkar

    How can two people exchange digital assets without either party having to trust the other to go first? That's the problem I'm exploring with zk-barter , a research project involving Solidity smart contracts, zero-knowledge proofs, and escrow-based digital exchanges. Author : Rushidev Gajanan Ukalkar GitHub Repository: https://github.com/Rushidev-Jain/zk-barter The idea Consider a simple exchange: Alice wants to sell Bob a digital product key. Bob wants proof that the key is genuine before paying, while Alice doesn't want to reveal the key before receiving payment. Traditional escrow mechanisms don't completely solve this problem. The zk-barter project explores combining cryptographic verification with smart-contract escrow to make such exchanges more trust-minimized. Technologies and concepts The project explores: Solidity smart contracts Zero-Knowledge Proofs (ZKPs) Groth16 proof systems libsnark Cryptographic commitments and verification Smart-contract-based escrow Current development This is an ongoing research and prototype project. The cryptographic circuit implementation and integration still require substantial work. It is not production-ready or independently audited. I'm sharing the source code publicly to document the project and its development. Explore the repository: https://github.com/Rushidev-Jain/zk-barter Feedback and technical discussion are welcome.

  • DEV CommunityThe Giantsread at source

    Updating Rustup 1.29.3 while keeping the compiler fixed

    The toolchain manager and the compiler have separate version numbers. I updated an isolated Rustup installation from 1.29.2 to 1.29.3 , kept its linked compiler at 1.99.1 , then compiled and ran a small program through that same toolchain. That gives me a useful way to handle this patch: update the manager that selects the tools, then check which compiler a project actually uses. Recorded versions from the isolated update and the compiled sample. Image by the author. What the patch changes The Rustup team reports two regression fixes in 1.29.3: an illegal-instruction failure on certain x86_64 CPUs without SSE4.1, and an unsupported-lock error on Solaris. Those are upstream release claims; this walkthrough does not reproduce either hardware-specific failure. [1] If you already have Rustup, the release instructions say to stop programs using it and run: rustup self update The word self matters. This updates Rustup itself. It is different from asking Rustup to update installed Rust toolchains with rustup update . That broader command can also update the manager. [1] Check both sides of the selection I used separate CARGO_HOME and RUSTUP_HOME directories for the trial, with shell startup files left alone. Rustup documents these locations as configurable. [2] I linked an existing compiler under the custom name pinned-local ; I did not download a fresh compiler or replace the usual installation. Here is the version ledger: Component Before After Rustup 1.29.2 1.29.3 Linked Rust compiler 1.99.1 1.99.1 To check the selection in that shell, I ran: rustup --version rustup show active-toolchain rustc --version The active toolchain was pinned-local (default) . Keep the complete version output when troubleshooting; the table above extracts the version fields so the two components are easy to compare. Rustup's rustc and cargo commands are proxies: they pass the invocation to a selected toolchain. Updating that routing program does not, by itself, request a different compiler. [3] There is one practical prerequisite here: the shell must be reaching those proxies. A rustc supplied by another installation can produce a perfectly valid version line while bypassing the Rustup selection you intended. Mayur Kumbhar's environment setup walkthrough makes the related point that verifying the compiler and Cargo in a fresh shell is part of installation, rather than an optional last step. [4] Compile through the named toolchain For a small end-to-end check, I saved this as demo.rs : fn main () { let values = [ 2_u32 , 3 , 5 ]; println! ( "sum={}" , values .iter () .sum :: u32 > ()); } Then I selected the linked toolchain explicitly: rustup run pinned-local rustc demo.rs -o demo ./demo The executable printed: sum=10 pinned-local is the custom name from this trial, not a toolchain Rustup ships. Use a toolchain you have actually installed or linked when adapting the command. This is a narrow update check: manager version, compiler selection, compilation and program output. It does not test all Cargo dependencies or establish that a project will build on every target. For a real project, keep its selected compiler visible alongside the manager version. “Rust updated” hides a distinction that the tools themselves already let you inspect. References and resources The Rustup Team, Rustup 1.29.3 release announcement . The Rustup Book, installation locations and environment variables . The Rustup Book, how Rustup and its proxies work . Mayur Kumbhar, Rust Essentials: How to Set Up Your Development Environment . Asset credits Original version-track diagram from the recorded update and compile check. No third-party image assets. AI disclosure AI was used to draft the article.

  • Hacker News Front PageThe Giantsread at source

    Debian apt security update (man-in-the-middle)

  • CSS-TricksThe Giantsread at source

    Smashing AI Conference

    The AI 2027 Conference is a live online day for designers and engineers on where AI stands today, what to expect in 2027, and where teams are getting it right. Smashing AI Conference originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: AI Gude – my feeds as a daily podcast, revived with AI

    Comments

  • Hacker News Front PageThe Giantsread at source

    US voters roundly reject data centers in ballot measures

  • Hacker News Front PageThe Giantsread at source

    Jaron Lanier on parallels between AI and social media

  • Hacker News Front PageThe Giantsread at source

    North Korean fake job interview led to $6.3B Binance heist

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: Chinese sentence checker with pinyin and English explanations

    Comments

  • Flavio CopesMore Front-end Bloggersread at source

    Cheap code can still create expensive decisions

    Review AI code changes with a runnable example: catch a broken supplier code, trace its consumers, and check what a rollback can recover.

  • HeyDesignerDeveloper/Designer Newsread at source

    AI prototyping inside your design system

    I let AI build. I don’t let AI decide, There’s no better name for design systems, State of a system.

  • Frontend Masters BlogMore Front-end Bloggers12 min read

    Data Access Testing With @testcontainers

    Testing data access code has always been awkward: unit tests want to be fast and isolated, and a real database is neither. With Docker and @testcontainers you can spin up a throwaway Postgres inside your Vitest suite, push your Drizzle schema into it, and verify that your real insert and query code round-trips correctly.

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: 13M opinions on 48k products extracted from Reddit and HN

    Comments

  • CSS WizardryTop Front-end Bloggersread at source

    Web-Perf Wednesday 016 – Lighthouse 13.6 Can Lift Scores Without a Faster Site

    Lighthouse 13.6 changes simulated FCP and LCP, so PageSpeed Insights scores can improve even when the page itself has not changed.

  • SyntaxPodcastsAudioListen

    1053: What’s in Our Home Lab

    Scott and CJ tour their homelabs, from a fully 3D printed server rack to a custom OPNsense firewall load balancing two ISPs. They dig into Proxmox, Tailscale, Caddy, Synology vs. DIY ZFS storage, Home Assistant, Jellyfin, Immich, Kiwix, and coding over the network with T3 Code…

  • Hacker News Front PageThe Giantsread at source

    AI is forcing us to pay off 40 years of technical debt

  • AdactioTop Front-end Bloggersread at source

    честитке, Serbia Parabéns, Brazil Congratulations, USA

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: Trainlint, static checks for ML bugs that don't crash

    Comments

  • Hacker News: Show HNLibraries, Frameworks, etc.read at source

    Show HN: Agent-screenplay – Create beautiful screen recordings with one prompt

    Comments

  • Net NinjaYouTube ChannelsVideoWatch on YouTube

    GitHub Copilot App Tutorial #8 - Using Plan Mode

  • Flavio CopesMore Front-end Bloggersread at source

    Cloudflare Zero Wire: what it is and how to use it

    Zero Wire is Cloudflare's public vulnerability feed on Radar. What a briefing gives you, the agent prompt inside it, and what it changes for a small server.

  • Flavio CopesMore Front-end Bloggersread at source

    terminal-mac: give your computer-use agent its own Mac

    terminal-mac runs a macOS guest inside your terminal, so an agent drives that VM instead of your desktop. Install, setup, MCP tools and isolation limits.

  • Flavio CopesMore Front-end Bloggersread at source

    The complete guide to Cursor

    Learn Cursor from your first project to daily work: Agents Window, planning, visual edits, debugging, models, project rules, skills, MCP and the CLI.

  • Flavio CopesMore Front-end Bloggersread at source

    How to run SEO checks from the terminal

    Run seobot from the terminal to check a site, then hand the report to Cursor or Codex with the pages and the edits ready.

  • AbduzeedoMulti Author Blogsread at source

    Typography: Rosco Jr by TypeMates

    Rosco Jr by TypeMates is a typography project. Rosco Jr is a bouncy, brassy and poco-loco geo-grotesque. View the full typography gallery. Rosco Jr by TypeMates starts from a specific historical detou...

  • AbduzeedoMulti Author Blogsread at source

    AI Design: Conversational Video by Tavus

    Tavus pushes real-time AI design into conversational video, creating interactive digital humans that see, hear, and respond face-to-face. Testing conversational interfaces usually means trading realis...

  • Chris HawkesYouTube ChannelsVideoWatch on YouTube

    I Tracked 125,000 Tech Jobs. Nearly 25% Are Ghost Jobs

Tuesday, 3 November 2026

  • AbduzeedoMulti Author Blogsread at source

    MUDA '26: Kinetic Web Design by Etter Studio

    Etter Studio's web design for Zurich's MUDA pairs a squishy cobalt SVG menu with pixel-grid branding and clean Swiss exhibition layouts. Most museum menus hide in a corner. Etter Studio went the oppos...

  • AbduzeedoMulti Author Blogsread at source

    Poster Design: 10 Inspiring Get Out the Vote Posters

    Explore 10 graphic poster design works celebrating Election Day and US voting history, featuring Guerrilla Girls, Hank Willis Thomas, and more. Election Day brings a familiar urgency. Across street co...

  • Frontend Masters BlogMore Front-end Bloggers5 min read

    Multi-Column Different-Speed Scrolling

    Scroll-Driven Animations can step in and make scrolling feel different even if you aren't actually interfering with the actual page scroll.

  • AdactioTop Front-end Bloggersread at source

    Tuesday session

  • AbduzeedoMulti Author Blogsread at source

    Branding: LAB Institute identity by BOND

    BOND rebuilt the LAB Institute identity as a living system: a malleable logo students reshape themselves, in black, white and bold color. The idea lands first at poster scale. On a white wall, giant b...

  • AbduzeedoMulti Author Blogsread at source

    Berghs: Inside Kurppa Hosk's Visual Identity System

    Kurppa Hosk updates the visual identity for Berghs School of Communication, turning an exclamation mark's negative space into a bold grid. Berghs School of Communication has shaped Swedish creative cu...

  • HeyDesignerDeveloper/Designer Newsread at source

    I don't use Figma anymore, and it cost me my job

    Struggle together, Building beautiful websites with Claude, Design as a garden, Building an AI-ready design system library, and more.

  • Mux BlogCompany/Startup Blogs22 min read

    Agent experience and agent-led growth: a chat with Caelean Barnes

    Gauge CEO Caelean Barnes joins Dev Talks to explain how coding agents pick developer tools, why docs sway their choices, and how to test what agents do.

  • Next.js BlogLibraries, Frameworks, etc.read at source

    November 2026 Security Release

    The November 2026 security release for Next.js is now available

  • Engineering at MetaCompany/Startup Blogs10 min read

    F3 Lightning: How Meta Accelerates Ads ML Features to Production at Scale

    Facebook Feature Framework (F3) is Meta’s framework for authoring, compiling, and serving the machine learning features underlying ads ranking models, where a single request can require more than 20,000 features. We first presented F3 at AI @ Scale 2020. F3 reduced execution computational costs by compiling all features into a single merged graph, but that [...] Read More... The post F3 Lightning: How Meta Accelerates Ads ML Features to Production at Scale appeared first on Engineering at Meta .

  • Level AccessCompany/Startup Blogs5 min read

    AI Is Building Faster. Can Accessibility Keep Up?

    To keep accessibility moving at AI speed, catch issues in pull requests, fix them while context is fresh, and pair automation with expert The post AI Is Building Faster. Can Accessibility Keep Up? appeared first on Level Access .

  • SitePointThe Giantsread at source

    Why Your AI Agent Can't Read the Web (and How to Build a Fetch Layer That Can)

    null Continue reading Why Your AI Agent Can't Read the Web (and How to Build a Fetch Layer That Can) on SitePoint .

  • AbduzeedoMulti Author Blogsread at source

    Wolff Olins Unveils BMG Brand Identity

    Wolff Olins builds the new BMG brand identity around a faceted play symbol, acid Limelight, deep Midnight and metallic neutrals. BMG started in 2008 as a bold voice in music, and by 2025 it had grown ...

  • AbduzeedoMulti Author Blogsread at source

    Branding & Visual Identity: NISCHE Restaurant by Myundones

    Explore the visual identity for NISCHE, a Berlin fine casual restaurant by Myundones blending German culinary comfort and understated typography. German dining often suffers from two opposing aestheti...

  • David BushellMore Front-end Bloggers2 min read

    Death comes for XSLT

    Last halloween, Google decided to kill XSLT. That was not a unilateral decision mind you, Google said “jump” and other browser vendors said “how high?” In response, I published my Intent to Deprecate and Remove Google Chrome. A performative declaration of course, I don’t install spyware. […]

  • CSS-TricksThe Giantsread at source

    Re-Implementing :nth-child() With Modern CSS

    Combining :nth-child with style queries and sibling-index() to conditionally select child elements. Re-Implementing :nth-child() With Modern CSS originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.

  • SitePointThe Giantsread at source

    How Motion Design Improves SaaS Onboarding and Feature Adoption

    null Continue reading How Motion Design Improves SaaS Onboarding and Feature Adoption on SitePoint .

  • Dave RupertTop Front-end Bloggersread at source

    Write mo'

    I decided not to do #NaNoWriMo this year. Part of that is because I’ve never done it. Never even attempted it. Don’t even want to. Writing a novel is a life goal of mine, but cramming it all into one month isn’t for me. November is impossibly busy. But I do think it would be cool to have a big excuse for avoiding all those obligations. “Dave, come to this holiday party!” “Sorry, I’m writing a novel.” “Dave, come work at the school’s fall carnival!” “Sorry, I’m writing a novel.” “Dave, pay attention to your kids!” “Sorry, I’m writing a novel.” See, that level of self-preservation and pre-emptive boxing out of other responsibilities would be so cool. Like cigarettes cool. Despite not having a novel excuse, I am feeling compelled to wri’ mo’ this month. Whether it’s autumnal ghosts or pumpkin spices, there’s a draw pulling me back to my text editor. A vapor of creativity stolen by corporate dementors and their infernal machines, seeping back into my lifeless shell. Last week I powered through a handful of short stories by Arthur C. Clarke. Vintage sci-fi inspires me. Partly because the experimental short form factor containing a single “ What If? ” thought experiment seems achievable and because most of the stories are complete shit. In a modern world of blockbuster movie adaptations and eight volume octologies, vintage sci-fi sets the bar real low. One story I came across was The Nine Billion Names of God . The audiobook has a sick-ass cover of a skeleton in a cracked space helmet on a dying planet with a giant sun rising in the distance. You can pause this and get through it in ten minutes. Nothing in the story relates to that cover. Rather, the story is about two Western men that work for a fancy computer company that makes the Mark V . They’re hired by a group of Tibetan monks to help them write a program that will procedurally generate the nine billion names of God which they believe will bring about the end of the world. The Mark V will shorten the task of writing down all the possible names of God from 15,000 years of manual writing down to 100 days! Incredible productivity gains! AAABBBAAA AAABBBABA AAABBBACA AAABBBADA AAABBBAEA AAABBBAFA AAABBBAGA AAABBBAHA AAABBBAIA AAABBBAJA AAABBBAAB AAABBBABB AAABBBACB AAABBBADB AAABBBAEB AAABBBAFB AAABBBAGB AAABBBAHB AAABBBAIB AAABBBAJB AAABBBAAC AAABBBABC AAABBBACC AAABBBADC AAABBBAEC AAABBBAFC AAABBBAGC AAABBBAHC AAABBBAIC AAABBBAJC AAABBBAAD AAABBBABD AAABBBACD AAABBBADD AAABBBAED AAABBBAFD AAABBBAGD AAABBBAHD AAABBBAID AAABBBAJD AAABBBAAE AAABBBABE AAABBBACE AAABBBADE AAABBBAEE AAABBBAFE AAABBBAGE AAABBBAHE AAABBBAIE AAABBBAJE AAABBBAAF AAABBBABF AAABBBACF AAABBBADF AAABBBAEF AAABBBAFF AAABBBAGF AAABBBAHF AAABBBAIF AAABBBAJF AAABBBAAG AAABBBABG AAABBBACG AAABBBADG AAABBBAEG AAABBBAFG AAABBBAGG AAABBBAHG AAABBBAIG AAABBBAJG ... ... ... ... ... ... ... ... ... ... THIS STORY HAS NO MODERN DAY PARALLELS. An altruistic sex cult from a specific locale using a mountain of money to hasten the end of the world with their enormous computers that endlessly generate combinations of nonsense words that they believe will summon God… well, that would be a work of cheesy science fiction, not real life. The Nine Billion Names of God flipped a switch in me and has renewed my courage to write more. As someone with ideas about ideas burning holes in my head, it’d be worthwhile to offload some of my cognitive surplus. I don’t have any solid plans, words-per-day goals, charts, graphs, storyboards, outlines, or some Benjamin Franklin life hack schedule to make this happen. Instead I have an Obsidian vault with a hundred unsorted drafts. I don’t want to commit myself to publishing every day, but my goal is to get up and spend thirty minutes to an hour each day writing something . I want to carve out time before work, before doing my puzzles, before doom-scrolling the news. I want to use those premium dopamine reserves –the flavorful floating creme of consciousness that comes from a good night’s sleep, not the metallic bitter dregs distilled from caffeine and stimulants– I want to savor and use that precious natural dopamine on writing. My promise to you, dear reader, is that I will write more this month. I will write no less than nine billion stories and/or blog posts by the end of November. And upon completing my works, I can shed this mortal coil and leave this forsaken world.

  • freeCodeCamp.orgYouTube ChannelsVideoWatch on YouTube

    Vector Databases Full Course for Beginners – Embeddings, Similarity Search & ChromaDB

  • SitePointThe Giantsread at source

    How Developers Can Improve Their Learning and Productivity With AI

    null Continue reading How Developers Can Improve Their Learning and Productivity With AI on SitePoint .

  • Flavio CopesMore Front-end Bloggersread at source

    Tailscale alternatives for your own servers

    Tailscale alternatives for a VPS: November 2026 prices, the SSH fixes, and when WireGuard, Headscale, or Cloudflare Access fits.

  • Smashing MagazineThe Giants12 min read

    Modern CSS Might Make Your Front-End More Complex

    Replacing JavaScript with a modern CSS feature can simplify a piece of code while making the wider application harder to reason about. Gabriel Shoyombo explores what happens when logic is split between CSS and JavaScript, sharing practical guidance to help you keep complexity in check during migration.

  • AdactioTop Front-end Bloggersread at source

    Bad AI doesn’t smell | Clearleft

    The best way to avoid AI mistakes is to run research the old-fashioned way; get out there and run research in the field and complete your own analysis of the findings. It may take a little longer, but truly valuable research is worth the effort. adactio.com/links/22825

  • SitePointThe Giantsread at source

    Top 4 MCP Servers for Marketers: Features, Use Cases, and Limitations

    null Continue reading Top 4 MCP Servers for Marketers: Features, Use Cases, and Limitations on SitePoint .

  • Flavio CopesMore Front-end Bloggersread at source

    How to move a DigitalOcean Droplet from Ubuntu to Debian

    Move a DigitalOcean Droplet from Ubuntu to Debian: new server, copy the data, then switch the reserved IP. In-place conversion is unsupported.

  • Net NinjaYouTube ChannelsVideoWatch on YouTube

    GitHub Copilot App Tutorial #7 - MCP Servers & Skills

  • SitePointThe Giantsread at source

    How to Learn Java with AI: A Practical Guide for Beginners

    null Continue reading How to Learn Java with AI: A Practical Guide for Beginners on SitePoint .

  • HTML All The ThingsPodcastsAudioListen

    What Does Your Small Business Website Actually Need?

    Does your small business website really need a slider, testimonials, a blog, pricing tables, and every other feature you've seen on successful websites? Not necessarily. Websites are a lot like LEGO. They're made up of individual building blocks that can be arranged in countless…

  • HeyDesignerDeveloper/Designer Newsread at source

    The new full-stack designer (video)

    Design will never be the same (video), The era of personal software, Making features generic in CSS.

See everything from the last 30 days →

Articles belong to their publishers. This site only collects what their feeds provide.

Updated 4 November 2026 at 15:17