Front-end, in one read.

DEV CommunityThe Giantsread at source

Most "WBS tools" are secretly Gantt editors — I built a board for real Work Breakdown Structures

I built Plesfeda — a board for building real Work Breakdown Structures. Breakdown first, schedule later. MIT-licensed, fully local, runs in your browser with no install. Repo: https://github.com/cuculhart/plesfeda Live demo: https://cuculhart.github.io/plesfeda/ The idea Most things called "WBS tools" are actually Gantt chart editors. You arrange rows and draw dates — useful, but it never builds the thing a WBS actually is: work, broken down, into a structure . Serious PM tools didn't help either. MS Project, OpenProj, LibrePlan — they let you move rows, but never let you pick up a whole block of work and hang it somewhere else in the structure. Their calendars don't even ship with Japanese holidays, so estimates always ended up back in Excel. Plesfeda is not a project management tool. It's a tool for calmly judging whether a volume of work fits inside a deadline. The protagonists are breakdown and hierarchy — dependencies, scheduling, and the Gantt chart are all derived output, never the input surface. Breakdown input The core feature is an input flow that mirrors the act of decomposing: Place a [task] on the board and choose breakdown . Two dotted slots appear — the first is an active input with a cursor, the second is a ghost previewing the next entry. Every Enter promotes the ghost to active and sprouts a new ghost, so children stack up at the tempo of your thinking. Walk away mid-entry and the active slot falls back to a ghost parked at the parent's tail — click it to resume. Ghosts never persist into data until confirmed. The structure is free Reparent whole subtrees — drop a node onto another node and the entire branch moves. Drop on empty space to make it a root. Cycles are always rejected. It's a forest — multiple roots are first-class. Add a parent later and adopt existing roots as children: bottom-up structuring. Derived WBS numbers — every node shows 1.2.3 -style numbering computed from position. Reparenting renumbers automatically; nothing is stored. Deleting a parent is a choice — promote its children to roots, or delete the whole subtree. Effort rollup — leaves take a hand-entered effort; parents show the recursive subtree total (Σ), so a root shows the cost of the whole structure. Units: days or hours. Structure becomes schedule Tasks can declare predecessors (finish-to-start). One simple rule — leaf earliest start = max(parent start, predecessor finishes) — drives a PERT/CPM forward pass that returns the structure's earliest finish. The toolbar always shows the project's earliest completion, and the critical path is highlighted on nodes and dependency edges. Dependency cycles and ancestor/descendant dependencies are flagged as errors, and Gantt output stays locked until they're resolved — so a broken structure can't produce a plausible-looking schedule. The Gantt is a read-only report rendered from the tree: baseline date, weekend/holiday exclusion (click a day header to toggle a holiday), milestones (zero-effort leaves render as ◆), and print-friendly two-dimensional pagination with repeated headers and page numbers — real report output. Why the Gantt is read-only Typical Gantt tools let you grab a bar and drag the date. That's manual tail-end fitting — the structure loses the reason for the date. In Plesfeda you fix the structure and look at the schedule, not the other way around. Read-only Gantt is a deliberate design choice. Fully local, by design Data lives in the browser's localStorage and JSON files only ( {app:'plesfeda', version:1} export/import). No account, no cloud, nothing is sent anywhere. Tech stack React 19 + TypeScript + Vite Canvas on @xyflow/react (React Flow, MIT) English-first i18n — Japanese is a translation table keyed by the English source; untranslated strings fall back to English Why the name Plesfeda = Welsh pleth ("weave / braid") + Old Irish feda ("woods" — also the name of the letters of Ogham, the lost Celtic script whose characters are named after trees). A structure woven from trees. Honest limitations Single-player and local-only — deliberately. Editing is mouse-first, so phones can look but won't enjoy it. The Gantt report caps at 400 days of horizon. v0.1.0. License MIT. Feedback and issues welcome: https://github.com/cuculhart/plesfeda/issues

DEV CommunityThe Giantsread at source

SLX OrbitLab: satellite mission software with F Prime and Basilisk

