0. SpaceX to buy Cursor for $60B (reuters.com)
1148 points · 1699 comments · by itsmarcelg
We couldn't summarize this story. [src]
The acquisition of Cursor for $60B is viewed by many as a "bizarre" pivot that values the IDE at the cost of 150 modern hospitals [0]. Critics argue Cursor lacks a moat and is overvalued [4], while others suggest the deal is a strategic move to justify SpaceX's growth by targeting a massive $26 trillion AI market or facilitating space-based data centers [3][6][7]. While some engineers find Cursor’s interface "annoying" compared to direct LLM workflows [1], power users defend its "Plan Mode" and agentic capabilities as highly efficient for complex development [9]. Ultimately, the move is seen by some as a way for Elon Musk to consolidate his companies and inflate market caps through "Monopoly money" and speculative "meme" value [2][5][8].
1. Running local models is good now (vickiboykis.com)
1582 points · 604 comments · by jfb
Recent advancements in local AI models, such as Google’s Gemma 4 and OpenAI’s GPT-OSS, now allow for effective agentic coding and complex development tasks on personal hardware with performance nearing that of frontier API models. [src]
While local models like Qwen-2.5-27B are now considered viable daily drivers for tasks like coding, users disagree on whether the experience is truly "good" yet [0][1][9]. Proponents value the privacy, lack of rate limits, and absence of the "preachy" personalities found in commercial models like Claude [1][2][9], but critics argue that running them effectively requires expensive hardware, complex tuning, and results in loud, thermally constrained laptops [0][3][6][8]. There is a significant divide between those who see local hosting as a way to escape the "rent-seeking" cloud model and those who believe businesses will continue to pay a premium to outsource the headache of infrastructure management [2][4][5]. Ultimately, achieving performance comparable to top-tier APIs still necessitates substantial investments in VRAM and compute
2. GrapheneOS has been ported to Android 17 (discuss.grapheneos.org)
1017 points · 615 comments · by Cider9986
GrapheneOS has successfully been ported to Android 17, with official releases of the privacy-focused operating system expected to arrive soon. [src]
Users are increasingly migrating to GrapheneOS to escape intrusive marketing and "intelligence system" features in stock Android, such as forced movie promotions and deep AI integration [0][2][4]. While many appreciate the minimal, "de-Googled" experience, some note minor trade-offs like the lack of specific keyboard gestures and SMS reaction bugs [2]. A significant point of contention remains the hardware requirement; while Pixels are currently the only devices meeting the project's strict security standards, a forthcoming partnership with Motorola aims to expand availability to those who wish to avoid Google hardware entirely [6][7][9].
3. I admire Fabrice Bellard. He is almost certainly a better overall programmer (twitter.com)
936 points · 463 comments · by apitman
Renowned programmer John Carmack expressed his admiration for Fabrice Bellard, stating that Bellard is almost certainly a better overall programmer than himself. [src]
Fabrice Bellard is widely regarded as a "household name" in programming circles for his prolific ability to transform complex technical specifications into foundational software like FFmpeg and QEMU [1][5]. While some compare his genius to Mozart, others argue his work is characterized by "spaghetti code" and "ivory tower" development that prioritizes speed and proof-of-concept utility over long-term architectural elegance [0][2][3]. This has sparked debate over whether his success stems from raw technical skill or a unique talent for picking high-impact projects, with some critics noting that his lack of focus on maintainability has led to his original code being entirely replaced in projects like FFmpeg [4][6][7].
4. Is Meta destroying its engineering organization? (newsletter.pragmaticengineer.com)
662 points · 614 comments · by throwarayes
Meta is reportedly undermining its elite engineering culture by forcing thousands of developers into menial AI data-labeling roles, implementing invasive keystroke tracking, and prioritizing AI-generated code. These drastic shifts have led to plummeting morale, high-profile security outages, and a mass exodus of senior talent seeking more autonomous environments. [src]
The discussion reveals a deep-seated moral animosity toward Meta employees, with some arguing that engineers who chose to work there despite the company's documented societal harms deserve no sympathy [0][6]. While some defend the workers by noting that the roles would simply be filled by others [7], former employees suggest the internal culture is inefficient and largely sustained by the reputations of acquired companies like Instagram and WhatsApp [1][3]. Furthermore, there is skepticism regarding reports that high-priced engineers are being reassigned to data labeling, though others warn that this "AI psychosis" and the resulting toxicity are becoming an industry-wide trend [2][5].
5. Apple's weird anti-nausea dots cured my car sickness (theverge.com)
897 points · 270 comments · by neilfrndes
Apple’s Vehicle Motion Cues feature uses moving dots on the periphery of iPhone, iPad, and Mac displays to sync visual data with a vehicle's movement, effectively reducing or eliminating motion sickness for users. [src]
The "Vehicle Motion Cues" feature aims to resolve the sensory conflict between the eyes and the vestibular system, a discrepancy theorized to trigger an evolutionary "poisoning" response that causes nausea [1]. While some users are eager to test the feature for lifelong motion sickness, others report that current implementations—including third-party Android alternatives—do not work for everyone and may suffer from "rough" execution or excessive permission requirements [0][2][3][5]. Discussion also highlights a distinction between car sickness and "simulator sickness," where fixed-position viewing of moving screens (like FPS games) causes similar distress for some individuals [2][8].
6. Feds freaked over Fable 5 after 'fix this code', not jailbreak, say researchers (theregister.com)
611 points · 360 comments · by _tk_
A security researcher claims the U.S. government’s ban on Anthropic’s advanced AI models was based on a simple "fix this code" prompt rather than a sophisticated jailbreak, arguing that the restriction harms defensive cybersecurity efforts more than it deters attackers. [src]
The federal alarm over Fable 5 stems from a "jailbreak" that bypassed security guardrails simply by asking the model to "fix this code," which inadvertently generated exploits via test cases [0][5]. Commenters argue this highlights a fundamental flaw in AI safety: bulletproof denials are likely impossible because the model cannot distinguish between legitimate debugging and malicious intent without becoming useless for development [0][1][3]. While some suggest technical fixes like internal "verbal loops" or strict developer verification [2][9], others dismiss these as impractical and view the government's reaction as a "retaliatory shakedown" or a strategic move to maintain technological control [4][6][7].
7. Has AI already killed self-help nonfiction books? (tim.blog)
417 points · 487 comments · by imakwana
Author Tim Ferriss reports a sharp decline in self-help book sales, suggesting that AI chatbots are replacing prescriptive nonfiction by providing instant, personalized advice that previously required reading long-form texts. [src]
The self-help industry faces criticism as a "mafia" of interconnected influencers selling redundant products, with some users arguing that most books could be condensed into simple blog posts [0][8]. While skeptics question whether these materials offer any truly new information or facts, proponents credit specific communication and parenting techniques found in books and seminars with profoundly improving their personal lives and leadership abilities [1][3][8]. Meanwhile, the rise of AI and hypertext is seen as a superior alternative to long-form content, allowing users to bypass "filler" in videos and books to find actionable steps more efficiently [2][8].
8. Apple is about to make Hide My Email useless (arseniyshestakov.com)
527 points · 342 comments · by SXX
Apple is transitioning its "Hide My Email" and "Sign in with Apple" aliases to a new @private.icloud.com subdomain, a move critics argue will make it easier for services to identify and block these private addresses. [src]
Apple’s decision to move "Hide My Email" aliases to a dedicated `@private.icloud.com` subdomain has sparked concerns that websites will now find it trivial to identify and block privacy-conscious users [6]. While some users argue that they would rather avoid services that block such aliases [0], others point out that this is often impossible when dealing with essential utilities like municipal parking apps [5][9]. Proposed workarounds include using custom domains with catch-all forwarding [4], though critics note that personal domains can be less private and are occasionally blocked by services that only trust major providers [3][8]. Meanwhile, some business owners defend the ability to block these aliases, viewing anonymity as a potential liability or risk signal [7].
9. Mechanical Watch (2022) (ciechanow.ski)
741 points · 128 comments · by razin
This article provides a detailed technical breakdown of a mechanical watch movement, explaining how components like the mainspring, gear train, escapement, and balance wheel work together to track time without electronics. [src]
The discussion highlights a deep appreciation for the educational quality of the linked content, praising its ability to simplify complex mechanical concepts into accessible knowledge [5][9]. Enthusiasts emphasize that horology is a demanding craft requiring the ability to fabricate parts from scratch, though some distinguish between technical mastery and "celebrity bling" watches [0][2]. A common point of contention involves the financial practicality of luxury timepieces, with some users debating the merits of purchasing high-end models versus more modest, reliable alternatives like Seiko or Timex [3][4][6][7].
10. Stop Using JWTs (gist.github.com)
490 points · 318 comments · by dzonga
Developers are advised to stop using JSON Web Tokens (JWTs) for user sessions, as they are insecure and inefficient for long-term authentication compared to traditional cookie-based sessions or more secure alternatives like PASETO. [src]
The consensus among commenters is that JWTs are often inappropriate for browser-based user sessions but remain highly effective for service-to-service communication [0][1]. Critics highlight that JWTs introduce unnecessary complexity and historical security vulnerabilities, such as "none" algorithm exploits, while offering little benefit over opaque session IDs for applications that already require stateful lookups [1][5][7]. However, proponents argue that JWTs can optimize performance by reducing database load through smaller revocation lists and embedded session data, provided that modern libraries with sane defaults are used [2][3][4].
11. Calvin and Hobbes and the price of integrity (therepublicofletters.substack.com)
557 points · 244 comments · by pseudolus
This profile of *Calvin and Hobbes* creator Bill Watterson explores how his uncompromising artistic integrity led him to reject millions in merchandising and eventually retire at the height of his success to preserve the strip's "magic" and creative purity. [src]
Bill Watterson is widely praised for his uncompromising integrity, which preserved the "purity" of *Calvin and Hobbes* by refusing to "sell out" to mass marketing or repetitive storylines [0][1][4]. While some argue this lack of commercialization has caused the strip to fade from public consciousness among younger generations [2], others contend that avoiding the "cheap" branding seen in properties like *Garfield* has allowed the work to age better and retain its artistic value [0][3]. Notable anecdotes highlight Watterson's extreme commitment to his vision, including his refusal to take a call from Steven Spielberg and allegedly burning a box of prototype plushies sent for his approval [8][9].
12. TIL: You can make HTTP requests without curl using Bash /dev/TCP (mareksuppa.com)
543 points · 238 comments · by mrshu
Bash can perform manual HTTP requests by opening a TCP socket through its internal `/dev/tcp` redirection feature, providing a useful connectivity testing method for minimal containers that lack tools like curl or wget. [src]
While Bash can open TCP sockets via `/dev/tcp`, users clarify that it does not natively "speak" HTTP; rather, it allows users to manually construct requests, which is useful for debugging in minimal environments where tools like `curl` or `nc` are missing [0][2][4]. This technique is often a formative "no magic" moment for developers learning how protocols function, though it is considered "insane" for production use due to the lack of proper HTTP parsing [1][5]. Some argue for keeping production images minimal to reduce CVE surface area, while others maintain that including standard utilities like `curl` is essential for troubleshooting [3][8][9].
13. U.S. pulling ocean sensors a 'shock' for Canadian research as El Niño nears (timescolonist.com)
460 points · 275 comments · by ResearchAtPlay
The U.S. National Oceanic and Atmospheric Administration is removing critical ocean sensors from the Northeast Pacific, a move that surprises Canadian researchers and threatens to create significant data gaps just as a major El Niño event approaches. [src]
The removal of ocean sensors is viewed by experts as part of a broader "anti-science" crusade by the Office of Management and Budget (OMB) to dismantle American scientific infrastructure through restrictive international collaboration rules and political grant approval processes [0][3][4]. Critics argue that the decision is not about fiscal responsibility, as the government is actively spending money to retrieve the sensors rather than allowing other organizations to take over their management [8]. While some suggest this "collateral damage" stems from a reaction to perceived wasteful spending on niche social research [7], others highlight the absurdity of cutting relatively inexpensive programs that provide critical climate data while the military budget remains near $900 billion [1][5].
14. The time the x86 emulator team found code so bad they fixed it during emulation (devblogs.microsoft.com)
503 points · 171 comments · by paulmooreparks
Microsoft's x86 emulator team once discovered a program that initialized 64KB of memory using 65,536 individual instructions instead of a loop; they subsequently updated the emulator to detect this inefficient code and automatically replace it with a tight loop during translation. [src]
Software performance is frequently bottlenecked by inefficient coding patterns, such as applications that trigger thousands of single-byte system calls or redundantly erase screen areas multiple times before drawing [0][1][8]. To mitigate these issues, developers of hardware, drivers, and compatibility layers like Proton often implement transparent workarounds or "hotfixes" that improve performance without requiring changes to the original application source code [1][2][3]. This practice has a long history, including Microsoft patching a "read-after-free" bug in *SimCity* within Windows 95 to ensure system stability [4].
15. DuckDB Internals Part 1 (greybeam.ai)
471 points · 149 comments · by marklit
DuckDB is a high-performance, in-process analytical database that achieves speed through zero-copy execution, a sophisticated 33-pass query optimizer, and a columnar storage engine. By running as a library, it eliminates network serialization overhead while utilizing pipeline-based parallelism and zone maps to accelerate large-scale data processing. [src]
DuckDB is widely praised for its exceptional ergonomics, speed, and ability to act as "data superglue" between disparate ecosystems like S3 and local storage [0][1][5]. Users highlight its utility in analyzing large datasets on a single laptop, noting that its ease of use allows AI agents to effectively write queries [0][9]. While some debate its advantages over Python libraries like Pandas or Polars, proponents argue that DuckDB offers superior performance and a more accessible SQL interface for complex data manipulation [4][7][8].
16. Google Chrome update will close the door on ad blockers (9to5google.com)
270 points · 342 comments · by speckx
Google Chrome is moving to permanently disable Manifest V2 extensions, a transition that will effectively end support for many popular existing ad blockers. [src]
The transition to Manifest V3 (MV3) has sparked a strong push for users to switch to Firefox to preserve robust ad-blocking and an open internet [0][1][4], though some argue Firefox has already lost the "browser wars" due to its low market share and perceived UI sluggishness [7][8]. While some users find MV3-compliant blockers like uBlock Origin Lite sufficient [3], others contend these versions are significantly neutered compared to their predecessors [5]. Meanwhile, Brave is attempting to bypass these limitations by hosting and supporting core MV2 extensions directly within its engine [6].
17. How we run Firecracker VMs inside EC2 and start browsers in less than 1s (browser-use.com)
320 points · 237 comments · by gregpr07
Browser Use Cloud has optimized its infrastructure by running Firecracker microVMs inside regular EC2 instances, reducing browser startup times to under one second and costs to $0.02 per hour. The system achieves high security and stealth through nested virtualization, custom memory handling, and a patched headless Chromium fork. [src]
The discussion centers on the ethics of bypassing anti-bot measures, with critics arguing that such services are "selfishly entitled" and force websites to implement more intrusive hurdles for human users [0][3][6]. Conversely, proponents argue that scraping is necessary for personal data analysis, price monitoring, and competing with scalpers, viewing anti-bot measures as "techno-authoritarian" restrictions on public resources [1][2][4]. Technically, participants debated the necessity of Firecracker VMs over containers for isolation [9], noting that while "hot staging" VMs could eliminate startup times, each environment must remain ephemeral to protect user privacy [5][7][8].
18. I Could've Rickrolled the FIFA World Cup. All I Needed Was My ID (bobdahacker.com)
308 points · 98 comments · by BobDaHacker
A security researcher discovered a critical vulnerability in FIFA's internal platforms that allowed anyone with a registered agent ID to hijack live 2026 World Cup broadcast streams and modify match data. The flaw, caused by a lack of server-side authorization, was patched after the researcher contacted CISA, the FBI, and MediaKind. [src]
The author gained full access to FIFA’s World Cup 2026 broadcast infrastructure by registering on a public portal, discovering that the backend APIs failed to validate roles or permissions [5][9]. While the technical vulnerability allowed for the potential hijacking of live global feeds and match data, the discussion largely shifted toward the author's use of AI as a writing assistant [0][4][5]. Critics argued the AI-influenced style undermined the story's credibility, while others defended the use of LLMs as a tool for neurodivergent writers to organize complex research into readable narratives [0][2][4][6][7].
19. Correlated randomness in Slay the Spire 2 (tck.mn)
308 points · 89 comments · by rdmuser
Slay the Spire 2’s use of C#’s `System.Random` class has created "correlated randomness," a bug where the linear nature of the underlying algorithm allows players to predict future random events, such as specific card rewards and potion drops, based on early-game outcomes. [src]
The discussion highlights that game developers should treat random number generators (RNG) as core gameplay code rather than relying on platform-specific standard libraries, which can vary across devices or change over time and break seed reproducibility [1][2][5]. While some users questioned the necessity of using multiple distinct RNG streams [0][6], others noted that stable, seeded randomness is essential for players to share specific "runs" and for developers to ensure deterministic procedural generation across all hardware [4][8]. Commenters also observed that while "cryptographically secure" RNGs avoid correlation issues, they are often incompatible with the design goal of reproducible, seed-based gameplay [3][7].
Brought to you by ALCAZAR. Protect what matters.