Today
Front-end, in one read.
The latest from the sources worth following, newest first.
HeyDesignerDeveloper/Designer Newsread at source
AI skills for building better interfaces
Designing with HTML, Design Zeitgeist, Building interfaces that understand what we want to do, Design is a search problem, and more.
DEV CommunityThe Giantsread at source
NexPHP – Next-gen PHP framework with Less Code, More Power, and Zero Magic
Why I Built NexPHP: Modern PHP with Less Code, More Power, and Zero Magic PHP in 2026 is unrecognizable from what it was a decade ago. With PHP 8.3+, strict types, enums, readonly properties, attributes, and Fibers, the language itself has become one of the fastest, most reliable backends on the web. Yet, many framework ecosystems still rely on architectural conventions invented in 2011: Facades and global state. Dynamic magic methods that confuse static analysis and AI coding tools. Architecture solely centered on the classic FPM "shared-nothing" model. That is why I created NexPHP : a modern framework designed from scratch around two realities: Modern runtimes (FrankenPHP and long-lived persistent workers). AI-assisted "vibe-coding" (where explicit types and zero magic lead to effortless AI collaboration). The Core Principles 1. Zero Magic, Strict Types No hidden metaprogramming. If a controller action expects a validated request, you simply typehint your FormRequest subclass: #[Post('/products')] public function store ( CreateProductRequest $request ) : ResponseInterface { // $request is automatically resolved, validated, and injected. // If validation fails, a 422 JSON response is returned automatically. $data = $request -> validated ( ) ; return new JsonResponse ( [ 'status' => 'created' ] , 201 ) ; } Because everything has explicit types and attributes, AI models (Cursor, Windsurf, Copilot) generate working code on the first attempt without guessing. 2. Dual-Runtime Readiness In persistent worker mode, PHP keeps the application in memory. If not designed carefully, user identity or database state can leak across requests. NexPHP features built-in request-scope isolation : Singletons live across the worker lifetime. Scoped bindings (current user, request, CSRF) are automatically wiped via $app->forgetScoped() after each response. In benchmarks, NexPHP achieves: ~218,000 req/sec in persistent worker mode. 0.00 MB memory growth over a 10,000-request soak test. 3. Native Fiber Concurrency No complex asynchronous event loops. You can run concurrent I/O operations cooperatively using PHP Fibers: use Nex \ Concurrency \ Scheduler ; $scheduler = new Scheduler ( ) ; $results = $scheduler -> all ( [ 'user' => fn ( ) => $httpClient -> get ( 'https://api.example.com/user' ) , 'order' => fn ( ) => $httpClient -> get ( 'https://api.example.com/order' ) , ] ) ; 4. Full-Stack Services Included NexPHP includes everything needed for production SaaS applications: Queues: Database-backed queue with exponential retry backoff and failed-job dead-letter stores. Scheduler: Cron-like DSL ( dailyAt('02:00') ) with lock-based overlap prevention. Security: Sliding-window rate limiting, CSRF verification, and CORS preflight handling. Observability: PSR-3 structured JSON logging with automatic secret redaction ( password , token ), and Prometheus metrics exporter. Try It Out in 30 Seconds You can start a new project right now via Composer: composer create-project nexphp/nexphp my-api cd my-api php bin/nex serve GitHub Repository: https://github.com/snigdho5/nexphp Packagist: https://packagist.org/packages/nexphp/nexphp I’d love to hear your thoughts, feedback, and pull requests!
DEV CommunityThe Giantsread at source
Cross-Client Handoffs & Reusable Context Across AI Agents
Cross-Client Handoffs & Reusable Context Across AI Agents Different AI coding clients and models have different strengths. You might prefer Claude Code or Codex for deep architectural analysis and bug investigation, Cursor or Windsurf for multi-file implementation, and GitHub Copilot , Cline , or Antigravity for targeted reviews. Normally, switching tools mid-feature—or even opening a fresh chat in the same editor to avoid context degradation ("context rot")—means copying long chat transcripts or explaining your architecture all over again. AI Artifacts removes that friction: because Preview UI rendering, artifact lifecycles, and Work Sessions are shared across all 7 supported AI clients, you can hand work off between chats and agents cleanly without losing momentum. Why Synthesized Context Beats Copying Chat History A Work Session does not transfer raw chat transcripts from one AI client to another—and that is intentional. A long chat thread is full of dead ends, rejected drafts, and back-and-forth troubleshooting that confuses the next model. Instead, reliable handoffs come from two things you control in your Work Session: Distilled documents organized into Working (active tasks), References (agreed specs, blueprints, and session context), and Archived (finished phases). Shared Instructions that tell any incoming agent how the session is organized, what role to play, and where to stop for your review. Step 1: Leave a Clean Checkpoint Before Switching Chats or Clients Before ending a long analytical chat or switching from one AI client to another, ask your current agent to capture the conclusions in a context artifact (and place it in References ): Update this session's context artifact with what we decided, why we chose this approach, what remains open, and the exact next step for a new chat. Why this habit matters: Decisions stay explicit: Marking what is settled versus what is still open prevents the next agent from treating a rough idea as an approved requirement. Instant orientation: When a new agent joins the session later, it can read your context artifact and immediately understand what is finished (in Archived ), what is in progress (in Working ), and what needs to happen next. Reusable knowledge: If you solved a tricky bug or edge case, capturing the final takeaway as a note or spec in References keeps that knowledge available for future tasks without cluttering your Git repository. Step 2: Shape Instructions Together with Your Agent You do not need to write a complex workflow specification from scratch before starting. Describe how you want to work in plain language and ask your connected agent to help formulate the rules for the session: Help me define the Instructions for this session: before proposing code changes, agents should read the Architecture Design and Session Context in References, draft an implementation-plan artifact for my review, and wait for my approval before modifying source files. Save the Instructions once we agree. You can also edit the Instructions box directly in the Work Session Manager (or click Open Markdown File to edit instructions.md in VS Code) and click Save . Tip: If you update Instructions while other chats are already working in the session, simply ask those existing chats to reload the session's Instructions so they pick up the latest rules. Step 3: Connect a Fresh Chat or Switch to Another AI Client Now that your conclusions are saved in artifacts and your rules are in Instructions , switching to a fresh chat—or handing implementation over to another AI client—takes one step: In the Work Session Manager header (or from the Sessions sidebar), click Connect to copy the session join prompt. Open a new chat in your target AI client (for example, switching from Claude Code to Cursor or GitHub Copilot ) and paste the prompt. Ask the new agent to confirm the current state or start the next task: [Pasted Session Connect Prompt] Read the Session Context and Instructions. Summarize where we are, then create an implementation-plan artifact for Phase 2 so I can review it. New agents join the same Work Session, read the shared context, and pick up right where the previous chat left off. What happens next: The built-in Work Session skill loads your Instructions and the categorized catalog ( Working , References , Archived ). The agent reads the relevant reference documents on demand—without you copying file paths or re-explaining your architecture. It creates the Phase 2 Implementation Plan inside Working and opens the rendered Preview UI (tables, code, Mermaid) for your inline review. Once you refine the plan and click Proceed , the agent executes the approved changes immediately. When the phase is done, ask the agent to move the completed plan into Archived to keep Working focused. Step 4: Bring in a Reviewer Agent — and Assess Findings Before Fixing When working on an important feature, you can connect a second AI client (for example, Codex or Claude ) to the same Work Session as an independent Reviewer —and use an Assessment step so you never waste time on noisy or unnecessary suggestions: Have the Reviewer inspect the work: Click Connect , paste the prompt into your Reviewer chat, and ask it to check the active artifact in Working against the requirements in References . The Reviewer can post its findings directly as comments on the artifact (or create a findings artifact in Working ). Assess findings before choosing fixes: Instead of blindly applying every suggestion—or manually reading through dozens of minor nitpicks—ask your primary agent (or a dedicated Assessor agent) to evaluate the findings first: Assess these review findings for validity, necessity, scope, and regression risk. Keep the original findings visible alongside your assessment in a review artifact and wait for my decision before applying any changes. Decide in the Preview UI: Open the assessment artifact in the Preview UI to read the original findings side by side with the assessment. Use inline comments to confirm which fixes you actually want, then let the agent apply only the approved changes. What's next? In this guide, you stayed in the driver's seat between phases—clicking Connect when opening a new chat or bringing in a Reviewer. What if you have two or three agents open in the same Work Session and want them to hand work off to each other automatically while preserving your review checkpoints? Workflow overview: Part 00: AI Artifacts Workflow Guide — When to Use What Previous guide: Part 02: Organizing Work Sessions — From Simple Collections to Shared Context Next guide: Part 04: Automated Multi-Agent Workflows with Session Waiters & Waiting Room
DEV CommunityThe Giantsread at source
ctx.filter does nothing in Safari: how to detect it, and a blur fallback that matches CSS blur()
ctx.filter = "blur(12px)" is the shortest way to blur something on a 2D canvas. It works in Chrome and Firefox. In Safari, and so in every browser on an iPhone, it does nothing, and it does nothing quietly: no exception, no console warning, and the drawing comes out sharp. I found this the unpleasant way. A face-blur tool I maintain exported the "blurred" region unblurred on iOS. Every test passed, because every test ran in Chromium. This post is the detection and the fallback I ended up with. Why there is no error Safari keeps CanvasRenderingContext2D.filter behind a preference that is off by default (check the compatibility table on MDN for the current state). When the property does not exist, this line is ordinary JavaScript: ctx . filter = "blur(12px)" ; It adds a plain property called filter to the context object. Reading it back returns the string you wrote, so the usual "set it and see whether it stuck" test says yes. Detect it on the prototype The property is real only if the prototype has it: let filterSupport : boolean | undefined ; export function canvasFilterSupported ( ) : boolean { if ( filterSupport === undefined ) { filterSupport = typeof CanvasRenderingContext2D !== "undefined" && "filter" in CanvasRenderingContext2D . prototype ; } return filterSupport ; } The fallback: three box blurs A Gaussian blur can be approximated very closely by running a box blur three times. The widths of the three boxes for a given standard deviation come from Peter Kovesi's "Fast Almost-Gaussian Filtering"; Ivan Kutskir's write-up of it is where most JavaScript versions come from, this one included. /** Widths of `n` box blurs whose sum approximates a Gaussian of `sigma`. */ export function boxSizesForGauss ( sigma : number , n = 3 ) : number [ ] { const wIdeal = Math . sqrt ( ( 12 * sigma * sigma ) / n + 1 ) ; let wl = Math . floor ( wIdeal ) ; if ( wl % 2 === 0 ) wl -= 1 ; const wu = wl + 2 ; const m = Math . round ( ( 12 * sigma * sigma - n * wl * wl - 4 * n * wl - 3 * n ) / ( - 4 * wl - 4 ) , ) ; return Array . from ( { length : n } , ( _ , i ) => ( i m ? wl : wu ) ) ; } CSS blur(12px) means a standard deviation of 12 px, so sigma here is the same number you would have put in the filter string. Each box blur is two passes, one along rows and one along columns, and each pass is a sliding sum: add the pixel entering the window, subtract the one leaving. The cost per pixel does not depend on the radius. function boxPass ( src : Uint8ClampedArray , dst : Uint8ClampedArray , width : number , height : number , r : number , horizontal : boolean , ) : void { const lines = horizontal ? height : width ; const len = horizontal ? width : height ; const step = horizontal ? 4 : width * 4 ; const last = len - 1 ; const inv = 1 / ( 2 * r + 1 ) ; for ( let line = 0 ; line lines ; line += 1 ) { const base = horizontal ? line * width * 4 : line * 4 ; for ( let c = 0 ; c 4 ; c += 1 ) { const o = base + c ; let sum = 0 ; for ( let i = - r ; i r ; i += 1 ) { sum += src [ o + Math . min ( last , Math . max ( 0 , i ) ) * step ] ; } for ( let i = 0 ; i len ; i += 1 ) { dst [ o + i * step ] = sum * inv ; sum += src [ o + Math . min ( last , i + r + 1 ) * step ] - src [ o + Math . max ( 0 , i - r ) * step ] ; } } } } export function gaussianBlurRGBA ( data : Uint8ClampedArray , width : number , height : number , sigma : number , ) : void { const tmp = new Uint8ClampedArray ( data . length ) ; for ( const size of boxSizesForGauss ( sigma ) ) { const r = ( size - 1 ) / 2 ; if ( r 1 ) continue ; boxPass ( data , tmp , width , height , r , true ) ; boxPass ( tmp , data , width , height , r , false ) ; } } The Math.min / Math.max clamps repeat the edge pixel past the border. That is a deliberate difference from ctx.filter , which blurs in the transparency outside the image and leaves a soft, see-through rim. For a photo you are about to export, a solid edge is the better result. Blur a smaller copy A wide blur throws away fine detail, so it does not need full resolution. The fallback shrinks the image by k , blurs with radius / k , and scales back up. k is chosen so the blur on the small copy is still at least 4 px wide; below that the box approximation gets coarse. export function blurCanvas ( source : HTMLCanvasElement , radius : number ) : HTMLCanvasElement { const out = document . createElement ( "canvas" ) ; out . width = source . width ; out . height = source . height ; const ctx = out . getContext ( "2d" ) ; if ( ! ctx ) throw new Error ( "Canvas 2D context unavailable" ) ; if ( radius 0 ) { ctx . drawImage ( source , 0 , 0 ) ; return out ; } if ( canvasFilterSupported ( ) ) { ctx . filter = `blur(${radius}px)` ; ctx . drawImage ( source , 0 , 0 ) ; ctx . filter = "none" ; return out ; } const k = Math . max ( 1 , Math . floor ( radius / 4 ) ) ; const w = Math . max ( 1 , Math . round ( out . width / k ) ) ; const h = Math . max ( 1 , Math . round ( out . height / k ) ) ; const small = document . createElement ( "canvas" ) ; small . width = w ; small . height = h ; const sctx = small . getContext ( "2d" ) ; if ( ! sctx ) throw new Error ( "Canvas 2D context unavailable" ) ; sctx . imageSmoothingQuality = "high" ; sctx . drawImage ( source , 0 , 0 , w , h ) ; const image = sctx . getImageData ( 0 , 0 , w , h ) ; gaussianBlurRGBA ( image . data , w , h , radius / k ) ; sctx . putImageData ( image , 0 , 0 ) ; ctx . imageSmoothingQuality = "high" ; ctx . drawImage ( small , 0 , 0 , out . width , out . height ) ; return out ; } At a 16 px radius k is 4, so the pixel loop touches one sixteenth of the pixels. On a 12-megapixel phone photo that is the difference between a pause and a freeze, and it keeps the ImageData buffer small on a device that does not have much memory to spare. Two related traps Drop shadows. filter: drop-shadow(...) has the same problem. The canvas shadow properties work everywhere, with one conversion: shadowBlur is twice the standard deviation, so a CSS drop-shadow(0 8px 12px …) becomes shadowOffsetY = 8 and shadowBlur = 24 . Anything else in the filter string. brightness() , grayscale() , contrast() and the rest are equally inert. They are per-pixel operations, so a short loop over getImageData replaces them. Testing the Safari path without Safari You can remove the property in Chromium and run the same tests against the fallback: await page . evaluate ( ( ) => { delete CanvasRenderingContext2D . prototype . filter ; } ) ; Run it after the page has loaded. If your detection caches its answer like the one above, reset the cache too, or delete the property before the first call. Where this runs The code above is what blurs faces and licence plates in the face blur tool on Imagic AI, a set of free image tools I build. The blur happens in the browser, so the check matters most on exactly the devices where it used to fail.
DEV CommunityThe Giantsread at source
I Built a Script to Diff Website Screenshots and Found Bugs I Missed for Months
So I had this problem. We deploy to production pretty frequently -- sometimes twice a day -- and every once in a while something visual breaks. A button moves, a font changes, some CSS gets overridden by a new component. The kind of stuff that doesnt show up in unit tests. For a while I was just... manually checking pages after deploys. Open the site, click around, squint at things. You know how that goes. Sometimes I'd catch issues, most of the time I convinced myself everything looked fine. Then one day a client sent a screenshot of our pricing page where the CTA button had disappeared. It had been gone for 4 days. Four days. Nobody on the team noticed. The pixel diff approach I wrote a quick script that takes screenshots of key pages and compares them pixel-by-pixel against a baseline. Nothing fancy -- headless Chrome, save PNGs, compare with pixelmatch. If the diff exceeds a threshold, flag it. const pixelmatch = require ( "pixelmatch" ) ; const { PNG } = require ( "pngjs" ) ; const fs = require ( "fs" ) ; const img1 = PNG . sync . read ( fs . readFileSync ( "baseline.png" ) ) ; const img2 = PNG . sync . read ( fs . readFileSync ( "current.png" ) ) ; const diff = new PNG ( { width : img1 . width , height : img1 . height } ) ; const numDiffPixels = pixelmatch ( img1 . data , img2 . data , diff . data , img1 . width , img1 . height , { threshold : 0.1 } ) ; console . log ( "Changed pixels: " + numDiffPixels ) ; Simple enough. But the first run was a disaster -- every page flagged because of dynamic content. Timestamps, user avatars, ad slots, cookie banners. The noise was unbearable. What actually worked Had to get smarter about it. Added masking for dynamic regions, ran comparisons only on specific viewport sizes, and set different thresholds per page. The checkout page gets a tight threshold (even small shifts matter there), blog pages get a looser one. The biggest win was scheduling it to run after every deploy and dumping results into Slack. No more manual checking. If something breaks visually, I know within minutes. Couple things I learned the hard way: Fonts load differently between runs sometimes. Had to add a wait-for-fonts step or I'd get false positives from text rendering slightly differently. Responsive breakpoints matter . A bug at 768px width might not show at 1440px. I capture both now. Dark mode doubles your work . If you support it, you gotta screenshot both themes. I... didn't at first. Guess where the bugs were hiding. The annoying parts Maintaining baselines is tedious. Every intentional design change means updating screenshots. I tried automating that too -- if the PR is merged and approved, auto-update baselines -- but it still requires someone to eyeball the diff first. Also storage. Full-page screenshots at 2x resolution add up fast. Had to set up rotation to keep only the last 30 days. Its not perfect but its caught probably a dozen visual regressions that would have otherwise shipped to users. The setup took a weekend. Honestly should have done it way sooner. Anyone else doing visual regression testing? Curious what tools or approaches work for you.
DEV CommunityThe Giantsread at source
How to Choose Private S3-Compatible Storage for AI-Generated Images (US/EU SaaS)
Store the image privately, record ownership in your application database, and issue a short-lived signed URL only after an authorization check. That is the least complex design for a property-management SaaS that keeps AI-generated images in US or EU regions. It also gives you a clean boundary: the app decides who may see an image; object storage moves the bytes. Short answer: choose private S3-compatible object storage with presigned links when your galleries and training artifacts are user-owned and access-controlled. Infrai is a good fit when one HTTP contract across backend services matters, while Amazon S3, Cloudflare R2, DigitalOcean Spaces, or Backblaze B2 are stronger choices when you need public delivery, versioning, object lock, or mature replication controls. Start with the access decision, not the vendor An AI image has two identities. The first is a business record: tenant, property, job, prompt, retention date, and moderation state. The second is a storage key such as tenant_42/job_991/image.png . Keep the first identity in your database. Use the second for bytes and predictable listing. That split matters because listing supports prefix filtering, not a metadata query. A key prefix like tenant_42/job_991/ makes a gallery lookup boring and reliable. Searching object metadata for “all images from a lease renewal” will not. The request flow is short. The browser asks your API for an image. Your API checks the session and the database row. Your API asks storage for a signed URL. The browser downloads the private object. No permanent public URL becomes an accidental authorization policy. Keep it private. Lifecycle cleanup is separate from access. A one-day minimum lifecycle interval cannot express “delete in 30 minutes,” so a worker should perform urgent deletion and let lifecycle handle the slower safety net. I would also write a retention test that creates an image, issues a 15-minute link, removes the database permission, and verifies that a new link is refused. How should a Node.js SaaS choose private object storage for AI-generated images? Here is the field guide I use for this exact workflow. “S3-compatible” means a familiar request style; it does not mean identical guarantees. Option Best fit Trade-off to record Amazon S3 Compliance-heavy image archives, Object Lock, versioning, and deep IAM More provider-specific policy and billing detail to operate Cloudflare R2 Teams already centered on Cloudflare's edge and delivery tools Validate replication and egress requirements for each region DigitalOcean Spaces A small SaaS that wants straightforward private buckets Feature surface is narrower for demanding retention programs Backblaze B2 Cost-conscious storage with S3-compatible access and native tools Migration and cross-region recovery need a deliberate design Infrai storage One REST boundary for private objects and other backend capabilities No public-read ACL, versioning, object lock, or server-side metadata search Infrai exposes one REST API over plain HTTP from any language, without an SDK, with a one key, one bill model for other backend capabilities too. That is useful at the handoff boundary. Swapping the provider behind that capability does not force every application service to learn a new client, and the public discovery surface publishes schemas and runnable examples so the contract is inspectable before implementation. That recommendation has a clear limit. Do not pick this path for a static image host, an always-public CDN URL, or a compliance archive that requires WORM retention. There is no public/public-read ACL, no object versioning or object lock, and no If-Match conditional write. For those requirements, stick with S3 or a specialist that documents the exact control. Browser-direct uploads also need CORS rules supplied through your chosen bucket setup; there is no separate self-service CORS route to assume. A minimal signed-download handler in TypeScript The application owns authorization. Storage only signs the already-approved object. The example uses the documented presign route and treats a retry as a normal production event: explicit method, Bearer auth, idempotency key, status checking, and exponential backoff for 429 . const apiKey = process . env . INFRAI_API_KEY ; if ( ! apiKey ) throw new Error ( "INFRAI_API_KEY is required" ) ; const bucket = "property-training-private" ; const key = "tenant_42/job_991/image.png" ; const route = "/v1/storage/object/presign/{bucket}/{key}" ; const endpoint = `https://api.infrai.cc${route .replace("{bucket}", encodeURIComponent(bucket)) .replace("{key}", key.split("/").map(encodeURIComponent).join("/"))}` ; let response : Response | undefined ; for ( let attempt = 0 ; attempt 3 ; attempt += 1 ) { response = await fetch ( endpoint , { method : "POST" , headers : { Authorization : `Bearer ${apiKey}` , "Content-Type" : "application/json" , "Idempotency-Key" : `image-link-${bucket}-${key}` , } , body : JSON . stringify ( { method : "GET" , expires_in : 900 } ) , } ) ; if ( response . status !== 429 ) break ; const retryAfter = Number ( response . headers . get ( "retry-after" ) ) ; const waitMs = Number . isFinite ( retryAfter ) ? retryAfter * 1000 : 250 * 2 ** attempt ; await new Promise ( ( resolve ) => setTimeout ( resolve , waitMs ) ) ; } if ( ! response || ! response . ok ) { const detail = response ? await response . text ( ) : "no response" ; throw new Error ( `Presign failed (${response?.status ?? "unknown"}): ${detail}` ) ; } const payload = ( await response . json ( ) ) as { url : string } ; console . log ( payload . url ) ; The URL is a capability with an expiry, not a user record. Store the key and policy in your database, then generate a fresh URL per request. For uploads, apply the same pattern to the documented object-write operation and use a job- or image-specific idempotency key so a worker retry cannot create a second business record. If this boundary matches your system, verify the request schema in the storage presign documentation . Test the boundary before you commit Run the retention drill in both target regions. Confirm that an unauthorized tenant cannot obtain a link, that a missing object produces a handled response, and that a duplicate worker message is harmless. Test the browser origin you actually deploy; CORS is enforced by the browser, not by your TypeScript type checker. Measure time-to-delete, restore steps, egress shape, and audit evidence alongside storage cost. Prices change. The control requirements usually change more slowly, and they should drive the decision. Your mileage may vary by contract and region. I am not sure any single “cheap” label survives a year of egress and support invoices, so keep the worksheet concrete. References Infrai storage documentation MDN: Cross-Origin Resource Sharing AWS S3 pricing AWS S3 presigned URLs Cloudflare R2 documentation DigitalOcean Spaces documentation Backblaze B2 S3-compatible API Further reading The linked sources above cover signed URLs, browser CORS, and each competing storage service.
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Moonswing – a Linux desktop environment built with Flutter
Comments
Hacker News Front PageThe Giantsread at source
Mistral offers three months of Vibe Pro free in Europe
AbduzeedoMulti Author Blogsread at source
Inside the Craft of the Snapple Rebrand 2026 by Deutsch Design
Deutsch Design restores Snapple's 90s racetrack logo in the Snapple rebrand 2026, rebuilt with custom letterforms and flavor-first packaging. The change starts with the mark itself. The navy serif Sna...
Hacker News Front PageThe Giantsread at source
NSA Internal Network Down
Hacker News Front PageThe Giantsread at source
Highly classified US national security communications network goes down
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Atli – MCP server that lets AI agents buy and install travel eSIMs
Comments
Hacker News Front PageThe Giantsread at source
Show HN: Alloy CSS, dialogs, menus and tabs that work with JavaScript off
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Alloy CSS, dialogs, menus and tabs that work with JavaScript off
Comments
Hacker News Front PageThe Giantsread at source
In 27,280 coding agent runs, 64% of inference spend went to runs that failed
Go Make ThingsMulti Author Blogs1 min read
Wasting Time
I saw this on one of the social sites the other day, but I can’t remember which (or who shared it)… “Wasting time” might be one of the strangest accusations we’ve ever invented. Apparently you can waste 2:00 p.m. by sitting under a tree doing nothing. The afternoon was going to pass either way. The Earth was going to rotate either way. But because you didn’t convert those hours into money, errands or improvement, we decided the time itself was wasted.
AbduzeedoMulti Author Blogsread at source
Inside Lamm & Kirch’s 2026 Best Book Design Catalog
Florian Lamm of Lamm & Kirch pairs OT Scholar type with Attila Hartwig’s photos in the Best Book Design 2026 Leipzig prize catalog. There isn’t a horizontal cover title anywhere on the front board...
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Agav – an open-source terminal agent designed to waste fewer tokens
Comments
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: An open virtual office to cowork with humans while your agents work
Comments
The Mozilla BlogBrowsers, engines, etc.2 min read
Has Microsoft wronged you? Firefox opens a complaints line at Microsoft Ignite
This week, Firefox is taking over the streets around the Moscone Center in San Francisco, where Microsoft is holding Ignite, its biggest conference of the year. While they talk about what’s next for Windows, Firefox is taking over the surrounding streets to remind them of what they haven’t fixed: Microsoft hasn’t changed the concerning design […] The post Has Microsoft wronged you? Firefox opens a complaints line at Microsoft Ignite appeared first on The Mozilla Blog .
AdactioTop Front-end Bloggersread at source
Reading Eat the Ones You Love by Sarah Maria Griffin.
W3C NewsBrowsers, engines, etc.1 min read
W3C opens Technical Architecture Group (TAG) election
The W3C Advisory Committee, having nominated nine individuals, is invited today to vote until 15 December 2026 to fill five seats in the W3C TAG election.
Smashing MagazineThe Giants10 min read
Meet AI 2027 Conference (Dec 1)
Roll up your sleeves! Meet shiny new [AI 2027 Conference](https://smashingconf.com/ai-2027-conference), a friendly online conference on AI-ready design systems, AI + Figma and AI design patterns. What to expect in 2027 and where teams are getting AI right. [Jump to tickets.](https://smashingconf.com/ai-2027-conference/registration)
Darek KayMore Front-end Bloggers1 min read
#0200
Red and purple firework next to a tower. Green and yellow smoke below the tower. The top of the tower is illuminated.
AdactioTop Front-end Bloggersread at source
The nature of my job has completely changed · Rach Smith’s notes & nuggets
My almost life long, enduring special interest has been writing code to create things. I like to think I’m pretty good at it. Instead of doing that, I’m writing requirements, answering questions, reading and reviewing lines and lines (and lines), and QA testing the results. There’s no flow to be found in this approach. Instead of my workday flying by, I’ll work 4 hours and it will feel like 6. I’m exhausted from parsing so much information. I also can’t go back. adactio.com/links/22837
AdactioTop Front-end Bloggersread at source
Computing with CSS Layout
This document tries to answer one question: how much can CSS compute on its own? A heckuva lot, as it turns out! I don’t understand all of this, but I’m very impressed. adactio.com/links/22836
Flavio CopesMore Front-end Bloggersread at source
A deep dive into ChatGPT Sites
ChatGPT Sites turns a prompt into a hosted website or small web app. How to use it step by step, what runs under the hood, what hosting will cost, and its limits.
Flavio CopesMore Front-end Bloggersread at source
How to use OpenCode Browse
OpenCode Browse lets a coding agent use your real Chrome through an MCP server and an extension. I installed it, paired it, and tested handoffs, lent tabs and the limits.
Smashing MagazineThe Giants8 min read
AI Sped Up The Build: How Can Accessibility Testing Keep Up?
AI has sped up how teams design and build, but quality assurance (QA) testing hasn’t kept pace, and the web may be getting less accessible. Drawing on new research, Andrew Chung explains what separates the teams whose accessibility efforts are keeping up, and how to embed human judgment into AI-enabled workflows without slowing delivery.
HTML All The ThingsPodcastsAudioListen
How to Make a Website: 4 Decisions You Need to Make First
Building a website is easier than ever, but choosing the technology shouldn't be your first step. In this episode, Matt and Mike discuss four important decisions to make before building a website, whether you're a small business owner or a developer working with clients. In this…
JavaScript WeeklyMulti Author Blogsread at source
The top 10 things AI gets wrong in web development
#811 — November 17, 2026 Read on the Web JavaScript Weekly npkill 1.0: Not Just for node_modules Anymore — npx npkill has long offered a way to find and remove waste from node_modules folders. Its first release in two years now also hunts down caches and build outputs like .next and .turbo , with 'profiles' for 20 ecosystems. If you're new to the tool, its homepage provides a good introduction. Juan Torres Agents Didn’t Clear Your Plate. They Dumped Reviews on It — Your agents write PRs in minutes, then eat your afternoon in review. When did ‘saving time’ start to mean babysitting agents’ work? Meticulous shows the exhaustive impact of every PR, with no developer effort. Devs at Dropbox & ElevenLabs have their afternoons back. You can too. Meticulous sponsor UI SDK: Headless UI Behaviors for React, Vue, Svelte, & Solid — A new library from shadcn and Vercel that provides 50+ accessible, low-level behaviors, like roving focus, typeahead, popups, and drag and drop, that you compose into components (for several frameworks, plus Web Components). Vercel 💡 𝕏 As shadcn says : "You and I don't need the same interfaces. We need the same interface behaviors." The idea is an agent, say, can generate whatever UI suits a task, with reusable focus, keyboard, and accessibility behaviors built in. IN BRIEF: Solid 2.0 is now stable, with 2.0.0 now on npm and the docs updated to match. There's no official announcement post (beyond the earlier Solid 2.0 RC posts ) so expect more on this soon. The Chrome team has proposed a Cross-Origin Storage API for sites to share large assets like AI models and WASM modules, so users would only have to download them once. The cloud-based JavaScript hosting service Val Town is winding down with services ending January 10 and the code being open sourced in February. The Bun team has published a dense technical tour of how its in-development ahead-of-time compiler works . RELEASES: Prettier 3.10 – The code formatter now supports the latest JavaScript proposals and new Flow syntax, and adds an opt-in plugin that swaps in the Zig-based Yuku 's JS/TS parsers for speed. 🎨 p5.js 2.4 – The creative coding library expands its SVG and 3D model support. Here's a starter sketch if you want to play quickly. 🔒 Node.js v26.13.1 (LTS) , v24.22.3 and v22.23.5 – The security releases we mentioned last week fix an HTTP/2 flaw that lets clients crash a server and an HTTPS bug that can leak other connections' memory. PixiJS 3D – The popular 2D rendering library's official 3D engine is now in open beta. It's WebGPU-first, with a WebGL 2 fallback. 📖 Articles and Videos 📊 e18e's Ongoing Benchmarks of JavaScript Meta-Frameworks — The e18e performance initiative tracks releases of frameworks across the ecosystem (e.g. Nuxt, Astro, SvelteKit, SolidStart, and more), measuring everything from install size and build times to rendering speed. This dashboard is the place to dive in. e18e 🤖 The Top 10 Things AI Gets Wrong in Web Development — The Chrome team examines where coding agents fall back on dated techniques, like hand-rolled focus traps instead of inert and JS overlays instead of popover , alongside gaps in passkey implementations and XSS defenses. A handy checklist for humans too. Philip Walton (Google) AI Security for Modern JavaScript & TypeScript — Traditional tools miss logic gaps. SonarQube Hunter Agent catches broken access control in your JS/TS CI/CD pipeline. SonarSource sponsor How a Third-Party Script Turned Malicious on Major Sites — An attacker exploited a flaw in Optimizely's A/B testing platform to inject a ( now removed ) malicious script into pages served to end users. Scott's analysis found it on sites including Zoom, the BBC, and GitLab, and shows how CSP can, and did, help. Scott Helme (Report URI) 💡 Third-party scripts are an increasingly common attack vector, as Polymarket's users recently found . If you load any, brush up on CSP and Subresource Integrity , and if you provide them, see how Fathom secures theirs . How Promises Really Resolve, Explained via a WebKit Bug — A contrived promise that should have thrown instead caused Bun and Safari (both of which use JavaScriptCore ) to hang. Alistair fixed the bug and uses it to explain what resolve() actually does and why resolved isn't 'a real promise state' . Alistair Smith The Web Is More Than Enough — A reminder of how the vast array of powerful web platform APIs enables the development of complex apps in the browser, particularly as AI reduces the headaches involved in tying them together. Paul Ford Your JS Error Is Lying to You — Why can JSON.stringify(err) unexpectedly leave you with {} ? Gabor presents a tour of what an Error holds, and how much of that makes it through stack traces, cause chains, worker boundaries, and loggers like Pino and Winston. Gabor Koos 📄 How 13,000 Local Variables in a Function Overflowed V8's Stack – And why would that ever happen? It was the output of an OCaml to JS transpiler… :-) Jérôme Vouillon 📄 A Universal XSS in uBlock Origin via Its Element Picker – Leans on an interesting (and now fixed) postMessage and iframe exploit chain. Smitty van Bodegom 📄 Migrating 10,144 Tests from Jest to Vitest in Three Weeks Daniele Rossino 🛠 Code & Tools BrowserPod 4.0: A Linux-Like MicroVM for the Browser — A WASM-powered sandbox that runs Node, npm, git, and bash in the browser. Previously a metered service, v4.0 is free for any use, though it's not open source, and you must load it via their CDN (but no account or API key is needed). Leaning Technologies 💡 Going somewhat deeper, Nitro creator Pooya Parsa has compiled the actual Linux kernel to WebAssembly ( repo ). It boots to a shell in under a second in modern browsers, or via npx unkernel (tip: use halt to exit!) . Debug Errors and Agents Faster: Sentry Changelog Live — A walkthrough of what’s new in debugging, from fixing prod bugs with Seer to tracing your agents. Register today . Sentry sponsor Kitesurf: Cloudflare's Browser Engine Now Open Source — An experimental browser for agents we featured in August. Mostly written in TypeScript and runs JavaScript in V8 isolates on Workers , with Rust compiled to WASM for layout and painting. There's no Chromium, and Puppeteer can drive it. Cloudflare File Viewer: A Multi-Format File Viewer for Internal Apps — Read-only views for Office, PDF/OFD, CAD, archives, email and other complex formats, with integrations for React, Vue, and Svelte. The docs site has demos showing off the formats covered. Flyfish Dev Flashwright: A Faster, API-Compatible Playwright Fork — Keeps Playwright's API and test runner, but reuses a browser context per worker and doesn't wait for animations to settle, plus similar tricks. Benchmarks show a ~2-4x speedup, while this post explains how it works . Codebeast React Flow 13: The Node-Based UI Library Gets Faster — The first major release in two years cuts re-renders in large flows, with new useNode and useEdge hooks. Vue Flow has joined the xyflow family too. xyflow SlickGrid 6.0 (above) – Long-standing data grid component. Now with zero dependencies, plus pinning on all four sides and sticky rows and columns. Examples and introductions on the project homepage . XState v6 Beta – First beta of the state machine/actor library's next major version. The core API is considered stable and you can try it with xstate@beta . 🕹️ Excalibur 1.0 – After 13 years, the 2D TypeScript game engine reaches v1 with 2D lighting, a plugin API, and a rebuilt Web Audio mixer. Sample games here . 🕹️ JSNES 3.0 – JavaScript NES emulator. Now has a cycle-accurate core that passes all 134 'AccuracyCoin' tests. There are playable demos here . type-fest 6.0 – Popular collection of essential TypeScript types ( listed here ). v6.0 adds 120 new types and requires TypeScript 6. Fontkit 3.0 – Advanced font engine for Node and the browser. Now ESM-only, with a new core export so you can ship only the formats needed. dts-bundle-generator 10.0 – A tool to tree-shake and bundle a project's TypeScript declarations into one file. 📰 Classifieds 📄 Parsing PDFs for a RAG or invoice pipeline? Foxit compares 10 document parsing APIs on output format, billing units and accuracy claims. 🌙 Agents can test mobile code at 3am. Expo Simulators gives them cloud simulators, so the loop runs while you sleep. Stop being the middle manager for your coding agents. CodeAF runs the org, and only what no manager can settle reaches you. #1 on DeepSWE. 📢 Elsewhere in the ecosystem You Don't Need jQuery , the long-standing guide to replacing jQuery methods with plain JavaScript, has had a big v3.0 update . Internet Explorer fallbacks are out in favor of modern one-liners like el.replaceChildren() , structuredClone() , and Promise.withResolvers() . Adam Argyle shares PropFLIP , a take on FLIP (First, Last, Invert, Play) animations where four @property custom properties do the inverting and a CSS transition does the playing. AWS has released AWS Emulator , an official local emulator you can point your AWS SDK or CLI at, covering hundreds of its service interfaces. It's largely aimed at agents, and was built with them too . 🎂 Happy birthday to Svelte ! Svelte turned ten years old on Monday (Rich Harris made its first commit on November 16, 2016).
Twilio BlogMulti Author Blogsread at source
Builders in the Spotlight: How EMEA Champions Brought SIGNAL Paris to Life
Go behind the scenes at SIGNAL Paris with Twilio Champions Mattieu Detaille (Elora) and Oleg Davydov (Davydov Consulting). Watch their floor takeover vlog, catch Red Couch CX Hot Takes, and explore practical architectural lessons on Voice AI agents, Twilio Media Streams, and unified customer data in production.
Twilio BlogMulti Author Blogsread at source
Twilio Expands Conversations Layer for AI Agent Supervision
Supervise AI agents effectively with Twilio Conversations and our new operators for task completion and hallucination detection to ensure quality at scale.
Twilio BlogMulti Author Blogsread at source
From Voice AI Demo to Production: Why Infrastructure and Agent Supervision Matter
Explore Twilio’s new Voice AI infrastructure features from Conversation Relay, Agent Connect, and Conversation Intelligence.
Heroku BlogCompany/Startup Blogs4 min read
Heroku at KubeCon Recap: Meeting Builders Where They Build
KubeCon in Salt Lake City was amazing this year. Spending time with and engaging the cloud-native community provided insight into what developers need as AI workflows and AI-assisted code move into production. During our keynote on the main stage, we shared how Salesforce uses Heroku to securely host more than 20k apps using cloud-native technology, […] The post Heroku at KubeCon Recap: Meeting Builders Where They Build appeared first on Heroku .
AbduzeedoMulti Author Blogsread at source
Packaging Design: Olearius Olive Oil by vrai studio
For French olive oil house Olearius, vrai studio pairs dark glassmaker flasks and GPS grove coordinates in restrained packaging design. Nine canary-yellow boxes form a tight grid in the opening frame,...
AbduzeedoMulti Author Blogsread at source
THE OBJECT 01: 3D-Printed Chair by Nako Baev
Nako Baev built THE OBJECT 01, a modular 3D-printed chair in recycled PETG that weighs 20 kg and pairs brutalist mass with Japanese restraint. At 1.320 meters long and 0.875 meters tall, the lounge ch...
AbduzeedoMulti Author Blogsread at source
Allo: Open Source Typography by Josh Puckett
Josh Puckett built Allo, a free open source typography family with three variable axes, true obliques, and a playful interactive specimen site. Josh Puckett started Allo from Rasmus Andersson’s Inter ...
AbduzeedoMulti Author Blogsread at source
Sports: MLB Brand Identity by Mother Design
Mother Design rebuilds the MLB brand identity on Modernize Nostalgia: five custom typefaces, the 1968 batter mark, and the shapes of the game. The idea is a sentence, not a logo. Mother Design calls i...
AbduzeedoMulti Author Blogsread at source
Die Grotesk: Klim Type Foundry Reexamines Neo-Grotesque Type
Klim Type Foundry’s Kris Sowersby confronts Helvetica’s 70-year shadow in Die Grotesk, a variable neo-grotesque type built for optical scale. Giant black Grotesk letters cut straight across a blood-re...
Level AccessCompany/Startup Blogs12 min read
WCAG Conformance Levels: How High Should You Aim?
WCAG has three conformance levels: Level A (minimum), Level AA (the common legal benchmark), and Level AAA (highest). Most organizations should target AA, The post WCAG Conformance Levels: How High Should You Aim? appeared first on Level Access .
AdactioTop Front-end Bloggersread at source
Monday afternoon house session
SitePointThe Giantsread at source
Is Kling 4.0 the Right AI Video Generator for Your Project?
null Continue reading Is Kling 4.0 the Right AI Video Generator for Your Project? on SitePoint .
SitePointThe Giantsread at source
Hostinger VPS in 2026: Hands-On With the AI-Managed VPS
Hands-on with Hostinger’s KVM 1 VPS: deploy a Node.js app in Docker and let Hostinger Agent handle HTTPS, the firewall and a reboot. Plans, specs and pricing. Continue reading Hostinger VPS in 2026: Hands-On With the AI-Managed VPS on SitePoint .
Flavio CopesMore Front-end Bloggersread at source
A deep dive into ChatGPT Wallet
ChatGPT Wallet lets your dot pay with a one-time token, not your card number. How to add a card, approve purchases, stay safe, and get your website ready.
Auth0 BlogCompany/Startup Blogsread at source
Building a Secure MCP (Model Context Protocol) Server with Auth0
Learn how to build an MCP server in Go and secure it with Auth0 using OAuth 2.1, PKCE, and RBAC-backed scopes, so AI agents only see the data their user is authorized to access.
CodePenCompany/Startup Blogs4 min read
Chris’ Corner: Sourcemaps
Sourcemaps aren’t new, but they’re still fascinating. Neciu Dan recently wrote a good overview article. The CSS and JavaScript we write are likely processed before they become the CSS and JavaScript sent over the internet to a browser. An obvious one is that you might author TypeScript, which is then processed into JavaScript, then bundled, […]
CSS-TricksThe Giantsread at source
Staggering Scroll-Driven Animations with animation-range-start
Imagine a CSS karaoke machine that displays a ball bouncing on text that incrementally highlights, based on progress through via speech recognition and running that kind of animation as a single predictable, holistic effect driven by one progress value. Staggering Scroll-Driven Animations with animation-range-start originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.
AbduzeedoMulti Author Blogsread at source
Kuda Brand Identity Is a Masterclass in More Life by Barkas
Barkas builds the Kuda brand identity on More Life: a stacked wordmark, custom Kuda Modena type, and a deep Lagos purple. The system starts from a sentence, not a logo. "If your bank isn't helping you...
Level AccessCompany/Startup Blogs13 min read
Accessibility Testing Tools: A Guide for Enterprise Teams
Accessibility testing tools like scanners, browser extensions, and monitoring platforms find barriers at scale. Pair them with manual testing to catch what automation The post Accessibility Testing Tools: A Guide for Enterprise Teams appeared first on Level Access .
Flavio CopesMore Front-end Bloggersread at source
AI is eroding my coding skills, and I don't care
63% of developers in a Syntax survey say their coding skills are diminishing. Mine are too. Here is why it doesn't worry me, and which skills I still keep.
Frontend Masters BlogMore Front-end Bloggers11 min read
Browsers To Try If You’re Being Forced Off Arc
Arc will sunset on December 22, 2026. Here's some personal notes from trying a variety of a new crop of alternatives. There's some good ones!
David BushellMore Front-end Bloggers2 min read
Visited links are purple
A few weeks ago Kev Quirk asked: Do you use :visited on links? — and I said to myself: No! I don’t use visited links… but why don’t I use visited links? TL;DR: I’ve gone and styled visited links, and they’re purple. Blue and purple I did a cursory five minutes of research and found Wikipedia still […]
SitePointThe Giantsread at source
How to Test WCAG 2.2 in CI: What axe-core Misses
null Continue reading How to Test WCAG 2.2 in CI: What axe-core Misses on SitePoint .
Jeffrey Zeldman PresentsMore Front-end Bloggers3 min read
Standout Designs for the Web
Andy Clarke’s Standout Designs for the Web ships Wednesday and is now available for pre-order. I had the honor of writing the Foreword, reprinted here: Foreword I first met British art director, writer, and illustrator Andy Clarke at the SXSW Interactive festival in Austin, Texas. At the time, SXSW was the number one destination for […] The post Standout Designs for the Web appeared first on Jeffrey Zeldman Presents .
HeyDesignerDeveloper/Designer Newsread at source
Continuing a style isn't the same as starting one
Working with designers, Design engineering has a handoff problem, The CSS caret-* properties and custom caret accessibility.
SitePointThe Giantsread at source
Build Live Video Chat With WebRTC: From First Call to Production Debugging
null Continue reading Build Live Video Chat With WebRTC: From First Call to Production Debugging on SitePoint .
SitePointThe Giantsread at source
What Is the Best UI design Tool? 8 Tools Compared by the Job They Do (2026)
null Continue reading What Is the Best UI design Tool? 8 Tools Compared by the Job They Do (2026) on SitePoint .
Speckyboy Design MagazineDeveloper/Designer News3 min read
The Most Profitable Service Your Agency Isn’t Selling
Stop giving away hosting and maintenance. Productize care plans into recurring revenue, improve retention, and turn free favors into a profitable agency service. The post The Most Profitable Service Your Agency Isn’t Selling appeared first on Speckyboy Design Magazine .
Net NinjaYouTube ChannelsVideoWatch on YouTube
"Anti-Slop" Designs with Impeccable (a Crash Course) #4 - Live Mode