Stories with Tag feasibility

• Is it possible to write plain C iOS app in 2025?

  permalink

  Posted: 2025-04-14 16:21:29

  Verbose tl;dr

  Yes, it's technically still possible to write a plain C iOS app in 2025 (and beyond). While Apple pushes developers towards Swift and SwiftUI, and Objective-C is slowly fading, the underlying iOS APIs are still C-based. This means you can use C, potentially with some Objective-C bridging for UI elements or higher-level functionalities, to create a functional app. However, this approach is significantly harder and less efficient than using Swift or Objective-C, lacking modern tools, libraries, and simplified memory management. Maintaining and updating a C-based iOS app would also be a considerable challenge compared to using more modern, officially supported languages and frameworks. Therefore, while possible, it's not generally recommended for practical development.

  The Hacker News post titled "Is it possible to write plain C iOS app in 2025?" poses the question of whether developing an iOS application using solely the C programming language will still be feasible in the year 2025. The author elaborates on their motivations, expressing a desire to avoid the perceived complexities and overhead associated with more modern iOS development approaches, such as using Swift, Objective-C, or UI frameworks like SwiftUI and UIKit. They specifically highlight concerns about the size and performance implications of these frameworks and languages, expressing a preference for the leaner, more direct nature of C.

  The author acknowledges that using C for iOS development might present certain challenges, particularly concerning user interface design and interaction with the operating system's APIs. They seem to be aware that Apple's preferred and officially supported methods heavily favor higher-level languages and frameworks. However, they express a hope that lower-level access to the system might still be possible, possibly through leveraging older APIs or exploring alternative methods. The underlying motivation appears to stem from a desire for greater control over the application's performance and resource usage, potentially aiming for a smaller application footprint and optimized execution. The question ultimately seeks to gauge the practical viability of pursuing this unconventional approach to iOS development in the near future. They are implicitly inquiring about potential roadblocks, available tools, or alternative strategies for achieving their goal of a C-based iOS app while acknowledging the prevailing trend towards higher-level development paradigms within the iOS ecosystem.

  • iOS
  • C
  • Objective-C
  • Swift
  • App Development
  • mobile development
  • Programming Languages
  • Software Development
  • Cross-Platform Development
  • Native Development
  • 2025
  • feasibility

  Summary of Comments ( 53 )
  https://news.ycombinator.com/item?id=43682984

  Verbose tl;dr

  Hacker News users discussed the practicality and challenges of writing a plain C iOS app in 2025. Several commenters pointed out that while technically possible, using only C would be incredibly difficult and time-consuming, requiring significant workarounds to interact with essential iOS frameworks (mostly written in Objective-C and Swift). Some suggested leveraging existing C libraries and frameworks like SDL or raylib for cross-platform compatibility and easier graphics handling. Others questioned the motivation behind such an endeavor, given the availability of more suitable languages and tools for iOS development. The general consensus was that while a pure C app is theoretically achievable, it's a highly impractical approach for modern iOS development. Some pointed out that Apple's increasing restrictions on low-level access make a pure C app even more challenging going forward.

  The Hacker News post "Is it possible to write plain C iOS app in 2025?" generated a fair number of comments discussing the feasibility and practicality of using C for iOS development.

  Several commenters pointed out that it's technically possible but likely not practical or advisable. One commenter explained that while the entry point of an iOS app might be compiled C, interacting with any iOS frameworks would necessitate using Objective-C or Swift wrappers. They highlighted that even if some parts could be written in pure C, integrating with the iOS ecosystem would be challenging, requiring significant bridging work.

  Another commenter explored the potential use of a cross-compiler targeting a suitable runtime like WASM/Wasmer, allowing for more C code. However, this approach was acknowledged as having potential performance limitations. This led to a discussion about whether such an approach would even be allowed on the App Store, given Apple's restrictions on interpreters and JIT compilers.

  Some commenters offered alternative perspectives, suggesting that using C for specific performance-critical components within a larger Swift/Objective-C application might be a more realistic scenario. They argued that rewriting an entire app in C wouldn't be worth the effort, given the mature tooling and frameworks available for Swift/Objective-C development.

  A few users mentioned existing projects and tools that allow for C development on iOS, such as the SDL library and Beeper (an iMessage client largely written in C++). These examples served to demonstrate that C can indeed be used, but often in conjunction with other languages and primarily for specific use cases.

  A recurring theme in the comments was the trade-off between performance and developer productivity. While C might offer potential performance gains in some scenarios, the increased development time and complexity involved in interfacing with the iOS ecosystem were generally seen as outweighing those benefits.

  Finally, some commenters discussed Apple's policies and their potential impact on C-based iOS development. The possibility of Apple further restricting or disallowing certain approaches was raised, reinforcing the notion that relying solely on C for iOS development is a risky proposition.

