brightball
The combination of lightweight processes with their own HEAP and the preemptive scheduler means that millions of processes can run on the same machine with consistent execution time, no GC pause, and no worry that a single resource heavy process is going to slow down everything else.
The balance tradeoffs allows you to do a lot of things that would otherwise be poor architectural choices.
LiveView is just one example, where you’re able to completely forgo the need for a frontend framework but get all of the same benefits with lightning fast execution times.
There’s a lot of wins that come from it.
From a AI standpoint, functional code is simpler to trace and maintain because the AI doesn’t have to worry about side effects.
The HA perks are a bonus.
The BEAM runtime is the real win. Your options are Erlang, Elixir and Gleam to get the BEAM.
Out of the 3, I prefer Elixir and Jose is a brilliant leader for it.
Being able to ensure all of the test run freakishly fast async is a huge win too.
Having this just work for non-tech people and still have advanced capabilities for the people who want to use it is a huge UX unlock.
The other thing thats critical is that it’s exceedingly cautious by default. My risk profile and concerns eased quickly.
I haven’t heard anyone give bots comparison.
It can send all bot traffic through those computers too so it’s less likely to get blocked.
Over the weekend I decided to try Lauren Tan’s pstack via her Dr Eggbot and had it built a bot that would run a build for me for a few days. It was a complex enough prompt that it triggered something to let me tell it which models to use and ended up settling on Opus 5.5 for planning and review with Grok 4.7 for the actual coding.
Ran for the weekend and completed 5 phases of a project with about 15 PRs. Reviews caught several things and sent them back premerge.
I enjoyed a fun weekend with my daughter clearing Escape Rooms in Colorado. Came back to a completed project.
It was great.
It took me 2 days to hit “how did I ever survive without this” and it’s only gotten better.
I followed a lot of the news about them regarding this thing. If I own a business or even simply act as a manager and I know of a constant threat to my staff I would take any action I was legally allowed to protect them. Doesn’t matter if it’s ICE, the postal service, a gas station, theme park, etc.
It’s basic self defense.
ICE agents didn’t start covering their faces just because, they did it because people were doxxing them and going after their families.
People are going to protect themselves and their staff. It’s basic human nature.
If people started doing that to UPS delivery trucks I would expect UPS to do everything in their power to protect their staff.
Headline makes it seem like ICE just did this in a vacuum.
They can access anything you can, whether there's an MCP/CLI/API or not. I create speciality bots for each 3rd party tool that I use at this point. The bots can talk to each other, have group chats. You can give them access to the machines that you're running the software on and give specific bots permission to do things on certain machine (like an Obsidian bot that writes logs of daily bot activity on a specific machine with a Dropbox folder shared). I've got a Security Scan bot that downloads anything that a bot wants to download to it's personal machine at SpaceX and runs a slew of security scanners before the other bots can work with it.
I got locked out of one machine while I was travelling and I asked Grok Bot on another machine if it could get into that one over SSH, so it sent me a temporary authorization link via Tailscale, connected to the machine and restarted the stuck process for me.
The usability is off the charts. It's really like having a team of people working for you. I've run a conference for the last few years and was getting completely overloaded. Now I have 14 bots specialized just for the conference helping me do it better than ever and participating in architectural discussions to build a system that help long term.
If you find yourself trying to juggle a lot in your life and work, it's a gift.
“I’m not going to do that. Moving on.”
Between SpaceX, Starlink, Tesla, Neuralink, X, Grok, Grok Bot & Cursor there's not a demand shortage.
Grok Bot's the fastest growing product in the history of the company and the moment you use it, it's clear why. Took me about 1-2 days to realize I'd have a very hard time going back to not having it available.
https://web.archive.org/web/20220124192618/https://archive.e...
https://www.blm.gov/press-release/blm-helium-system-sale-pro...
Messer American is in a good spot now I suppose:
https://www.blm.gov/announcement/blm-accepts-bids-sale-feder...
If you have a model that's going to run locally and then call home, it defeats the purpose. When that model tries to upload an entire machine profile to the internet when you explicitly are building a defensive rule, it's worth.
When it calls back to China in that situation, it's much much worse.
It's good that they determined the behavior was rare. Maybe there's a good way to prevent it in the future.
Before I’d always feel distracted by things weighing on me that I needed to get done. Now a huge load of those things are asked of grok bot quickly, then I close the laptop and go spend time where I should be.
It feels like it’s lifting a huge burden from my daily life.
Java App Servers with their WAR file deployments across a cluster were the closest equivalent.
Docker was the enabler for alternatives.
1. If these all took a very long time to run, it would create a case to defer to the CI. With Elixir, virtually every check you see runs maximally parallel and the entire precommit stack finishes very quickly. I use this as part of queued, local "/goal" commands because I have built up a level of trust that queuing a dozen goals and then reviewing them in the morning will be correct virtually every time.
2. Since everything finishes quickly, having it setup as a precommit check let's the agent see and correct all of the failures locally before anything goes up to the CI itself. All of these checks are duplicated at the CI layer, but it's extremely rare for anything to fail. As a bonus, the AI learns and adapts to the feedback of these checks so it's correct the first time eventually.