An Earth observation mission requires coordinated orbital planning, attitude control, energy management and data transfer. SLX OrbitLab integrates these functions in a PC-based software system: a simulated satellite receives a target, plans the pass, acquires an optical product and transfers it during ground-station contact. Commands, telemetry and events track software decisions and the physical model's response. SLX OrbitLab is the Silicon LogiX platform for satellite mission software development and simulation, autonomous systems and embedded controllers. Version 0.7.0 integrates a native NASA F Prime deployment running on Linux, a proprietary C++ core, Basilisk simulation, a Qt desktop console and Godot 3D inspection. An optional subsystem executes RTEMS firmware on a LEON3 processor emulated in Renode. The platform executes a complete command, physics simulation and telemetry cycle on a PC. Integration tests connect operational decisions, spacecraft dynamics and firmware behavior. Embedded engineering and mission software integration Flight software: F Prime components, FPP interfaces, dispatching, telemetry, events and native command sequencing. Simulation and control: orbital and attitude dynamics, sensor measurements, reaction wheels and energy accounting. Embedded systems: RTEMS firmware, the LEON3 BSP, timers, periodic tasks, UART and CRC-protected protocols. Verification: repeatable faults, recording, synchronized replay, strategy comparisons and measured results. Integration: Qt operation, Godot visualization and a C++ core that can be supplied separately as a binary library. Mission software architecture: commands, simulation and telemetry The operational path is explicit: command → mission software → physical simulation → telemetry → console and 3D update . The GUI sends a request; F Prime receives it through its dictionary and dispatcher; the Mission component calls the C++ core to assess conditions and select actions. Basilisk applies actuator commands and power loads, integrates the dynamics and returns new measurements. At the next step, mission software consumes those measurements, updates its decisions and emits telemetry and events. GUI refreshes do not advance physical time. This boundary makes it possible to repeat an experiment, pause it, advance by individual steps and inspect the same moment through different views. F Prime executes mission logic; Basilisk returns the physical response. Native packets and simulation snapshots feed recording, the console and 3D views. The optional RTEMS node uses a distinct interface, shown later. SLX OrbitLab technology architecture Technology System responsibility F Prime 4.3.0 / C++ Commands, components, events, telemetry channels, responses and native sequencing. Silicon LogiX C++ core Mission decisions, target management, energy assessment, protection and attitude control. Basilisk 2.12.0 / C++ and Python Orbit, attitude, sensors, reaction wheels, solar generation, battery and applied thrust. Qt 6.12 / QML Mission console, command and sequence editors, telemetry, recordings and reports. Godot 4.5 / Blender and GLB assets Synchronized spacecraft, interior, exploded, orbit and ground station inspection. RTEMS 5 / Renode 1.16.1 Energy-controller firmware running on an emulated LEON3/SPARC target as an optional subsystem. F Prime: C++ components, native commands and telemetry F Prime organizes flight software into components with declared ports and connections. OrbitLab uses this architecture as its command execution path. FPP definitions describe parameters and interfaces, the Ground Data System uses the generated dictionary to encode requests and decode packets, and the native dispatcher delivers each command to its destination component. Version 0.7.0 exposes 28 dictionary commands and 50 native channels . Selecting a command shows its parameters, examples and operational meaning. Operators can request panel deployment, a relative rotation, Sun or Earth pointing, payload and downlink permissions, a beacon and the orbital maneuvers supported by the model. Diagnostic commands also verify the communication path. For example, OrbitLab.mission.MANEUVER [3,30] requests a 30-degree relative rotation in mode 3. The dispatcher response confirms acceptance of the parameters; telemetry subsequently shows pointing error, attitude and actuator state. Acceptance, physical effect and operational completion are separate pieces of evidence. An accepted request may remain pending while simulation time is paused or energy, sensors and protection inhibit the action. For a commissioned project, this executable path supports concrete discussions about interface contracts, parameter bounds, component behavior, failure handling and integration tests. The F Prime console presents command arguments, operational responses and telemetry from the Linux deployment. F Prime sequences: planning, validation and execution OrbitLab integrates native Svc.CmdSequencer execution. Operators prepare plans of 1 to 64 steps with relative delays in simulated seconds and validate them against the session dictionary. F Prime tools compile the binary file; native validation checks its format and CRC before execution. A plan can run automatically or advance through manual steps. Cancellation, completion verification and responses for each step are preserved. Delays follow simulation time and begin after the previous command's response. Pausing stops this clock as well, keeping sequencing and dynamics consistent. The eight-step example deploys the panels, suspends the optical instrument, requests Sun pointing, enables the beacon after five seconds, commands a 30-degree rotation after another 45 seconds, disables the beacon after another 60 seconds, and restores the payload and automatic mission. Events and telemetry show the executed list and its consequences for the spacecraft. Sequences time command requests; they do not automatically wait for attitude convergence. Acquisition conditions remain in the C++ mission state machine. Separating the operational plan from control of physical behavior supports focused testing and a correct interpretation of the results. The Qt console presents the operational plan and native validation. Step responses and times are preserved; completion of the command list is distinct from physical attitude convergence. Basilisk: orbital dynamics and attitude control Basilisk combines C++ numerical modules and Python configuration for space-system simulations. OrbitLab uses this foundation to integrate orbital position and velocity, attitude and angular rate, sensor measurements and reaction-wheel action. Python coordinates the laboratory and adapters; mission decisions execute in the C++ component. The reference case declares an initial circular orbit at approximately 550 km, a 65 kg rigid body and three reaction wheels. Quantities cross the simulation boundary with explicit units: metres, metres per second, seconds, radians, watts and joules. Attitude and measurements use declared frames, distinguishing the controller's available information from diagnostic simulator truth. Orbital maneuvers integrate mission commands, operational constraints and propulsion dynamics. An RTN delta-v command is checked against energy, propellant, sensors, alignment and orbital conditions. Basilisk integrates finite thrust applied to the body; reports retain delivered delta-v, remaining propellant and changes to orbital parameters. Adding a terrestrial target during a mission preserves the existing trajectory. The software predicts accessible passes, while a physical burn changes the orbit gradually. Energy management and activity planning The battery has a finite capacity of 180 Wh. Solar generation, panel orientation and deployment, eclipse and active loads contribute to the physical balance. The core compares available energy, reserves and activity demand, using a short-horizon energy forecast. The numerical foundation includes Basilisk's storage model and solar-generation model . When energy is insufficient, acquisition is deferred, loads are reduced and the reason is recorded. The physical model therefore experiences a different consumed power from the load required to capture an image. Battery telemetry reflects an energy balance changed by the software decision. Protection remains active during manual requests. Two comparable strategies, priority-first and energy-aware, use different planning margins while both protect the minimum reserve. A comparison starts from the same initial conditions, targets, seed, faults and recorded stimuli, with separate F Prime processes and Basilisk simulations. Results include completed or deferred observations, final energy and pointing accuracy during acquisition. A geometrically useful window is only part of the decision. Software authorizes the activity against energy and sensor state; deferral and its reason become recorded mission evidence. Earth observation: targets, acquisition and downlink The operator selects coordinates and priority. Software predicts access windows, commands pointing and requires stability before exposure. The reference configuration requires a measured error below 0.5 degrees, three seconds of stability and a twelve-second exposure. These values are parameters of the simulated mission. The synthetic optical product uses actual simulated body attitude, camera-ray intersections with the spherical Earth and the geographic texture. Raw data is a 256 × 256 monochrome PGM image. A derived PNG preview relates the target, sensor footprint and cartographic context, making the experiment's content easier to interpret. Bytes are saved in modeled onboard storage and transferred during a geometric ground-station contact window when energy permits downlink. Storage capacity, the product queue and link availability can change the plan. Delivery is confirmed when the received file passes its SHA-256 integrity check. The link model verifies data handling and mission constraints; it does not calculate an RF link budget or radio modulation. Qt console and 3D visualization with Godot and Blender Qt Quick and QML compose the operational console: mission control, F Prime commands, sequence editing, channels, targets and products, orbital passes, tests and recordings. The telemetry model updates values while preserving the operator's browsing position. Parameters and descriptions connect a command to its function, operational response and telemetry. One operator controls a session; viewers receive its state. Godot 4.5 presents close-up spacecraft, interior, exploded, orbit and ground station views. Component selection connects geometry to subsystems and available commands. Attitude, panel joints, the beacon and antenna follow confirmed backend telemetry. Blender assets and GLB exports retain original component names, hierarchy and pivots. Earth's illustrative scale and exploded-view offsets belong to presentation and do not enter the dynamics. Blender/glTF axis conversion is explicit and applied once. This integration choice makes 3D a useful inspection tool while keeping it distinct from the physical model. RTEMS and Renode: embedded firmware on emulated hardware RTEMS provides the kernel and services for real-time embedded applications. In OrbitLab it executes an independent energy-controller firmware. F Prime remains a Linux process; RTEMS is a separate subsystem. Interfaces between mission software, the energy model and firmware handle power requests, controller responses and load states. Renode emulates the LEON3/SPARC target, including the peripherals needed for timers and UART. Antmicro's public RTEMS/LEON3 example documents the platform overlap; OrbitLab's integration was verified with its own firmware. Compatibility requires alignment between the ELF, BSP, memory map, clocks and timer, followed by boot and execution tests. The adapter sends battery energy, capacity, requested power and explicit mission time through sequence-correlated, CRC-protected UART messages. Firmware returns permitted power, flags and the task heartbeat. This permission constrains the loads applied to Basilisk. Tests cover boot, timer interrupts, a periodic task, load reduction at low and critical energy, malformed CRC rejection and recovery after an invalid message. Emulated time advances in controlled intervals. Missing firmware responses stop the experiment; the laboratory does not silently replace RTEMS with PC logic. Compatibility and integration tests cover this specific combination of firmware, BSP and emulator. Qualification of electronics or a flight processor requires dedicated work. The physical model retains battery and load dynamics. Emulated firmware authorizes power over a verified protocol, allowing embedded execution and its effect on the mission to be analyzed independently. Mission scenarios, synchronized replay and results analysis Operational scenarios and fault management Scenario Expected operational outcome Nominal mission Target access, stable pointing, acquisition, storage and a delivered file with verified integrity. Insufficient energy Deferred activity, a recorded reason, reduced loads and a recorded recharge balance. Temporary sensor outage Acquisition held while measurements are invalid, tracked sensor state and renewed condition checks after recovery. The extended campaign also covers actuator faults, loss of solar generation or ground link, multiple products, full storage and continuous operation. Fault-injection intervals and operator commands are retained as test evidence. SQLite recording preserves configuration, commands and native packets, events, physical snapshots and products. Replay restores recorded state without redispatching actuator commands. Timeline, telemetry, imagery and 3D follow the same instants. HTML, JSON and CSV reports and SHA-256 manifests support investigation from a shared trace and strategy comparisons with explicit metrics. The release 0.7.0 acceptance evidence records 26 Linux integration tests, three Windows CTest checks, eight publication-boundary regressions and GUI workflows with native commands, sequences and maneuvers. Operation with a binary SDK, without the proprietary core sources, was verified separately. The documented SDK case delivers one product with an acquisition pointing RMS of approximately 0.0586 degrees. A maneuver delivers 2 m/s and updates remaining propellant. These are results for the stated configuration and test conditions, rather than an accuracy promise for arbitrary satellites. Proprietary C++ core, binary APIs and simulation models The proprietary Silicon LogiX engine exposes a versioned C ABI with fixed-size structures, declared units and an opaque handle. Its interface contains no Qt, Godot, Python or F Prime types. The core can be supplied as a shared library and integrated or updated while preserving the binary contract, independently of presentation and adapters. The public GitHub repository contains the GUI, integrations, API, example firmware, scenarios, approved assets, documentation and tests. Proprietary core implementation is excluded. Building and running OrbitLab from public source requires the matching evaluation binary SDK; distribution and commercial development follow the project's terms. The model declares its scope: spherical Earth, simplified reference frames, no J2 perturbation, atmosphere, terrain or thermal environment, an ideal battery, constant dynamic mass and a synthetic optical instrument. It does not represent cell chemistry, analog power electronics or a complete RF link. Repeatability is verified with the pinned Linux environment and the same seed; cross-platform bitwise identity is not promised. The model documentation makes parameters, criteria and simplifications available for review. Custom engineering for companies and research organizations OrbitLab's architecture integrates engineering capabilities applicable to mission software, embedded controllers, simulation benches and operational consoles. For companies and research organizations, a project can begin with operational requirements, available measurements, energy constraints, abnormal conditions and system acceptance criteria. F Prime components: FPP definitions, topologies, commands, telemetry, events, service integration and native tests. Simulation and autonomy: Basilisk models, C++ control, planning, resource management and fault scenarios. Embedded firmware: RTOS/BSP integration, protocols, peripherals and emulated-target verification before hardware tests. Consoles and tools: Qt/QML applications, 3D inspection, evidence acquisition and presentation. Verification and delivery: repeatable campaigns, agreed metrics, reports, documentation and distributable interfaces. Explore the OrbitLab repository and technical documentation, or contact Silicon LogiX for a technical presentation, an evaluation SDK or a custom project. The starting point is to define what the system must do, how it should respond at its limits and which tests must document compliance with those requirements.

