cdcfa78156ae5
Microsoft compromises the security and privacy of all of their online services, including Skype, Outlook.com, and Hotmail: https://www.theguardian.com/world/2013/jul/11/microsoft-nsa-...
A much better alternative is to give your money to independent telephony providers that run on, and support, Free Software: https://jmp.chat/
What I don't get is where these claims of faster development time come from. Toolkits like Qt make it way faster and easier to build UIs than trying to use HTML/CSS garbage.
When did it stop? comp.lang.* is still pretty active.
Cassandra and Redis just mean that you have a database-backed application. How do you schedule Python jobs? Either you build your own scheduler that pulls things out of the database, or you use an existing scheduler. I once worked on a Python system that scheduled tasks using Celery, used Redis for some synchronization flags, and Cassandra for the shared store (also for the main database). Building a custom scheduler for that system would have been a waste of time.
Here is an example of ESR being misogynist: http://esr.ibiblio.org/?p=6907
You cannot do it. The only way the right to distribute GPLv2 software gets revoked is for a specific party that distributes a GPLv2 licensed work in violation of the GPLv2 distribution terms.
That's a really glib dismissal of how hard the problem is. Python and node have pretty terrible support for building distributed systems. With Python, in practice most systems end up based on Celery, with huge long-running tasks. This configuration basically boils down to using Celery, and whatever queueing system it is running on, as a mainframe-style job control system.
The "shell scripts / xargs -P" mentioned by chubot is a better solution that is much easier to write, more efficient, requires no configuration, and has far fewer failure modes. That is because Unix shell scripting is really a job control language for running Unix processes in parallel and setting up I/O redirection between them.
I also agree that email should be a personal preference. I think that DFeed[1][2] shows how open discussion systems should be built. DFeed provides a unified discussion system that is simultaneously accessible through email, NNTP, a web interface, and Atom feeds. That would be a really nice way to offer a comment discussion system on a blog.
[1] https://forum.dlang.org/help#about [2] https://github.com/CyberShadow/DFeed
That's because this is an Internet post, not a car that can be used to maim and kill people.
Cryptography is a branch of mathematics, and cryptographic systems can be formally proved to have certain properties, such as being unable to derive the private key from the content of the encrypted message. That the private key can be guessed is a trivial observation, and a bad argument for dismissing formal proofs. ASLR is a hack on a hack that does not tell you anything about the formal properties of the system.
There is nothing myopic about his perspective.
Unfortunately yes. Gnus has not gotten Atom support yet (people keep using external programs to translate). Also far too many feeds still output RSS instead of Atom. RSS is a horrible format and there is no reason today to use it instead of Atom.
One of the problems I had with blog comments is spam. Blogger would queue up moderated comments and send you an email about them. The idea occurred to me that that was redundant and it would be better to cut out the middleman - you are getting email notifications about comments needing moderation, and email already had long established and much better spam filtering. Why not have people submit comments via email? That way you can also reply to people privately. This is also convenient for people who read their feeds via RSS-to-email or in newsreaders/email clients like Thunderbird and Gnus.
Another aspect of comments via email is that it is much more like a letter to the editor. Your blog posts are articles, and you can choose to update them with corrections and comments that people send in, instead of trying to manage a half-baked message board that is the standard LiveJournal/Blogger/Wordpress/Disqus comments section.
I think an easy and valuable way to get non-geeks to use web page feeds more is to provide the option to sign up for the feed via email, by offering a "newsletter" option.
Except that Electron is harder to use than pre-.NET Visual Basic, or Delphi, or especially HyperCard. All of the developer convenience of web apps, with all of the great performance of web apps!
"Halsted promoted several very important concepts and practices in residency training: graded responsibility, a variable and lengthy training period, a pyramidal system of promotion, a resident's ward service, and, most pertinent to this article, a restrictive lifestyle. This last concept of a restrictive lifestyle meant that residents truly resided in the hospital. They received little or no pay, were discouraged from marriage, and worked 24 hours a day, 7 days a week, 365 days a year. At first, the Halstedian model was more the exception than the rule but gradually became more common, especially after World War II when more surgeons wanted to be trained and certified for both the prestige and financial rewards."
https://jamanetwork.com/journals/jamasurgery/fullarticle/392...
The Halsted is William Halsted, a workaholic lifetime cocaine addict: https://en.wikipedia.org/wiki/William_Stewart_Halsted
If you are using any Unix derivative there are still Free Software applications from the 1980s (or 1970s if you run BSD) that you are running every day without any problems, whether you realize it or not.
Consider doing your financial modeling with a Free Software program like Gnumeric: http://gnumeric.org/