• Is It Lunacy to Put a Data Center on the Moon?

  permalink

  Posted: 2025-02-26 20:20:39

  Verbose tl;dr

  Storing data on the moon is being explored as a potential safeguard against terrestrial disasters. While the concept faces significant challenges, including extreme temperature fluctuations, radiation exposure, and high launch costs, proponents argue that lunar lava tubes offer a naturally stable and shielded environment. This would protect valuable data from both natural and human-caused calamities on Earth. The idea is still in its early stages, with researchers investigating communication systems, power sources, and robotics needed for construction and maintenance of such a facility. Though ambitious, a lunar data center could provide a truly off-site backup for humanity's crucial information.

  The article "Is It Lunacy to Put a Data Center on the Moon?" from IEEE Spectrum delves into the intriguing, albeit seemingly outlandish, proposition of establishing data centers on the lunar surface. While acknowledging the inherent complexities and exorbitant costs associated with such an undertaking, the piece explores the potential benefits and the nascent technological advancements that could make this ambitious vision a reality.

  The primary motivation behind this lunar data center concept stems from concerns about the vulnerability of terrestrial data centers to various threats, including natural disasters like earthquakes, floods, and solar flares, as well as human-induced catastrophes such as cyberattacks and even nuclear war. The Moon, being geographically isolated from Earth, offers a potentially secure and stable environment, safeguarding crucial data from these terrestrial risks.

  The article meticulously outlines the substantial challenges involved in constructing and operating a lunar data center. These include the logistical hurdles of transporting materials and equipment to the Moon, the harsh lunar environment characterized by extreme temperature fluctuations, radiation exposure, and the absence of atmosphere, and the need for reliable power generation on the lunar surface. Specifically, the extreme temperature swings between lunar day and night pose a significant threat to the sensitive electronic equipment within a data center, necessitating robust thermal management solutions. The article discusses potential mitigation strategies, such as locating the data center in permanently shadowed lunar craters near the poles, which offer consistently low temperatures, or leveraging lunar regolith for insulation and thermal regulation.

  Furthermore, the piece examines the potential power sources for a lunar data center, highlighting solar power as a viable option, particularly in areas with near-continuous sunlight. The challenges associated with solar energy on the Moon, such as the lunar night, are also addressed, potentially necessitating energy storage solutions or supplemental power generation methods.

  Beyond the physical construction and operational challenges, the article also touches upon the complexities of data transmission between the Moon and Earth, acknowledging the latency introduced by the vast distance. While this latency might not be suitable for all applications, the article suggests that lunar data centers could be ideal for archiving and long-term data storage, as well as serving as a backup for critical terrestrial data.

  Ultimately, the article concludes that while a lunar data center is not an immediate reality, it is a concept worth exploring further. The potential benefits in terms of data security and resilience, coupled with ongoing advancements in space exploration and related technologies, suggest that a lunar data center may not be as fantastical as it initially appears. The authors emphasize the need for continued research and development to address the significant engineering challenges and economic considerations, but leave open the possibility that lunar data storage might become a practical solution in the future. The article doesn't explicitly advocate for the immediate construction of a lunar data center, but rather presents a balanced perspective on the potential advantages, challenges, and future possibilities of this ambitious concept.

  • Data Centers
  • Moon
  • lunar infrastructure
  • Space Exploration
  • off-world data storage
  • data preservation
  • Disaster Recovery
  • latency
  • radiation
  • thermal management
  • power generation
  • cost
  • feasibility
  • engineering challenges
  • extraterrestrial computing

  Summary of Comments ( 9 )
  https://news.ycombinator.com/item?id=43187759

  Verbose tl;dr

  HN commenters largely discuss the impracticalities and questionable benefits of a moon-based data center. Several highlight the extreme cost and complexity of building and maintaining such a facility, citing issues like radiation, temperature fluctuations, and the difficulty of repairs. Some question the latency advantages given the distance, suggesting it wouldn't be suitable for real-time applications. Others propose alternative solutions like hardened earth-based data centers or orbiting servers. A few explore potential niche use cases like archival storage or scientific data processing, but the prevailing sentiment is skepticism toward the idea's overall feasibility and value.

  The Hacker News post "Is It Lunacy to Put a Data Center on the Moon?" generated a moderate amount of discussion, with a mix of skepticism, cautious optimism, and explorations of potential use cases. Many commenters questioned the practicality and cost-effectiveness of such a venture, particularly highlighting the challenges of latency, maintenance, and the harsh lunar environment.

  One compelling line of discussion revolved around the specific types of data that would benefit from being stored on the moon. Several users suggested that the moon could serve as a backup location for crucial data, safeguarding it from terrestrial disasters or geopolitical instability. The concept of a "lunar ark" for human knowledge and culture was also mentioned, with proponents arguing that the moon's relative isolation could protect valuable information in the long term. However, counterarguments emphasized the difficulty and expense of retrieving data from the moon in case of emergency.

  Another significant theme in the comments was the technological feasibility of building and maintaining a lunar data center. Concerns were raised about the effects of radiation, extreme temperature fluctuations, and micrometeoroid impacts on hardware. The logistics of transporting equipment and personnel to the moon were also discussed, with commenters pointing out the high costs and potential risks involved. Some users suggested that robotic construction and maintenance could mitigate some of these challenges, but others remained skeptical about the reliability of such systems in such a hostile environment.

  The discussion also touched upon the potential environmental impact of a lunar data center, with concerns raised about the energy requirements and the potential for pollution. The ethical implications of commercializing the moon were also briefly mentioned.

  While some commenters expressed enthusiasm for the potential scientific and technological advancements associated with a lunar data center, the overall sentiment seemed to be one of cautious pragmatism. Many users questioned the immediate need for such a facility, arguing that the current challenges and costs outweigh the potential benefits. However, the discussion also highlighted the potential long-term value of a lunar data archive for preserving human knowledge and culture, suggesting that the idea may be worth exploring further in the future.