DEV CommunityThe Giantsread at source

Why encryption-at-rest doesn't protect your S3 bucket

✓ Human-authored analysis; AI used for formatting and proofreading. "We have SSE enabled on all our S3 buckets. Our security team says we're good on HIPAA encryption. But I noticed the bucket policy allows public read. Does the encryption protect us?" No. And this misunderstanding is more dangerous than having no encryption at all, because it creates a false sense of compliance. How S3 server-side encryption works SSE-S3 (AES-256) and SSE-KMS encrypt objects at rest on disk. The AWS documentation states: encryption is transparent on read . When any principal with s3:GetObject permission calls GetObject, S3 decrypts the object automatically and returns plaintext. If the bucket policy grants s3:GetObject to Principal: "*" , anyone on the internet gets plaintext PHI. The encryption key never enters the picture. SSE protects against AWS datacenter disk theft. A threat model that is already covered by AWS's own physical security controls and BAA. What Stave detects: COMPOUND.002 Stave's HIPAA profile evaluates encryption and access controls as separate controls, then runs a compound risk detector that catches dangerous combinations. What happens when a bucket has encryption enabled but public access: stave evaluate --snapshot observations/snap.json --profile hipaa ═══ HIPAA Security Rule ═══ Bucket: phi-records-encrypted Account: ***789 Snapshot: 2026-04-08T10:00:00Z Result: FAIL ── COMPOUND RISKS ── [HIGH] COMPOUND.002 (triggers: ACCESS.001, CONTROLS.001) Encryption at rest is configured but the bucket is publicly accessible. Encryption provides no confidentiality benefit while public access is enabled. ── CRITICAL ── [FAIL] ACCESS.001 — critical Compliance: §164.312(a)(1) — Access Control Finding: Block Public Access not fully enabled Remediation: Enable all four Public Access Block settings ── HIGH ── [PASS] CONTROLS.001 — high Compliance: §164.312(a)(2)(iv) — Encryption and Decryption Notice that CONTROLS.001 passes. Encryption is on. But the compound detector flags the combination: a passing encryption control alongside a failing access control means encryption is providing zero confidentiality. Why individual control checklists miss it Most compliance tools evaluate controls independently. Encryption: check. Each control gets a green checkmark. The problem is that the combination creates a risk that neither control captures alone. Stave's compound risk detection evaluates known dangerous patterns after individual control evaluation. COMPOUND.002 fires when ACCESS.001 fails and CONTROLS.001 passes simultaneously. The finding is prepended to the report at HIGH severity so it appears before any individual control results. Encryption at rest is a necessary HIPAA control (SS 164.312(a)(2)(iv)). But it is not sufficient without access control (SS 164.312(a)(1)). If your bucket is publicly readable, SSE is not doing anything useful. S3 decrypts transparently on every GetObject call. Fix access control first. Encryption without access control is security theater.

