Article URL: https://www.apple.com/os/ios/ Comments URL: https://news.ycombinator.com/item?id=49700193 Points: 7 # Comments: 4
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
A report citing Oxfam, linked from a Hacker News discussion, finds that the richest 0.1% of the world's population, roughly 8 million people, generate more carbon pollution than about 3.5 billion people. The figure highlights the sharp disparity in emissions between the ultra-wealthy and much of the global population. The source material available here is limited to the headline and link, so the full methodology and time frame are not confirmed. The findings are presented by Oxfam as a press release on the emissions footprint of the ultra-rich.
GitHub restricted its stargazers listing to repo admins and collaborators this year, which broke existing star history tools. In September it added a star history endpoint that returns stars grouped by calendar week for any public repo without authentication. The author built a README chart generator on it, fetching pages in parallel and summing weekly totals, which matched live star counts on seven tested repos. Because README images cannot run scripts, the chart is a server-rendered Svelte component producing an animated SVG, while a separate plain SVG converted to PNG handles social previews.
A common naive word counter splits text on whitespace, which breaks on contractions, hyphens, em dashes, decimals, and emoji. The article argues this is a text segmentation problem rather than a rounding issue. It recommends the browser's Intl.Segmenter API, using word granularity and filtering by isWordLike to exclude emoji from word counts. It also notes that text.length counts UTF-16 code units rather than visible characters, so grapheme granularity is better for character counts. The author discloses that they built a browser-based word counter that processes text locally without uploading it.
The article explains that every command has three text channels: stdin for input, stdout for normal results, and stderr for error messages. The > operator sends stdout to a file and overwrites it, while >> appends to the end of an existing file. Because stderr is stream 2, the 2> operator captures error messages separately, and 2>&1 merges errors into the same destination as normal output, with the order of redirections mattering. A pipe (|) passes one command's stdout directly into the next command's stdin, allowing small tools to be chained together. The piece notes that pipes carry only stdout, so errors from the left-hand command bypass the pipe.
Discussion (0)
Log in to join the discussion and vote.
Log in