great series, half of these binaries are things you type for years without ever knowing what they actually do. autotools is its own kind of archaeology, aclocal and the m4 macro mess is exactly why everyone quietly moved to cmake and meson

The "real-time collaboration" piece is an interactive Product Architect agent you keep live alongside the loop to monitor, steer, and explain what's running. Still rough and in progress, but the Autotools × Notion line fit too well not to answer.

After years of slow development, aMule is back with version 3.0.0, bringing one of the biggest updates in the project’s history. The release modernizes the classic eD2k/Kad file-sharing client and delivers huge performance improvements. According to the developers, download speeds can be between 100x and 380x times faster than those in version 2.3.3 on the same hardware. Some of the biggest changes include: - Download speeds up to 380× faster than aMule 2.3.3. - Upload speeds up to 4.8× faster than eMule 0.70b in some tests. - Disk operations no longer block the main thread, making the client more responsive. - Upload and download speed limiters have been completely redesigned. - Better support for very large libraries with more than 100,000 shared files. - HTTPS support has been restored using modern TLS libraries. - The project now uses CMake instead of autotools, making development easier. - Native builds are available for Linux, Windows, and macOS, including ARM64 devices. - Shared folders are rescanned automatically, and overall UI responsiveness has been improved.

Chinese hand tools factory Focus on hand tools more than 19 years Please contact me to get our catalog and price list WhatsApp or Wechat: 8618306575560 #workshoplife #mechanicshop #mechlife #technologythesedays #auto #autotools #tools #manufacture #manufacturer #export #import

🚀 We’re excited to share that we’re participating in the CINECA training course on HPC Build Systems & Package Managers - a three-day hands-on program focused on the tools powering high-performance scientific software. The course covers: ⚙️ Makefiles ⚙️ GNU Autotools ⚙️ CMake ⚙️ Python packaging ⚙️ Spack for HPC environments As we continue building AI systems and graph-based intelligence platforms like Verbis Graph, strengthening our expertise in scalable software infrastructure and HPC workflows is incredibly valuable. Always learning. Always building. 🚀 #HPC #CINECA #HighPerformanceComputing #AIEngineering #CMake #Python #Spack #SoftwareEngineering #VerbisGraph #AIInfrastructure #TechInnovation

Saw @patrickc ask if anyone's building this. Been at the coding-agent half for ~a year - files context per agent, worktree-per-task, 30 in parallel, agents debating each other in a group chat (screenshot: them drafting this very reply). The hard parts on his list still open: multi-human realtime collab shareable compiled outputs. "autotools × notion" nails the feel.

@patrickc wild seeing this today as i had the exact same thought (probably a lot of people are having this thought at the same time), and i built something this week to do this for my own workflow which i call upskill. it's a file-based system for recursive, self-improving agent skills (inspired by microsoft’s SkillOpt paper, karpathy’s LLM-wiki, and garry tan’s gstack line of work). core idea: a skill whose job is to recursively improve skills (including itself) automatically every session. it reads the run, runs the retro, and folds improvements back into markdown files in a git-native, repeatable, low-cognitive-load way. it auto-loads input files context, stores & evolves prompts/workflows, and handles VCS/snapshots shareable compiled outputs (and works natively as a skill in any agent harness). gonna write it up properly in a post, but in meantime, demo repo here: x.com/yungbose/status/206342… keen for your take - it's been a key lego brick for me, and feels like it aligns with your Autotools × Notion vision 🫰🏽

xz was obfuscated in autotools, this is a bigger issue than just regular clear patches. It never would have worked if it weren't a maintainer adding the backdoor because it would have been scrutinized

@patrickc This sounds a lot like what I've been building with Hyper-Waterfall — a traceable, approval-driven harness for LLM-powered coding workflows. It turns GitHub Issues PRs structured docs into a full build system for AI agents: - Human approval gates at every stage - All prompts, plans, stage reports, and artifacts stored in the repo (super resumable & shareable) - Works seamlessly with Claude Code, Codex, etc. - Feels like “Autotools Notion” but for iterative AI pair programming Would love your thoughts: github.com/postmelee/hyper-w…

This is very close to what we’re building at LobeHub. An open-source, self-hostable workspace for teams to run agents over shared files, prompts, workflows, and outputs. The direction is basically: Notion-style collaboration versioned agent runs reusable prompts/workflows enterprise control/traceability. GNU Autotools x Notion is a good way to frame it.

> With real-time collaboration. With the exception of this (I hate syncing) I've implemented the rest in combinations. Build/store/version graphs. Deterministic reruns/experiments. Data provisioning. Clearly I'm missing something big here, maybe productionized normie tool? You've already mentioned autotools, so it looks like you want to have Maven/Bazel-style wrapper or something? enterprise CI/CD for agents?

One thing we've learned building @mem_base: most teams don't struggle with workflows first. they struggle because the context needed for those workflows lives across Slack, docs, emails, meetings, and different agents. before you can build "GNU Autotools x Notion", you need a shared context layer.

One thing we've learned building @mem_base: most teams don't struggle with workflows first. they struggle because the context needed for those workflows lives across Slack, docs, emails, meetings, and different agents. before you can build "GNU Autotools x Notion", you need a shared context layer.

I want some kind of LLM workflow tool. • Ability to manage a set of input files (Markdown or similar), plus other general-purpose context. • With real-time collaboration. (And maybe some concept of snapshots or VCS integration.) • And the ability to create/manage a inference workflows and a stored set of prompts. • Access to general-purpose coding agents (and not just chat models). • Some concept of compiled outputs/inference results (which ideally can be shared externally). Many projects have this feeling: "there is all this stuff, which I want to process/compute over in this iterated way, with some build artifacts being important/worth saving." GNU Autotools x Notion or something. Is anyone building this?

AIX っていう名前の UNIX (あってる?) 上の ksh (GNU autotools の実行) がなんか異様に遅いってのを思い出した。深追いてないので何が悪いのかは知らんけど。パイプ使うときいちいち一時ファイルを使ううんぬんという話を見かけたが真偽は確認してない。

🚗⚡ Power when you need it most! Clore Automotive JNC660 delivers 1700 Peak Amps for fast, reliable jump starts. 🛒 amazon.com/dp/B000JFJLP6?tag… #JumpStarter #CarBattery #AutoTools a.co/d/05YoYip4

openssl, autotools, sendmail, systemd, 80% of all the Javascript stuff, useless microservices everywhere, SOAP, ...

One underappreciated aspect of @antirez's projects: they are always dead simple to build. No npm, no autotools, no bazel, no meson, no cmake, no ninja, no nix flakes. Just make.

atarist-toolkit-docker v1.3.0: the community ships autotools support Massive shout out to the Atari ST homebrew community on this one. v1.3.0 adds autoconf, automake, libtool, and pkg-config to the Docker toolkit, plus the MiNT gemlib and pml libraries, so cross-compiling against m68k-atari-mint just works out of the box. Huge thanks especially to @neilrackett, who drove the autotools integration end to end. The maintainer's role here was the easy part: review, merge, bump, release. All the substance of the change is community-built, which is exactly how this kind of toolkit should evolve. The installers also bake the install-time Docker account and image tag into the generated stcmd wrappers, so the toolkit drops cleanly onto any workstation. Grab v1.3.0 here: github.com/sidecartridge/ata…