ak39

The company with the widest moat. Unassailable. A virtual monopoly at this stage of the market data game. Is there even a market for "number 2"?

I felt ashamed because it fooled me into believing it had feelings like a living thing.

In order to simulate true human like intelligence, we have to simulate digital dopamine. Desire. Autonomous desire. Until then it’s still a clanker.

This is a great analogy, thanks.

That means folks using LLMs starting off with 300 bits KNOW that they lack the full payload of information to transfer to you. IOW, they know they need to transfer much more than 300, so they use LLM to fill those gaps. That's the crux of the slop universe out there. Folks are using LLMs for the 700 bits on top of their 300 bits and passing off the full 1000 bits as their own.

I echo the writer's sentiment. "I don't want to read the clanker's 700 bits. I want only your synthesis." (I can get the clanker to generate those 700 myself. Unless ... unless this whole LLM slop market is all about saving you the time to get an LLM to generate those 700!)

Using FF here, no such warning on my side. Likely your ISP?

Why hasn't anyone created a windows and mac client that git pushes changes to remote after file activities of local computer, and polls remote repo every 1 minute for changes to pull? I'd gladly pay for that. :-)

What is the point of any treaty with the current US administration which does not play by international laws? Rules and laws that the USA itself spearheaded after WW2.

"let them" in this use understood as: "let the while loop run indefinitely" as opposed to letting some autonomous robot decide for itself

Quite correct with that question.

I believe the universal answer is: incompetent malicious actors are now capable too. Which implies the pool from which to draw the intersection between capable and malicious has grown. (That's my reading)

This type of story about management getting rid of the old guard is so common and typical, it remains one of the most frustrating aspects of this industry.

In the “enterprise scene”, this sort of purge strategy is likely linked to a big percentage of money wasted and sometimes total failure.

Why do managers keep making this mistake? “Legacy” is only a bad word in IT. :-(

Thank you for this.

(I think HN should consider creating TLDR type of comments for upvoting separately from commentary. @Dan incentivise with different karma credits?)

I read "man months".

Off-topic: TIL wal2 mode in the works. Wow. That's a no-brainer feature, IMHO.

Is the 300x performance boost attributable to the threading model vs process model?

Was the code for the threading model written by hand or was it translated from the WIP threading model the human PG team is busy with as part of the 2028 roadmap?

Chuckled at the anti-climactic sentence ending! lol

Unlikely. It goes further by also using the word "exploit".

If they needed permissions for conversion, they'd have made a specific mention of that and thereafter confirmed legal ownership.

Genuine question: how did you figure this was AI generated? (If that is what you meant.)

Nice.

Is if a one thread per request model?

Does it support async await type of architecture?

By definition, a FK has to reference a PK in the “parent”.

Same

Shouldn't there be a unit test to confirm landlock is on/off? (I mean, this seems a crucial aspect of the code which needs 100% test coverage.)

Yip, this was impressive. Only a copy & paste into VSCode (Windows) revealed the rectangle around the "c" in the second line.

Impressive.

Thank you. Also, what database was in use?

Thanks for the easily understandable TLDR!

And here I thought Snowflake was for the data model!

Indeed. It's by no means "straightforward"

I didn't say we should ignore splits. To reiterate: most third-party data providers include splits by restating historical prices. This only works if you want to analyse performance at individual stock level by ignoring holdings. But if you want to do performance analysis for your own portfolio of stocks, relying on restated prices is incorrect.

Eg. If you bought say 10 stocks at the old price, you cannot take the restated historical price with your 10 stocks and you cannot take the units held of 10 stocks with the new prices. You have to account for this via transactions to increase your holdings (for splits) by leaving the prices historically the same.

Valuations are straightforward in a world without corporate actions like splits, consols, dividends etc.

Most (all?) data providers rerate historical prices after corporate actions that affect prices and this is not really the correct way to do continuous valuations using the restated prices.

ORMs and NoSQL were a direct result of the desire to have an object-oriented data worldview in a programming landscape dominated by OO languages. They were not introduced because programmers didn’t want to learn SQL (implying incompetence etc).

Node might not, but Javascript (even on the server) will mostly be.*

* assuming that the 100 years hyperbole is accepted