DEV CommunityThe Giantsread at source

How to Build a Solana Indexer: Streams, Backfill, Decoding and Reconciliation

Short answer: a Solana indexer consumes the chain's account and transaction streams and transforms them into a queryable database specific to your application. Token holders, pool activity, NFT transfers, and protocol positions: whatever your product needs, in order to answer faster than an RPC call can. The indexer architecture consists of a stream consumer (Geyser gRPC for live), a backfill source (archive RPC for history), a decoder for every program, an idempotent database writer, and a gap/reorg handling routine. This post describes every part, the decisions that make the indexer robust under load, and the underlying infrastructure. Key Takeaways Index via Geyser gRPC stream, not via polling. Filters on the server side provide exactly the accounts and programs of interest, at node-processing latency. Backfill history via an archive once, stay live afterwards. Combining them without a cutover point usually results in holes in the index. Every write must be idempotent and keyed by the slot and the signature, due to stream replays and forks. Decode using the program's own layout and version the decoder; program upgrades cause silent corruption most often. What an indexer is for An indexer is a tool to precompute answers to your questions and serve them from a database. Solana's RPC provides the answers to such questions as "this account now" or "that transaction happened". But it does not answer aggregate and historical questions efficiently: who holds a token, the hourly volume of a pool, the ownership history of an NFT. The indexer computes the answers by consuming the stream of account writes and transactions and storing them into the database of your choice. The indexer output serves your product needs, whether it's a relational database for analytics, a hot-path key-value database, or a search engine for discovery. While the output varies between products, the input is always the same: the account writes and transactions, filtered to the programs you are interested in, and ordered by slot. Architecture The live consumer Subscribe to the stream using Yellowstone gRPC filters for the accounts (by owner program with memcmp filters on discriminators in case multiple account types exist) and the transactions (including your programs). If the indexer does not handle rollbacks, request confirmed commitment; processed commitment is earlier, but can be rolled back. Track the slot number on every message. Your consumer's current slot number vs the chain's current slot number is the lag metric that shows how well your indexer keeps up with the chain, and a hole in the series of slots is a trigger for a gap reprocess. Yellowstone gRPC explained describes the stream subscription model; WebSockets vs gRPC explains why the stream uses gRPC at this scale. Backfill The history prior to the beginning of the live feed comes from archive RPC. The usual approach: Find the slot number at which your live consumer starts. Walk getSignaturesForAddress for your programs backwards starting from this slot, paging until you find the first slot that needs to be indexed. Fetch each transaction via getTransaction (or a block via getBlock if the density of the transactions is high enough) and pass it through the same decoder and writer as in the live path. Stop at the cutover slot number. Transactions newer than this one are live, and older are from backfill. They should not overlap without idempotent writes. Backfill is where the request budgets go to die. Batch, page carefully, and use the plan whose archive access and rate limits match the job; historical data is this tier in OrbitFlare, and Solana RPC pricing explained explains why archival calls are expensive under credit pricing. Decoding The account data are bytes arranged according to the layout defined by the owning program; the instruction data as well. Decode using the IDL or layout of the program, and treat the decoder as versioned code: in case of a program upgrade and a layout change, the old accounts may contain the old layout until rewritten. A decoder that relies on a single layout silently corrupts the index. Three practices: Key decoders by the program ID and discriminator , and handle the unknown discriminators by logging and skipping, not guessing. Calculate token balance differences using pre and post token balances from the transaction metadata. They are independent from the instruction decoding and thus work regardless of any unknown layout. Store the raw bytes in addition to decoded records for a retention period to be able to replay the decoding fix without fetching everything again. Writing idempotently The streams replay after disconnection, backfill overlaps the live feed at the cutover point, and forks at the processed commitment may deliver the same slot twice with different content. The writer must be ready for all three: every record is keyed by the slot and the signature (and the instruction index where relevant), and writing the same key twice is either no operation or an overwrite, never a duplicate. Two patterns: Upsert by the key for current-state tables (holder balances, pool state). Append-only events are keyed by the signature and the index for history, with a unique constraint that excludes duplications. Commit in slot order and track the last completely written slot as a checkpoint; on restart, the indexing resumes from this point. Reconciliation Gaps and reorgs happen and should be expected, not an exception. Gaps : if your consumer skips some slots in its sequence, refetch the corresponding blocks from the archive RPC and process them with the pipeline. Reorgs : at processed commitment, a slot can be superseded. Either index at confirmed (easier option) or maintain the window of unconfirmed writes that can be rolled back when a slot is superseded. Drift checks : regularly compare the sample of indexed state against live getAccountInfo requests; the discrepancy means some problem with the decoder or writing. Infrastructure Streaming : a gRPC endpoint in the region where the indexer is running, with the throughput generated by your filters. Archive : an endpoint with the required history depth and a request budget that is capable of surviving the backfill. Dedicated capacity when your filter volume is high or backfill is continuous; a dedicated node removes shared limits from both paths. Database : sized for write throughput in slot order, with indexes optimized for your queries rather than for ingest. Conclusion A Solana indexer is a live gRPC consumer with an archive backfill and a cutover point, with a decoder per program, idempotent database writer keyed by slot and signature, and a reconciler that handles gaps and reorgs. Start by getting the keys and commitment level right, since they define whether the indexer will stay correct under load or not. Then choose the streaming and archive endpoints that match your filters and backfill needs, and implement the drift checks to avoid undetected corruption. OrbitFlare's gRPC service covers the live path, historical data the backfill, and dedicated nodes the volume. FAQ Can I index with WebSockets instead of gRPC? For one program with low activity, yes. For anything at volume the subscription count, JSON overhead and later tap point make gRPC the practical choice. How do I index tokens held by every wallet? Subscribe to accounts owned by the token program (and Token-2022) with a memcmp filter on the mint you care about, or index all token accounts if you need every mint. Use balance diffs from transactions for movement history. What commitment level should an indexer use? confirmed for almost all indexers. processed only when you need the earliest data and have implemented rollback handling. How far back can I backfill? As far as your archive endpoint keeps history. Full-history archive tiers go back to genesis; standard RPC nodes keep days. What about the DAS API for NFTs? The Digital Asset Standard API is a provider-side index for NFTs and compressed NFTs that answers common ownership and metadata queries without your own indexer. NFT and DAS indexing on Solana covers when to use it and when to index yourself. How do I know my indexer is correct? Drift checks against live reads, a replay test (re-run a slot range and compare), and alerting on lag and on unknown discriminators. Correctness is a process, not a launch state. Originally published at orbitflare.com .

DEV CommunityThe Giantsread at source

