Philip-J-Fry

Feels better to me in the sense that it doesn't try to be too clever. When I ask it to do things it actually generates code that a developer would write. That still lets me build software in layers like I do mentally. And it keeps you in control of where abstractions are.

Some people would say that you don't need this at all with the frontier llms. But when extending existing software or writing software that fits into an existing ecosystem, I find I still need to offer a lot of guidance. And it's better that the context window isn't flooded with code that was reverted after I looked at it.

9 hours is certainly excessive considering there's only 8 hours or less in a work day!

I think it's just a matter of what people want from a city builder. Some people play the game to build the city they wish they had. While others play the game to build the city they've already got.

The line is don't push your religion in your science content. Not a hard line to not cross.

Destin of Smarter Every Day went down the drain in my books as soon as he published a video about Flagella, and ended it by suggesting it could be intelligent design and told viewers to read a book authored by someone who is a staunch believer of intelligent design.

Crossed the line as a science Youtuber. You don't need to be athiest to be a scientist, and he definitely isn't. But you should at least know the line.

Finding out this site is basically just a copy of something that already existed and something they knew existed just further degrades my opinion of him. Especially with it being littered with ads. The ad literally takes up half my screen.

LLMs change the calculus on DRY in some cases. I would say it's still very much a no-no on the frontend side of things. Code repetition is directly correlated with bad loading performance. When you're optimising for people on slow mobile connections, your HTML/JS/CSS being 500KB instead of 1.5MB matters a lot.

The folding/unfolding animation is one of the coolest I've seen from a foldable. So slick.

Lets consider something like the right to take sick leave. There is no strict definition of what "sickness" is. It is something that YOU feel impacts your ability to work. Maybe a bad nights sleep, sore back, headache, runny nose, bad tummy, etc. There's no need to provide any amount of proof to an employer when taking a single day off sick, and they need to pay at least the statutory sick pay, many companies pay full.

Most people agree that this rule works well in practice. Most people don't take a sick day because they don't feel 100%, even when its within their rights. If everyone decided to take Monday off because they're sick, that would be possible within the law, there's no need to provide proof you're sick. Yet, if that happened, the country would grind to a halt.

Now ask yourself, how could you implement that without eroding someone's rights and without introducing more friction?

Sometimes, you just have to assume that people are honest and won't take the piss out of the system. Or you have to introduce friction to discourage the exercise of their rights. The friction for sick leave is that you usually have to notify your employer ASAP and that you may have to fill out a return to work form.

Never really a sound argument.

It's like having new solar panels installed every week. Sure you're "profitable" on the $0.20/kWh you're selling your "free" energy at when you ignore the cost of the solar panels you're buying every week.

That doesn't apply to a corporate travel portal. If you're on the portal, you're booking a business trip. You're not going to not book a trip because it takes 1 click too many.

Yeah, I know the benefits. There isn't a lot of data transferred though. The GitHub repo for this robot has design decisions on it so you can read their reasoning for themselves.

At the end of the day, it's an open source robot so someone can implement these protocols if they see the reason to.

Yeah but not any language.

JSONRPC can be trivially implemented in any language which can read/write a Unix socket. Which is any language worth using.

It's the trade off for performance and accessibility.

Because now you're locked into the Rust ecosystem.

JSONRPC over Unix sockets is a better interface for language agnostic IPC.

That's a completely different class of robot. The Beni robot is just a toy, it's just connect the app and drive it around, record videos and do some fancy tricks like flips. It is not meant to be a platform you program yourself.

The Microduck is meant to be a hacker toy. Train it yourself, write software, hack it, etc.

It depends what you're trying to get for your daughter. Is it something to get her into robotics? Then probably the Microduck is the way. If it's literally just a toy, then the Beni robot is better because that's literally all it is.

I open it to do the daily puzzles. But it means that I'm subject to 1 or 2 cringe posts before I get there.