It doesn’t sound too AI generated, and the stories flow well without much text that mean nothing. (Also, she’s a consultant, so writing this content is meant to signal some professional skill. There’s not much spam, just 1 blog article a month.)
Even if it had AI help to edit, the content still matches my lived experiences of people mgmt.
Not sure if it's worth it. I don't see them complaining about speed and they use specific python dependencies then they would need to translate that to rust also.
Rewriting it in Rust isn't automatically faster and more importantly Eve's gameplay is constantly being iterated on and Rust has proven to be bad for that.
Moreover, most of Eve's bottleneck isn't single server speed, it's mostly network IO and database queries and latency. The big TiDi skirnishes in particular are slow due to this.
On the iteration: I'm not sure that's the case anymore? Sure new content is added but it's largely within existing systems. The game is closing in on 25 years old at this point.
I've no insight into what specifically their bottleneck is. The database doesn't sound like it'd be a factor, though, since the slowdowns are isolated to single nodes handling the area with players and don't effect others.
>The database doesn't sound like it'd be a factor, since the slowdowns are isolated to single nodes handling the area with players
It doesn't sound like it because you haven't been paying attention. By and large, the TiDi slowdowns are because of network IO (i.e. too many players connected to a single node), but the database causes stutters when large numbers of ships are exploded at once.
DB needs to update inventory, skills, implants, and killboards which requires multiple round trips. Moreover, while these round trips to the DB happen, the core processing threads often end up yielding waiting for the SQL Server instance to respond.
But again, I only mentioned it as part of the problem. The core of the issue is definitely Network IO. Someone activates a module or weapon, you need to send that info to 1-10k players as a packet update. That's the source of delays, not processing speed. Rust won't magically speed that up, the network layer is already written in C.
Could I see your sources for how Rust is slower for iterations?
I've been working in JS, Python, C#, TS, and F# for about ten years. I'd guess F# and TS are tied for me for prototyping speed. I have to wonder how much the "common knowledge" that strongly typed languages are slower for prototyping is driven by unfamiliarity with the tool.
I didn't say anything about strongly typed languages being bad for prototyping. I specifically said Rust is bad for prototyping speed. Lots of high profile cases of Rust being abandoned (Witchbrook comes to mind as an example).
I say this as a big fan of Rust. I use it for CLIs, microservice development and more. The borrow checker, traits, enums, etc. are amazing for maintainability, reliability and speed. Fast iteration where you'll want to completely redo a system at the drop of a hat? Rust is a royal pain in the behind.
Largely, proponents of Rust who push it for game development have their minds stuck in the solutions space and forget about the problem space. The fact that Rust was even proposed to fix Eve here is a huge example of solutions focused thinking (bad bad bad) because is misunderstands that Eve was never bottlenecked on processing speed of its physics or business logic.
Depends on what you do. For prototyping GUIs without well-defined framerwork, Rust is terrible. TypeScript wins completely. For back-ends, not so clear, since it is easier to write the intent there and even prototype must be somewhat correct, and TS is not as explicit as Rust is.
I’ve been doing this on a large system I’m building. Anything that takes longer than an hour to run, processes a high rate of events (maybe >5/s averaged over a day) or has downstream gpu waiting for it.
Python + tests cross compiled to rust has huge benefits for memory footprint and secondly cpu.
It’s allowing me to achieve wonders on a small amount of hardware.
I don’t know what datasets are available to these LLMs, but I’d imagine if there was training on CAD code, text, and images, a prompt steered towards that probably could get it pretty good.
I am not a mechanical engineer, so even prompting well with ME lingo probably will take some effort.
I would go even further and suggest that "fact/opinion" is just a framing that falls apart under scrutiny.
My framework is more or less that anything we might call a fact or an opinion is a statement, statements have varying degrees of veracity/falsifiability, and statements are essentially meaningless until they're processed through the lens of underlying beliefs/values/frameworks.
"The sky is blue" - What is the sky? What is blue? Who is viewing the sky, (someone who has sight, and isn't colorblind perhaps)? Isn't it sometimes gray? And so on.
> Group projects were also a common complaint. You were randomly assigned a group, but it was often unclear if the participants were even doing the course - many people were in completely ghost groups.
I see that nothing has changed in 20 years. Even when attended the courses physically in person, group project usually had 1 or 2 people doing all the work and the rest nowhere to be found, or just hanging out. :p
I once had a group project during a masters course where one guy disappeared halfway through the semester. Didn’t respond to phone, email, anything. The rest of us were discussing how to let the professor know after he had been over a month MIA (we didn’t need him but didn’t want him to get the group grade) when the professor emailed us to say he had heard from the guy, who had been literally hit by a truck and was still in hospital; medical withdrawal.
I still remember in a varsity project, we're a group of three. I took over the design and coding. Another guy was bad at coding, so he took over all the documentation etc. The last guy was doing db design and write some basic SQL for the CRUD.
We were supposed to integrate everything a week before submission. Project was assigned about 6 weeks before submission. The last guy kept saying he's working on it and we don't have to worry.
Then a week before submission, he has nothing to show. Didn't type one word.
I had to scramble and get it done myself. Time was not enough anymore; we got B instead of A. I was already known to get A grade in every project where teachers would give me A++ if that was a grade. The teacher of that course was so disappointed...
Since then I did all projects solo. Had to fight a little with some teachers to get that approval; esp when there were really big projects for 5/6 people group. Still did solo and got rated as best project in every single one of them.
The point of group projects is not to make the best project, it’s to learn to navigate working with other people and all the messiness that entails. Soft skill development and the slackers are a feature not a bug. Doing group projects solo completely defeats the point of the exercise—I’m surprised you got approval from any profs for that.
You are not completely wrong but you are missing out a lot too. It is accountability without authority issue.
Yes, learning to navigate working with other people is important. But why are you learning that? Because you will need that in work place.
You know what is there in workplace that is not present in varsity project?
Accountability: If someone is not doing their job, you can complain to the manager/boss. There is none in group project.
Authority: In varsity project, everyone is equal. I have no authority over others, even when I have much more experience/know-how. Telling prof one guy is slacking doesn't get much done.
Right to Choose: In work env, if I am highly skilled, I have the option to choose the place I work and thereby increasing the chance of like-minded like-skilled peers. In varsity project, I can get paired with a dumbass and have to bring myself to lowest common denominator. Sorry, I don't (have to) work with idiots in an equal setting. There's a reason that guy is doing some unrelated bank managerial job for $1k/month and I buy $1k worth of collectible items per month without blinking an eye.
If a varsity project is setup in a work env way where I get to interview who joins my team and have the right to fire them if they don't get their shit done, then I'm happy to do group project. Similarly, I'm happy to go thru the same process to join another person's team (if I consider them better).
PS: I did 2 group projects with a friend before that incident and we had zero issues with anything. Simply because we did the work and our skill levels were similar. He's working as Principle Engineer at Oracle now and it is no surprise.
The syntax looks like rust, but esp w/the memory management model (reference counting), it’s going to have more overhead than rust when it’s running, more like Swift or at worse, Python.
It doesn’t have a garbage collector, it uses reference counting with a cycle detector. So, no GC pauses. It should be suitable for hard real time systems.
It doesn’t sound too AI generated, and the stories flow well without much text that mean nothing. (Also, she’s a consultant, so writing this content is meant to signal some professional skill. There’s not much spam, just 1 blog article a month.)
Even if it had AI help to edit, the content still matches my lived experiences of people mgmt.
reply