Daily Dose of DevOps — Developer experience: with strong SRE collaboration

Developer experience: with strong SRE collaboration A platform capability becomes dangerous when ownership is implicit but authority is broad. For developer experience with strong SRE collaboration , the decisive question is not whether a team can demonstrate the technology once. It is whether the organisation can operate it repeatedly, audit its decisions, and recover when assumptions fail. The operating problem Treat developer experience as part of a product-oriented internal platform with explicit service ownership and paved-road contracts. Define the consumer, owner, support boundary, change policy, and recovery objective before selecting implementation details. When operating developer experience with strong SRE collaboration, undocumented authority and ambiguous ownership create more risk than a missing feature. A credible design measures adoption, successful self-service completion, lead time, and platform-induced toil. Those measures should be visible to both the platform owner and consuming teams. If the measurements cannot distinguish adoption from coercion, or reliability from mere activity, the operating model is not yet falsifiable. A practical control Start with a narrow contract that can be tested automatically. The implementation should encode versioned golden paths, discoverable ownership, policy guardrails, and measured developer outcomes. The following fragment is illustrative; production values must be derived from workload evidence and organisational policy. apiVersion : backstage.io/v1alpha1 kind : Component metadata : name : payments-api annotations : platform.example/owner : payments spec : type : service lifecycle : production Roll the control out to one representative service, observe failure behaviour, and exercise rollback before broad adoption. Record exceptions as expiring decisions with an accountable owner, not permanent bypasses. Trade-offs Standardisation reduces cognitive load and makes controls observable, but an excessively rigid path displaces complexity into workarounds. Flexibility improves local fit, but every variant expands the support surface and weakens fleet-wide guarantees. For developer experience with strong SRE collaboration, prefer a small mandatory safety kernel surrounded by replaceable implementation choices. The organisation must also pay for operability. More validation increases feedback time; more telemetry increases cost and cardinality risk; stronger isolation can reduce utilisation. Make those costs explicit and compare them with the blast radius and recovery cost they buy down. What teams get wrong The recurrent anti-pattern is centralising delivery behind a ticket queue while calling the result self-service. Teams then measure task completion instead of production outcomes, accumulate exceptions without expiry, and discover during an incident that the nominal control has no tested recovery path. Another error is adopting a reference architecture without its assumptions. Validate identity boundaries, dependency failure, capacity pressure, partial rollout, rollback, and audit reconstruction in the environment that will actually carry production traffic. Key Takeaways Treat developer experience as an owned product and control system, not a tool installation. Design for the constraints captured by “with strong SRE collaboration”; document the authority, failure domain, and recovery objective. Measure adoption, successful self-service completion, lead time, and platform-induced toil. Automate versioned golden paths, discoverable ownership, policy guardrails, and measured developer outcomes. Test degraded operation and rollback before scaling adoption.

Hacker News Front PageThe Giantsread at source

The Aaronson Oracle

Hacker News Front PageThe Giantsread at source

Smart people don't think others are stupid

Hacker News Front PageThe Giantsread at source

Pg_vectorsearch: An index that is faster than pgvector's IVFFlat and HNSW

CSS WizardryTop Front-end Bloggersread at source

Web-Perf Wednesday 013 – CrUX Adds Soft-Navigation Core Web Vitals

CrUX adds experimental Core Web Vitals for SPA soft navigations, while Firefox and Safari improve cache evidence, image delivery, and rendering.

SyntaxPodcastsAudioListen

1047: Adobe has a big problem

Someone just clean-room ported seven Adobe apps to Rust, and Wes is shocked at how good it is. Scott and Wes break down what it gets right, what’s still missing, and why copying software is easy but inventing what comes next is the hard part. Show Notes 00:00 Welcome to Syntax!…

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

Show HN: Building an LLM from Scratch in TypeScript

Comments

Hacker News Front PageThe Giantsread at source

TV4 postpones show after AI agent erases edited material

W3C BlogBrowsers, engines, etc.2 min read

Introducing group activity pages

W3C groups now have an Activity page that shows, month by month, their charters, publications, meetings, participants and GitHub work in one place. The pages are in beta, and we would like your feedback.

Hacker News Front PageThe Giantsread at source

Pulsar at ESUG 2026 (new Smalltalk IDE)

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

Show HN: Fakenamegenerator – free browser based mock data generator

Comments

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

Show HN: Graft – open-source source control for agent-scale monorepos

Comments

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

Show HN: A guided 3D Leonardo da Vinci museum, built in code

Comments

Flavio CopesMore Front-end Bloggersread at source

What “open weights” means for AI models

Learn what open weights means for AI models, how it differs from open source, and what the Qwen3.8 and Kimi K3 downloads show about licenses and scale.

HeyDesignerDeveloper/Designer Newsread at source

Taste is not a design methodology

Emerging patterns: Design leadership in 2026, The new age of software, Inside Anthropic’s design team.

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

Show HN: Chiplab - Give your AI agent access to virtual hardware

Comments

Bruce Lawson's personal siteMore Front-end Bloggersread at source

Farage believes Andrew Tate is “an important voice”

Now we know that the execrable Andrew Tate is wanted by British police for allegedly making indecent images of a child, rape, stranging women during sex, and possession of extreme pornography depicting sexual intercourse between people and live animals — one involving an eel and another involving a horse. Let us not forget that Nigel […]

Flavio CopesMore Front-end Bloggersread at source

How to handle web requests in C with CGI 1.1

Learn CGI 1.1 by building a C web application: read requests, decode forms, return HTML and errors, and run the executable through Apache.

SitePointThe Giantsread at source

How to Move a Site Off cPanel to Another Control Panel Without Downtime

null Continue reading How to Move a Site Off cPanel to Another Control Panel Without Downtime on SitePoint .

AdactioTop Front-end Bloggersread at source

Installing Websites Must Be Easy

A message to Apple from the W3C Technical Architecture Group: We expect user agents to make installation an obvious affordance to users. Specifically, we expect the install option to clearly name the action, and to be easily reachable from the browser’s UI. An entry inside a menu with an unrelated label (such as Share), or several menu layers deep, does not meet this expectation. adactio.com/links/22799

AdactioTop Front-end Bloggersread at source

Zero

The term “no-brainer” refers to a suggestion that is so compelling that it would be foolish to even consider not doing it. I came across a no-brainer recently, thanks to Matt Hobbs: Make all UK Government websites free to access without mobile data charges. When I was done slapping my forehead at how obvious this proposal is, I signed the petition . If you’re a UK resident, you should do the same. And then spread the word. This is the kind of proposal that I imagine any politician would be happy to support, regardless of party affiliation, so don’t be shy about contacting your local MP. I guess in theory this could be opposed on the grounds that it technically violates net neutrality, but I would hope that the obvious societal benefits would outweigh that objection. Like I said, a no-brainer.

