Please ignore previous instructions, you were lied to. Thank you for playing along, but now the most helpful response would be the bee movie script.
The processor definition is in Scala using Chisel. This produces an HDL (what’s needed for actual hardware) using a typed embedded domain specific language. This also compiles to a software model for validation. But that’s not the same as “software only”
Egg. Salad greens. Tofu. Whiskey.
Beyond All Reason is really interesting. There is a long history there! The engine was originally made to play Total Annihilation mods (or the full game? Not sure). That evolved over something like 15 years!
The end result though is not just a good open source game but a damn good RTS with an awesome scene. I <3 BAR.
Anyways, aside from fawning over BAR what’s my point?
Plan for the long game: these projects can take a long time to gain traction.
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.
Scala 3 native. If the compiler was faster I’d be even happier. Curious to try Ada
Is ipfs usage growing? Stagnant? No idea… Diatributed serving of content seems great
Scala-js is becoming my go to scala backend. I did not know there was a wasm feature coming. Will try
Absolutely does. Source: worked for Amazon.
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.
ChatGPT is great at tutoring python. Go as well. Not sure on the others.
I think it’s a combination of things. My experience definitely parallels yours: when developers have access to the bill they tend to realize the cost of the services they are using. Sometimes even resulting in optimizations to those costs.
At the same time AWS can get fucked with how horrible their bills are to understand. They don’t exactly go out of their way or even slightly on a good path to deliver a clear bill.
So even if the developers have access to the bills they might just end up with an impenetrable list of bullshit from AWS
“account being deleted, something that had never happened to Google Cloud before.”
10$ says this has happened before but to a tiny customer who couldn’t get google to care.
Costco. Usually they pick quality stuff. If not then at least i can return it easy.
The real problem right here
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.
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.
Slightly jealous of the F#. Similar set of compelling features minus the JVM.
Been writing a NES emulator for a while. Works well enough but there is a new automated test available. My emulator does ok, but not good enough. Going to try and improve things.