Falkon is a lightweight and customizable web browser built with the Qt framework and focused on KDE integration. It utilizes QtWebEngine to render web pages, offering speed and standards compliance while remaining resource-efficient. Falkon prioritizes user privacy and offers features like ad blocking and tracking protection. Customization is key, allowing users to tailor the browser with extensions, adjust the interface, and manage their browsing data effectively. Overall, Falkon aims to be a fast, private, and user-friendly browsing experience deeply integrated into the KDE desktop environment.
In 2008, amidst controversy surrounding its initial Chrome End User License Agreement (EULA), Google clarified that the license only applied to Chrome itself, not to user-generated content created using Chrome. Matt Cutts explained that the broad language in the original EULA was standard boilerplate, intended for protecting Google's intellectual property within the browser, not claiming ownership over user data. The company quickly revised the EULA to eliminate ambiguity and explicitly state that Google claims no rights to user content created with Chrome. This addressed concerns about Google overreaching and reassured users that their work remained their own.
HN commenters in 2023 discuss Matt Cutts' 2008 blog post clarifying Google's Chrome license agreement. Several express skepticism of Google, pointing out that the license has changed since the post and that Google's data collection practices are extensive regardless. Some commenters suggest the original concern arose from a misunderstanding of legalese surrounding granting a license to use software versus a license to user-created content. Others mention that granting a license to "sync" data is distinct from other usage and requires its own scrutiny. A few commenters reflect on the relative naivety of concerns about data privacy in 2008 compared to the present day, where such concerns are much more widespread. The discussion ultimately highlights the evolution of public perception regarding online privacy and the persistent distrust of large tech companies like Google.
Microsoft Edge users are reporting that the browser is disabling installed extensions, including popular ad blockers like uBlock Origin, without user permission. This appears to be related to a controlled rollout of a new mandatory extension called "Extensions Notifications" which seems to conflict with existing extensions, causing them to be automatically turned off. The issue is not affecting all users, suggesting it's an A/B test or staged rollout by Microsoft. While the exact purpose of the new extension is unclear, it might be intended to improve extension management or notify users about potentially malicious add-ons.
HN users largely express skepticism and concern over Microsoft disabling extensions in Edge. Several doubt the claim that it's unintentional, citing Microsoft's history of pushing its own products and services. Some suggest it's a bug related to sync or profile management, while others propose it's a deliberate attempt to steer users towards Microsoft's built-in tracking prevention or Edge's own ad platform. The potential for this behavior to erode user trust and push people towards other browsers is a recurring theme. Many commenters share personal anecdotes of Edge's aggressive defaults and unwanted behaviors, further fueling the suspicion around this incident. A few users provide technical insights, suggesting possible mechanisms behind the disabling, like manifest mismatches or corrupted profiles, and offering troubleshooting advice.
Mozilla's Firefox Terms state that they collect information you input into the browser, including text entered in forms, search queries, and URLs visited. This data is used to provide and improve Firefox features like autofill, search suggestions, and syncing. Mozilla emphasizes that they handle this information responsibly, aiming to minimize data collection, de-identify data where possible, and provide users with controls to manage their privacy. They also clarify that while they collect this data, they do not collect the content of web pages you visit unless you explicitly choose features like Pocket or Firefox Screenshots, which are governed by separate privacy policies.
HN users express concern and skepticism over Mozilla's claim to own "information you input through Firefox," interpreting it as overly broad and potentially invasive. Some argue the wording is likely a clumsy attempt to cover necessary data collection for features like sync and breach alerts, not a declaration of ownership over user-created content. Others point out the impracticality of Mozilla storing and utilizing such vast amounts of data, suggesting it's a legal safeguard rather than a reflection of actual practice. A few commenters highlight the contrast with Firefox's privacy-focused image, questioning the need for such strong language. Several users recommend alternative browsers like LibreWolf and Ungoogled Chromium, perceiving them as more privacy-respecting alternatives.
Mozilla has updated its Terms of Use and Privacy Notice for Firefox to improve clarity and transparency. The updated terms are written in simpler language, making them easier for users to understand their rights and Mozilla's responsibilities. The revised Privacy Notice clarifies data collection practices, emphasizing that Mozilla collects only necessary data for product improvement and personalized experiences, while respecting user privacy. These changes reflect Mozilla's ongoing commitment to user privacy and data protection.
HN commenters largely express skepticism and frustration with Mozilla's updated terms of service and privacy notice. Several point out the irony of a privacy-focused organization using broad language around data collection, especially concerning "legitimate interests" and unspecified "service providers." The lack of clarity regarding what data is collected and how it's used is a recurring concern. Some users question the necessity of these changes and express disappointment with Mozilla seemingly following the trend of other tech companies towards less transparent data practices. A few commenters offer more supportive perspectives, suggesting the changes might be necessary for legal compliance or to improve personalized services, but these views are in the minority. Several users also call for more specific examples of what constitutes "legitimate interests" and more details on the involved "service providers."
The author successfully ran 240 instances of a JavaScript Pong game simultaneously in separate browser tabs, pushing the limits of browser performance. They achieved this by meticulously optimizing the game code for minimal CPU and memory usage, employing techniques like simplifying graphics, reducing frame rate, and minimizing DOM manipulations. Despite these optimizations, the combined processing load still strained the browser and system resources, causing noticeable lag and performance degradation. The experiment showcased the surprising capacity of modern browsers while also highlighting their limitations when handling numerous computationally intensive tasks concurrently.
Hacker News users generally expressed amusement and mild interest in the project of running Pong across multiple browser tabs. Some questioned the practicality and efficiency, particularly regarding resource usage. One commenter pointed out potential improvements by using Web Workers or SharedArrayBuffers for better performance and inter-tab communication, avoiding the limitations of localStorage. Others suggested alternative, more efficient methods for achieving the same visual effect, such as using a single canvas element and drawing the game state across it. A few appreciated the whimsical nature of the project, acknowledging its value as a fun experiment despite its lack of practical application.
The Chrome team is working towards enabling customization of the <select> element using the new <selectmenu> element. This upcoming feature allows developers to replace the browser's default dropdown styling with custom HTML, offering greater flexibility and control over the appearance and functionality of dropdown menus. Developers will be able to integrate richer interactions, accessibility features, and more complex layouts within the select element, all while preserving the semantic meaning and native behavior like keyboard navigation and screen reader compatibility. This enhancement aims to address the longstanding developer pain point of limited styling options for the <select> element, opening up opportunities for more visually appealing and user-friendly form controls.
Hacker News users generally expressed frustration with the <select> element's historical limitations and welcomed the proposed changes for customization. Several commenters pointed out the difficulties in styling <select> cross-browser, leading to reliance on JavaScript workarounds and libraries like Choices.js. Some expressed skepticism about the proposed solution's complexity and potential performance impact, suggesting simpler alternatives like allowing shadow DOM styling. Others questioned the need for such extensive customization, arguing for consistency and accessibility over visual flair. A few users highlighted specific use cases, such as multi-select with custom item rendering, where the proposed changes would be beneficial. Overall, the sentiment leans towards cautious optimism, acknowledging the potential improvements while remaining wary of potential drawbacks.
Ruby on Rails applications can now run directly in web browsers thanks to WebAssembly. This is achieved using a new project called "Spreetail/wunderbar-wasm", which compiles Ruby and Rails to WASM using a custom-built toolchain. This allows developers to build full-stack Rails apps that execute client-side, offering potential performance benefits for certain applications by reducing server roundtrips. The WASM approach allows for offline functionality and removes the need for separate frontend and backend deployments. While still experimental, this technology opens up new possibilities for building web applications with Ruby on Rails.
Hacker News commenters expressed skepticism about the practicality of running Ruby on Rails in the browser via WebAssembly. Concerns focused on performance, particularly startup time and overall speed, doubting it would be suitable for production applications. Some suggested alternative approaches for achieving similar functionality, like using a server-rendered backend with a JavaScript frontend framework. Others questioned the use cases, wondering if the complexity was worth the effort compared to established approaches. Several commenters pointed to the large size of the Wasm bundle as a major drawback. A few expressed cautious optimism, acknowledging the technical achievement while remaining unsure of its real-world applicability. Finally, some highlighted the potential benefits for specific niches, such as online code editors or interactive tutorials.
Some websites display boxes instead of flag emojis in Chrome on Windows due to a font substitution issue. Windows uses its own Segoe UI Emoji font for most emoji, but defaults to a lower-quality bitmap font called "Segoe UI Symbol" specifically for flag emojis. This bitmap font lacks the necessary glyphs for many flag combinations, resulting in the missing emoji. Websites can force Chrome to use the correct, vector-based Segoe UI Emoji font by explicitly specifying it in their CSS, ensuring flags render properly.
Commenters on Hacker News largely discuss the technical details behind the issue, focusing on the surprising interaction between Chrome, Windows, and the specific way flags are rendered using two combined code points. Several point out the complexity and unexpected behaviors that arise from combining characters, particularly when dealing with different systems and fonts. Some users express frustration with the inconsistency and lack of clear documentation around emoji rendering. A few commenters offer potential workarounds or solutions, including using a fallback font or pre-rendering the flags as images. Others delve into the history and evolution of emoji standards and the challenges of maintaining compatibility across platforms. A compelling comment thread explores the tradeoffs between using the combined code points for flags versus using dedicated single code points, highlighting the performance implications and rendering complexities. Another interesting discussion revolves around the role of fonts and the challenges of designing fonts that support a rapidly expanding set of emojis.
The "Subpixel Snake" video demonstrates a technique for achieving smooth, subpixel-precise movement of a simple snake game using a fixed-point integer coordinate system. Instead of moving the snake in whole pixel increments, fractional coordinates are used internally, allowing for smooth, seemingly subpixel motion when rendered visually. The technique avoids floating-point arithmetic for performance reasons, relevant to the target platform (likely older or less powerful hardware). Essentially, the game maintains higher precision internally than what is displayed, creating the illusion of smoother movement.
HN users largely praised the Subpixel Snake game and its clever use of subpixel rendering for smooth movement. Several commenters discussed the nostalgic appeal of such games, recalling similar experiences with old Nokia phones and other limited-resolution displays. Some delved into the technical aspects, explaining how subpixel rendering works and its limitations, while others shared their high scores or jokingly lamented their wasted time playing. The creator of the game also participated, responding to questions and sharing insights into the development process. A few comments mentioned similar games or techniques, offering alternative approaches to achieving smooth movement in low-resolution environments.
Summary of Comments ( 40 )
https://news.ycombinator.com/item?id=43297590
HN users discuss Falkon's performance, features, and place within the browser ecosystem. Several commenters praise its speed and lightweight nature, particularly on older hardware, comparing it favorably to Firefox and Chromium-based browsers. Some appreciate its adherence to QtWebEngine, viewing it as a positive for KDE integration and a potential advantage if Chromium's dominance wanes. Others question Falkon's differentiation, suggesting its features are replicated elsewhere and wondering about the practicality of relying on QtWebEngine. The discussion also touches on ad blocking, extensions, and the challenges faced by smaller browser projects. A recurring theme is the desire for a performant, non-Chromium browser, with Falkon presented as a possible contender.
The Hacker News post titled "Falkon: A KDE Web Browser" has generated a modest number of comments, mostly focusing on Falkon's performance, features, and its place within the broader browser ecosystem.
Several commenters praise Falkon's speed and lightweight nature, particularly appreciating its responsiveness compared to other browsers. One user specifically highlights its efficiency on older hardware, mentioning its snappy performance on a ten-year-old laptop. This sentiment is echoed by others who find it a viable alternative to more resource-intensive browsers.
The discussion also touches upon Falkon's use of QtWebEngine. Some express concern about potential performance limitations and memory usage associated with QtWebEngine. However, counterarguments suggest that these concerns are either outdated or overblown, with some users reporting satisfactory performance in their experience.
Falkon's integration with the KDE desktop environment is another recurring theme. Commenters appreciate the seamless integration with KDE's features and settings. This integration is seen as a significant advantage for users already invested in the KDE ecosystem.
A few comments delve into specific features, such as ad blocking and the ability to disable JavaScript. These features are viewed positively, aligning with users' desire for a customizable and privacy-respecting browsing experience.
Some users share their history with Falkon, mentioning their past usage and reasons for switching to or from the browser. These anecdotes provide valuable insights into the browser's evolution and its strengths and weaknesses from a user perspective.
Finally, a few comments compare Falkon to other browsers like Firefox and Konqueror. While acknowledging Falkon's merits, some express a preference for established alternatives due to factors like broader extension support or familiarity.
Overall, the comments paint a picture of Falkon as a nimble and KDE-integrated browser appreciated by a niche user base for its speed and efficiency. While questions about QtWebEngine's performance linger, many users report positive experiences, particularly on less powerful hardware. The discussion highlights Falkon's role as a viable alternative for users seeking a lightweight and KDE-centric browsing experience.