chrsig

i just hope for a sufficiently smart compiler shrug (i'm pretty sure go has some autovectorization)

before jumping to another language, I suggest perhaps examine the memory layout and access patterns.

ok, that seems like a bit of a moved goal post, but you do you.

is there any particular impact you see that having? Postgres has had it's share of data integrity issues due to things like locale differences between primary and replica, where strings would get sorted differently.

I'm not advocating for one over the other. I love both, but neither are perfect.

https://www.citusdata.com/blog/2020/12/12/dont-let-collation...

https://wiki.postgresql.org/wiki/Todo:ICU

On the flip side, sqlite is also a great choice in those circumstances. so regardless of attitude, outcome seems good to me.

incredibly well tested for scenarios where data loss is likely, code is in the public domain, available on all major operating systems, included in language standard libraries... it's one of the most ubiquitous pieces of software out there.

no, it just tends to need to be a violent offense

well, one major problem is that you can't force people to get mental health treatment. the courts can, but that means things need to be brought before a judge.

i don't read that as a condemnation of usefulness of integrating w/ the system tzdb (every language stdlib does this under the hood)

my biggest issue is that the structs and function definitions are pretty opaquely named and make it very hard to learn let alone teach newcomers.

eh, i think i disagree. a new stdlib on its own wouldn't come with a lot of abi/linking baggage that tends to hold up tooling and migrations when you start introducing a different language. (see recent rust/linux drama).

i mean, if the committee members can make it happen or not, i don't know. but it's still a worthy thing to explore, I think. there's going to be a lot of C code that will need a very gradual migration path to safer apis for a very very long time.

> For clarity, tree-wide fixes for C in the kernel are automated via Coccinelle. Coccinelle for Rust is constantly unstable and broken which is why manual fixes are required. Does this help to explain the burden that C developers are facing because of Rust and how it is in addition to their existing workloads?

Yes actually, I really wish someone would bring that sort of thing to the forefront, because that's a great spot to welcome new contributors.

I'm a bit out of my depth, but I think I recall Gerald Sussman talking about dealing with a similar problem using an operator that indicated that evaluated to exactly one out of a finite set of elements but can be evaluated to any in the set.

If I'm recalling, it was ok because each of the elements of the set were differentiable functions, but the operator produces a set of possible results, but doesn't specify which. Sort of like a monad, it seemed.

I want to say he was referring to a quadrature, but I honestly can't recall and wont be able to spare the time to hunt down the talk until later.

Coincidentally, I just got a copy of structure and interpretation of classical mechanics just the other day, so hopefully I'll get some more appreciation for the problem.

[0] https://mitpress.mit.edu/9780262553452/structure-and-interpr...

This is the first time I'm encountering Norton's dome, and I'm not particularly academic, just really like learning about math -- so I'm hoping a friendly HNer can help me out here.

Is norton's dome essentially describing a saddle point? Is the only reason it's nondeterministic because at that point things go to infinity? If we're in the world of mechanics, wouldn't it be up to the machine to determine what to do at that point? Implementation defined, one might say?

isn't the point of the chaos that as time progresses the predictability of outcomes severely deteriorates?

or maybe a better frame:

any simulation the seed would still result in the same answer, since the computation is deterministic, but the system being simulated is not likely to behave the same at that time under the same initial conditions.

I mean...you're kinda using sentimental anecdata to pat hn on the back a little bit here. There are definitely other explanations for sentiment change than being presented with facts.

if it's any consolation, when the sky isn't blue, it's mostly because the ground is on fire. a situation which is exacerbated by anthropogenic climate change.

so i mean, it's hard to agree on the basics when the basics are changing, I guess.

Also a pager/phone going off incessantly isn't useful either. manage your alarms or you'll be throwing your phone at a wall.

ouch, i didn't even know about that

eternal september; people new people are continually learning new strategies.

You're correct, the real issue comes down to

1. making sure those printf statements don't wind up in prod, spilling potentially sensitive data or corrupting a data stream

2. making sure that non-printf tooling is built so that only printf debugging isn't used

We tend to get caught up in false dichotomies.

nah, not crazy. it's pretty crazy to think that sort of shit doesn't happen.

I think it depends on who the documentation is intended for. I often let public facing documentation be the source of truth for expected behavior unless it's infeasible to coerce the system to that behavior. If the latter does occur, the documentation gets updated.

If the question is what does the software actually do, then of course the code, toolchain, and runtime are the authority.

I think they got the nature of intuition wrong. It seems intuitive to me that information shapes the intuition. Introverts (probably, on average) spend more time ingesting the information, in turn shaping intuition.

no, but they do make them normal.

It looks like he's staying on the committee and what not, just changing his day job. That's actually one of the benefits of having a committee & iso standardization process -- things aren't so reliant on a single engineer staying employed at a single company.

I'm sure it's never as clean a situation as anyone would like, but hey, world is a rough place sometimes.

> but C++ sings its siren von Neumann song to the wizards, and there will always be wizard musicologists who steer their projects toward those rocks and, when they have just enough wax in their ears, they sail right past the rocks and come out the other side of the straits leading the rest of the fleet.

beautiful, in equal parts true, sad, and endearing.

but also remember the vasa.

The other end of the spectrum has snakeoil salesmen grifting from town to town. It's a hard equilibrium to blance.

> One problem we discovered while running 1:1 coaching is that people weren’t able to actually follow through (in real life) on the ideas they came up with during their weekly sessions with their coach.

Really?

No, you did not discover this, it's quite predictable.

> since ADHD coaching is not reimbursed in the US, the price is hard for us to bring down because the largest cost component is the coach’s compensation.

Yeah, body doubling doesn't scale. The whole need for another human body thing is a real hurdle, huh?

> we’d love for you to check out coaching & body doubling and give us critical feedback.

Too much text with numbers too big. I already utilize body doubling the analog way, you've told me absolutely nothing about what on earth you're adding to the equation.

> While that may be true, isn't another reasonable explanation that the Copilot development team is moving as fast as they can and these sorts of workarounds are being forced through in the name of team velocity?

this strikes me as most likely. it is anti-competitive, but it's probably not their motive.

yeah, getting people to think through consequences is like pulling teeth.

also the puts are 5x as expensive as the get operations

it wouldn't be unprecedented. dynamodb-local exists.

> This is a ton of work to ask of a small group of volunteerss and leaves users vulnerable for longer.

Perhaps consider purchasing a support contract if people's charity endangers your users.

> I just don't reply to greetings coming from people I know aren't looking to talk to me to ask me how I've been.

Yep, it's in there with "please use the public channel rather than DMs".

Some nettiquite, please.

Of course, in the process of typing out their question, they usually find the answer on their own.