`rmdir` is not `rm -rf`. It only removes empty directories.

slop is such a poorly defined term that it's very hard to answer your question meaningfully. Is all code generated by AI slop? Many different opinions on this and questions to be answered as LLMs continue to shift the programming landscape.

Having said that, you could have just clicked the link and found https://github.com/nordstjernen-web/nordstjernen/commits/mai... with a bunch of commits by claude. It took longer to write this than it took to figure out whether AI was used.

Yeah, why do you think I said it looks like AI slop?

I think this criticism is very poor. Claude is competent and well suited for implementing a web browser.

I took a look at the code, it showed the usual tells for slop, hence my question.

Claude is well suited for many things, it does not mean that it never is used to generate slop.

Just read the linked Readme if you don't want to read the code, it's the usual slop.

As far as I'm concerned, it's a feature when the viewer controls the number of spaces per tab, it's a bug when someone else does (as is often the case online via css `tab-size`).

We may be getting off-topic, but I despise how LLMS made em-dashes a thing that people associate with slop posts.

it's because they were trained on lots of stolen fluff pieces in major publications, also part of why they have such an annoyingly positive tone

Can someone help confirm whether I understand correctly the semantics difference between the final-line eval of

    x^

vs.

    x*

?

It seems like either one evaluates the contents of the `box`, and would only make a difference if you tried to use `x` afterwards? Essentially if you final-line eval `x^` and then decide you want to continue that snippet, you can't use `x` anymore because it's been moved. Awkwardly, it also hasn't been assigned so I'm not sure the box is accessible anymore?

> It seems like either one evaluates the contents of the `box`, and would only make a difference if you tried to use `x` afterwards?

More or less. x^ moves the whole box whereas x* copies the contents of the box.

> Awkwardly, it also hasn't been assigned so I'm not sure the box is accessible anymore?

Yes, if you move something and don't assign it then it gets dropped, same as rust.

Great, thanks for the clarification!

> holds my place

can you give an example of what you mean and how you might expect it to be achieved with a reloaded diff? otherwise `while true; git diff --color=always |less -r; done` gets you most of the way to what you are asking for

Realistically, I will be reviewing a diff, see a hunk I don’t like, change it, and want to see the change back in less. So saving my scroll offset would accomplish my goal. I guess I should add that I want to be able to quit as well?

Like I said, fzf does this. Bind a key to an action that effectively changes the file from stdin to a different command that it runs, while preserving view state.

Thanks for sharing!

> Before writing any code, I spent time on detailed specs, an architecture doc, and a style guide. All public: https://github.com/brightbeanxyz/brightbean-studio/tree/main...

> It took me tho 4 full days to get the specs to the level I was happy with.

When I click on history there I see only a single commit for these docs. Would you be willing to share some or all of the conversation you had with the LLM (in a gist or in the repo) that led to these architecture docs? Understand if you can't, but I'm sure it would be super instructive for people trying to understand the process of doing something like this and the types of guide rails that help to move the process forward productively.

Most likely the (legally) correct thing to do in the US is to first report the landlord to the relevant agency, possibly named something like Licensing and Inspections or Fair Housing or somesuch. Each local jurisdiction will have it's own agencies for this, so do research. Failure to respond to that would next involve a landlord-tenant lawyer.

Whether or not it's worth all the trouble and time is a different matter. For most people, I'd say reporting to relevant authorities to make the landlord's life harder without needing much continuing effort is probably worth doing, but the lawsuit side is likely to be a huge time and money sink and it's almost always easier to just move. Let the city sue them for continuing to accrue complaints of unsafe living conditions.

In the same way, a landlord cannot evict you themself if you just fail to pay rent, but there are multiple legal mechanisms to eventually get the sheriff to do it for them. Basically, if landlord-tenant negotiation fails, I think the only legal recourse is to involve governmental third parties unless you technically open yourself up to legal reprisal.

No. MIDI controllers have their place, but many people work without one, or only use one for live performances. There are often also way more knobs in the various FX chains in a DAW than you would reasonably want to map to a controller, but still want to touch at least a few times while making a song.

Knobs are confusing when converted to a mouse paradigm because there can be a few strategies to control them (click+drag up/down, click+drag right/left, weird rotational things, etc), and you have to guess since each FX studio and software may implement it just a little different.

For the sake of easy reference, I'll leave the relevant snippet from the linked article so people can decide for themselves with a bit more information:

> Another important note - some binary blobs and other non-free software components are used today in PebbleOS and the Pebble mobile app (ex: the heart rate sensor on PT2 , Memfault library, and others). Optional non-free web services, like Wispr-flow API speech recognizer, are also used. These non-free software components are not required - you can compile and run Pebble watch software without them. This will always be the case. More non-free software components may appear in our software in the future. The core Pebble watch software stack (everything you need to use your Pebble watch) will always be open source.