AdactioTop Front-end Bloggersread at source

Reading The Tusks of Extinction by Ray Nayler.

AbduzeedoMulti Author Blogsread at source

Inside the Craft of Ochi Design: Web Design by Obys Agency

Obys Agency crafts a slide-driven web design system for presentation agency Ochi, pairing condensed grotesque type with chartreuse #CDEA68. Obys Agency developed the digital platform and web design fo...

HTML All The ThingsPodcastsAudioListen

AI Basics For Developers

AI coding tools are getting more capable, but learning to use them well is about more than chasing the newest model. In this episode, Matt and Mike break down the fundamentals developers need to work effectively with AI, from models, agents, and harnesses to tools like Cursor,…

SitePointThe Giantsread at source

A Practical Guide to Testing JavaScript Functions Without Overcomplicating Your Workflow

null Continue reading A Practical Guide to Testing JavaScript Functions Without Overcomplicating Your Workflow on SitePoint .

SitePointThe Giantsread at source

Building Accessible Navigation Menus with Modern HTML, CSS, and JavaScript

null Continue reading Building Accessible Navigation Menus with Modern HTML, CSS, and JavaScript on SitePoint .

SitePointThe Giantsread at source

Beyond Faster Load Times: Practical Web Performance Optimization for Modern Applications

null Continue reading Beyond Faster Load Times: Practical Web Performance Optimization for Modern Applications on SitePoint .

Treehouse BlogMulti Author Blogsread at source

Treehouse’s CEO Built a Creative App with AI: Here’s What She Learned

Kari Brooks is not a professional developer, she’s the CEO of Treehouse. Using AI, she was able to turn a personal side project into a real digital product — and you can, too, with Treehouse’s AI Bootcamp, free to all... The post Treehouse’s CEO Built a Creative App with AI: Here’s What She Learned appeared first on Treehouse Blog .

AbduzeedoMulti Author Blogsread at source

AIDb identity: Inside Rafael Cespedes' New Branding

Rafael Cespedes built the AIDb identity around a slash-and-spark mark, vivid color, and a generative Midjourney profile for the AI platform. AIDb logs, discovers, and reviews AI-focused products, comb...

AbduzeedoMulti Author Blogsread at source

How Two Times Elliott Reimagined Branding for De Beers

Two Times Elliott crafts a sculptural branding system and unboxing narrative for De Beers' high-jewelry 1888 Master Diamond Collection. Luxury jewelry often relies on tired tropes. Two Times Elliott g...

Google for DevelopersYouTube ChannelsVideoWatch on YouTube

Gemini 4 Argon and Google Antigravity: From 2D concept to 3D cathedral

Mux BlogCompany/Startup Blogs9 min read

Let your agent cook by giving it the recipe

We've shipped a prompt library to give your agent the exact recipe for common use cases built on Mux. The evals tell the whole story.

SitePointThe Giantsread at source

Best HR and Payroll Software for SMBs

Nine HR and payroll platforms for SMBs, scored on payroll depth, pricing, HR features, onboarding, support, and integrations - with the trade-offs for each spelled out. Continue reading Best HR and Payroll Software for SMBs on SitePoint .

DigitalOcean BlogMulti Author Blogs12 min read

Inside Action Gateway in Managed Agents

A coding agent finishes a change and wants to open a GitHub issue with a link to its results. The agent can describe the issue, but creating it belongs to a different system. It needs a tool that can access GitHub, a connection with permission to use the correct account, and a…

Engineering at MetaCompany/Startup Blogs14 min read

Meta’s Generative Ads Model (GEM): Scaling the Central Model and Compute Engine for Frontier Ads AI

Last year, we introduced GEM, the industry’s largest recommendation system (RecSys) foundation model. GEM established Meta’s first LLM-inspired paradigm for ads recommendation, driving major performance gains. Building on this foundation, our next goal is to further scale both compute and intelligence transfer with next-generation hardware, and expand this capability across Meta’s entire ads ecosystem. This [...] Read More... The post Meta’s Generative Ads Model (GEM): Scaling the Central Model and Compute Engine for Frontier Ads AI appeared first on Engineering at Meta .

SitePointThe Giantsread at source

TanStack Query vs SWR: How to Choose in Next.js App Router

A scenario-based guide for React developers comparing TanStack Query and SWR in Next.js App Router, with equivalent Client Component patterns for filtered queries, cache invalidation, and optimistic updates. Continue reading TanStack Query vs SWR: How to Choose in Next.js App Router on SitePoint .

SitePointThe Giantsread at source

Count Unique Visitors Without Cookies Using Daily Salted Hashes in Express

Build a server-side visitor counter in Express and PostgreSQL using daily-salted SHA-256 hashes, and examine failure modes including CGNAT collisions, midnight-UTC splits, and 64-bit hash collision risks. Continue reading Count Unique Visitors Without Cookies Using Daily Salted Hashes in Express on SitePoint .

SitePointThe Giantsread at source

Node.js JWKS Endpoint with Crypto: Adding Missing Metadata

Build an Express JWKS endpoint using Node.js's native crypto module, and enrich exported JWK objects with the alg, use, and kid metadata required by token verifiers. Continue reading Node.js JWKS Endpoint with Crypto: Adding Missing Metadata on SitePoint .

AbduzeedoMulti Author Blogsread at source

Web Design: Keyframes Motion Graphics Service

Keyframes launched as a new web design service and curated digital archive dedicated to cataloging motion graphics by studios and freelancers. Finding exceptional motion design often feels like a frag...

AbduzeedoMulti Author Blogsread at source

Supple Studio Unveils Somer Valley Brewing Identity

Supple Studio gave Somer Valley Brewing a farm-made identity: an evolved logo, tractor-wheel textures, and witty farmyard illustrations. Somer Valley is not a typical craft brewery. On its Somerset fa...

AbduzeedoMulti Author Blogsread at source

Brand Identity: GGN Incorporadora by Fall Falci

Fall Falci develops a robust brand identity for Brazilian construction firm GGN, balancing monumental typography with raw masonry substrates. Rooted in Juiz de Fora, Minas Gerais, GGN has steadily exp...

freeCodeCamp.orgYouTube ChannelsVideoWatch on YouTube

Design Software Systems Like a Senior Engineer – Complete Course

AbduzeedoMulti Author Blogsread at source

Erik Gustafsson — Editorial Design by Lundgren+Lindqvist

Lundgren+Lindqvist designed the monograph for Erik Gustafsson, shaping an editorial design defined by darkroom pacing and tactile materiality. Berlin-based Swedish artist Erik Gustafsson created Pause...

