dfajgljsldkjag

It is very important that we treat the natural world like data that needs a backup. The environment changes so fast that we will lose the history of these plants if we do not save them in a digital format. This collection gives us a way to check the past against the future so we can see what has been lost.

I think we try too hard to solve problems that we do not even have yet. It is much better to build a simple system that is correct than a messy one that never stops. I see people writing bad code because they are afraid of the network breaking. We should just let the database do its job.

I really like that you used the live code components inside the documentation pages. The biggest problem we have in this industry is that the manual becomes wrong as soon as we update the software. If the documentation runs on the same code as the app then it will never be out of date. This is the only reliable way to keep the instructions accurate over time.

I see this happen all the time when people just want their new toys to work right away. They copy and paste commands from the internet to open up the connection but they forget to put a lock on the door. It is dangerous that so many people run these programs without understanding the basics of how networks work.

the chinese will probably figure out a way to sneak the nvidia chips around the sanctions

I always had trouble getting AIs such as ChatGPT to get out of their assistant mode and give natural and conversational replies. No matter what I put in the system instructions it always responds with the same old walls of text and same old it's x not y etc.

Does this one have a prompt that actually takes care of this problem? Does anyone have some nice prompts that make the ai actually useful as a practice partner?

Hello HN, I have an important thing to point out:

THIS EXTENSION DOES NOT WORK!

let me put it another way:

THIS EXTENSION DOES NOTHING USEFUL!

The author did not reverse engineer anything. He simply asked Claude Code to make this without testing or verifying any of the outputs.

The author did not check if the extension actually works. He simply asked Claude Code to make this without testing or verifying any of the outputs.

Other commenters in this thread have noted that this extension cannot do what it claims. [1] The author simply asked Claude Code to make this without testing or verifying any of the outputs.

Thanks for listening to my ted talk.

1: https://news.ycombinator.com/item?id=46803836

This looks like it will help a lot of students and families who are on a budget. If you can just plug your phone into a screen you do not need to buy a separate laptop anymore. The browser extensions are the most important part because that is what makes a computer useful. I am glad to see they are thinking about this.

I have fixed many broken systems that used redis for small tasks. It is much better to put the jobs in the database we already have. This makes the code easier to manage and we have fewer things to worry about. I hope more teams start doing this to save time.

It's interesting that the AI tool just writes react rather than creating a figma drawing. All that training on writing code has made it easier for AI to just write the app than make an illustration of it.

These were neat to use at whole foods but I never saw them anywhere else. I guess Amazon just didn't really have much penetration in payment terminals in general. Maybe a deal with clover or toast could have changed things.

It is very sad that we are ignoring the lessons we learned about security twenty years ago just because we want new toys. We spent so much time making sure that user input could not change how a program runs and now we are doing the exact opposite. The video is right that the problem is not a bug in the code but a flaw in how the whole system thinks. We are building a house on sand.

I like Whole Foods because it feels warm and the food looks good. The Amazon stores felt like walking inside a vending machine and that is not how people want to buy dinner.

It is worrying to see a major vendor release code that does not actually work just to sell a new product. When companies pretend that complex engineering is easy it makes it very hard for the rest of us to explain why building safe software takes time. This kind of behavior erodes the trust that we place in their platform.

The author is a healthy person but the computer program still gave him a failing grade of F. It is irresponsible for these companies to release broken tools that can cause so much fear in real people. They are treating serious medical advice like it is just a video game or a toy. Real users should not be the ones testing these dangerous products.

I always felt that the biggest problem with low code was the wall you hit when you tried to change something small. You had to fight the tool just to make the button look the way you wanted. AI gives you the speed of low code but allows you to build anything you can imagine. It makes sense to stop paying for tools that limit your freedom.

The term was coined then, but people have been doing it with claude code and cursor and copilot and other tools for longer. They just didn't have a word for it yet.

It creates a conflict to build a system that is both a private friend and a public performer. You cannot maximize intimacy and fame at the same time.

Complexity acts like a gate. When we make the code too hard to understand, we are telling regular people that they are not allowed to participate. True ownership of your data is only possible if you can actually afford to host it yourself. We should focus on making things simple enough for anyone to use.

Interesting. It appears this doesn't use AI itself (though it's probably vibe coded). Figma in dev mode already gives react components and css styles [1] and this seems like a more automated way to pull that functionality. It's unfortunate figma paywalls dev mode and this might be a good way to work around the limitation.

1: https://help.figma.com/hc/en-us/articles/15023124644247-Guid...

Each whatsapp user needs to enable the setting once to allow chats with multiple number of third party users.

It's better than nothing. If you have a different app and want to talk to your friend who uses whatsapp it's much easier to convince him to toggle a setting than to download a different app.

It is nice to see the multiple windows feature finally working. I have seen many projects fail because they could not handle the complexity of the modern web. This update shows that Servo is becoming a serious tool and not just an experiment. We need this to succeed to keep the internet healthy.

Certainly refactoring is better than a hack fix, but what I'm talking about is where the 10 line fix cleanly and fully addresses the bug, and the refactor is just thrown in anyways.

I've always known about algorithms that solve mazes, but never about actually making them. It's interesting seeing all these algorithms and how the mazes they generate look different.

Recently I've seen coworkers frequently turn what should be a <10 line bugfix into a 500+ line refactor across multiple files. I suspect it's due to AI.

There's a time and place for refactoring, but just fixing an isolated bug isn't it. But I've seen that often AI can't help itself from making changes you didn't ask for.

It requires a bit of tinkering, but I think pipecat is the way to go. You can plug in pretty much any STT/LLM/TTS you want and go. It definitely supports local models but its up to you to get your hands on those models.

Not sure if there's any turnkey setups that are preconfigured for local install where you can just press play and go though.

Last I heard E2E speech to speech models are still pretty weak. I've had pretty bad results from gpt-realtime and that's a proprietary model, I'm assuming open source is a bit behind.

Big if true. There's another article that seems to report more details, but it's paywalled. There's a summary here: https://old.reddit.com/r/LinusTechTips/comments/1qkae55/open...

The banned list proves that context matters more than having the newest tools. These features work well for small apps but they cause problems in a project this size.

I think it is beautiful how this cat is like a story passed down by people. The code is different every time but the feeling is the same. It shows that software can belong to everyone instead of just one company. That is how things should really be built.