Hacker Newsnew | past | comments | ask | show | jobs | submit | jmull's commentslogin

There’s a much less awkward way to keep a change log:

Keep a change log.


This is not without struggles. Many times the changelog updates are missed. You can try to catch this in code review, but that could also be missed. So you can try to automatically verify the changelog was updated, but you can't force that as a pass/fail check since not all changes require a user facing change. Or your project maintainers simply copy the commit message and paste it into the changelog, and at that point, why not just automate it with something like conventional commits?

Could/should the changelog be considered a first-class deliverable with care and attention provided? I think so, but I'm not in a position to exert direct control over that across dozens of repos and team members.


> Many times the changelog updates are missed.

In my experience, LLMs are great at reviewing changelogs for potential gaps from a user POV (and even creating draft changelogs wholesale, if you're backfilling) based on git history.


I 100% agree. I found https://keepachangelog.com/en/1.1.0/ as I was writing the article which advocates for exactly this!

We'd need a good definition of consciousness to get anywhere on this.

I suspect such a definition would include agency, which includes desires and goals for the self.

LLMs don't seem to have agency, and seem unlikely to get it since they are specifically engineered to do as told.

No doubt someone is trying, as we speak, to do just this. But I doubt the effort will be large -- LLMs are engineered to do as told because that's where the money is, and you need a lot of money to create LLMs, at least when doing anything novel.


Lots of discussions about consciousness yet no useful definition. All fall into one (or more) categories:

- not observable (feelings, agency etc)

- not useful (spiritual definitions, definitions that degrade into consciousness = being human/animal)


Agency is entirely observable.

How do you observe the ability to make decisions which action to take? You can observe that one does something, not that they could decide to do something.

LLMs do not have an unconscious, the negative dimension from which a subject can question what they. LLMs do not have desire because they are thoughts without a thinker. The problem is not LLMS but rather, that subjectivity itself is not popular in discussion. I suggest reading Freud, Lacan, Hegel for a start.

Regardless, the question still stands: "What does computers getting more intelligent has to do with it getting conscious?"

Just because consciousness emerged for we humans and other animals through one mechanism doesn't mean consciousness has/will/can emerge from current LLM technology.

For this extraordinary claim, I think the burden is firmly on those who are arguing that it has/will/can.


The other point of view is that the burden is on those who suggest that biological consciousness is somehow special. What makes it so, and if the answer isn’t metaphysical, what’s stopping us from constructing it artificially?

how is anyone supposed to decide if something is conscious if no one has the slightest idea what consciousness really is

I believe this is just about the behavior of std.debug.assert.

You can pretty easily have a different kind of assert that disappears in release builds (if you want).


It's in the article.

> you can implement your own version that internally checks a build-time flag, approximating C/C++ behavior


> That's an INSANE default.

I agree that not running arbitrary installation scripts is the right default, but it's just an incremental improvement.

The practical difference between code that runs at installation and code that runs when the package is executed is, very typically, a small amount of time.

IMO, the hyperbole here hurts because it distracts from more effective efforts.


> IMO, the hyperbole here hurts because it distracts from more effective efforts.

For example?


Can I just run npm update diff and see all changes across all updates compared to the last reviewed code in node_modules? Why not?

'course, software development itself is a domain.

A large, complex, unasked for PR is pretty likely pointless to throw at any serious project. (Well, it's pointless if your goal is to merge something.)

Working together is a two-way process. To land a big change, the bun people probably needed to have been working/coordinating with the zig people throughout. E.g., zig outright cannot accept PRs that break the language in unplanned ways and any conflicts with the roadmap would need to be resolved.

I would assume the bun people know all this. That makes it more of a publicity stunt than a serious attempt to contribute to zig, and we should probably all treat it that way.


Of course, and it is expected that large pull requests/RFCs are iterated on. I will not believe Bun seriously asked for a pull request to be merged with absolutely no expectation of back and forth discussion. But this isn’t what happened. The whole reason everyone thought it was rejected by Zig because Bun used LLM to generate it was because they responded in a way that someone would if they didn’t want a certain pull request accepted under any circumstances. Which is my point; it I just insane that their largest project submitted a pull request, and they just rejected it with prejudice, gave some statement saying the real and potentially fixable reasons why, then turn around and say we don’t want your help, we are doing this in house.

I don't really get the objection here. Who should make decisions about zig's roadmap, priorities, and approaches, the zig people or the bun people?

There's no value to iterating on a PR when the approach itself is not right.


My interpretation of what they said is closer to “we already improved compilation speeds by 4x and we did it without compromising our plans to go much further - also this PR introduces specific timing bugs.”

A key point to their success, highlighted in the article:

They had a strong understanding of exactly what zendesk was doing for them and how it integrated with their other stuff.

People hoping to do something similar should try to put themselves in a similar situation.


You missed a key detail: the NYC valuation system undervalues properties to the tune of around 10% of their actual market value. So your 6.5% tax is effectively aroubd a 0.65% tax against actual market value. That’s not bad (it’s a lot better than what I pay for my regular middle class home. Not in NYC, but I pay a bit shy of 2% annually)

The difference between "mostly true", "misleading", and "false" is context, and responses are specifically not allowed to include any context. Even "true" has a little context, since few things can be said to be absolutely true. "Unknown" also isn't allowed.

What's 2 + 2? The answer must be one of the colors of the rainbow.

(People can draw their own conclusions, but the only coherent reason I can think of for the design of this experiment is to generate a misleading conclusion.)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: