otikik

Just to add a little bit of perspective here. When I was a manager, if a candidate reached an interview with me, they had already had an interview with the recrui-I mean, "talent acquisition expert", with whom the compensation had already been previously discussed. I often had no idea what was the salary offered and I could not negotiate on it.

That was the other guy's job, and it as a prerequisite - they would not reach me if the compensation was not to their satisfaction. My job was to determine whether the candidate could perform at the offered post. If I needed to discuss compensation then someone before me would have screwed up.

Then you must have had such a good time that you forgot everyone’s flaws!

> surrounded by his loyal band of perfect lieutenants, who apparently have zero desire to advance, and have no flaws at al

Sir, I believe you have not watched it.

AI is definetly taking a big portion of the marketing budget as well.

Just today I was served a clearly AI-generated Halloween ad for Coca-Cola.

That is how it has always been (not that I agree with it).

My bet is that it will work ok in some cases and be confidently wrong in others.

The private sector is more efficient, yes, but only at extracting value.

Oh no!

Anyway...

If you’re not charging anything for it it’s free press for the original content creators imho

That is absolutely not the case.

Numerical loops in Lua are inclusive:

    for i=1,#t do t[i]=0 end

On the example above the i starts at 1 and goes up to (and including) the length of t.

With 0-based indexes, and that numerical loop format, it would be minus-one everywhere:

    for i=1,#t-1 do ...

I had a similar impression. It feels "not idiomatic". I disagree on the diagostic though - I think parenthesis-free calls are not what define what idiomatic lua is.

To me it is more about expressiveness and usage of basic language features. For example here's how a text field is set up currently.

           ito.TextField(draft)
                :label("Name")
                :focused()
                :on_submit(function(value)
                    if value:match("%S") then
                        phase.value = "review"
                    end
                end)
                :on_cancel(function()
                    phase.value = "choose"
                end),

The field is created on the first line, and then altered further with subsequent method calls that alter it. This reads like someone very used to Rust (and its Builder pattern) and then translating it verbatim to Lua. A more native Lua interface for me would look like this:

           ito.TextField(draft, {
                label = "Name",
                focused = true,
                on_submit = function(value)
                    if value:match("%S") then
                        phase.value = "review"
                    end
                end,
                on_cancel = function()
                    phase.value = "choose"
                end),
           })

As in: just pass a table to the builder. And if they ned to modify it later, they can just do:

           some_textfield.on_cancel = <some other function>

No need to "guard" the internal table with those extra methods.

Well, cancer operates like that, too.

I would like us to find a way to live without killing our host.

> leverage their ubiquity

We live in different worlds

> Someone made a fantastic joke website about how you can copy code with AI and claim it's made in a clean room, so technically you're not under any licensing agreements.

It is not a joke! The naming is so bad so it sounds like a joke. So people like the author assume it is a joke and move on without suing them. They are counting on that.

"The world" xD

Fair. I didn't include the word primarily in my sentence. Please assume it is included now.

> You're not anywhere near paranoid enough

I refuse to touch anything crypto with a ten-foot pole. I don't know if that makes me "paranoid", but it is certainly very easy. Just stay away from the thing doing drug markets, scams and rugpulls every month.

Doesn't the "growth" mindset also feels a bit alien to you?

Everything must grow all the time because all we care about is compounding interest, and that can only exist with continuous growth.

Finite resources and time be dammed.

Less coal lying around?

I hope when I am in need and someone thinks about helping me they don't find someone like you, man.

Because they exploited the rest.

Yes and no.

Yes part: LLMs have had the capability to generate code, including glue code, to do several steps in a single program.

No part: until some months ago, MCP servers were not prepared to use that glue code at all.

Your LLM could generate the code it wanted, and you could execute that code wherever you wanted, including letting the LLM run it. but every call to any of the tools exposed by the LLM is meant to be consumed by your LLM in the old paradigm. If said program makes 80 tool calls, your LLm would still have to send them, and parse their responses, consuming tokens.

In code mode the glue code is sent to the server, which executes it, and returns the final result. It’s a single invocation and a single response, instead of 80 like before

"We are star stuff", Carl Sagan [1]

[1] https://www.youtube.com/watch?v=LNqqFhFa4dI

I'm Spanish, born in Jaén (the most Olive Oil producing province in Spain).

There's multiple kinds of olives, each producing different kinds of oil. The processing used also affects the end result (extra virgin olive oil comes from the first press, less quality oils from successive processing).

* Picual is the most popular one. It has a strong taste, that "bite" that you mention, and a long shelf life. This means that it is the most exported one. That is probably why you (and others) have associated olive oil with that strong profile. It is however not the only kind out there!

* Cornicabra is the second most popular one. It is milder than Picual in taste, but still strong and durable. You might find it in some specialist shops.

* Arbequina has less of that "bite" that you mention at the end. Unfortunately it has a shorter shelf life as well, which means that it also tends to be exported less.

Because of this is unlikely that you will find it outside of Spain. At the same time it would be the best kind for making mayonnaise, especially if you don't like the bite at the back of the throat (that some people actually enjoy).

And these are just the 3 more popular varieties. There's many more local, smaller ones.

"!" is like half of the size of "?". Even if that's faithful to the keyboard, it is very annoying.

"Your scientists were so preoccupied with whether or not they could, they didn’t stop to think if they should"

Still too many words in my opinion. It's really just 2 things.

1. Search: The server publishes its tools via a query interface and with gradual level of detail. This way an LLM can discover the tools it needs without loading the ones it doesn't into context. Saves context.

2. The LLM sends glue code when it needs to use multiple tools together. Said code gets executed by the MCP server itself, and it returns the result. Saves tool calls, which saves tokens.

On point 2: Imagine there's 2 tools in the server. One lists customers the other gives sales for a given customer. For a task like "add all the sales for the customers whose name begin with A".

With traditional MCP: the LLM has to use the MCP like a regular HTTP API: first get the customers (1 tool call). Then for every customer begining with A, get their sales (N tool cals). Then add all of the sales (potentially 1 tool call).

With code mode the LLM sends a single program. The program has code that does things like `customers = call_tool("get_customers"); for each c in customers do if customer.name.begins_with("A") then ...` etc etc. That code is sent to the server for execution. So for the LLM it counts as a single tool call.

On the downside, the "code execution" on the Server means that it is executing untrusted code coming directly from LLMs. In order to offer this confidently your MCP servers really needs a very tight sandbox in which to execute this "glue code".

That is just your opinion, not a general rule. In my opinion.

Well they will start caring when their teen with image issues starts getting targetted beauty ads[1], or when they get pregnant, want to abort, and get directed to an anti-abortion center instead[2], and afterwards they get served "abortion reversal pills" ads[3].

Or when they are hit by any other privacy fuckup like that.

[1] https://futurism.com/facebook-beauty-targeted-ads [2] https://www.bbc.com/news/health-61320202 [3] https://tech.yahoo.com/general/articles/facebook-made-money-...

Oh Meta not giving a damn about privacy and security? Say it ain't so.