Readit NewsI currently use ChatGPT for random insights and discussions about a variety of topics. The memory is basically a grown context about me and my preferences and interests and ChatGPT uses it to tailor responses to my knowledge, so I could relate better.
This is for me far more natural and easier than either craft a default prompt preset or create each conversation individually, that would be way too much overhead to discuss random shower thoughts between real life stuff.
This is my use case and I discovered that this can be detrimental to specific questions and prompts and I see that it can be more beneficial to have careful written prompts each time. But my use case is really ad hoc usage without the time. At least for ChatGPT.
When coding, this fails fast. There regular context resets seem to be a more viable strategy.
(This obviously simplifies things, but ultimately we as humans still haven't found the one and only true philosophy or moral, and maybe that's not possible (I'm no philosopher))
I know iPhones aren't affordable for the layman in many countries. But for anyone with an option, why would you buy an Android? All the "customization" things I cared about when I was on Android are either doable on an iPhone now with better implementation, or something I don't care about.
I was a die-hard until I went through enough cycles of Google deprecating and reinventing their apps and services every year, breaking my workflow/habits, that I got sick of them and moved to Apple everything. And all the changes I've seen since then are only making me happier I got out of the ecosystem when I did. Unlimited Google Photos backups with Pixels are gone, Google Play Music is gone, the free development/distribution environment is gone, etc.
If people can't even develop for the thing without going through the Google process, they're really just a shitty iOS knockoff.
But I still agree - if the benchmark was in memory, Stoolap might be optimized for speed. Sqlite is optimized for persistence, so you have to benchmark on disk and compare how it performs when writes fail.
I always considered it the best solution to have both: VPN encryption and TLS encryption over the VPN. Different OSI Layers. Different Attack Surfaces.
Not sure if that is a recommended pratice though (see initial remark ;) )
Is this related in anyway to your https://citrine-lang.org/ project? At a quick glance the syntax looks quite similar.
I can't tell if your comment is a joke or not.
Oh that is cool! Somehow I imagined that virtualization is more of a "modern" concept, but clearly that is naive thinking.
A form of virtualization was first demonstrated with IBM's CP-40 research system in 1967, then distributed via open source in CP/CMS in 1967–1972, and re-implemented in IBM's VM family from 1972 to the present. Each CP/CMS user was provided a simulated, stand-alone computer.
Source: https://en.wikipedia.org/wiki/Virtualization
Sometimes it feels like we don't have any actual innovation in CS anymore and it's all from pre 2000s and only made mainstream starting then.