Developer Releases Pure Python JavaScript Runtime with C FFI and DOM Support

·3 views

A developer has published 'myjs' on PyPI, a JavaScript runtime built entirely in Python that enables JS code to run within a Python process. The runtime uses a Python-ported Acorn AST engine to parse and execute JavaScript, giving scripts direct access to Python's standard library and OS capabilities. It integrates with the domonic library for server-side DOM manipulation and leverages Python's ctypes and cffi modules for low-level access to native C binaries. The project aims to eliminate the need for tools like node-gyp, C++ addon build chains, or IPC bridges such as gRPC when combining JavaScript with native libraries. It can be installed via pip or pipx and is positioned as a lightweight, portable alternative to embedding engines like V8.

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)

Dev shares workflow for building company websites with AI tools and Nginx setup

A developer at DEV Community has documented their experience building a company official website and several sub-sites, highlighting lessons learned during deployment—particularly around domain-to-IP mapping. The article outlines a modern web development workflow spanning feasibility study, prototyping, UI design, coding, testing, and deployment, with AI tools like Cursor, Claude, and Codebuddy playing a central role. The author notes that AI has transformed prototyping by allowing requirements documents to be fed directly into tools that generate functional web pages, replacing slower drag-and-drop methods. A key observation is that UI designers can now export HTML, Vue, or TSX files directly from design platforms, reducing the handoff burden on front-end engineers. The developer argues this shift is gradually blurring the traditional distinction between front-end and back-end engineering roles.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Corporate Compliance and Code Reviews Killed the Secret Easter Egg

Easter eggs — hidden features secretly embedded by developers in software — date back to 1979, when Atari programmer Warren Robinett hid his name inside the game Adventure without telling anyone. Microsoft Excel 97 famously contained a fully functional flight simulator, complete with randomly generated terrain and a developer credits monolith, unknown to most users. Microsoft banned easter eggs in 2002 after a memo from Bill Gates raised concerns that undocumented hidden code was indistinguishable from security backdoors, a problem especially acute for government clients. Beyond corporate policy, modern software development practices — including mandatory code reviews, audit trails, and continuous patching — make it nearly impossible for a single developer to quietly embed an unauthorised hidden feature. The conditions that once allowed easter eggs to exist, namely small teams, unreviewed code, and unpatched cartridges, have been systematically eliminated by the software industry's push for security and accountability.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Local AI Inference on Consumer Macs Is Becoming Everyday Infrastructure

Growing consumer demand for running AI models locally has reportedly caught Apple off guard, with Mac Mini and Mac Studio units selling out as buyers prioritize on-device inference over traditional computing tasks. A recent demonstration showed a 104GB model running at roughly 12 tokens per second on a 48GB Mac Mini, highlighting how quantization techniques are closing the gap between hardware limits and model size. Separate community posts indicate that local AI setups are no longer niche experiments but routine configurations for everyday users. Analysts and developers note that the local AI tier differs from frontier lab competition, focusing on model-hardware fit, privacy, and zero per-token cost rather than raw scale. Key gaps identified in the ecosystem include local-first workflow templates, model selection guides, and reproducible benchmarks — areas where smaller developers may find the most opportunity.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

FSx for ONTAP S3 Access Points Support Qtrees, Quotas and FlexClone Despite Docs

A developer completing a six-part series on building a file portal with Amazon FSx for NetApp ONTAP tested whether core ONTAP features remain usable when accessing storage via AWS S3 access points. Testing conducted on 26 August 2026 in the ap-northeast-1 region found that qtrees, tree quotas, FlexClone at both volume and file granularity, and FlexGroup volumes all functioned correctly through the S3 access point path, despite NetApp documentation listing them as unsupported for the ONTAP S3 server. The author cautions that documentation restrictions on the ONTAP S3 server do not automatically apply to the AWS S3 access point path, since the two mechanisms are distinct. However, three undocumented issues were uncovered: an NTFS volume with a UNIX identity silently blocks all data operations with AccessDenied despite showing as available, newly created volumes can take 10–20 minutes to appear in the AWS API, and volumes that have ever hosted an S3 access point cannot be deleted from the ONTAP side even after detachment. The series concludes by noting that scheduled automation, rather than manual portal controls, handles certain recurring storage operations in this architecture.

0 comments Read more at DEV Community