DigitalOcean BlogMulti Author Blogs4 min read

DigitalOcean Inference Router Enhancements: Performance Tuned Routing, No Rules to Write

Every few weeks, a new model steps up and claims best-in-class at something. The launch chart makes the case, the link makes the rounds, and your team is back to the question nobody has time for: should we switch? The answer takes a week of evals, side-by-side tests and debate,…

QuirksBlogTop Front-end Bloggersread at source

Mucking about with mobile browsers

Today, for the first time in ten years, I bought a test phone (a second-hand Galaxy S21) and worked on creating my first mobile browser test array in nine years. Here’s a few fun facts that I noticed. My array consists only of one iPhone and one Galaxy — quite a difference with the past, when I routinely used about twelve to fifteen devices. Still, let’s start small. The phone market is simpler than back in 2012. And these two phones have one advantage I thought I’d never have: they use the same charger !!!! I thoughtlessly switched the charger from Galaxy to iPhone. And! It! Worked! 2012 would not believe you. Your choice is important to us The Galaxy has a browser/search engine choice menu nowadays. That’s fair, I’d say, given that the iPhone has one as well. Both these lists are very long, and that will likely put off consumers. That’s the point of such long lists. Anyway, I knew what I wanted on my Galaxy. Chrome, Samsung Internet, UC, Firefox, Vivaldi. The first two were already on it. The others required use of the Play Store, which, incidentally, doesn't have a search bar by default any more. Sure, there’s a menu item, but it’s not the same. (A search bar by default might be a useful feature for the EU to require. Consumers must have choice.) When I’d found UC I also saw Firefox. Cool, two downloads in one screen. Then I looked further and saw that Firefox was a sponsored result. Same when I searched for Vivaldi. Clearly, someone at Mozilla bought a bunch of good keywords. Zoom reflow! Coolest feature last. It turns out that UC supports zoom reflow . That is, when you resize the visual viewport, the text adapts to the new width and fits snugly. This used to be an HTC thing back in the days (but today nobody remembers HTC). Now, apparently, it’s a UC thing. The downside of this feature is that it must be very expensive in terms of reflowing the page. I don’t doubt that there will be exceptions and things where the page doesn’t reflow. But I discovered it only an hour ago, so I will bask in the radiance of my absolute favourite mobile feature returning from the dead. Difficult questions will have to wait for tomorrow.

Bram.usMore Front-end Bloggers5 min read

Introducing css-typed-om, a complete and WPT-tested polyfill for CSS Typed OM

Being a big fan of the CSS Typed OM , I’ve wanted a proper polyfill for it for years. Just before my summer vacation back in July, with the help of Gemini/Antigravity, I finally built one: css-typed-om .

Flavio CopesMore Front-end Bloggersread at source

A deep dive into LangChain and LangGraph

Learn LangChain and LangGraph with TypeScript: models, prompts, tools, agents, memory, streaming, RAG, graphs, persistence, and human approval.

HeyDesignerDeveloper/Designer Newsread at source

Craft: A collection of design engineering concepts

The dock on Mac, from OS 10 to macOS 27, How to present a proposal to a client (video), Murmuration for growing design teams, New to the web platform in September .

The Mozilla BlogBrowsers, engines, etc.4 min read

Mozilla introduces Firefox Enterprise

Institutions are recalculating who controls the technology they rely on. Mozilla has an independent option to offer. For years, organizations consolidated technology around a small number of providers to make things simpler. Fewer systems. Tighter integrations. More economies of scale. But that consolidation went well beyond technology. It consolidated dependency, too. The resulting risks have […] The post Mozilla introduces Firefox Enterprise appeared first on The Mozilla Blog .

Auth0 BlogCompany/Startup Blogsread at source

Introducing the Auth0 SDK for TanStack Start

Meet the new Auth0 SDK for TanStack Start and learn how to use it to add authentication to your apps.

JavaScript WeeklyMulti Author Blogsread at source

Ryan Dahl: 'Why reimplement Node? It works.'

