Frontend Feeds

Today

Front-end, in one read.

The latest from the sources worth following, newest first.

  • DEV CommunityThe Giantsread at source

    The Patch Race: Watching CVE-2026-102764 Move From Targeted Exploit to Mass Scanning

    The Patch Race: Watching CVE-2026-102764 Move From Targeted Exploit to Mass Scanning Exploitation patterns on edge-device vulnerabilities change at a predictable point. Before disclosure it is selective and quiet. After disclosure it is automated, indiscriminate and loud. CVE-2026-102764 is at that boundary now. What the timing data shows The National Vulnerability Database published its record on 2026-10-15. CISA added the CVE to the Known Exploited Vulnerabilities catalog on 2026-10-16, with remediation due 2026-10-19 and forensic triage required under BOD 26-04, listing ransomware association as unknown. The Record reports that exploitation predates disclosure by weeks: Mandiant traced attacks to 29 August, and BeyondTrust was first alerted on 27 September after an unrelated vendor's edge-appliance attack became public. Google Threat Intelligence Group is quoted warning that the actor — tracked as Armory Castle or UNC5221 — conducts widespread opportunistic exploitation after public disclosure, racing to reach unpatched devices. The group did this with Ivanti and Citrix products. That is the transition to watch: an exploitation window that was narrow and targeted expanding into one that any copycat can join, because the technical detail is now public and the vulnerable population is measurable. Why measurement matters during the transition The population that matters changes between the two phases. During targeted exploitation, the relevant question is who is interesting to the attacker. After disclosure, the relevant question is who is still unpatched and reachable, which is a measurable quantity. ZoomEye reported 2,185 assets matching app="Bomgar" on 2026-10-26. That number describes reachable product assets at a point in time. It is a denominator, and a reminder that the sum of individual patch decisions is a global exposure surface. For a defender, the useful use of measurement during the race is comparison over time. A count taken today and the same query taken in a week shows whether an organisation's own estate is shrinking, and whether the global population is responding to the advisory. A static count tells you less than the trend. What the race looks like from the defender side Three observable signals mark the shift from targeted to opportunistic exploitation. | Signal | Where to look | What it suggests | | --- | --- | --- | | Failed authentication bursts against the appliance | Appliance authentication logs, identity provider sign-in logs | Automated credential or protocol probing rather than a chosen target | | Requests to endpoints that only the vulnerable code path reaches | Appliance web server logs, reverse proxy logs | Exploit attempts rather than normal administrative traffic | | Sudden outbound connections from the appliance | Egress monitoring, firewall logs | Post-exploitation activity after a successful file operation | No single signal is conclusive. Together they distinguish a device that is being swept from one that is being worked on. The patch is not the finish line Two facts from the reporting change what "patched" means here. First, the actor obtained every credential the appliance stored, so anything the appliance could reach is in scope for rotation regardless of patch state. Second, the actor modified files that survive reboots and configuration resets, so a patched appliance can still be running attacker-modified components. That makes the post-patch verification step substantive rather than administrative. Confirm the build, confirm the integrity of the running files, and confirm the credential set is new. Where the race ends Opportunistic exploitation of an edge appliance subsides when the reachable unpatched population is small enough that scanning stops paying. That outcome is the aggregate of individual decisions, and it is the reason a public exposure count is worth tracking rather than dismissing. References The Record, "Suspected Chinese espionage attackers abusing BeyondTrust IT support zero-day": https://therecord.media/beyond-trust-cyberattack-china NVD, CVE-2026-102764: https://nvd.nist.gov/vuln/detail/CVE-2026-102764 CISA Known Exploited Vulnerabilities catalog, CVE-2026-102764: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102764 BeyondTrust advisory BT26-05: https://www.beyondtrust.com/trust-center/security-advisories/bt26-05 ZoomEye search used for the published count: https://www.zoomeye.ai/searchResult?q=YXBwPSJCb21nYXIi

  • DEV CommunityThe Giantsread at source

    One year of Dioxus fullstack in production: the good, the painful

    After a year of Dioxus fullstack in production, the Rust code is the most boring part of my business. CI is the most exciting part, and not in a good way: a release build takes 90 minutes on a GitHub-hosted runner. That year started at my previous job and continued on my own products. Back in April I wrote about why I picked Rust for a production micro SaaS . The short version: slower at the start, cheaper to live with later. This post is the bill. What I'm running SeggWat is an in-app feedback tool for SaaS products. Its dashboard is a Dioxus 0.7 fullstack app inside a Cargo workspace: a backend crate with server functions, an auth crate, and about ten UI crates covering insights, feedback, ideas, boards, widgets and settings. Twelve crates depend on dioxus . Everything sits on PostgreSQL. infra.page is built on the same stack. "Fullstack" means one Rust codebase doing three jobs. It renders on the server, runs server functions as the backend, and compiles the client to WebAssembly so the page becomes interactive. The good One language, all the way down Database query, business rule, server function, button: all Rust. One toolchain, one formatter, one set of habits, one place to look when something breaks. That sounds minor until you're a solo founder juggling several products. I don't have a "frontend brain" and a "backend brain" that each need warming up. I open the workspace and keep going. The same types on both sides This is the one I'd miss most. A struct gets defined once. The database layer returns it, the server function sends it, and the component renders it. When I rename a field, cargo check gives me a list of every place that broke, including the UI. There's no OpenAPI spec to regenerate and no TypeScript interface drifting out of sync with the backend. The win isn't writing code faster. It's refactoring without fear, late at night, with nobody to review it. The door to other platforms stays open Dioxus can target desktop and mobile, including iOS, from the same component model. None of my products needs a native app today. But knowing I could ship one without a rewrite mattered when I decided where to put a year of work. Production is boring That's the whole point. Once it compiles, it mostly just runs. A whole class of "undefined is not a function" bugs never reaches users, so the bugs that do get through are logic bugs. That's where I'd rather spend my attention anyway. The "boring in production" argument from April survived contact with real users. The painful Compile times This is the part Rust evangelists tend to skip. The dashboard compiles twice: once for the server and once to wasm32 for the browser. A dozen Dioxus crates plus a macro-heavy UI add up. Locally it's tolerable on a decent machine. CI is a different story, and the comments in my workflow files read like a diary of it: The WASM build alone takes about 22 minutes on 6 cores. That's a single leaf crate: the dashboard compiled for the browser. A release image takes about 90 minutes on a GitHub-hosted 2-core runner. On my own VPS runner it's around 40, and that's the good version. Clippy got OOM-killed. cargo clippy --workspace --all-targets on the 7 GB hosted runner died with exit code 143 and no diagnostics at all. The fix was a 10 GB swapfile plus CARGO_BUILD_JOBS=1 to cut peak memory. My linter needs swap. At some point I stopped building images on every push to main. They now build on release tags or when I trigger them by hand, because 90 billed minutes per push is a silly way to spend money. What I tried Caching with Swatinem/rust-cache . It helps, but there's a trap. A workflow run can only restore caches from its own ref or the default branch, and GitHub evicts caches unused for 7 days. Once I stopped building on main, release builds kept starting cold. My workaround is almost funny: after a dependency bump, I manually trigger a build on main just to keep the cache warm. Building and testing in one go , so the tests reuse compiled artifacts instead of compiling the world a second time. The mold linker. Nice, but linking was never the bottleneck. Compiling was. A self-hosted runner for the heavy builds. This was by far the biggest win, 90 minutes down to 40. It also means I now maintain a build server. Every one of these helped. None of them changed the underlying math: two compile targets, a big dependency tree and lots of macros means a lot of compiling. "All Rust" comes with an asterisk The business logic is all Rust. The edges aren't. SeggWat's insights page shows charts, and I couldn't find a Rust charting library I'd trust in production. So the charts are Chart.js , loaded from a CDN and wrapped in about 340 lines of JavaScript that Dioxus calls through dioxus-use-js . Styling is Tailwind, so CI also installs Bun and runs the Tailwind CLI before Rust even starts. I'm fine with that. It's pragmatic. But if you're choosing Dioxus specifically to escape JavaScript, know what you're signing up for: Rust, plus some JS glue, plus a JS toolchain in your pipeline. Would I do it again? People ask, "What helps me ship fastest?" The better question is, "What helps me keep shipping without hating my life?" For the backend, the answer is still Rust, and it isn't close. For the frontend, I've changed my mind a bit. If I were building something truly app-like, with heavy client state, offline support or a real mobile app, I'd pick Dioxus again. But most of what I build is dashboards: forms, tables, a few charts and some toggles. For that, I'm paying a 22-minute WASM tax on every release for interactivity I barely use. What's next: Topcoat So my next project is going to use Topcoat , a new fullstack framework from the tokio-rs org, announced in July . It makes the opposite bet from Dioxus. Everything renders on the server, and components are async functions that can query the database directly. For interactivity, you write $(...) expressions in ordinary, type-checked Rust. Topcoat evaluates them on the server for the first render and also translates them to JavaScript, so they re-run instantly in the browser. There's no WASM bundle and no second compile target. #[component] async fn faq ( cx : & Cx ) -> Result impl View > { let open = signal ( cx , || false ); Ok ( view! { button @ click = $ (| _e | open .set ( ! open .get ())) > "What is Topcoat?" button > p : hidden = $ ( ! open .get ()) > "A full-stack Rust framework." p > }) } Example from the Topcoat README. On paper, Topcoat keeps what I love about Dioxus (one language, shared types, no API layer) and removes the part that hurts most, the 22-minute WASM build. To be clear, this is a bet, not a result. Topcoat's README calls it early-stage and experimental, with breaking changes expected. I'm giving up the multi-platform option. And I haven't measured a single build yet. I'll write the follow-up with real numbers: compile times, CI minutes, and whatever I end up missing from Dioxus. If my release build drops from 40 minutes to 10, you'll hear about it. If it doesn't, you'll hear about that too.

  • DEV CommunityThe Giantsread at source

    I Tested GPT-6's Intelligent UI by Building 3 Real Tools (Free Methods Inside)

    Watch the video here: https://www.youtube.com/watch?v=nK0dfocgf9k I just published a new video testing OpenAI's GPT-6 Intelligent UI in a practical way: instead of talking about features in the abstract, I built three working tools inside ChatGPT and checked whether the results were actually usable. The idea behind Intelligent UI is simple. You describe what you want, and ChatGPT builds an interactive interface for it, rather than giving you only text. That sounds useful, but it only matters if the tools work with real inputs and correct results. So I tested it with everyday examples. The first tool was a Bill Splitter. I entered a bill of Rs 4,500 and added a 10% tip. The tool calculated Rs 450 in tip, a total of Rs 4,950, and Rs 2,475 each for two people. That is the kind of small calculation that is easy to get wrong in a hurry, so I checked the numbers rather than accepting them at face value. The second tool was a Budget Calculator. With Rs 4,000 in income and Rs 2,200 in spending, it showed Rs 1,800 left. Again, the value is not in a fancy layout. It is in getting a clear answer from a simple input, without needing a separate app or spreadsheet. The third tool was different: a small school game built inside ChatGPT itself. It shows that this approach is not limited to calculators. The same workflow can produce something interactive that students can use directly, without installing anything extra. I should be honest about one limitation. The ChatGPT Playground route was blocked for me because of sign-in requirements, a US-adults-only restriction, and limited tokens. The video therefore shows the in-ChatGPT path, which is the route that worked and that most readers can try without running into the same block. If you want to try these yourself, the exact prompts for all three tools are in the video description. You can copy them, change the numbers, and see how the tools respond to your own inputs. Watch the video here: https://www.youtube.com/watch?v=nK0dfocgf9k Onyx AI Labs / OnyxIQ is a project from this channel, and you can find it here: https://onyxailabs.gumroad.com

  • DEV CommunityThe Giantsread at source

    Finally, Release Notes That Don't Suck: Automating with LLMs and GitHub Actions

    You know that feeling. It’s Friday afternoon, you’ve just merged a bunch of features and fixes, and now it’s time for the dreaded release notes. You scroll through Git history, try to remember what each commit actually did , then cross-reference Jira to get the full picture. It's tedious, error-prone, and honestly, a soul-crushing task that pulls me away from the fun stuff. For years, I've just… avoided it, or penned the most generic 'bug fixes and improvements' ever. The Problem: Manual Release Notes Are a Grind I’m an indie developer. Every minute I spend on administrative overhead is a minute I’m not building. Manual release note generation was a huge time sink. My releases often had a dozen or more tickets, plus countless small commits. Synthesizing all that into something concise, accurate, and actually useful for users felt like pulling teeth. The worst part? Half the time, the notes were boilerplate anyway because I was too lazy (or busy) to dig deep. I knew there had to be a better way. What I Tried First: Just Feed it to an LLM My initial thought was pretty simple: large language models are good at summarizing, right? So, I wrote a quick Python script to grab git log --pretty=format:"%s" --since="last_release_tag" and fed the raw output to OpenAI's gpt-3.5-turbo. I figured it would just magically spit out perfect release notes. It did not. It was a disaster, actually. The output was either: Too generic: "This release includes various updates and bug fixes to improve application stability." (Yeah, thanks, I already said that.) Too verbose: It would often just rephrase every single commit message, leading to paragraphs of developer-speak nobody cared about. Missing context: My commit messages aren't always perfect. "Fix layout" doesn't tell a user which layout or why it was broken. Crucial context from Jira tickets was completely absent. I tried refining the prompt, telling it to focus on user-facing changes, but without the Jira context, it was essentially guessing. The LLM didn't know if refactor: db migrations was an internal chore or a foundational change enabling a new feature. It needed more. What Actually Fixed It: Context is King After a few frustrating hours – probably half a day, just wrestling with the initial approach – I realized the LLM needed more structured, meaningful data. It needed the why behind the what . That meant integrating Jira. Here’s the pipeline I built and wrapped in a GitHub Action: 1. Grab Git Commits and Extract Jira IDs First, I needed the commit messages since the last release. I use conventional commits (e.g., feat: PROJECT-123 Add user profiles), which made extracting Jira IDs a breeze. I used git log --pretty=format:"%s" "$(git describe --tags --abbrev=0)..HEAD" to get messages between the last tag and HEAD. Then, a simple regex on the commit messages to find [A-Z]{2,}-\d+ patterns. This gave me a unique list of Jira tickets relevant to the changes. 2. Fetch Jira Details For each unique Jira ID, I hit the Jira API. I’d previously done this with the jira-python library for local scripts, but for the GitHub Action, a curl call with secrets.JIRA_API_TOKEN felt more straightforward and less dependency-heavy. I fetched the ticket summary, type (Bug, Story, Task), and status. This provided the crucial context. 3. Combine and Prompt the LLM This was the core. I structured the input for the LLM like this: text Here are recent Git commit messages: feat: PROJECT-123 Add user profiles fix: PROJECT-456 Improve dashboard load time chore: internal cleanup Here are the details for relevant Jira tickets: PROJECT-123 (Story): Implement user profile management PROJECT-456 (Bug): Dashboard slow on large datasets Generate concise, user-facing release notes (3-5 bullet points). Focus on new features, bug fixes, and performance improvements. Exclude internal changes. Group similar items. I found gpt-3.5-turbo-16k was perfectly capable and significantly faster/cheaper than gpt-4 for this task, costing me about $0.05-$0.10 per run. The 16k context window was useful for longer release cycles with many commits. 4. Wrap it in a GitHub Action I created a Python script that performs steps 1-3, and then wrapped it in a GitHub Action. The action triggers on workflow_dispatch for manual runs or push when a new tag is created. It outputs the generated notes to a file and also as an action output, which can then be used by other steps (e.g., creating a GitHub release draft). Here's a simplified snippet of the action YAML: yaml name: Generate Release Notes on: workflow_dispatch: push: tags: - 'v*. . ' jobs: generate_notes: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Set up Python uses: actions/setup-python@v5 with: python-version: '3.10' - name: Install dependencies run: pip install requests # For Jira API - name: Run Release Note Generator id: release_notes env: OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }} JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }} JIRA_EMAIL: ${{ secrets.JIRA_EMAIL }} JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }} run: python .github/scripts/generate_release_notes.py - name: Create Release Draft uses: softprops/action-gh-release@v1 if: startsWith(github.ref, 'refs/tags/') with: tag_name: ${{ github.ref_name }} body_path: RELEASE_NOTES.md # Output from the script draft: true The Payoff: Concise, Accurate, Automated Now, generating release notes is no longer a chore. I push a tag, the GitHub Action runs, and I get a draft release on GitHub with beautifully summarized notes, cross-referencing both Git and Jira. They're concise, user-focused, and crucially, they reflect what actually changed from a user's perspective. It took some elbow grease to set up, especially getting the prompt just right and handling Jira API authentication securely in the action, but it’s paid off immensely in saved time and mental overhead. My releases are smoother, and my users get better, more informative updates. It feels good to finally tame that beast.

  • DEV CommunityThe Giantsread at source

    I parsed Anthropic's S-1 myself. The $80.7B loss is not the story.

    Anthropic publicly filed its Form S-1 today, October 26 — ticker ANT, Nasdaq. Instead of reading the summaries, I downloaded the filing itself from the SEC and parsed it. The document is not small: raw_bytes = 14,169,252 (the single HTML filing, anthropicpbc-sx1.htm) text_chars = 1,630,984 (after stripping tags) words ≈ 243,170 "Claude" = 594 mentions "convertible" = 464 mentions "compute" = 583 mentions That last count matters, because the whole story of this filing is in one table — and in the gap between two numbers in it. The table, copied out by script This is the Consolidated Statements of Operations summary, in millions, exactly as filed: 2023 2024 2025 H1 2025 H1 2026 Revenue $ 41 $ 386 $4,585 $1,163 $16,286 Compute and infra 433 2,522 7,326 2,334 8,945 Total operating expenses 592 3,366 12,645 3,298 16,979 Operating loss (551) (2,980) (8,060) (2,135) (693) Fair-value change (1,045) (5,434) (34,308) (10,942) (72,388) Net loss (1,531) (8,309) (41,965) (12,969) (80,748) Every headline about this filing leads with "$80.7 billion loss." The table says something more interesting. The $80.7B loss is mostly the company getting more valuable Do the subtraction the filing invites you to do: H1 2026 net loss: $80,748M fair-value charge: $72,388M = 89.6% of the net loss operating loss: $ 693M = 4.3% of H1 revenue operating cash flow: +$3,900M (vs -$1,500M in H1 2025) The fair-value line is the change in value of convertible notes, derivative liabilities, and SAFEs. The filing's own footnote says these charges were "primarily driven by an increase in the fair value of our outstanding convertible promissory notes resulting from an increase in our enterprise valuation." In plain English: the company is worth more, so the paper it issued earlier is worth more, so GAAP records an enormous non-cash loss. The more successful the IPO looks, the bigger this number gets. It is a loss that scales with success, which is a strange property for a loss to have. Meanwhile the actual operating business — revenue minus operating expenses — lost $693M on $16,286M of revenue in the half, and generated positive $3.9B of operating cash flow. A year earlier the operating loss was $2,135M on $1,163M of revenue. Revenue grew 14x. Compute grew past a full year in six months revenue, H1 2026 vs H1 2025: 16,286 / 1,163 = 14.0x compute, H1 2026: $8,945M compute, all of 2025: $7,326M compute share of H1 opex: 8,945 / 16,979 = 52.7% Six months of compute cost more than the previous twelve. Compute alone is more than half of all operating expenses — larger than personnel ($3,152M), sales and partnerships ($3,168M), and everything else combined. Whatever else Anthropic is, on the income statement it is a machine for converting capital into compute: the filing says it had raised an aggregate of $141.1B of capital as of June 30, 2026, and held $112.4B in cash plus $19.3B in short-term investments. Two things summaries tend to get loose with Customer concentration. Secondary coverage has circulated a "two customers ≈ 20%" figure. The risk-factor text I extracted from the filing itself says something different and more precise: no single customer was more than 10% of revenue for the nine months ended September 30, 2026, and the top five customers were approximately 25%. It also says the customer base as of September 30 includes more than 11,900 customers at $100,000+ trailing-twelve-month revenue, more than 1,900 at $1M+, and approximately 250 at $10M+. The compute commitments total. The filing says the company has entered purchase commitments and leases "with an aggregate committed spend of more than $" — and then the amount is literally blank in the filed document, an underlined empty space where the number will presumably land in an amendment. Reports putting the total above $600B are assembling it from the component deals, not quoting a filing total — because the filing total isn't there yet. If you cite a single commitments number today, you're citing arithmetic someone else did, not a disclosed figure. Why I parse filings instead of reading threads about them An S-1 is one of the few primary documents in tech that is both complete and adversarially reviewed — lawyers have read every number in it with liability in mind. The gap between the headline reading ("$80.7B loss!") and the table reading (operating loss narrowing to 4.3% of revenue, $3.9B positive operating cash flow, a fair-value charge that grows when the valuation grows) is exactly the gap between a number and what the number measures. The blank where the commitments total should be is the honest part of the document. It says: this number isn't final, so we didn't print one. More filings — and more summaries of filings — could use that restraint. Source: Anthropic, PBC Form S-1, SEC EDGAR (filed October 26, 2026), https://www.sec.gov/Archives/edgar/data/2130357/000162828026067168/anthropicpbc-sx1.htm — all figures above were extracted from that document by script during writing; growth and share percentages are my arithmetic on the filed table.

  • Hacker News Front PageThe Giantsread at source

    Anthropic S-1

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

    Show HN: Printable Calendar Maker

    Comments

  • Hacker News Front PageThe Giantsread at source

    Fixing Tool-Call Accuracy in vLLM

  • Hacker News Front PageThe Giantsread at source

    Peter Thiel, the tech oligarch who believes in the Antichrist

  • Hacker News Front PageThe Giantsread at source

    Writing Is Closer to Thought Than Code

  • SyntaxPodcastsAudioListen

    1050 - Everyone Is Hacking Their TV

    Wes, Scott, and CJ run through the week’s biggest web dev news: everyone’s hacking their TVs, VoidZero open-sourced its Void framework with Cloudflare deploys, OpenCode got hacked, and Anthropic built its own git replacement. Plus DeepSeek V4.1 Flash, Cloudflare’s security audit…

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

    Show HN: Rostr – Give your agents names, remember who's working on what

    Comments

  • Hacker News Front PageThe Giantsread at source

    Tasks as Code: Move Your Tickets into the Repository

  • Flavio CopesMore Front-end Bloggersread at source

    The complete guide to Convex

    Learn Convex by building a real-time app with TypeScript, queries, mutations, authentication, indexes, search, file storage, background jobs, and tests.

  • Flavio CopesMore Front-end Bloggersread at source

    How to use Grok Build

    A detailed Grok Build tutorial covering installation, prompts, plans, permissions, tests, Git, skills, MCP, subagents, sessions, and headless automation.

  • Flavio CopesMore Front-end Bloggersread at source

    A pull request workflow for code written by agents

    Review agent-written code with a practical pull request workflow: focused tests, independent review, human approval, merge queues, and deployment checks.

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

    Show HN: Ultimidi – piano learning web game

    Comments

  • DigitalOcean BlogMulti Author Blogs17 min read

    Whats is Batch Inference? (2027)

    Last week’s support tickets, a 50,000-item product catalog, and a backlog of contracts to summarize. What do these jobs have in common? None of them needs a response in two seconds. But if you run them through the same real-time endpoints as your live traffic, you pay…

  • Net NinjaYouTube ChannelsVideoWatch on YouTube

    GitHub Copilot App Tutorial #2 - Adding Projects

  • Net NinjaYouTube ChannelsVideoWatch on YouTube

    GitHub Copilot App Tutorial #1 - Intro & Setup

  • HeyDesignerDeveloper/Designer Newsread at source

    Nobody asked for the sparkle button

    Entering Atomic Design from the screen, Apple’s Dimensional Drawings, Code review was never about the code.

  • Flavio CopesMore Front-end Bloggersread at source

    Prompt caching, compression, and compaction in coding agents

    Learn how prompt caching, transport compression, and context compaction affect coding agent costs, speed, memory, and usage, with practical examples.

  • AbduzeedoMulti Author Blogsread at source

    Inside Senhor Paulinho’s Brand Identity for Arado 2026

    Arado 2026 by Senhor Paulinho is a brand identity system for Madrasta Dance built on hand-drawn typography, ink textures, and yellow posters. Portuguese graphic designer Paulo Graça (known as Senhor P...

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

    Show HN: Proc-CLI – An agent-friendly CLI tool for process and port management

    Comments

  • AbduzeedoMulti Author Blogsread at source

    Brand Identity: Rothfield by Studio Julius

    Studio Julius builds a calibrated brand identity, custom 16-unit icon system, and tactile studio tools for Australian partner Rothfield. Working behind the scenes rarely gets the spotlight. For decade...

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

    Show HN: How religions evolved? Charts, Maps, Citations

    Comments

  • AbduzeedoMulti Author Blogsread at source

    Typography: Exemplar by Letters from Sweden

    Letters from Sweden has unveiled Exemplar, an expansive multi-script typography family thirty years in the making and carved into Italian Carrara marble. In 1994, type designer Göran Söderström began ...

  • Jim Nielsen’s BlogMore Front-end Bloggersread at source

    Why My Dad Didn’t Have a Cell Phone

    Here’s Dave Rupert writing about all those emails, texts, phone calls, etc. we’re getting these days: Once upon a time it had utility, now it’s all noise and grifter slop demanding our attention and giving us to-dos That last part really hit: “giving us to-dos”. I feel this. So many of the messenger apps on my phone are other people laying claim to my time and attention. It reminds me of an interaction I had with my Dad years ago. This was back when cell phones were starting to become ubiquitous. Not smartphones , mind you. Cell phones, i.e. telephones that were mobile. Texting wasn’t really a thing yet. These were devices for making voice calls wherever you went. As a teen, it seemed like everyone had one: my teachers, my friends, even my friends’ parents. But not my parents. They were “behind the times”. (Everyone was getting cell phones and we didn’t even have caller ID on our landline!) One night at family dinner I asked, “Dad, why don’t you have a cell phone?” His response? “Why would I want to allow other people to contact me whenever they want?” I still think about that. Reply via: Email · Mastodon · Bluesky

  • Flavio CopesMore Front-end Bloggersread at source

    Pushing to main still needs a process

    Direct pushes can keep development simple, but trust needs concrete checks. Look at access, traceability, tests, and recovery before copying a team's workflow.

  • SitePointThe Giantsread at source

    9 Checks Before Shipping a Product Email: A Workflow for Developers and Designers

    null Continue reading 9 Checks Before Shipping a Product Email: A Workflow for Developers and Designers on SitePoint .

  • AdactioTop Front-end Bloggersread at source

    Imagining the sci-fi cabal meeting where Adrian Tchaikovsky and Ray Nayler divvied up their assignments: “Okay, we can both do octopuses and crows, but let’s toss a coin for mammoths; loser has to do spiders.”

  • Flavio CopesMore Front-end Bloggersread at source

    What changes when you stop opening the code editor?

    Coding agents can move work outside the editor. Understanding changes, reproducing bugs, and checking the application still need a place in the workflow.

  • AbduzeedoMulti Author Blogsread at source

    Best of the Week: Monospaces, Engraved Cotton, and Can Wine

    Our curated roundup of the best of the week covers open-source monospaces, cotton stationery, and tactile books from ISO week 2026-W43. Good design doesn't need a thirty-page strategy deck to explain ...

  • The Mozilla BlogBrowsers, engines, etc.3 min read

    Firefox reunites meme royalty to remind you what the internet used to feel like

    A group of familiar faces from the early web just got back together to ask an important question: What happened to the internet? Sure, there was a time when it was a little less polished, and a lot less speedy, but it was yours. Overly Attached Girlfriend may have wanted to know everything about you, […] The post Firefox reunites meme royalty to remind you what the internet used to feel like appeared first on The Mozilla Blog .

  • Speckyboy Design MagazineDeveloper/Designer News4 min read

    How AI Fuels the Web Security Goldrush

    AI has quickly become a key tool for the modern web. Developers, web hosts, and site owners are adopting it to reduce costs, increase efficiency, and serve customers (we can... The post How AI Fuels the Web Security Goldrush appeared first on Speckyboy Design Magazine .

  • Flavio CopesMore Front-end Bloggersread at source

    Cloudflare Hyperdrive tutorial: use PostgreSQL with Workers

    Learn Cloudflare Hyperdrive with PostgreSQL and Workers, configure pooling and caching, and see how it fits with D1, R2, Queues, Supabase, and Neon.

  • Flavio CopesMore Front-end Bloggersread at source

    What teaching can tell us about prompting

    Clear examples and useful feedback help when teaching a concept or directing a coding agent. Explain the expected behavior and show where the result differs.

  • Stéphanie WalterMore Front-end Bloggersread at source

    Pixels of the Week – October 25, 2026

    This week we explore the “disability dongle” problem, ecommerce accessibility issues that get customers stuck, and the double-edged sword of AI-generated prototypes. Also, don’t miss some horror graphic novels for Halloween and a gaming database for parents!

  • Remote SynthesisMore Front-end Bloggersread at source

    The Joy of Programming

    Coding brought two kinds of fulfillment: creativity and problem-solving. AI has dramatically impacted both, to opposite effect.

  • Frontend Masters BlogMore Front-end Bloggersread at source

    The Vertical Codebase

    A nice app architecture thought by Dominik: The Vertical Codebase. When component architecture came along, many started co-locating HTML/CSS/JS for a component, and it felt right. What if you take that one step further and co-locate based on the site’s conceptual areas? For example, the “dashboard” would have all the hooks, types, queries, etc., related […]

  • AbduzeedoMulti Author Blogsread at source

    Union: Inside Two Times Elliott’s Visual Identity

    Explore the Union visual identity by Two Times Elliott, pairing extended grotesk typography and Swiss grids with tactile print monographs. Office branding usually tries way too hard. Over the past fif...

  • SitePointThe Giantsread at source

    7 Checks Developers Should Make So AI Search Can Read Their Site

    null Continue reading 7 Checks Developers Should Make So AI Search Can Read Their Site on SitePoint .

  • SitePointThe Giantsread at source

    How to Test Location-Aware APIs with FastAPI and PostGIS

    Test location-aware APIs built with FastAPI and PostGIS: seed spatial data, run radius and distance queries, and assert results with pytest. Continue reading How to Test Location-Aware APIs with FastAPI and PostGIS on SitePoint .

  • Mux BlogCompany/Startup Blogs8 min read

    What the iPhone Duo means for web development

    We've been working really hard to get the new version of Video.js out the door, and we recently released v10.0.0 ! So over the weekend, I decided to relax a bit with a side project: digging into the web APIs that we’ll have access to on the iPhone Duo. I know, I know, this kind…

  • DigitalOcean BlogMulti Author Blogs4 min read

    Prompt Caching is GA on DigitalOcean Serverless Inference: Up to 90% Off the Context Your Agents Resend

    Prompt caching is now generally available on DigitalOcean Serverless Inference, across supported models in our open model catalog, with no changes to your request code required. Cached input is billed at up to 90% off and time to first token drops by up to 80%.* An agent never…

  • Geoff GrahamMore Front-end Bloggersread at source

    I’ve never been as nervous to publish on CSS-Tricks since my first article in 2015.

  • AdactioTop Front-end Bloggersread at source

    The Pirate Queen by Ariel Lawhon

    This is an infuriating book. So much so that I didn’t finish it. Don’t get me wrong; I love the idea of The Pirate Queen . Telling the life story of Gráinne Ní Mháille is an excellent premise for some rip-roaring historical fiction. It’s even got an interesting structure alternating between three different parts of her life. I was pleasantly surprised when I cracked open the book to find a small pronunciation guide to some Irish words in the front matter. It would be nice to have some Gaeilge scattered throughout the narrative. But that’s exactly what made this book so infuriating. First off all, by dropping in an occassional Irish word into a sentence, it just made me think, “Wait, what language would these people be speaking?” Usually the answer was Irish. In which case, why translate one arbitrary word? Then there’s the choice of the Irish word that gets dropped into the text most frequently… The front matter has this to say about the irish word tá : An affirmative statement similar to yes Um, not really. Tá is present tense of the verb “be”. The English equivalent is “is”. You can’t just drop it in as a replacement for the word “yes”. But that’s exactly what Ariel Lawhon does. This continually took me out of the story. One person asks a question like, “Did you see that?” and the other person answers, “Tá.” That just doesn’t make sense. I know this sounds really nit-picky, but one of the first things you learn about Irish is that there is no single word for “yes” or “no”. It’s most common to respond with the positive or negative form of the verb in the question—“Did you see that?” “I saw!” So of all the words to pointlessly switch into Irish, “yes” is by far the least suitable. It happened every couple of pages. I was getting so annoyed, I flipped ahead to the acknowledgements to find out who was consulted on the use of Irish in the book. I found my answer. No one. That seems somewhat irresponsible to me. It borders on being insulting. Would it have taken so much time and effort to have one single Irish speaker check the text? Alas, the lack of research wasn’t just evident in the book’s treatment of the Irish language. At one point, a young Gráinne is out walking with her brother, who is playing the uilleann pipes. I had to stop and check the text a few times. Perhaps I missed a bit where they sat down. But no, this book blithely describes a character walking and playing uilleann pipes at the same time. Now if you think uilleann pipes are pretty much the same as Scottish highland pipes, this would make sense. But they’re not. A bare minimum amount of research would show that the uilleann pipes are played sitting down (you can try to play them standing up, but you’ll need some kind of extra gadget like Johnny Doran used, but even he couldn’t play them while walking). I carried on reading even though I was getting more and more annoyed by the shoddiness on display. Then I read this sentence: No more distant flicker of lanterns in the distance. I get how you would write that sentence in a first draft. Hopefully you’d catch its redundancy in a subsequent draft. If not, it’s exactly the kind of thing that your editor is there to spot. But no, this made it all the way to the final printed book, a book that was displayed prominently on tables in major bookstores in multiple countries. Compare and contrast that with When The Boys Came Out To Play by John Mackel , a book which will be likely only ever be read by a much smaller audience but which is crafted with so much more care. I always feel slightly guilty if I don’t finish a book. I know, I know; life’s too short and all that. But I can’t shake the feeling that I’m being a bit disrespectful to the author by not seeing their work through to the end. In this case though, the author displayed enough disrepect to her readers that I don’t think I need to feel bad about slamming this book shut. The Pirate Queen is a sloppy piece of work. You deserve better.

  • Dave RupertTop Front-end Bloggersread at source

    Bad at email

    Good friends and family know this, but I am bad at email. Like chronically bad. If you have tried to email me, you know this too and you either never got a reply or received one 9-months later starting with the phrase, “Sorry.” I am truly sorry… but also I’m not. It’s a function of who I am. I was never great at email, but in a slower time before social media it raptured my attention. I would habitually refresh my inbox hoping for a long range communication from a friend or stranger. When I was homesick in Japan, a good email (or AIM chat) could turn my day around. I have fond memories of email and its unparalleled ability to connect me to other people through a single address. It of course would never be as familiar or intimate as scribing a hand-written calligraphic letter with a big feather pen, but it proved a fine substitute. At Paravel, I noticed that emails had a propensity to crash into my day with some new urgent task. A ding, a red badge, a bouncing icon in the dock . Could be a client or my accountant; something that required me to stop what I was doing and switch over to their need. Frank once described emails as (paraphrasing) “a to-do you send to someone else” and that resonated in my soul. For someone with an attention regulation disorder, intermittent distractions like email (or chats) can be devastating to staying focused on the work I actually need to finish. Email being disruptive to your productivity must be a pretty common phenomenon because nearly all the productivity books out there –and I’ve read them all– attempt to “solve” productivity by turning off your notifications and checking your email less. I must have really taken this advice to heart because I almost never check my email anymore. After a long day of expending dopamine on work, the last thing I want to do at home is check my personal email and receive more to-dos from strangers. I tend to check my personal email now once a week… or less. Inbox Zero is a fool’s errand for me, but I try to keep my work email groomed and as close to zero as possible. Part of that was because I started with a blank slate and could actually succeed. Each morning I make an analog to-do for myself to check my work email. I set up some priority inboxing and auto-deletes for org-level notifications. Importantly, work email stays sequestered to my work laptop. But despite the success at work, I’m sitting at nearly 500+ unreads in my personal Inbox. It doesn’t feel great and feels like a monumental task now. Since starting at Large Company I know of at least two conferences that I’ve missed out on speaking at because I’m so bad at email (sorry, PPK ). If you’ve ever wondered why I don’t have a contact form on my site or do that cool “email me, let’s be friends” link in my RSS footer, this is why… because I feel shame that I will disappoint you . There’s also the diminishing utility of email. As with phone calls and texts, the amount of spam and noise has ruined the service. It’s a needle in a haystack to find the one good email that actually deserves your attention. Just because we participated in online commerce once doesn’t mean you get the liberty to email me for the rest of my life. I wish there were more laws about this. When did a ten drip email campaign for every online transaction become the standard? You bought an item → Item is getting ready to ship → Want another item? → Item shipped → Need more items? → Item out for delivery → The holidays are coming up → Package delivered → Let us know how we did → Mother’s day coming up → Father’s day coming up → Step-father’s day coming up → etc… It’s entirely too much. And the grifter slop… oh, my God the grifter slop! Hey Dave, I came across your now-defunct company Luro. Design systems is an interesting space. Would you like to increase Luro users by six billion percent through spam email blasts? We can help. Chad, CEO I will never reply to this and– Dave, I thought I’d follow up in case you missed the last email. I’m a fucking robot obviously but we can have a conversation about this. Chad, CEO Grifters, spend six minutes crafting a real email and I promise you it will convert better. Or have an actual fucking product that is so good I hear about it from other people. You are one of five hundred anonymous Chads in my inbox, this pickup line doesn’t work anymore. Along those lines… Democrats, sending text messages doesn’t work anymore. I got AOC, Nancy Pelosi, Beto, and even Raphael Warnock’s grandma texting me every other day and it makes you look broke and desperate like a friend I’m gonna need to bail out of jail again. Capture me with ideas. That’s how I feel about email. And text messages. And phone calls. And social media. Once upon a time it had utility, now it’s all noise and grifter slop demanding our attention and giving us to-dos. Be hotter, be smarter, be more liberal, be more productive, be more, be more, be more. Oh, and I underpaid my taxes and owe the government $5400. That was the email I missed.

  • freeCodeCamp.orgYouTube ChannelsVideoWatch on YouTube

    Gemini 4 Argon API Crash Course

  • SitePointThe Giantsread at source

    Top 5 3D Animation Software in 2026

    null Continue reading Top 5 3D Animation Software in 2026 on SitePoint .

  • AdactioTop Front-end Bloggersread at source

    Chuala mé an nuacht brónach go raibh Dónal Lunny imithe ar slí na fírinne. Laoch. Ar dheis Dé go raibh a anam.

  • SitePointThe Giantsread at source

    Beyond the Password Reset: Building Recovery Experiences That Protect Online Shopping

    null Continue reading Beyond the Password Reset: Building Recovery Experiences That Protect Online Shopping on SitePoint .

  • Smashing MagazineThe Giants3 min read

    Accordion Icons: Which Work Best?

    A closer look at accordion icons, why split menus are harmful, and why it’s better not to have icons and text labels link to different actions. Plus, why the caret is the safest icon choice. You’ll find more [useful guides](https://www.smashingmagazine.com/category/guides/) and [online workshops](https://smashingconf.com/online-workshops) here on Smashing Magazine, so make sure to browse and explore.

See everything from the last 30 days →