@tedchoward
Uncategorized
23
Posts
4
Posters
38
Views
-
@tedchoward @davew You may have noticed some weeks back that I accidentally pushed a PR to your repo! I'm often telling Claude to reference it when investigating what the legacy app did if we get into a tight corner.
It's been going well, and I'm currently working on the low-level guts that would enable POSIX-based networking so that the web client & server will work. It's 100% headless, and my plan is for the UI to be a separate app.
Feel free to reach out if you have any questions! đ
-
@tedchoward @davew I actually never build it by hand, but that is the correct makefile. Develop is pretty broken still at the moment, but should get a lot more stable by the end of today. If you look at CLAUDE.md at the top of the project tree, there's a quick reference with a list of commands for running tests and doing db migrations, but oddly nothing about how to build. Lemme fix that!
-
@tedchoward @davew I actually never build it by hand, but that is the correct makefile. Develop is pretty broken still at the moment, but should get a lot more stable by the end of today. If you look at CLAUDE.md at the top of the project tree, there's a quick reference with a list of commands for running tests and doing db migrations, but oddly nothing about how to build. Lemme fix that!
@tedchoward @davew I asked Claude to assess the docs gaps and close them. The README.md now has build instructions, and docs/GETTING_STARTED.md is a new "newcomer" guide with: system requirements, prerequisites, step-by-step instructions, UserTalk examples, REPL usage, and troubleshooting guide. Hopefully this is enough to get you started playing around with it. đ
-
@tedchoward @davew I asked Claude to assess the docs gaps and close them. The README.md now has build instructions, and docs/GETTING_STARTED.md is a new "newcomer" guide with: system requirements, prerequisites, step-by-step instructions, UserTalk examples, REPL usage, and troubleshooting guide. Hopefully this is enough to get you started playing around with it. đ
@tedchoward @davew Just pull the latest develop to get the updates. I also have another PR coming in that fixes some eggregious issues in dot-path resolution. That'll take maybe 20 min, so you'll want to pull again and rebuild in just a bit.
-
@tedchoward @davew Just pull the latest develop to get the updates. I also have another PR coming in that fixes some eggregious issues in dot-path resolution. That'll take maybe 20 min, so you'll want to pull again and rebuild in just a bit.
@tedchoward @davew Well, I got a little ahead of myself. The REPL should work for some basic stuff, but there are still dot-path search issues I have to track down. This one has been a slog, but making slow and steady progress. Either way it's worthwhile to pull again and rebuild. From the top-level of the project you should be able to run:
./frontier-cli/frontier-cli ./databases/Frontier.root
... to start the REPL.
-
@tedchoward @davew Well, I got a little ahead of myself. The REPL should work for some basic stuff, but there are still dot-path search issues I have to track down. This one has been a slog, but making slow and steady progress. Either way it's worthwhile to pull again and rebuild. From the top-level of the project you should be able to run:
./frontier-cli/frontier-cli ./databases/Frontier.root
... to start the REPL.
@jsavin @davew Iâm getting a build error when I run `make -C frontier-cli`
```
âş make -C frontier-cli
../third_party/cmake-install/bin/cmake -S ../third_party/Paige -B ../third_party/Paige/build-headless -DCMAKE_BUILD_TYPE=Release -DCMAKE_OSX_ARCHITECTURES="arm64;x86_64"
/bin/sh: ../third_party/cmake-install/bin/cmake: Bad CPU type in executable
make: *** [../third_party/Paige/build-headless/libpaige.a] Error 126
```
It looks like itâs trying to use an embedded version of cmake. -
@jsavin @davew Iâm getting a build error when I run `make -C frontier-cli`
```
âş make -C frontier-cli
../third_party/cmake-install/bin/cmake -S ../third_party/Paige -B ../third_party/Paige/build-headless -DCMAKE_BUILD_TYPE=Release -DCMAKE_OSX_ARCHITECTURES="arm64;x86_64"
/bin/sh: ../third_party/cmake-install/bin/cmake: Bad CPU type in executable
make: *** [../third_party/Paige/build-headless/libpaige.a] Error 126
```
It looks like itâs trying to use an embedded version of cmake. -
-
@tedchoward @davew aah. Good to know. I'll have a look later. I've got an Intel machine I can try it on
-
@tedchoward @davew aah. Good to know. I'll have a look later. I've got an Intel machine I can try it on
-
This is the best thread ever.! đ
-
This is the best thread ever.! đ
This is cool
Frontier REPL - Interactive UserTalk Environment
Type /help for commands, /exit to quit
[root]> clock.now ()
1/26/2026; 6:12:54 PM
[root]> date.dayString (clock.now ())
Tuesday -
@tedchoward @davew And around now you're going to start to notice a whole bunch of stuff that's very broken. đ
For example I just tried parentOf (string.mid) and got system.compiler.["kernel"].string, which is totally wrong. Heheh. (That's the next battle. Then back to networking.)
-
@tedchoward @davew And around now you're going to start to notice a whole bunch of stuff that's very broken. đ
For example I just tried parentOf (string.mid) and got system.compiler.["kernel"].string, which is totally wrong. Heheh. (That's the next battle. Then back to networking.)
@tedchoward I fixed the bug that was causing weird dot-path lookups (I think). You should pull latest develop and rebuild to get it. [cc @davew]
-
jake savin is making good progress on porting frontier to run, headless, on linux and mac os. just wanted to make sure you were in the loop.
hope all is well! been following your work on old PCs, many of which i used "back in the day."
I _so_ miss Frontier (and its babies). Eager to se this happen!
-
I _so_ miss Frontier (and its babies). Eager to se this happen!
i am totally looking forward to it too.
jake is doing amazing work, and i'm going to be sure to clear a lot of my time when he's ready for me to start building stuff with Frontier on Linux.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Ce anno fatto un corteo pe er NO bruciando cartelli co la faccia mia e Nordio
Dateve na mossa a fĂ un contro corteo pe er SI bruciando cartelli co la faccia de i maggistrati
...no spe, troppo esplicito đ¤
https://www.open.online/2026/03/14/corteo-no-referendum-no-sociale-roma-bruciate-foto-meloni-nordio/
-
I know it's intended as a joke but it may not be that far from reality:
-
Non siamo (ancora) alla minaccia di dazi ma i concetti sono simili. Gli anglosassoni lo chiamano tantrum. Quanto alle minacce alla Cina, loro controllano il rubinetto delle terre rare...
Donald Trump warns Nato faces âvery bad futureâ if allies fail to help US in Iran https://www.ft.com/content/1ca6d121-760b-4ec5-b6ad-514fdaa94873
-
@ZoidbergForPresident @grumpygamer somebody made a doom mod where the monsters are processes and killing the monster kills the process; I bet something similar could be done for defragmenting
-
@annamam@mastodon.social hello and welcome to the #Fediverse
-
@dazo @grumpygamer Funnily enough, I remember reading a letter to a Your Computer (the British one) in Februray 1985, lamenting that these new 64 KB monster machines made for sloppy programming and had taken all the fun out of computers. đ
-
@jwz I know. Some people don't
-
Magnetic-Suspension Hoverboard is Only 11 Years Late
Anyone who saw Back to the Future II was disappointed when 2015 rolled around with nary a hoverboard in sight. There have been various attempts to fake it, but none of them quite have the feel of floating about wherever youâd like to go that the movie conveys. The little-known YouTuber [Colin Furze] has a new take on the idea: use magnets. Really big magnets.
If youâre one of [Colin]âs handful of subscribers, then you probably saw his magnetic-suspension bike. We passed on that one, but we couldnât resist the urge to cover the hoverboard version, regardless of how popular [Colin] might be on YouTube. Itâs actually stupidly simple: the suspension is provided by the repulsive force between alarmingly large neodymium magnets. In this case, two are on the base plate that holds the skateboard âtrucksâ, and two are on the wooden âdeckâ that [Colin] rides upon.
Of course magnetic repulsion is a very unstable equilibrium, so [Colin] had to reduce the degrees of freedom. In his first test, that was with a pair of rods and linear bearings. That way the deck could only move in the z-axis, providing the sensation of hovering without allowing the deck to slide off its magnetic perch. Unfortunately those pins transferred too much vibration from the ground into the deck, ruining the illusion of floating on air.
After realizing that heâd never be able to ollie (jump) this massive beast of a skateboard, [Colin] decides he might as well use a longboard instead. Longboards, as the name implies, are long skateboards, and are for transportation, not tricks. The longboard gets the same massive magnets, but after a couple of iterations to find a smoother solution â including a neat but unsuccessful tensegrity-inspired version â ends up with a pair of loosely-fitted pins once again, though relocated to the rear of the board. From the riderâs perspective, it looks exactly like a hoverboard, since you canât see underneath from that angle. According to [Colin], it feels like a hoverboard, too.
The only way to do better would be with eddy currents over copper, or superconductors over a magnetic track, but both of those methods limit you to very specific locations. This might be a bit of a fakeout, but its one with a degree of freedom. One, to be specific. You have to admit, itâs still less of a fake than the handle-less Segway we got in 2015, at least.
