postflopclarity

you are right one has to be careful to avoid the GC and dynamic dispatch, but if you do it can for sure reach the same level as C++. with tightly optimized Julia code there is little to no overhead over any other low-level language.

or maybe drivers should stop being reckless and dangerous

NOLA land sinking is also (in large part) due to human activity in draining the wetlands and swamps, so the dry soil starts compressing.

we can though? NOLA is sinking in large part because human activity has lowered the groundwater level by draining the swamps and wetlands, so the soil starts compressing.

correct. that number is a small fraction of the backlog. it's a big country.

my position has been steady since the start of my political consciousness (maybe ~12 years?)

all laws, including immigration laws, should be enforced consistently and universally, and without bias. and the laws should be changed to make it much simpler and easier to immigrate especially if you are able to already secure employment, housing, and health insurance.

US policy has also nearly completely eliminated the distinction, by making legal immigration close to impossible and ~arresting~ kidnapping people at courthouses who are there for their immigration hearings, then shipping them off to foreign torture camps.

the same is not true of gold.

it's more than that, because it's the one kind of wealth that has an (almost) completely inelastic supply

AI slop is often good at "reading fine" but the actual content is incoherent.

because it's AI slop

it's pretty easy to write basic trading api connectivity. the hard part is knowing what trades to send

even if we are very charitable and assume the comment refers only to like high-engineering-effort infra for trying to be super competitive on latency, that's still like the opposite of a durable edge, since everybody is looking at it. there's very little "hidden" knowledge and it's mostly a matter of elbow grease and careful engineering.

arbitrage is a rather overloaded word that people use for all kinds of strategies but yes, I predict most of the most profitable and consistent accounts are not actually attempting to forecast the outcome of these markets from first principles

it's only "better than human comments" if you have no idea what profitable trading looks like. it's a very-very thin mildly convincing veneer over what is fundamentally slop.

if you're not able to tell that OP's comment was AI slop, then you probably don't have much insight to contribute to the conversation either.

I'm not complaining "just" because it's AI.

I'm complaining because it's AI, and also slop.

> resolves into "cross-venue infrastructure" — which is also a more durable edge than within-venue alpha

anybody who actually trades knows that on these markets, "cross venue infrastructure" (aka vibe coding some exchange api integrations) is much less important / durable than actual alpha.

this comment was clearly written by AI. please don't do that.

> each side will think you're talking about the other side.

no. one side will say it, and think it. the other side will say it, but know they're lying.

now look at it measured from consumption per capita ...

> each side trying to imprison the other,

you're implying that the two sides are morally and legally equivalent, and both are just engaging in retaliatory squabbling. that is a ridiculous implication

one "side" routinely flaunts the law, steals from the public, abuses and ignores the courts, and has a complete disregard for civil rights, legal procedure, and credibility. it uses the DoJ as a personal henchman, stringing up frivolous charges targeted at political enemies.

the other "side" is trying to enforce the law.

I've found Julia is quite a nice target for AI coding agents

... yes. that's my point. the fable is not a good analogy in this context.

except that every time the boy cried wolf, there actually was a wolf and it ate some people, but then the people it didn't eat were like "idk what you're talking about, I'm doing just fine" and then plugged their ears.

> the 50th headline they’ve read on how we’re screwed today that hasn’t happened

the things are happening though.

e.g. if you read a headline in the 70s that said something like "ski seasons will shorten by an average of 1 day per year, leading to only 5 inches of snow water equivalent in Colorado resorts by 2026, and eliminating the economic viability of skiing in the northeast by 2060" that would have been completely correct.

> they decide what features are prioritized

this is not true; the other comment is wrong. there is no central body at all that "decides" what features are prioritized. features are simply worked on by whomever has the capacity, ability, and desire to do so.

many engineers at JuliaHub have all three of the capacity, ability, and desire to work on certain features because JuliaHub, in its capacity as a private business, pays them to do so. but with respect to Julia the programming language these are "just" third party contributions like any other.

the parent company is a consumer of Julia, and has no formal role in oversight or governance; they are of course invested in the success and performance of the language, but so are all other users!

this is exactly what julia does. boundschecks are default on, and there are compiler flags --- either locally, via the `@inbounds` macro, or globally with `--check-bounds=no`--- to disable them

high P/E means good income growth prospects. a good moat is one way to achieve that, but not the only way.

not true.

while I know it's only a secondary concern behind their primary business interests, I'm very excited to see how this might translate into increased support and activity on Julia itself!