Ruddle

Author again, https://github.com/Ruddle/EconomySimulator

Author here, In case all resources are equally owned, the QoL is bound to all of them (as opposed to none). It does take multiple purchases to increase the QoL, but it is the only way. Otherwise people would starve due to aboulomania.

The average QoL is sampled each end of day, step 73-75 depending on the random seed. At step 72 you are seeing the zeroth day average QoL ,with nearly all the intraday mutations of the first day.

The symmetry is nice. I did not expect to write, or code most of it. We were both taken by serendipity.

Thanks, and agreed. How ironic though, working on that fantasy is near certainly not economically viable. This blog post is merely procrastination that preempted job seeking.

Author here, simulation 16 shows that money printing, and tax have common effects. The state can replace one with another. Here the 65% tax is replaced with 10% tax plus inflation, i.e., giving new money to public servants. The new money creation decreases the value of money owned by producing workers.

We could even remove the tax entirely, and still support the 3 public servants. To be convinced you can look at each unit transaction and see that all resource are accounted for.

Another way to look at it, is that the QoL of producing workers is lower than if there was no public servants. Every resource a public servant has, is bought from a worker at some point, whether the money for the purchase comes from taxation or inflation.

Author here, if there is enough interest I can clean the code up and put it on GitHub. It is basically a state machine.

  Location: France
  Remote: Yes
  Willing to relocate: Yes
  Technologies: Rust, Javascript, webgl/webgpu, SQL
  Résumé/CV: https://github.com/Ruddle
  Email: mail@thomassimon.dev

I worked in medical research, military, video games, b2b/b2c, CMS, OS dev, audio. I assumed the role of CTO, lead developer, fullstack. I built products from a to z, sales sometimes included. Co-founder of 4 startups that failed. Lots of side project, recently Fomos that was on HN front page this week. Looking for new opportunities ! Ready to work now !

Author here. Your guess is correct. An app is its own callback. It might be possible to write an small app-level executor to get back those sweet language-level support for async though.

Author here, that's a neat idea. However I also like the simplicity in having only one runtime interface. If the OS has to handle every version anyway, an app in the future could just use padding to feel like it is "clean".

  struct Context{
   padding: [u8;256], // old stuff
   ctx: ContextV42
  }

Just typing that felt a bit wrong though. On the other hand the app declaring what version it is feels like what executable formats (like elf) already solve. I am trying alternatives.

Author here. Scheduling is a spectrum. Current OS are preemptive, but also a bit cooperative. An app can make the decision of yielding control.

The opposite could work: OS is cooperative, unless some threshold of resource usage is triggered (a timer interrupt of instance). It then context switch to enter a, hopefully rare, failure mode, thus turning preemptive. Kill the app, and get back into cooperative mode. Let's call it optimistically cooperative & pessimistically preemptive.

Location: France

Remote: Yes

Willing to relocate: Yes, anywhere !

Technologies: Rust, Scala, Scala.js, WebGpu, willing to learn something new

Résumé/CV: https://www.linkedin.com/in/thomas-simon-dev/

Email: thomas.simon.work@gmail.com

Github: https://github.com/Ruddle

I started 2 companies since I graduated. One failed and the other is now a passive income. I am looking for autonomy, responsibility and challenge. Ideally Rust but open to anything.

IMO any program with a sufficiently high number of entities in a low level language contains an ad hoc informally-specified bug-ridden slow implementation of a garbage collector

Hi, former non-US student here, I got an internship (J1 visa) in a US university in a lab. I got it thanks to one of my teacher. He knew a US professor and gave me the opportunity to talk to him. The professor did not even need a new student in the lab, but I proved him that I could be useful (showed some of my projects). The university took care of most of the paperwork. I hope this can help you.