This project introduces "SHORTY," a C++ utility that aims to make lambdas more concise. It achieves this by providing a macro-based system that replaces standard lambda syntax with a shorter, more symbolic representation. Essentially, SHORTY allows developers to define and use lambdas with fewer characters, potentially improving code readability in some cases by reducing boilerplate. However, this comes at the cost of relying on macros and introducing a new syntax that deviates from standard C++. The project documentation argues that the benefits in brevity outweigh the costs for certain use cases.
The blog post "My Favorite C++ Pattern: X Macros (2023)" advocates for using X Macros in C++ to reduce code duplication, particularly when defining enums, structs, or other collections of related items. The author demonstrates how X Macros, through a combination of #define directives and clever macro expansion, allows a single list of elements to be reused for generating different code constructs, such as compile-time string representations, enum values, and struct members. This approach improves maintainability and reduces the risk of inconsistencies between different representations of the same data. While acknowledging potential downsides like reduced readability and debugger difficulties, the author argues that the benefits of reduced redundancy and increased consistency outweigh the drawbacks in many situations. They propose using Chapel's built-in enumerations, which offer similar functionality to X macros without the preprocessor tricks, as a more modern and cleaner alternative where possible.
HN commenters generally appreciate the X macro pattern for its compile-time code generation capabilities, especially for avoiding repetitive boilerplate. Several noted its usefulness in embedded systems or situations requiring metaprogramming where C++ templates might be too complex or unavailable. Some highlighted potential downsides like debugging difficulty, readability issues, and the existence of alternative, potentially cleaner, solutions in modern C++. One commenter suggested using BOOST_PP for more complex scenarios, while another proposed a Python script for generating the necessary code, viewing X macros as a last resort. A few expressed interest in exploring Chapel, the language mentioned in the linked blog post, as a potential alternative to C++ for leveraging metaprogramming techniques.
CSS is poised for a significant upgrade with the introduction of custom functions, offering a way to encapsulate and reuse complex logic within stylesheets. Similar to functions in programming languages, these allow developers to define reusable blocks of CSS with parameters, enabling dynamic theming, responsive design adjustments, and streamlined maintenance. This functionality will bring enhanced flexibility and maintainability to CSS, potentially simplifying intricate styles and reducing code duplication. The introduction of custom functions signals a move toward more programmatic and powerful styling capabilities.
Hacker News users generally express excitement about the potential of CSS custom functions (also known as CSS variables). Several commenters highlight the benefits for theming and dynamic styling, particularly the ability to easily switch themes or adjust styles based on user preferences or context. Some anticipate improved code organization and maintainability through reduced redundancy. A few express caution, noting potential performance implications and the need for careful planning to avoid overly complex or difficult-to-debug stylesheets. One commenter suggests the feature could make CSS preprocessors like Sass less necessary, while another points out that preprocessors still offer additional functionality beyond custom functions. There's also discussion around the naming conventions and best practices for using custom functions effectively.
BritCSS is a humorous CSS framework that replaces American English spellings in CSS properties and values with their British English equivalents. It aims to provide a more "civilised" (British English spelling) styling experience, swapping terms like color for colour and center for centre. While functionally identical to standard CSS, it serves primarily as a lighthearted commentary on the dominance of American English in web development.
Hacker News users generally found BritCSS humorous, but impractical. Several commenters pointed out the inherent problems with trying to localize CSS, given its global nature and the established convention of using American English. Some suggested it would fragment the community and create unnecessary complexity in workflows. One commenter jokingly suggested expanding the idea to include other localized CSS versions, like Australian English, further highlighting the absurdity of the project. Others questioned the motivation behind targeting American English specifically, suggesting it stemmed from a place of anti-American sentiment. There's also discussion about the technical limitations and challenges of such an undertaking, like handling existing libraries and frameworks. While some appreciated the satire, the consensus was that BritCSS wasn't a serious proposal.
Summary of Comments ( 14 )
https://news.ycombinator.com/item?id=43629380
HN users largely discussed the potential downsides of Shorty, a C++ library for terser lambdas. Concerns included readability and maintainability suffering due to excessive brevity, especially for those unfamiliar with the library. Some argued against introducing more cryptic syntax to C++, preferring explicitness over extreme conciseness. Others questioned the practical benefits, suggesting existing lambda syntax is sufficient and the library's complexity outweighs its advantages. A few commenters expressed mild interest, acknowledging the potential for niche use cases but emphasizing the importance of careful consideration before widespread adoption. Several also debated the library's naming conventions and overall design choices.
The Hacker News post discussing the "shorty" C++ header for terser lambdas generated a moderate amount of discussion, mostly focused on the potential downsides and alternatives to the approach.
Several commenters expressed concern over the readability and maintainability of code using
shorty. One commenter argued that while brevity can be good, excessive terseness can harm readability, especially for those unfamiliar with theshortysyntax. They suggested that the potential gains in character count are outweighed by the increased cognitive load required to understand the code. Another user echoed this sentiment, pointing out that C++ is already a complex language, and adding more cryptic syntax likeshortyfurther exacerbates the issue. They questioned the real-world benefit, suggesting that saving a few keystrokes is not worth the potential confusion.The discussion also touched upon the potential for namespace pollution and name clashes. One commenter pointed out the risk of unintended consequences when using generic short names like those provided by
shorty, especially in larger projects. They suggested that more descriptive lambda names, even if longer, are generally preferable for clarity.Alternatives to
shortywere also proposed. One user mentioned using an editor snippet or macro to achieve similar brevity without introducing new syntax. Another suggested leveraging existing C++ features likeautoand structured bindings to simplify code without sacrificing readability. A commenter highlighted the benefits of refactoring complex logic into separate functions, thereby reducing the need for lengthy lambdas in the first place. They argued this approach often leads to more organized and understandable code.A few comments briefly acknowledged the potential usefulness of
shortyin specific, limited contexts, such as competitive programming or code golfing, where character count is paramount. However, the general consensus seemed to be that for most practical applications, the potential drawbacks ofshortyoutweigh its benefits. There was a clear preference for maintaining code clarity and readability over achieving extreme terseness.