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

Techno-libertarianism is indeed the water we swim in. I enjoyed this academic-ish book on the topic that interrogates its positions. It shows how radical some of them are https://www.upress.umn.edu/9781517918149/cyberlibertarianism...


Why would you need to short it? If you believe that is true just go long on AI stocks or buy calls on these companies


Going long on AI stocks is fairly hard. OpenAI, Antrophic, and xAI are privately held, as are most of the robotics companies and companies. Companies like Amazon, Google, or Tesla might are sort of AI investments, but they are just subsidiaries or small fractions of the parent (Zoox, Waymo, FSD, etc).

This isn't quite like the dot-com era, with tons of pure play investment options avaialable, regardless of whether you want to go long or short.


Most people's opinion of Elon, good or bad, is directly informed by his Xeets


I think the point is that they are informed by MSM and reddit reporting on his tweets.


Correct. MSM+reddit reporting of Elon’s tweets is very different from his tweets themselves


It's a very idealistic way of looking at things. A more materialist analysis would posit cultural trappings are just cover for actions people want to do anyway like you allude to


John has a higher Christology in addition to what other people said


What if there are multiple processes that require access to a shared cache?


And I think this is the main use case they were looking for. If you have a web app where each request is a separate process/call (not uncommon), and you don’t have a good shared global state, Redis is a great tool. It is an in-memory data structure store that can respond to requests from different processes. I always considered it an evolution from memcached.

If you only have one long lived process or good global variable control, then it is much less appealing in the single-server scenario. Similarly, if you require access from multiple hosts, it becomes a less obvious choice (especially if you already have a database in the loop). And redis is also overkill is you’re using it only as a cache.


>shared cache

As in performance improvement - cache should never be considered a datastore, e.g. you can pull the plug and nothing else happens (aside losing performance). It'd be a lot more beneficial all the processes to have a local cache, themselves. The latter is at least 4 orders of magnitude faster than redis. Now you may like some partitioning, too.


The most frequently used words are almost all Germanic. There are a lot of technical words with Latin or Greek etymologies that are hardly used in quotidian conversation.


> quotidian

iswydt


Don’t bring Welsh into this. ;)


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

Search: