My friends and I didn't have hard drives. But maybe we were just poor. But fair, you could infect another disk if you just switched disks. No need to have both connected at the same time.
Even then, what would that accomplish in most systems? That same disk would most likely be the only permanent storage available to the system when it's inserted. Maybe if you've got two drives and have two floppies inserted at the same time?
If it gets outdated they can review their policy. Right now it is sensible. We're at early ages of this type of AI and we don't know what the end game will be.
Someone forking it and makeing it better with AI is a possibility. If that happens will know it was better for the project for the maintainers to just review the code. If that happens, they can probably become maintainers in the fork. Or maybe they don't like that work and could just go do something else
I don't know if I want to create an ad-hoc list of permissions. What I would like would be something like take a snapshot of my current workspace in a VM. Run claude there and let it go wild. After the end of the session, kill the box. The only downside is potentially syncing the claude sessions/projects. But I don't think that'd be too difficult.
In the UK we move forward at 1am and they go backward at 2am. Doing it at midnight adds the extra complexity that now the day is different. Doing it in the early morning doesn't change the day.
My guess is that in the US they do the same but shifted by one.
It's hard to pin point what creativity is. But in your example, the more creative thing was really coming up with the scenario of pigeons selling balconies as real state. What followed was just applying usual tropes for that sort of joke on the subject matter. I feel like LLMs are not very good at coming up with something novel. I'm not even sure they are capable of that. It's not as if coming up with something novel is easy for humans either.
Regardless the etymology of the word phone, nowadays calling and sending sms is not the main usage of the device. Most people only make calls on emergencies only. In fact, calling when you don’t need something urgently is often considered rude. Anyway, that can also be done with FaceTime, WhatsApp, telegram, Skype, etc. Internet is far more important. When people make contracts with carriers most often than not they choose it based on the data and not minutes or sms. If you pay attention to ads by the carriers you’ll see that data is always the highlight, that’s what phones are actually used for these days.
That may be, but I suspect most users expect a browser, a way to message friends (whatsapp or telegram in most western countries) and a maps app. Games are popular too. Being able to call and send SMS is secondary. I think not having a good maps is a big issue, hopefully they'll be able to patch that eventually. Until then, maybe google maps is not too bad on the mobile browser?
Hm, yeah, I think a key-value store would be easier to implement. I haven't looked at redis for some time now, but last time I did, persistence was done through snapshotting and everything would really be loaded into memory at start time. So that wouldn't work for this use case, where all you can do is serve a static file.
But my question revolves around databases assuming that the disk they access is local or at least a fast network storage. I wonder if there are any databases optimized to access slow storage over low bandwidth, where you're really trying to optimize the amount of data read more than anything else.
Very clever. I wonder if there are databases optimised for this use case. I can imagine something that always requires indexes to do the queries and stores data in disk in ways to make it easy to fetch only the bits you need.
Interesting. A good book is very efficient at teaching you how to think in that particular language, rather than translating the ideas you have in another language into the new language. How do you learn that with your method? It sounds to me that it would require a long time programming in the new language to come to the same realisations by yourself.