truth_seeker

if you use them for long enoug tfor big project and conplex workflws, both of them have their own caveats.

Thats why i got irritated and wanted something thats scalable and lightweight.

https://github.com/corporatepiyush/yantra-coding-agent

1.mcp-memory : Persistent memory, a knowledge graph, code intelligence, and semantic search for LLM agents. Repo : https://github.com/corporatepiyush/mcp-memory

2.Secure Data Structures, Algorithms, Allocators, Thread Pools and Document parsing in C17. Repo : https://github.com/corporatepiyush/secure-c-lib

3. a coding agent that is cheaper, faster, more predictable, and dramatically more capable out of the box — because 584 of its 606 tools never touch a model at all. Repo : https://github.com/corporatepiyush/yantra-coding-agent

what really matters is :

how far can i get in X programming language by writing just idiomatic code?

how much of SDK and community libs, frameworks help me run my program at bare metal speed ?

What sort of change i have to do exisitng libs, frameworks and my legacy code for CPU, IO and memory efficiency as a migrate to new version ?

Even if TOP 250 npm packages are refactored through AI coding agent from security, performance and user friendly API point of view, the whole JS ecosystem will be in different shape.

Same is applicable for other language community, of course

The smart way to keep people passive and obedient is to strictly limit the spectrum of acceptable opinion, but allow very lively debate within that spectrum

All over the place, from the popular culture to the propaganda system, there is constant pressure to make people feel that they are helpless, that the only role they can have is to ratify decisions and to consume.

The whole educational and professional training system is a very elaborate filter, which just weeds out people who are too independent, and who think for themselves, and who don't know how to be submissive, and so on — because they're dysfunctional to the institutions.

If we don't believe in freedom of expression for people we despise, we don't believe in it at all.

― Noam Chomsky

Go is a reasonable compromise, very hard to ignore.

Bravo, such a well written article.

Feeling motivated enough to deep dive into .NET 10

https://www.scss.tcd.ie/jeremy.jones/CS4021/lockless.pdf

Downvotes to my comment proves Truth is offendig most of the time :)

cheers, anyway

THERE IS NO ALTERNATIVE TO ADOPTION OF THOUGHTFUL DESING AND PRINCIPLES.

For Java/JVM :

https://github.com/JCTools/JCTools

https://simonwillison.net/2025/Oct/15/csrf-in-go/

or at least Linter should catch this

https://golangci-lint.run/docs/linters/

False Sharing : "Pad for concurrent access: Separate goroutine data by cache lines"

This is worth adding in Go race detector's mechanism to warn developer

PostgreSQL Tuning further for this use case

- Reduce Page Size from 8KB to 4KB, great for write heavy operations and indexed reads. Needs to compile source with those flags, cant configure once installation is done.

- Increase Buffer cache

- Table partitioning for UNLOGGED Table which the author is using

- At connection session level, lower the transaction level from SERIALIZABLE

- The new UUID7 in PG 18 as a key might also help as primary indexed KEY type as it also supports range queries on timestamp

What a coincedence ! :)

Recently used MemorySegment in Java, it is extremely good. Just yesterday i implemented Map and List interface using MemorySegment as backing store for batch operations instead of using OpenHFT stuff.

Tried -XX:TLABSize before but wasnt getting the deserved performance.

Not sure about .NET though, havent used since last decade.

Note that the best-case scenario is the elimination of the overheads above to 0, which is at most ~10% in these particular benchmarks. Thus, it's helpful to consider the proportion of GC overhead eliminated relative to that 10% (so, 7% reduction means 70% GC overhead reduction).

Wow. amazing to see of off-heap allocation can be that good

https://go.googlesource.com/proposal/+/refs/heads/master/des...

On the topic of memory, with millions of particles the server barely breaks over 100mb

Although experimental as of now, but use of arena package is a natual fit here.

JSON Serialization, seriously ???

Why not "application/octet-stream" header and sending ArrayBuffer over the network ?

any reasons to use Java over Typescript, Go or Rust for server side programming?

Magic-RegExp aims to create a compiled away, type-safe, readable RegEx alternative that makes the process a lot easier. https://blog.logrocket.com/understanding-magic-regexp-regexp...

example from blog:

import { createRegExp, exactly, wordChar, oneOrMore, anyOf, } from "magic-regexp";

const regExp = createRegExp(

  exactly("http")

    .and(exactly("s").optionally())

    .and("://")

    .optionally()

    .and(exactly("www.").optionally())

    .and(oneOrMore(wordChar))

    .and(exactly("."))

    .and(anyOf("com", "org", "io")),

  ["g", "m", "i"]

console.log(regExp);

/(https?:\/\/)?(www\.)?\w+\.(com|org|io)/gmi

TLS servers now prefer the highest supported protocol version, even if it isn’t the client’s most preferred protocol version.

Both TLS clients and servers are now stricter in following the specifications and in rejecting off-spec behavior. Connections with compliant peers should be unaffected.

This is nice.

Are we on the same page ?

Whats really stopping you to parse and prioritise CUSTOM CONTEXT if given as text instruction in prompt engineering.

Agreed. but making ENGLISH or any human speakable language as main interface shoul be given highest priority IMHO !

Nah ! I am not convinced that context engineering is better (in the long trem) than prompt engineering. Context engineering is still complex and needs maintainance. Its much lower level than human level language.

Given that domain expertise of the problem statment, we can apply the same tactics in context engineering on higher level in prompt engineering.

You mean something like this:

https://www.npmjs.com/package/pkg

or perhaps this one:

https://www.npmjs.com/package/nexe

Compared to other programming languages, Rust's compiler and linters go a long way to implement best practices at build time.

Its areally great effort, but i would stick with PostgreSQL with PL/SQL procedure and tons of extensions.

Lowering down the TRSACTION LEVEL, Async transctions on disk backed tables and UNLOGGED Tables can help you go a long way.

Also, in next major version (v18) of PG, they are trying to implment io_uring support which will further drastically improve the random read/write performance.

wha about improving the compilation time ?

Without using SIMD CPU instructions, its gonna be super expensive.

Some like viterin/vek or kelindar/simd package could be helpful.