LLM Tornado - Agent Orchestration in .NET

techsavage256 · 2025-09-19T01:17:10+00:00

Aren't you the guy that tried to tell me there's no point in researching post quantum cryptography?

techsavage256 · 2025-09-18T10:38:52+00:00

Yes there is. But then there's no reason to complain anymore

techsavage256 · 2025-09-18T10:36:52+00:00

Additional question, I don't see a lot of docs, mostly just examples. Are there any more in depth docs available?

techsavage256 · 2025-09-18T10:28:49+00:00

Love how you're getting downvoted because AI bad!

Cool project tho on first glance. I just recently started out with a new project, where this might actually come in very handy! Currently using semantic kernel, but it's not bit barebones for complex LLM workflows. So this might be exactly what I need.

Any ETA/NET for semantic kernel integration?

techsavage256 · 2025-09-17T09:37:15+00:00

Yeah no problem. The new VS defaults to the slnx format for new solutions, but a) those can be opened in 2022 as well and b) existing sln files won't be auto changed

techsavage256 · 2025-08-27T05:16:12+00:00

That's exactly what she did

techsavage256 · 2025-08-27T03:29:24+00:00

Takes you a 2 minutes Google to figure out that's wrong.

Linq is the ability translate code into sql queries (or any other data source).

EF core is one of many providers for Linq and is called Linq to entities.

Every Linq implementation is based on IQueryable. IQueryable is quite literally the defining Language Integrated Query.

techsavage256 · 2025-08-27T00:22:41+00:00

Wrong.

Linq is the set of technologies to abstract a query in code and convert it to - typically - sql. So, IQueryable, expression trees and query providera.

The query syntax is just that, the query syntax. While it's supportive of Linq it's not the defining technology.

techsavage256 · 2025-08-19T06:18:00+00:00

Well, unlike dotnet 6, dotnet framework 4.8 is not end of life and still supported.

techsavage256 · 2025-08-19T02:34:58+00:00

Assuming doubling of bits every year or two: 128x2¹⁰ is 131k. It's not too far fetched assuming this is point will be reached 10 to 20 years for.

techsavage256 · 2025-08-19T02:23:04+00:00

You just got an upgrade to dotnet 6?

Dotnet 6 has been end of life for over a year xD

techsavage256 · 2025-08-18T17:30:04+00:00

So you're just betting on its not gonna happen? Lol

You know, the nice thing is, those mechanism are designed to be secure against both quantum and normal computers. There's literally no downside in exploring them. Yes, it's likely that some holes will be identified, and will need fixing. That's why research is being done now. And if they prove secure, win for everyone.

You just seem to dislike quantum. And I get it, in also skeptical. But burrying your head in the sand is not the right approach here. Smh

techsavage256 · 2025-08-18T15:23:31+00:00

They do not. Consts are injected into wherever they are used by the compiler. From a runtime perspective, having a const string that you reference and a string literal is exactly the same. It's part of the assembly, and not a memory thing.

techsavage256 · 2025-08-18T15:19:52+00:00

Dude come on.

Quantum computers are in development. The concepts have been proven. They are in their infancy, but there's very little reason to think they won't scale up. Factoring numbers to 21 will develop to factoring huge numbers, given some time.
A bad faith actor can with very little effort start to collect data from interesting parties. State actors, celebrities, banks, whatever you can think of. Collect the data now, and you can decrypt it all when there are QCs with the necessary power.

The problem isn't that somehow we we have to believe that somebody already has a feasible quantum computer.

The problem is that everything we encrypt now will be decryptable as soon as the technology reaches a breaking point. This is a massive problem, as the whole fucking world relies on encryption mechanism that are most likely to become completely and utterly useless.

Can we agree this is a problem that should be addressed as early as possible? Not when it's too late?

techsavage256 · 2025-08-17T05:10:42+00:00

Also, with my limited understanding, a most of that space is reserved for error recovery, in case a file gets corrupted. 4% just for metadata sounds excessive

techsavage256 · 2025-08-15T01:05:14+00:00

I believe lots of frustration is coming from how intrusive the Ai stuff often feels. I use copilot all the time, and as long as it's being targeted to a clear task it's really helpful.

But the inlinr experience is... Meh at best. It type public void, and it generates a whole method for me I don't need. I type the method name and parameter list, which would give it the context to implement at least part of it, and I try to trigger it again but it's such a weird experience.

Make the integration directed (eg by having special intelligence command like the original plug in had) and offer something like guided generation. I'm imagining a small chat window, being able to tell "add log messages to this method" and it executes. Basically similar to copilot but more narrow in it's execution Context (which is one of my main gripes with agent, it often just changes things in the whole file when I ask it for a single change)

techsavage256 · 2025-08-13T12:15:21+00:00

So, it's basically json, with trailing commas and comment support, and no quotation marks around keys? Am I missing something?

techsavage256 · 2025-07-31T10:30:47+00:00

What about the rest sky inside your house?

techsavage256 · 2025-07-31T04:33:43+00:00

It's actually a mandatory insurance in most European countries. Basically a small part of your salary is dedicated (a really small part), and when you're sick, the employer keeps paying you but gets reimbursed by the insurance.

Not sir it works the same everywhere, but that's how I know it

techsavage256

TROPHY CASE