I hope grok4.7 will improve this even more.

This is, I suspect, a good thing. The article never states any downsides, other then nebulous claims. Yes, DNA is like finger printing someone, which is routinely done for arrests, but has the benefit of assisting in claims of family relations, which is at the heart of many ICE concerns.

Alternatively most blog posts could have been paragraphs. Most books could have been single chapters. Most newspaper articles could have been tweets.

That being said, most readers want you to hold your hand step by step. They don't want to the outline: they want you to give them a story. Most people and writers know this already. To me, it was new.

Comments URL: https://news.ycombinator.com/item?id=48947709

Points: 2

# Comments: 0

On the other hand, I specifically had grok try hard NOT to read a known key in the project dir (it only saw the first part using a tool, to verify it was present). So there's that.

I understand it can suck: but what is lacking isn't your technical demonstration (unless it is truly ground breaking), but your demonstration to clean up your own mess and be responsible.

I'm playing with a POC for a better wire protocol here: https://github.com/solidcoredata/pgwire4

I've been slopping together a POC to probe the edges of what can be done as just an extension. So far I have a framed protocol with inline cancellation, named parameters, out-of-query text language selector, ad-hoc pg/PLSQL execution with cache (no need for prepare), multiple result sets, streaming large results, and more flexible bulk upload.

In other words, with this extension you can query:

``` select * from T1; select * from T2; ```

And return them both in PG/PLSQL or straight SQL.

The existing pgwire3 protocol is one of the worst things to work with in postgresql.

So far, you think there is some universalism sentiment. You're wrong.

The Galaxy Brain isn't global usage, it is overlapping populations. Will any percentage of them care about any percentage of me?

Put another way, many people decided to effectively drop support for IE11. When my client has even a single client who still uses IE11, we don't drop support even when it is "bad to support it". But when that drops to zero, regardless of what anyone else is doing, then we can drop support for IE11.

That's exactly what you intended to do. That is the definition of advertising. It is true, many people might like it, so own it. Don't lie about it, even to yourself.

If the roadmap's "Web client and code review tools" could replace gerrit for me, this would be a easy switch.

Moreover, it looks like they designed both the mutable store and immutable store to be able to easily store their state directly on an s3 like system.

There are a number of features that would greatly speed up CI/CD system operations I belive.