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

People have a right to privacy. People should value that more, before it's all gone.

They have a right to privacy, but they don't have the right to your product.

If people have a right to privacy, why is it disappearing?

I'm not a heavy AI user but there are a couple of things I noticed trying to make copilot generate something for me from scratch.

The first is that having a single file with everything you have in mind is very useful. So I end up writing what the project is about, how the model is organized, what each button does, etc. This is good practice in general because writing down everything that the AI will have to consider forces you to consider edge cases before you program them. E.g. if you write "the detail pane shows the fields of the selected item," it makes you consider what should it show when there are no items, or if multiple selection is possible. As you can imagine, this file ends up a very long document even for a simple project because the goal is to pseudo-program everything and let the LLM translate it to an implementation.

Then it still gets things wrong about design, e.g. which pane goes left and which goes right, if you don't also provide an image that shows the layout.

And then, if you supply an exhausting amount of detail, the agent can generate more or less what you had in mind....... or rather, it can generate an OUTPUT that matches your specification from scratch.

The problem is that if there is something you failed to consider, and the AI makes an assumption there, you can end up with a fundamentally broken architecture that you will have to untangle yourself later. And at that point it's easier to write everything from scratch than to fix a pile of AI code that is based on a flawed design.

And it turns out that due to the "totem pole" way that software works, there are infinite places in code that a bad design decision can affect everything it touches.

A good example is how 2 components in a UI are bound to data. You can use events, a bus, state reactivity, etc. Personally I think the mediator pattern is the simplest way to handle GUIs. But an LLM is probably just going to use events for property bindings.


I don't think I have ever seen someone outside of tech saying this. It's always people working with the data-copying machines, never the people creating the data protected by the law, that want said laws gone.

LOL. I wish people could make good software that easy!

How would you make an application designed for creating Hollywood grade cinema easier? The fact Resolve isn't two orders of magnitude more complex is astounding to me!

Resolve is like a top of the line professional camera: there are so many more knobs, buttons, and dials on those because top-end pros run everything manually changing settings as they take photos based on changing light conditions and what the subject is doing. Resolve isn't going to assume what you want and do it: it's a professional tool for professional users. The fact they are still giving it away is amazing to me.


I don't know about recent versions, but I managed to install 18 on Linux Mint.

Making it run wasn't easy, and it can't decode MP3 and some video codecs because of licensing issues. It also can't decode WebM. This is kind of a problem because of a lot of free music you can download to add to videos and a lot of video clips you can download from Pexels for example are encoded with codecs it can't decode, so you have to re-encode it with FFMPEG first to a supported codec.


Kind of ridiculous, isn't it? Personally I think recommendation algorithms should be more powerful, customizable, and transparent. Currently they just make too many assumptions about the user without providing mechanisms to directly assign positive and negative weights to categories of content, which is what makes them unusable as a tool.

"Pog"

The first step is to actually make a better platform.

The problem with all the decentralized alternatives is that they sacrifice usability for decentralization and then almost nobody cares about decentralization so for most people it's only downsides.


You are conflating extremely different things, and that is dangerous.

Somehow we went from:

1. People can see and hear your in public

2. Therefore public places are not private

3. Therefore people can record you

4. Therefore it's okay to build a network of cameras that can track and query every place you have ever been

The problem has always been on step 2. The assumption that "public places are not private" anymore just because everyone can record you and post it on TikTok. In reality before smartphones public places were extremely private compared to being broadcast to the entire planet.


Why is it not going away?

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

Search: