theowaway213456

This feels like a suboptimal solution to me because I personally like to keep comments in "unresolved" state so that they remain visible and other folks can weigh in on them if they want, but in a way that doesn't block the PR. Basically I wish that GitHub would either separate the "collapsed" and "resolved" concepts, or add this "approve without merging" button.

Yup. No matter how much you tell it to keep things simple, modular, crisp, whatever, it generates tons of garbage much too often.

lol after reading your first sentence I literally thought to myself "this sounds like the type of person who never closes their browser tabs"

In my experience, this mistake happens all the time for native English speakers born in the US.

If we're allowed to make modifications here then it should really be lose => looze and loose => luce

I 100% understand why you are using a subscription-based model. It makes sense, and I agree it's the most honest model given that you have to continually support it and you don't want to have to either over-promise on extended support, and offer refunds if you can't fulfill that promise.

I just hate managing subscriptions.

If you gave me the option to require manual subscription renewal, rather than auto-renewal, I would 100% buy this right now. Basically allow me to purchase for 1 year then click a button to confirm that I'm still getting value out of the product. If I don't click that button then you should assume I'm no longer interested and cancel my subscription.

(I don't like using my mac but sometimes I have to use it for work, and I wish I had this.)

Sorry, my attention started drifting when you said "epistolary."

In other words, it requires a tremendous amount of effort to fully communicate your tastes to the AI. Not everybody wants to expend the time or mental effort doing this! (Once we have more direct brain/computer interfaces, this effort will go down, but I expect it will not be eliminated fully)

Feels like AI generated market research. There must be a single company/person putting out these posts because I see a ton of posts like this following a similar structure

Anyone else feel like this post is AI generated? I've been seeing a lot of posts like this on reddit programming subs and now it's happening on HN too... The pattern is:

- some generic context, containing a bunch of em dashes of course, with a vague background that isn't tied to a specific incident

- a claim like "most ___ I've talked to about this" within the first few sentences.

- ends with a series of questions as though they're soliciting more input

I feel like these all must be coming from a single person who's trying to automate market research and sell the data or something

Five years ago, I would've loved this. I love the simplicity and power of good old Make. And I obsess over my workstation's configuration. I used to have a massive bash script I would use to reprovision my workstation after every clean upgrade of Ubuntu.

But these days, I just tell codex to install things for me. I basically use it as a universal package manager. It's more reliable honestly than trying to keep up to date with "what's the current recommended way to install this package?"

I also have it keep a list of packages I have installed, which is synced to GitHub every time the list changes.

This is my impression as well. ClickHouse has tons of useful features built in that seem like they'd work well here. Though the documentation about those features has been very scattered and hard to find in my experience

> table names, columns, virtual columns

This sounds solvable with clickhouse views?

> automatic joins

Is this also not solvable with views? Also, clickhouse heavily discourages joins so I wonder how often this winds up being beneficial? For us, we only ever join against tenant metadata (i.e. resolving ID to name)

> query optimization

This sounds potentially interesting - clickhouse's query optimizer is not great IME, but it's definitely getting better

Are there any good, non-tiling window managers that support tabs? (I struggle with tiling ones like i3 because I am a small-brained mouse user)

This is a pretty cool idea. Kind of a neat distribution hack if all you have is a TUI (and not a full GUI). Curious whether you know of any success stories yet

Thumbnails are not even needed - they can just use a plain old img tag in the readme with an external src.

em dash + "x rather than y" sentence construction is setting off my brain's LLM detector here.

Same, doesn't render well on Android/Chrome either.

Yeah, that's the intent. It's why I listed several options

Here's a (flawed) thought experiment: imagine that 100% of customers' RAM suddenly goes faulty at the same time, and RAM prices have suddenly skyrocketed to infinity at the same time.

Which outcome is ideal? Which one is morally correct?

(A) the retailer refunds every customer, loses all of their profits and probably goes bankrupt

(B) the retailer is forced to go into massive debt in order to replace everyone's RAM, and may not recover from the debt, and may face legal consequences if they can't replace the RAM

(C) in the first place, the retailer should have been required to have a backup RAM stick for everyone that purchases the RAM, so that they are able to issue replacements if necessary, plus extra in case the replacements themselves are faulty. As a result, RAM prices before this incident were well over 2X the real manufacturing cost, in order to cover this "backup" cost (manufacturing, storage, etc.)

(D) something else?

(This is a much more extreme version of what actually happened, but maybe instructive to think about)

I anticipated this problem and increased the BPM to get through it in about 30s to see if it'd be worth the time haha.

You can tunnel a port over SSH and get a web UI locally, though it's not commonly done. I feel like more people would actually do this if tunneling a port was just ever so slightly easier (like, you're already SSH'd into a box, then you run a command, then you somehow automatically get a tunnel for that command's UI port plus a local browser window open to the page)

Agreed - I just can't get excited about the world's fastest CPU core running on the world's most locked-down and developer-unfriendly OS.

I'm not a PL expert but isn't building a decent JIT a massive undertaking? I guess you're saying that the JIT itself would be what makes a project like this worth using in the first place?

I am confused for the same reason you are. Isn't the rust code just "pre-jitted" code essentially? i.e. hand optimized. You are going to want to hand-optimize some functions in cases where the jit cannot do a good job in its current form. You probably also want a benchmarking system where you compare the jitted code to the hand optimized code, to prove to yourself that the hand optimized code is still worth keeping, after any automatic jit improvements you make. And if you don't want the runtime overhead of the jit then you can pre-jit certain functions and distribute them as part of the binary's executable code

The evidence suggests that XML was never that popular though for the general audience, you have to admit.

For Web markup, as an industry we tried XHTML (HTML that was strictly XML) for a while, and that didn't stick, and now we have HTML5 which is much more lenient as it doesn't even require closing tags in some cases.

For data exchange, people vastly prefer JSON as an exchange format for its simplicity, or protobuf and friends for their efficiency.

As a configuration format, it has been vastly overtaken by YAML, TOML, and INI, due to their content-forward syntax.

Having said all this I know there are some popular tools that use XML like ClickHouse, Apple's launchd, ROS, etc. but these are relatively niche compared to (e.g.) HTML

.git/info/exclude is mentioned in the first section (about .gitignore)

> Unless you think they secretly run it which is a conspiracy

tbh this doesn't sound like a conspiracy to me at all. There's no reason why they couldn't have an internal subsystem in their product which detects math problems and hands off the token generation to an intermediate, more optimized Rust program or something, which does math on the cheap instead of burning massive amounts of GPU resources. This would just be a basic cost optimization that would make their models both more effective and cheaper. And there's no reason why they would need to document this in their API docs, because they don't document any other internal details of the model.

I'm not saying they actually do this, but I think it's totally reasonable to think that they would, and it would not surprise me at all if they did.

Let's not get hung up on the "conspiracy" thing though - the whole point is that these models are closed source and therefore we don't know what we are actually testing when we run these "experiments". It could be a pure LLM or it could be a hybrid LLM + classical reasoning system. We don't know.

Bazel as well.