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

this "documentary" has already been on all national news in India for past 2-3 days, so this is not an example of Streisand effect. Most people who turn on TV once a day are aware of this.


Well, now everyone outside of India wants to watch it as well.


> Our government is run by monkeys

except the fine print is decided by bureaucrats, and not politicians themselves. your bias against the current government is blinding your logic.


Have you encountered any Indian bureaucrats recently? They are so far detached from technology and science it's hilarious. But they are very smart (cunning) in imitating whatever the ruling government is doing. So if government is trigger-banning everything, bureaucracy will do the same (and double down in most cases) without ever questioning it.


apple music is the best advert for spotify


been there with crows. they attack you for a month or so.


is this sarcasm?


this is the non-vandalized version of the doc if anyone's looking for it


It's really easy to shoot yourself in the foot by using global mutable variables. How do you guard against those when using gevent in production?


It's actually quite doable in gevent, because you have a guarantee that only one thread will ever be touching those variables ever. You can have 5 or 50 lines of code and be guaranteed that they will operate atomically, read their writes, be immune to interruption, all that good stuff... as long as they don't do any I/O. Of course, the difference from a platform like Node.js or asyncio (where every async/await yield must be explicit all the way down) is that one of your libraries calling `logger.info(...)` might cause I/O, and then cause an implicit yield to the event loop, and break your atomicity without you knowing about it. But if you don't log, and you just work in memory, with code you own or have audited to not do I/O, the sky's the limit. And you almost always want this kind of well-tested, non-logging, high-performance abstraction layer around global mutable state access anyways.


Global state isn't a problem for multithreaded code. State updates are the problem; it doesn't matter whether it's global or local.

If you can solve the local case, you can solve the global case. Pick your technique; any ol' technique is just as good as any other.


After a long search (5 years), finally happily settled with selfhosted miniflux.


So should I move it to docker? Since X11 socket will be shared, I'm assuming screen sharing might work


why would you miss apple music? spotify wipes the floor with apple music!?


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

Search: