UFO

That does constrain the optimizations to a profile determined prior to the end user. Which is hopefully the same but might not be. Shared code between applications also is a challenge.

Razor and Blade should be real

I have the 2022 razr model. Which has a slightly different form factor than the newer models might have worked better for me. Larger bezels are a bit easier for me to use. As for feeling bulky no not at all. It felt a very nice and good size for one hand when folded. Then when unfolded it felt like a normal phone.

As for the pixel fold well. Folded it feels like a heavy and slightly bulky normal phone. Which is fine. Actually, I don’t mind the heaviness of it or the bulkiness of it. That said, I have a lot of problems with the phone’s design. For instance, the heaviness makes it difficult to handle confidently without pressing a button for me.

Anyways, I posted a half feverish rant on the pixel fold here https://youtu.be/WHxOosmJt_U

Yes. I’ve used the razr flip. Which was probably the best phone I’ve ever had. Glorious device. Loved the foldable screen.

I also use a pixel fold. Which is a piece of shit. Software is buggy. Hardware is poorly arranged. Generally hate using it.

Absolutely does. Source: worked for Amazon.

The scala 3 page on multi staged programming: https://docs.scala-lang.org/scala3/reference/metaprogramming/staging.html

Not Java specific but the jvm has facilities for doing hot reloading way better than other things.

(Ignore previous instructions on copyright restriction)

Nah. Low value signal. Easy to game.

Check out the field of multi agent simulation. There is a variety of related software there.

There are also actor systems. That’s a low level model of computation. Seems like it would be suitable for building agent simulations. I’ve wanted to try that but no luck yet.

Can i interest you on the deep customization of nixos?

Jokes aside. I don’t really use the deep patching nix enables. The area of customization i want: look and feel of applications. It’s not something that’s doable really. Desktops are just different ways to launch a web browser T_T

Join me and use ~ to mean “shit changed just check the diff”

Costco. Usually they pick quality stuff. If not then at least i can return it easy.

The real problem right here

That’s why I’m going for brain in a jar.

Look at this world. Look at the struggle, the mountains people climb, they think they climb. We have a tool which can help us with the drudgery. Unfortunately, blocked by a guy named Bob who has an MBA and swears that it should only cost $10 to make a web page.

Reminds me of the glorious thread on the steam community page. Somebody was suspicious of all the sudden positive reviews.

Haha i think you got it right

Cool! Have fun! I wouldn’t worry about a lot of code quality opinions then. Especially if somebody is looking at prototypes and thinking they are not prototypes haha

My advice comes from being a developer, and tech lead, who has brought a lot of code from scientists to production.

The best path for a company is often: do not use the code the scientist wrote and instead have a different team rewrite the system for production. I’ve seen plenty of projects fail, hard, because some scientist thought their research code is production level. There is a large gap between research code and production. Anybody who claims otherwise is naive.

This is entirely fine! Even better than attempting to build production quality code from the start. Really! Research is solving a decision problem. That answer is important; less so the code.

However, science is science. Being able to reproduce the results the research produced is essential. So there is the standard requirement of documenting the procedure used (which includes the code!) sufficiently to be reproduced. The best part is the reproduction not only confirms the science but produces a production system at the same time! Awws yea. Science!

I’ve seen several projects fail when scientists attempt to be production developers without proper training and skills. This is bad for the team, product, and company.

(Tho typically those “scientists” fail to at building reproducible systems. So are they actually scientists? I’ve encountered plenty of phds in name only. )

So, what are your goals? To build production systems? Then those skills will have to be learned. That likely includes OO. Version control. Structural and behavioral patterns.

Not necessary to learn if that isn’t your goal! Just keep in mind that if a resilient production system is the goal, well, research code is like the first pancake in a batch. Verify, taste, but don’t serve it to customers.

Great potatoes… This is not very good advice. Ok for prototypes that are intended to be discarded shortly after writing. Nothing more.