lime!

that means you fit in here <3

of course it isn’t the point, and i try to rp as much as possible in games like this, but sometimes you just need to talk tactics or get someone to do a quest with you. outright banning it seems counterproductive.

sounds impractical in what is basically a numbers game. i get it for things like muds.

surely you must be after something specific?

wdym “thoughts”?

i know what roleplaying is, or at least what this game seems to think it is…

i want to know what “enforced” means. they don’t say.

what do they mean roleplaying is “enforced”?

other way around. they pivoted to offering enterprise solutions based on ai interpretations of their database to business customers. only they were too slow, since everyone had already scraped them.

well yeah they went all in on ai.

neeeeerd

i see you haven’t had to pleasure of using office 365

at least you don’t have to use simulink, right?

…right?

matlab is nobody’s favourite language. although using it does require an engineering degree, which makes you a nerd.

XFCE looks closest shape-wise. it also has the advantage that you can customise it using css.

while not exactly what you’re looking for, DesktopPal97 may be worth looking into as a base for your own theme.

vibe coding is when you let an llm write almost all your code, taking its output at face value. tony stark in the films just vaguely describes to his computer what he wants and trusts that it does the right thing.

please tell me you have an accepted code style with proper tooling and precommit hooks set up

you can get the same performance by using the restrict keyword in C.

basically, C allows pointer aliasing while fortran does not, which means C programs need to be able to handle cases when a value is accessed from multiple locations. fortran does not, so a lot of accesses can be optimized into immediates, or unrolled without guards.

restrict is a pinky-promise to the compiler that no overlapping takes place, e.g. that a value will only be accessed from one place. it’s basically rust ownership semantics without enforcement.

it is a dynamically typed language, but it’s not a weakly typed language.

the main thing that makes fortran preferable to C is the way it handles arrays and vectors. due to different pointer semantics, they can be laid out more efficiently in memory, meaning less operations need to be done for a given calculation.

so it would be more accurate to just have tailwind be css with a suit.