4,245 karma · joined December 27, 2011
And putting captchas or logins on anything you have to protect from bots also "protects" from real people, most of them simply leave and don't bother with those thing.
export LANG=C
(obviously in both cases with prewarmed filesystem cache)You are giving a centralized 3rd party identifying information about you because of the subscription, control over your passwords because of the updates and you have to believe and trust it's never going to deny you access even without payment, issue an update to steal those passwords or be hacked by someone who does the same or hacks you through it. Oh, and they can do all the surveillance capitalism business models since they have access to the websites you visit.
This is purely ideological assertion that just excuses predatory behavior. Surplus capital does not enable innovation whatsoever.
Innovation is more like quality, it is habitual and cultural. Give all the right people an opportunity to apply themselves and you get innovation and, of course, give everyone a chance to become the right people, to raise their children that way, educate them the right way, not indoctrinate, etc. The role of capital and startups here is not creating such people, but that of wealth and power: to take ownership of future innovations that could be created by such people and remain wealthy and powerful.
[1] https://github.com/scylladb/seastar/wiki/Memcached-Benchmark
This is not as useful as you think. In nginx you only need a couple of extra lines of configuration to let an external program issue and renew certificates independently from nginx, without reloads, etc. Definitely not worth developing a C nginx module that starts a helper process that does that just so that a few people who run nginx on a single server could get their certificates issued with only one line of configuration.
That cell harming people you want to imagine would be some other government agency acting as part of a covert operation after a long time of planning and preparation, with plenty of spies deep in the government. And they don't actually harm people all that much, not the point, they do just a few acts of terror with a few deaths for war propaganda. But once they are caught on surveillance it's already too late, it means they are ready to approach the head of police and start using serious military weapons, and plenty of people are already on the wrong side of war propaganda.
> where sufficiently-organized individuals use modern technology to harm innocent people and government cannot stop them
Such things don't really happen anymore, governments are too authoritarian already and really like their monopoly on harming people. The only way sufficiently-organized people can coexist with the government is for them to subvert law enforcement or to originate from law enforcement. Governments can deal with either case by replacing everyone or by letting them have their corruption in exchange for being loyal to the government.
Basically surveillance is not the tool for anything you talk about, it's role is the exact opposite: to keep people from disobeying the government, the ruling class, the whole systems, no matter how much harm they do to the people.
That would be actors or processes communicating with each other, not a collaborative multi-threaded process.
Real world has pretty much no natural notion of threads, only of actors.
There are some broken ideas out there that mix different concurrency models, in particular async programming with shared memory multithreading, not realizing they are bounding themselves to the lowest common denominator, but I was never talking about any of them.
That's backwards. Rich megacorps are the ones that should be pressured to change their behavior, not individuals.
Plus the full Apple experience is just about getting your money, it's not actually better than the full Linux experience or the full Windows experience.
That's not true. In event loops to do cancellation you simply remove event handlers for associated client from whatever event notification mechanism you are using and delete (free) client's data structured, including futures, promises or whatever you are using. Since references to all of them are necessary for event loops to be able to even call event handlers, no awareness of any of it on event handlers' side is required.
How so? Growing children can probably handle a lot more junk food and sugar without any consequences than adults.
The assumption here is likely that read-only mapped pages of libpng could be shared across different running programs that link with it. But it ignores all the extra read-write pages as a consequence of dynamic linking and that there is basically just libc that is shared across different running programs. So it's mostly wrong, you can probably even reduce memory usage by switching to static linking.
Not necessarily. It's just free webservers don't bother dealing with it, but there are plenty of simple approaches. Like just dropping connections that are sending requests slower than some threshold or dropping the slowest connection when some total number of connections is reached. Or more complicated, which also works to protect from all kinds of attacks, dropping the highest malicious score or the lowest reputation score client when some resource usage threshold is reached.
None of these are easy to implement with synchronous multithreaded networking code though, like in Go. Realistically it's only viable with asynchronous single threaded programming models or an actor model.
The same way reimplementing Chromium in Firefox can't fix anything.