Earlier quoted context omitted.
That's pretty tame, if you want to be disturbed check out r/MyBoyfriendIsAI
[dead]
You what now? lol
What it feels like to work with Mythos
141–150 of 337 posts
Re: What it feels like to work with Mythos
#142Earlier quoted context omitted.
> At the same time, it is very dissonant to see the industry heading towards hour+ long workflows with an agent. At this point, pay me significantly more, and I'll do it.
> pay me significantly more Ha ha, that's how you negotiate yourself out of a job!
Fire me then, I can bring someone else drastically more value with AI tooling.
Re: What it feels like to work with Mythos
#143What I find fascinating that there is so little substance in this article about the quality of produced code and the medium. Is the code documented and tested? Is it understandable and extendable? Is it secure? What language, framework, database was used? Author mentions judgement and taste - well, is the code tasteful? Will the model rearchitecture the entire thing if I ask it to add new functionality, spending anot…
You probably don't care about the ingredients or engineering of asphalt, only if the road does its job well or is filled with potholes. Outside of the software industry, nobody gives a shit about code or databases.
I agree. But if I'm paying for the road (even as a taxpayer) I get angry that after a year it's full of potholes and that there are unnecessary signs warning about penguin crossing, making it cost 2 times more than it should have (and dont get me started why this road is really a highway leading to my house). I'd want certain qualities. And this article is basically = you will get a road, built quickly
But yes, you are right - I don't build roads and don't know what is a price to build a road and how to determine the quality of correctly built one, nor I will ever care or learn.
Re: What it feels like to work with Mythos
#144Earlier quoted context omitted.
now for the best question: whats your ROI here?
Humans are very expensive, so the equation almost always falls against them. It's not just salary, but also safety/labor regulation, legal risk, vacations, sick time, personal conflicts, HR, benefits. Even when automation is more expensive on paper, it's generally still cheaper
One of the large (and enjoyable IMHO) challenges in this line of work is developing a de facto understanding of your process and the context it's in service to, and that's only possible if you're actually on your industry equivalent of a "shop floor" for each domain the project touches.
As far as I can tell this part of the job isn't really on anyone's radar anymore.
Re: What it feels like to work with Mythos
#145Earlier quoted context omitted.
I’ve been working on implementing some common web infra type projects in Rust lately. Basically trying to use a lot of the great primatives in Rust like rustls (modern openSSL) and Tokio (async) to build memory safe or close, nginx drop in replacements. A small portion of this effort is having a high quality Lua in Rust repo. I’m using mythos to fix some of the performance issues with my Lua interpreter that gpt 5.5/…
What’s wrong with mlua?
Mlua works for many use cases but is a wrapper around the C code, so you need to bundle C as part of the build. So this is worse for cross compilation and makes it so you can't easily use mlua projects in wasm32-unkown-unknown. An example is that it would be hard to run a game in the browser that exposes Lua scripting with mlua.
The other reason is that because mlua is just a wrapper around the C code, it has unsafe you can't really get around. So for example Lua is used in Redis, which has this critical CVE https://github.com/redis/redis/security/advisories/GHSA-4789... that a memory safe version of Lua wouldn't have to deal with.
Mlua is still fine or even better for many other cases though!
Re: What it feels like to work with Mythos
#146Earlier quoted context omitted.
now for the best question: whats your ROI here?
Humans are very expensive, so the equation almost always falls against them. It's not just salary, but also safety/labor regulation, legal risk, vacations, sick time, personal conflicts, HR, benefits. Even when automation is more expensive on paper, it's generally still cheaper
> Humans are very expensive, so the equation almost always falls against them.
You underestimate what these models cost. Uber's budget is $1,500/dev/month. I gather that was put in place because the dev's were going through $6,000/dev/month, which Uber decided could not be cost justified.
Fable costs at least twice as much, or $12,000/dev/month.
Fable can apparently work for hours without supervision, which means a skilled engineer can now have it working on many tasks concurrently. I would not be at all surprised if they can put a nought or two on that number. If you do that, you are well out of "what a human costs" territory.
Re: What it feels like to work with Mythos
#147Earlier quoted context omitted.
What’s wrong with mlua?
Mlua works for many use cases but is a wrapper around the C code, so you need to bundle C as part of the build. So this is worse for cross compilation and makes it so you can't easily use mlua projects in wasm32-unkown-unknown. An example is that it would be hard to run a game in the browser that exposes Lua scripting with mlua. The other reason is that because mlua is just a wrapper around the C code, it has unsafe…
The WASM thing makes sense. Do you need unknown-unknown? Seems like support exists for emscripten and wasi: https://github.com/mlua-rs/mlua/issues/366
It just seems like a lot of hassle to write a lua interpreter, although it would be nice to see a high quality one in Rust :)
Hematita was promising, but looks abandoned.
Re: What it feels like to work with Mythos
#148Reading the first few paragraphs of what he calls "the most sophisticated academic social science paper I have yet seen from an AI" does not impress as much as I hoped. "Posterior beliefs about market demand are purely referencedependent: holding dollars raised constant, they track only performance relative to the founder’s self-chosen goal—jumping half a standard deviation at the threshold, responding steeply for th…
[deleted]
Re: What it feels like to work with Mythos
#149Earlier quoted context omitted.
Mlua works for many use cases but is a wrapper around the C code, so you need to bundle C as part of the build. So this is worse for cross compilation and makes it so you can't easily use mlua projects in wasm32-unkown-unknown. An example is that it would be hard to run a game in the browser that exposes Lua scripting with mlua. The other reason is that because mlua is just a wrapper around the C code, it has unsafe…
The WASM thing makes sense. Do you need unknown-unknown? Seems like support exists for emscripten and wasi: https://github.com/mlua-rs/mlua/issues/366 It just seems like a lot of hassle to write a lua interpreter, although it would be nice to see a high quality one in Rust :) Hematita was promising, but looks abandoned.
Yeah an example is that currently you can't build Bevy games in the browser with scripting in Lua, so I've gotten a little traction there.
And yes it seems like there has been many attempts to get a solid Rust Lua over the years and most never reached parity so hoping some people can find use case for it! This one is at full parity in terms of behavior and performance is getting to within striking distance.
Re: What it feels like to work with Mythos
#150Earlier quoted context omitted.
The WASM thing makes sense. Do you need unknown-unknown? Seems like support exists for emscripten and wasi: https://github.com/mlua-rs/mlua/issues/366 It just seems like a lot of hassle to write a lua interpreter, although it would be nice to see a high quality one in Rust :) Hematita was promising, but looks abandoned.
Yeah an example is that currently you can't build Bevy games in the browser with scripting in Lua, so I've gotten a little traction there. And yes it seems like there has been many attempts to get a solid Rust Lua over the years and most never reached parity so hoping some people can find use case for it! This one is at full parity in terms of behavior and performance is getting to within striking distance.
Best of luck! We used mlua at $JOB for scripting support, and it worked great, but we’d have preferred a pure rust solution if one existed with the right performance profile