Developer builds offline-capable survey widget requiring no backend or dependencies

·1 views

A developer has released AuraSurvey, a vanilla JavaScript survey widget designed to function without an internet connection. The tool stores user responses in localStorage, allowing surveys to work seamlessly online or offline. It can be embedded into any website or mobile app webview using a single script tag, with no external dependencies required. AuraSurvey also includes built-in chart visualizations, PDF export functionality, and white-label support. The project was motivated by frustration with existing survey tools that fail without connectivity and require server-side infrastructure.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

C# Generic Math Explained: Static Abstractions Beyond Numerical Libraries

Generic Math, introduced in .NET 7 on November 8, 2022, allows C# developers to write generic code that enforces operators, identities, and type-level behavior without relying on reflection or dynamic dispatch. Before this feature, writing even a simple generic summation function was impossible in C# due to the lack of operator constraints on type parameters. The feature is built around interfaces in the System.Numerics namespace, such as IAdditionOperators and IAdditiveIdentity, which define static abstract members that types like Int32 can implement. Beyond arithmetic, the same mechanics apply to parsing, domain-driven design types, database models, tensors, and SIMD operations. Despite its power, Generic Math carries performance and complexity costs when overused, and a developer poll found that most C# programmers remain unfamiliar with the feature and its broader applications.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Feature Flag Mismanagement Behind Major Outages at Knight Capital, LinkedIn, DoorDash

Feature flags, software toggles used to control code behavior in production, have been linked to several high-profile tech failures when left unmanaged. A 2012 incident at Knight Capital saw a forgotten flag reactivate obsolete trading code, triggering $440 million in losses within 45 minutes and collapsing the firm. A June 2026 GrowthBook report found that 75% of feature flags linger in codebases for up to 49 weeks after their purpose ends, despite developers intending to remove them. DoorDash disclosed in August 2026 that it manages over 60,000 flags across 623 repositories, adding roughly 2,300 new ones monthly, with more than 1,000 already flagged as stale. LinkedIn suffered a full outage in February 2026 after an accidental change switched all feature flags on simultaneously, exposing the compounding risks of unaudited, accumulated toggles.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Hot Coffee Linked to Increased Oesophageal Cancer Risk, Study Suggests

New research suggests that drinking very hot coffee may be associated with a higher risk of developing oesophageal cancer. The findings, reported by The Economist in September 2026, point to heat — rather than coffee itself — as the likely contributing factor. Scientists believe repeated thermal injury to the lining of the oesophagus may trigger cancerous changes over time. The research adds to a growing body of evidence connecting the consumption of scalding hot beverages to oesophageal cancer risk.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Manual Edit, Script, or Browser Tool: How to Choose the Right Image Crop Method

Cropping images for the web involves three main approaches — manual editing in tools like Photoshop or GIMP, batch scripting via Python or ImageMagick, and browser-based utilities — each with distinct trade-offs. Manual editing suits single hero images or creative framing but introduces inconsistency when processing multiple files, which can cause alignment issues in product grids. Scripted pipelines using tools like Pillow, sharp, or ImageMagick excel at repetitive, rule-based tasks but require precisely defined crop logic and clean, uniform source files to function reliably. A practical pre-commitment test is to dry-run any script on ten sample files and review the outputs before scaling up. Choosing the right method depends on factors like file volume, consistency of the crop rule, and whether retouching needs to accompany the crop.

0 comments Read more at DEV Community