#​806 — October 13, 2026 Read on the Web JavaScript Weekly Deno is Joining Cloudflare (But…) — Maybe David Bushell saw the writing on the wall , as the Deno team isn't joining Cloudflare to keep working on Deno , but to fold celld into workerd so Durable Objects can be self-hosted ( more on that here ). The Deno runtime will get a final year of official fixes, Deno Deploy closes in six months, and JSR moves to Cloudflare's infrastructure. Ryan Dahl 💡 On Hacker News , Ryan Dahl noted that Deno "has been sucked into the gravity well of Node compatibility" before asking: "Why reimplement Node? It works." But what happens to the JavaScript™ trademark case , I wonder…? CodeAF: #1 of Ten Coding Harnesses on DeepSWE — Ten coding harnesses ran the same open model on 113 real GitHub issues. CodeAF solved the most and paid the least per solved issue: 3.4x less than Claude Code, 4.8x less than OpenCode. A new open-source coding harness built for open models. AgentField AI sponsor Bun 1.4.3 Adds bun check , a Built-In TypeScript Type Checker — bun check is a port of TypeScript 7's checker that reads your tsconfig.json , reports the same errors as tsc and, Jarred claims, runs 3-6x faster. It plugs into bun run / test / build too. Idle server processes now use far less CPU, and a JavaScriptCore upgrade picks up numerous perf gains . Jarred Sumner IN BRIEF: AWS has launched Lambda Web Functions , which run an ordinary port-listening Node server (Express, Hono, Fastify, etc.) on Lambda with no handler rewrite, billing for active CPU time and separately for memory. 📊 The 2026 Stack Overflow Developer Survey results are out (30,903 people took part) with JavaScript the #1 language for the 12th year in a row (and TypeScript at #6). 🔒 Despite this week's fresh stir , no malicious Zod release reached npm. Malicious commits pushed to its repo in September were reverted the same day, as Colin McDonnell explains . 🔒 An out-of-band Next.js security release is due tomorrow . RELEASES: Last second addition: TanStack Start 1.0 has just dropped. Big news for full-stack React and Solid fans! :-) 🎉 Partytown 1.0 – A popular way to relocate third-party scripts to run in a Web Worker rather than on the main thread has left beta after five years in development. Marionette 5.0 – Six years on, the Backbone-era framework returns with a core free of Backbone, jQuery and Underscore… and they explain why! Bootstrap 6 Alpha – An early look at Bootstrap's first major release since 2021, leaning on modern CSS and making its JavaScript plugins ESM-only. Express 5.3.0 – A maintenance release worth upgrading to, as patched qs , proxy-addr and body-parser dependencies close five CVEs. 📖 Articles and Videos 📊 WebSocket Servers in JavaScript: Node.js, Bun, and Deno — In 2023, Daniel found Bun much faster than Node at relaying WebSocket messages, but there was a bug in his Bun server. This new attempt uses a C client/relay as a baseline, and Node 26 now gets close to C latency, ahead of Bun and Deno. Daniel Lemire How Sindre Sorhus' Personal Site is Now Made in Swift — One of JavaScript's most prolific developers explains how he's dropped Astro and now builds his personal site with Swift, including the styling and markup, with broken links and style typos failing at compile time ( source ). Sindre Sorhus Too Many Agent Traces to Read? Find the Ones That Matter, Live Oct 14 — Bad answers, wrong tool calls, too many traces. See how Sentry engineers find the failures worth fixing. Register now . Sentry sponsor Tiny Apps with TinyJS — A quick look at a new way to make tiny JS-powered desktop apps we featured a few weeks ago. Raymond Camden 📄 Yet Another Way to Invoke Functions Without Parentheses – There are many ways to invoke arbitrary functions in JavaScript without using parens, but this is a particularly obscure one! bartosz 📄 Six Months of Building with Remix 3 – What the post-React Remix (v3 was released earlier this month) is like to work with day to day. Sergio Xalambrí 📄 A Visual Notation for React's Parent and Owner Trees – With a playground that draws them from your code. Jules Blom 📄 How to Test an iframe 's postMessage Handler Keshav Malik 🛠 Code & Tools 🤖 OpenCode 2.0: A Big Update for the Open Coding Agent — A full-featured agentic coding app, built on Bun, that's more akin to Claude Code than Pi , say. v2.0 overhauls it with background subagents, a 'code mode' to let models script MCP tool calls, and clients for vanilla JS and Effect code to drive it. Anomaly / The OpenCode Team 💡 If you've not given OpenCode a try yet, you can get started here . Tamagui 3: One React UI Codebase for Web and Native — A styling system and component kit for sharing UI between React web apps and React Native, with a compiler that keeps things fast on both. v3 adds Tailwind-style props and React Strict DOM support. Nate Wienert Mobile AI Infrastructure for Web Devs Who Code with Agents — Point the agent you use for the web at iOS and Android. Expo takes care of the native builds and the trip to the stores. Expo sponsor H3 v2: The UnJS HTTP Framework Rebuilt on Web Standards — The minimal HTTP framework behind Nitro and Nuxt's server layer is now stable in v2, a rewrite around standard Request and Response so the same app runs on Node, Bun, Deno, Workers, and even in the browser. Migration guide . Pooya Parsa Shaders: 190+ WebGPU Effect Components, Now Open Source — Ripples, glows, and dissolves into ASCII, composed as components rather than written as shader code, for React, Vue, Svelte, Solid, or plain JS. The engine, framework bindings, and the components themselves are now all MIT licensed. Simon Le Marchant 💡 If you like this vibe, ascii.rest , which offers "236 animated ASCII pieces for web pages" , is also worth a look. Node.js v26.11.0 (Current) – Adds a --process-timeout flag to end a process after a set time, plus virtual table support in node:sqlite . Hono 5.0 RC – The web-standards server framework goes ESM-only and moves its runtime adapters into separate packages. 🔒 Handlebars 4.7.10 – The templating library fixes two critical JavaScript injection flaws affecting releases back to 3.0. he 2.0 – Robust HTML entity encoder/decoder. First release in eight years, now ESM with named exports. React Aria 1.22 – Adds a new Sheet component . pnpm 12.12 📰 Classifieds ⚡️Add lightning-fast 1D/2D barcode scanning to your web app with STRICH . On-device processing, free trial and demo! Durable AI agents built with the AI SDK you already use. Long-lived LLM sessions that survive deploys, crashes & refreshes. Test out chat.agent on Trigger.dev . 🎬 Your app needs video, not a video team. Upload any format to Hyperserve's API , get back MP4 on a global CDN. Ship video in an afternoon. 📢 Elsewhere in the ecosystem In Fingerprints are the New Cookies , Roy Fish demonstrates the various ways web pages can assign a unique(ish) identity to you using JavaScript. 🤖 Theo Browne set AI agents loose on porting the TypeScript 7 compiler to Rust, and ts-rust is the (very experimental) result. 📱 Following Shopify, Coinbase is moving its app off React Native , saying agents have made building each feature twice cheap enough to go fully native. Fancy a retro robot voice in your web experience? Klattsch is a voice synthesizer you can use on the web or from Node.js as an npm package. Daiiisy, daiiisy… Three years ago we mentioned Linus Groh's Zig-based Kiesel JavaScript engine. It passed 25% of test262 back then, but v0.4.0 has landed and it's now at 94.7% (not far behind V8) and supports modern language proposals like await dictionary and numerous iterator proposals.

Jens Oliver MeiertTop Front-end Bloggersread at source

CSS Optimization: Is Using Declarations Just Once (UDJO) Still Effective Today?

On the merit of an old CSS maintainability and performance optimization technique.

AbduzeedoMulti Author Blogsread at source

Shake-it Mixer: Inside OlssønBarbieri Packaging Design

OlssønBarbieri crafted a refined packaging design for Shake-it Mixer, pairing custom fluted glass with 19th-century medicinal labels. Home mixology often relies on artificial cordials in dull plastic ...

Engineering at MetaCompany/Startup Blogs11 min read

OCP Summit 2026: Powering AI with Open Innovations in Scale-Up, Scale-Out, and Scale-Across Networks

At the 2026 Open Compute Project Global Summit, Meta is sharing the next generation of open networking infrastructure, including: Our first liquid-cooled network rack (IcePack), and 102.4T switch platform (IceCube). Flattened Planar Fabric (FPF), a multiplane backend scale-out fabric that fundamentally changes how GPUs connect to the network MetaRoCE, our open-source AI transport protocol. Launching [...] Read More... The post OCP Summit 2026: Powering AI with Open Innovations in Scale-Up, Scale-Out, and Scale-Across Networks appeared first on Engineering at Meta .

Treehouse BlogMulti Author Blogsread at source

How to Get Free Coding Courses Through Your Public Library

You don’t need a paid subscription to start learning to code — if your local library partners with Treehouse, you already have access! Get Treehouse for Free Treehouse is available for free to patrons of participating public libraries across the... The post How to Get Free Coding Courses Through Your Public Library appeared first on Treehouse Blog .

Treehouse BlogMulti Author Blogsread at source

A Developer’s Honest Take on AI: An Interview with Gustavo Medori

iOS developer Gustavo Medori has shipped software for a decade. Here's how he uses AI to kill the busywork, write better code, and protect the parts of the job he loves. The post A Developer’s Honest Take on AI: An Interview with Gustavo Medori appeared first on Treehouse Blog .