Tweets & Toots.

“future” 1 à 10 sur 15

• "Just because a game is on disc doesn't mean it will work in the future" https://arstechnica.com/gaming/2026/07/the-disc-is-not-the-game-physical-releases-increasingly-require-extra-downloads/ #gaming
  
  > DoesItPlay tracks the many "physical" games that don't work without the Internet. https://www.doesitplay.org 12/08/2026 à 08:09 Permalien
• RT @zbruceli Deep dive into the Internet Archive's tech stack https://hackernoon.com/the-long-now-of-the-web-inside-the-internet-archives-fight-against-forgetting
  - the Internet Archive + Wayback Machine combats ephemerality of online content
  - operates physical infrastructure in San Francisco with PetaBoxes servers that store hundreds of petabytes of data
  - traditional crawlers struggle with JavaScript-rich sites: tools like Brozzler and Umbra are used
  - runs on a modest budget (~$25–30M/year) supported by donations, grants, and paid services like Archive
  - faced major copyright lawsuits
  - future Directions: DWeb, IPFS, Filecoin 14/01/2026 à 06:00 Permalien
• FUTURE WAR 198X年 「愛ゆえに哀しく」 https://www.youtube.com/watch?v=nXcl7fKX33g #anime
  
  RT @kaeruiwa1963 「FUTURE WAR 198X年」のアニメ主題歌「愛ゆえに哀しく」
  作詞：山上路夫
  作曲：風戸慎介
  編曲：青木望
  歌：ポプラ 05/09/2025 à 18:01 Permalien
• RT @mjd I think many people misunderstand the purpose of code review. The purpose of code review is not for the reviewer to find bugs, and certainly not for them to ensure that the code is bug-free. Anyone who depends on code review to find bugs is living in a fool's paradise. As everyone should know by now, it is not in general possible to find bugs by examining the code.
  
  The primary purpose of code review is to find code that will be _hard to maintain_. The reviewer looks at the code and tries to understand what it is doing and how. If they can't, that means it will be hard to maintain in the future, and should be fixed now, while the original author is still familiar with it. 27/08/2025 à 22:05 Permalien
• The mentioned source leaves a bit more room for doubt on the fact that the "The Transformers: The Movie" money trickled down to the anime adaptation of Saint Seiya.
  Yet it seems stated in Kōzō Morishita (森下孝三)'s bio (978-4758011860) and in Masami Kurumada (車田正美)'s Saint Seiya Taizen (978-4834216905). https://www.youtube.com/watch?v=EZtLpBsIdag&t=11m59s RT @titangoji Quick history lesson: TRANSFORMERS: THE MOVIE had a reported budget of $6M.
  This is actually not true.
  The real budget was ¥4B JPY, well over $20M in 1986.
  It was so big that Toei didn't use it all, and the leftover budget funded future projects. One of them was #SaintSeiya #anime 17/07/2025 à 06:11 Permalien
• I'm bouncing to the UPGRADE MUSIC https://youtube.com/watch?v=YDkD-N5goMg
  Have you ever seen such a smooth migration? https://dev.htmx.org/migration-guide-htmx-1/
  
  RT @htmx_org happy to announce htmx 2.0 beta4: https://dev.htmx.org/posts/2024-04-22-htmx-2-0-0-beta4-is-released/
  barring catastrophe, this will become htmx 2.0 in the near future
  htmx 2.0 will be released, but not set to `latest` in npm for a while so people aren't force-upgraded
  enjoy! #music 23/05/2024 à 12:37 Permalien
• "ChatGPT: The Future of #ai Is Here" https://tidbits.com/2022/12/09/chatgpt-the-future-of-ai-is-here/ #history 10/12/2022 à 10:38 Permalien
• I'm sold by the future-proof format of Obsidian https://obsidian.md/ Markdown is eating the world 01/11/2021 à 16:57 Permalien
• "What Comes Next Is the Future" A documentary film about the web. https://vimeo.com/177267839 Kids, this is #history :) 30/12/2016 à 12:20 Permalien
• Evolution of CSS Layout: 1990s to the Future http://fantasai.inkedblade.net/weblog/2012/css-layout-evolution/ #history 15/08/2012 à 18:28 Permalien