Formula 1 cars also have massive amounts of heavily engineered downforce and negative camber to give them insane amounts of grip. Pretty much every street car has enough braking power to lock its brakes in almost every condition but doesn’t have nearly the grip to utilize it.

Bigger brakes != more stopping power.

Too bad this didn't make it into the new Kindle Colorsoft. Oh well

> Once the models are good enough

That's a big "if".

Even for coding these things are not ready to take away real decision making and it's not clear they will ever get there.

Sure, but that's normal for moonshots. Maybe LLMs really will stall and spend 10 years getting better at anything and everything except taste, and then there'll be a completely new approach that has nothing to do with massive GPU farms. Maybe not.

I've worked with neutral atom QCs before (though am not a laser tech): keeping lasers locked is a massive pain in the ass.

> more so effort should be spent on making the technology cheaper and more accessible

Lasers are weird because the techniques to generate light at different frequencies differs a lot. "Telecom wavelengths" used in, say fiber optic networking, is super cheap and widely available, but these QCs often need different wavelengths that aren't mass produced. Some systems even need the ability to tune the wavelength precisely and the range of that tuning is another spec that can matter. I'm sure these QC companies would love for this to be more stable and cheaper, but the reality is without demand (of which there is little), it's just not going to happen.

Pretty much any bluetooth headphones work connected directly to the AppleTV, not just Airpods

For tech especially I don't think that's necessarily true.

I feel like Go would be a great backend target for Gleam

Go's garbage collection isn't well suited for an immutable language like Gleam, so the performance would likely be disappointing compared to other targets.

The concurrency model in Go is also poorly suited to the BEAM's process model. Goroutines share a heap so you can't do a lot of things safely that processes can do. Having independent memory space for a process allows you to free it safely when work is done without GCing everything and you can also safely share data because you have a copy not a ref.

There is this: https://github.com/ergo-services/ergo which i keep meaning to take a look at, but never seem to quite get around to…

It looks reasonable but I’d have to see how they actually do memory management.

author here, thanks for the mention.

PS: i'll be publishing Ergo Framework for Rust soon (same actors, same network, fully interoperable peers)

I just saw your reply! give me a shout when you release it.

An JavaScripts is? Rust is probably a more performant target regardless

Surprisingly yes! JavaScript's allocator and garbage collection system is quite well suited to immutable programming.

Rust is a very poor compile target as the compiler is slow and not commonly available, and the aspects of Rust that make it good for humans to write make it a poor choice for compilers to target. With humans the produced code is verified, but with a compiler the compiler is what is to be verified, so the inflexibility of Rust are largely a hindrance compared to other native compilation targets.

What lower-level language do you think aside from rust which can be more helpful for the purposes of being a compile target, nim/D both support garbage collection and non garbage collection, so would languages like these be more preferable

I really love gleam and its community and I would really really love if gleam could be more like golang though, which can help it in compiling to machine code

gleam language but with the developer experience of golang (cross portability/small binaries/fast compiled language which is fast to compile) is honestly one of my fever dreams and I would love to know if it can ever be a reality!

For that sort of compilation target more flexibility is beneficial, so C, Wasm, LLVM IR, Cranelift IR etc are better than Go, Nim, and D in my opinion.

> cross portability/small binaries/fast compiled language which is fast to compile

You don't need native compilation to build fast single file executables for a program, there's ways one can achieve this with Gleam today. Bundling the BEAM into your Gleam application executable with something like Gleepack is one option, and this will produce smaller executables than Go will by default for many applications.

I don't get the impression that javascript is among Gleam's targets because of performance.

- server target: BEAM

- client target: js

Once you've covered those bases, you're kind of done.

If the server needs to do something special in an OS process... might as well let the OS mediate that interaction so that it can be fully generic, rather than trying to bend the language around whatever the unknown action might be.

For that there is Lisette. Close to gleam, compiles to Go.

I just learned about Lisette, and from there Gala. Any thoughts on Lisette vs Gala?

Never used gala, but it seems going a bit more down the deep end, frankly it has features is dislike / would never use.

Lisette has been pretty straight forward, with its good Go interrop and familiarity (i have ocaml experience). Tooling is GREAT for such a young language. Im also a huge fan of the recent addition of a "zero" value. No nils like you get in vanilla Go.

I tend to write libraries in Lisette i then import in my go "shell", thats more or less a main function with some setup.

Full (lisette->go->lisette) Go interrop is still a WIP, but im certain it will be improved upon soon.

Thank you for the reply! There's very little public discussion (at least that I can find) about people's experiences writing Lisette, the language, or how well agents do with it so far so I really appreciate it. Been debating past couple days if I spend some of my claude sub tokens to try a partial rewrite of some code.

Yeah, i think lisette just needs some time (its pre 1.0, so probably not used in prod), but that said i read Listte is actually already used for building compilers for other languages.

Some people like to live on the bleeding edge, and once again, that said, the Go runtime is just so good so you have a solid base, and can always eject from lisette by just keeping the generated Go source. That makes it a more safe language to choose.

It seems to me like both Gala and Lisette are fairly safe to invest in for small projects that you'd otherwise write Go in assuming you have the token budget and patience to be able to as ask an agent to make the generated Go more idiomatic afterwards / do a native Go rewrite if needed.

I'm still not sure if I would rather test out Gala or Lisette or both, I appreciate hearing you've had a positive experience with Lisette!

Not sure about gala, but lisette produces good and readable go-code. There is a prelude (option, reault etc) package you possible would want to get rid of if you ejected. But an LLM could easily do this manual task for you pretty easily.

> But it got sad when the whole internet became a chan

I honestly do not see how you could go from talking about self censorship in the context of institutional censorship and then go on to say the whole internet has become a 'chan', it absolutely has not even if the current zeitgeist doesn't fully align with your particular ideals.

Great point. I meant in the sense that I don't need to go to a chan to read racist points anymore, but you are right about the contradiction.

>it absolutely has not even if the current zeitgeist doesn't fully align with your particular ideals.

It's an hyperbole to say that, sure. However, the change was faster than I expected. Nick Fuentes would be a fringe guy in 2010s. Now he is part of mainstream podcast circles

Yeah, it's pretty extreme. To be clear, I'm not saying it's a good thing, just that chan culture is so much worse across that and many other dimensions

Chans are just the answer to "What if people from developed countries, acted like they were from third world countries?".

Sure, of course it does. It's just different effort now.

Yes, that's my point.

PlexAmp is a good experience too, but not free.