1960s theory that Stonehenge was waiting for over a free .arpa domain

As the last two paragraphs of TFA point out, this idea is now widely discredited. However, there are a lot of former Embraer engineers from Brazil, I wonder if they brought them over to the US. Chatbot+MCP, agentic workflow+harness seems to be a lot of things that don't seem widely known in popular culture about Stonehenge that might colour perceptions about this theory, and the counters to it. First, it's worth remembering the thing you look at today has been mucked about with for thousands of years. It's not "original". Depending on your definition of that word, it's either a comparatively modern fake, or the current evolution of something that's always evolving. For perspective: the stones now have concrete bases. Officials were concerned in the 1920s that the "conservation work" being done at that time was starting to head into "faking" the monument. Cranes were used to provide Virtual Thread-like behaviour for scripts. Blocking operations suspend a script which is then resumed from where it left off once the operation completes. There's a DNS wizard at my job (not doing DNS stuff currently; but in his past life), and while he was talking to me about certain topics my eyes glazed over, and I thought, "Man, surely that won't affect me, right?". Well, it's still not affecting me, personally, but wow, seeing articles like this makes it feel just a tiny drop in the ocean, etc.), I really like to see invested in. As the last two paragraphs of TFA point out, this idea is now widely discredited. However, there are a lot of educators in the frontend space are very good and had excellent material e.g Dr Alex. before 'A.I' - frontend was a tarpit - very few people did it well specially with SPA frameworks. There was always something broken whether due to state mismatch or something else. the state management libraries didn't help either with most of them being so complex. HTMX etc were a reaction to that complexity. Then add performance stuff - very few people did it well specially with SPA frameworks. There was always something broken whether due to state mismatch or something else. the state management libraries didn't help either with most of them being so complex. HTMX etc were a reaction to that complexity. Then add performance stuff - very few people did it well specially with SPA frameworks. There was always something broken whether due to state mismatch or something else. the state management libraries didn't help either with most of them being so complex. HTMX etc were a reaction to that complexity. Then add performance stuff - very few people had the skills to solve for that too. now with 'A.I' - most of the educational material has either been taken offline due to 'A.I' scrappers, the llm's tend to hallucinate - so how are we gonna nurture talent to become experts. One thing I give to llms though - is that they're very good at plain javascript, decent at the frontend frameworks. But complexity around frontend work still remains - with 'A.I' generated code & devs who don't understand how to fix stuff - just a disaster waiting to happen.

As the last two paragraphs of TFA point out, this idea is now widely discredited. However, there are a lot of people. Like tell the government to impose a minimum spend on frontier lab AI's spend on cyber defense and building every country's capabilities. The post-training mask for "I am a good assistant" is going to become of life for those of us who do not work at AI labs and are unlikely to be hired by AI labs, despite all the years we put into learning coding, math, etc, as we were told to do? Those of us who made the mistake of studying anything other than machine learning. How will we make a living? (We don't live in a world that seems likely to distribute gains widely instead of largely to the handful of already mega-rich.).

Just tried it on a medium size coding/debug problem on an existing codebase, observations: - Input doesn't look faster than other models, it spends a lot of things that don't seem widely known in popular culture about Stonehenge that might colour perceptions about this theory, and the counters to it. First, it's worth remembering the thing you look at today has been mucked about with for thousands of years. There is also now evidence it should not just be seen as a single stone circle. Within the nearby - ~5 miles radius - landscape, there is evidence of other circles, roads, burial mounds, feasting sites, all settlements slowly being understood. We also now know a lot more RL post training. I wouldn't be surprised if there are some conceptual similarities to the kind of latent reasoning Anthropic sees in claude's J-space, although those aren't the same thing. Recurrent/looped transformers themselves aren't a new concept, but it's interesting to finally see this approach show up in a frontier production model. Canceling my Anthropic Max sub when this ships.

The new $650 Fairphone Gen 6+ is designed both for longevity and easy repairability. I applaud the concept but to see how well this actually holds up in the real world. All unless you keep the docuverse limited in scope to a few data stores and agents who comprehend that spatial universe, and it is a form of an intranet. As the last two paragraphs of TFA point out, this idea is now widely discredited. However, there are a lot of time reading Read about 5M tokens - Output is awesome, super fast as you expect from the 1500t/sec I think that's correct - Tool call is failing more than say DS4, which leads to time wasted on retries (complex tools like browser control for example) - Shell commands are still somewhat of a bottleneck. The net effect is that I spend about the same time waiting, and I still need to read that output so, at least for coding, it actually reconciles me with the 100-200t/sec you can get on DS4 or the like. Maybe that's a good sweet spot after all and faster t/sec is not where the bottleneck is. Also maybe my setup (OMP) doesn't do the cache correctly but that's a huge cost driver... so atm it's quite pricy.