Nue.js is a new JavaScript framework focusing on extreme performance and minimal bundle size for complex web apps. It achieves this through a reactive core inspired by SolidJS and Svelte, compiling templates to optimized vanilla JavaScript, and offering built-in features like routing, state management, and SSR. The blog post demonstrates Nue's efficiency by showcasing a full-featured to-do MVC app with a bundle size smaller than a single React button, while maintaining excellent performance metrics. This makes it particularly suitable for situations where performance and low bandwidth consumption are critical, such as mobile-first development and slow networks.
Open-UI aims to establish and maintain an open, interoperable standard for UI components and primitives across frameworks and libraries. This initiative seeks to improve developer experience by enabling greater code reuse, simplifying cross-framework collaboration, and fostering a more robust and accessible web ecosystem. By defining shared specifications and promoting their adoption, Open-UI strives to streamline UI development and reduce fragmentation across the JavaScript landscape.
HN commenters express cautious optimism about Open UI, praising the standardization effort for web components but also raising concerns. Several highlight the difficulty of achieving true cross-framework compatibility, questioning whether Open UI can genuinely bridge the gaps between React, Vue, Angular, etc. Others point to the history of similar initiatives failing to gain widespread adoption due to framework lock-in and the rapid evolution of the web development landscape. Some express skepticism about the project's governance and the potential influence of browser vendors. A few commenters see Open UI as a potential solution to the "island problem" of web components, hoping it will improve interoperability and reduce the need for framework-specific wrappers. However, the prevailing sentiment is one of "wait and see," with many wanting to observe practical implementations and community uptake before fully endorsing the project.
Svelte 5 significantly departs from its JavaScript framework roots by compiling components directly to vanilla JavaScript instructions that manipulate the DOM. This eliminates the virtual DOM diffing process typical of other frameworks, resulting in smaller bundle sizes and potentially faster performance. Instead of a framework mediating interactions, Svelte 5 generates imperative code tailored to each component, directly updating the DOM. This shift allows for optimized updates and reduces runtime overhead, making Svelte 5 applications more akin to handcrafted JavaScript than traditional framework-driven applications. While still using familiar Svelte syntax, the output is now a highly optimized, self-contained JavaScript module.
HN users discuss Svelte 5's compilation strategy, which moves reactivity out of the JavaScript runtime and into compiled code. Several commenters express excitement over the potential performance benefits and smaller bundle sizes, comparing it favorably to React and other frameworks. Some raise concerns about debugging and the implications for the ecosystem, particularly around tooling. A few express skepticism, questioning whether the performance gains are significant enough to warrant the shift and whether Svelte's approach will hinder wider adoption. There's also discussion about the blurring line between frameworks and compilers, and whether Svelte's compiled output still qualifies as JavaScript. The impact on hydration and server-side rendering is also a topic of interest.
celine/bibhtml introduces a set of web components designed to simplify creating and managing references within HTML documents. It leverages a bibliography file (BibTeX or CSL-JSON) to generate citations and a bibliography list automatically. By using custom HTML tags, authors can easily insert citations and the library dynamically renders them with links to the full bibliographic entry. This approach aims to offer a more integrated and streamlined workflow compared to traditional methods for handling references in web pages.
HN users generally praised the project for its simplicity and ease of use compared to existing citation tools. Several commenters appreciated the focus on web standards and the avoidance of JavaScript frameworks, leading to a lightweight and performant solution. Some suggested potential improvements, such as incorporating DOI lookups, customizable citation styles (like Chicago or MLA), and integration with Zotero or other reference managers. The discussion also touched on the benefits of using native web components and the challenges of rendering complex citations correctly within the flow of HTML. One commenter noted the similarity to the ::cite pseudo-element, suggesting the project could explore leveraging that functionality. Overall, the reception was positive, with many expressing interest in using or contributing to the project.
Summary of Comments ( 308 )
https://news.ycombinator.com/item?id=43543241
Hacker News users discussed the performance benefits of Nue.js, particularly its small bundle size compared to React. Some expressed skepticism about the benchmark methodology and questioned whether the "lighter than a React button" claim held true in real-world scenarios. Others were interested in the framework's approach and appreciated its focus on simplicity and performance. Several commenters pointed out the difficulty of comparing frameworks based on microbenchmarks and emphasized the importance of overall developer experience and ecosystem maturity. The lack of TypeScript support was also mentioned as a potential drawback. A few users discussed the tradeoffs between using a smaller, less mature framework like Nue.js versus a more established option like React, Svelte, or Preact.
The Hacker News post "Show HN: Nue – Apps lighter than a React button" generated a moderate amount of discussion, with several commenters engaging with the premise of the framework being lighter than React.
Several users focused on the practicality and relevance of the comparison to a single React button. One commenter questioned the fairness and usefulness of comparing an entire framework to a single component of another, suggesting that a more appropriate comparison would be to a minimal React app. Another echoed this sentiment, pointing out that a button in React incorporates the entire React library, making the comparison somewhat misleading. This user suggested a more accurate metric would be to compare a basic "hello world" application in both frameworks.
The discussion also touched upon the perceived complexity introduced by the choice of Rust and WebAssembly. One user argued that the use of these technologies would increase the complexity of development and debugging, particularly for tasks like profiling, and questioned whether the performance benefits would outweigh these downsides. Another user expressed concern about the overall ecosystem surrounding WebAssembly and Rust for front-end development, highlighting the potential difficulties in integrating with existing JavaScript tooling and libraries. The comment also expressed concern for a smaller community which could lead to a lack of resources to fix issues.
Some commenters shifted the focus from the size comparison to the more general benefits of using Rust and WebAssembly for front-end frameworks. One user highlighted the potential for performance gains, while another pointed out that the claimed size reduction might not be the most significant advantage. This commenter suggested that the performance improvements, especially in computationally intensive applications, could be a more compelling selling point.
Others questioned the long-term viability of the project and the potential challenges of maintaining a Rust and WebAssembly based front-end framework. One commenter expressed concern about the learning curve and the potential difficulties in attracting and retaining developers familiar with these technologies.
Finally, a few commenters requested more concrete examples and demonstrations of the framework's capabilities beyond the basic comparisons presented. They expressed interest in seeing real-world applications built with Nue to better assess its performance and practicality. One commenter asked about the status of a to-do list application that was mentioned in the past and how that would stack up in comparison to different implementations.