You're right. I just updated it to mention that this is US data. Additionally, I added a link and timestamp to the CDC data that drives this. This way it's not just another site of unsourced information.

This is a minimalist site that I made to create a real-time comparison between 9/11 and the current COVID crisis. PR's and feedback are more than welcome!

The conversations that led to the creation of this questionnaire were absolutely fascinating. I look forward to being able to share the results with everyone.

Post author here.

You've completely got me on that one. On the bright side, it requires much less cost of ownership than a more traditional DB solution.

So, there's that. :)

Post Author here!

I would probably expect the same thing from my employees as well. If I was to blame my bad attitude on the hours, that would be a total cop-out.

I've always had issues with soft-skills; especially in the area of attitude and communication skills. I've done a lot of work in the last couple of years to try and be a better communicator (and hopefully a better human being).

I'm still a work in progress though.

That's a complete straw-man argument. Both APT and YUM can, and do, suffer from outages.

I know I've gotten plenty of "temporary failure resolving..." issues when trying to work with APT repos.

Of course they can, but if you use official repositories and your own repositories, outages of the former don't affect you much because of mirrors, and outages of the latter you control.

It just happens that I almost never see people keeping their own replicas of RVM and gems repositories.

Edit: I only now realized I've omitted important part in my first comment: non-official Yum/APT repositories I use are my (my team's) own.

That actually makes your point even more of a Straw-Man.

It's non-trivial for most teams to setup personally managed dependencies for their dependencies (e.g., cvs, package management, etc.).

Maybe it's just my experience, but outside of the enterprise realm, I generally don't see that sort of thing.

I don't quite see your point here. That most of the programmers can't create Yum or APT repository? Or can't setup VCS server?

> Maybe it's just my experience, but outside of the enterprise realm, I generally don't see that sort of thing.

Most programmers are more interested in jumping into every new sexy library that just happened to appear than to make their working environment reproducible, robust, and controllable. That's why they don't think of how to package their code for installation and deployment, don't think where and how to keep their dependencies (not thinking about dependencies causes explosion of dependency fractal, which is a collateral damage), don't think how to work off-line, and so on.

I agree. I focus more on Passion and Flexibility. Without these two traits, it's much more difficult for someone to change and grow.

PayPal also charges a monthly fee if you want to accept credit cards (Website Payments Pro) and a fee for monthly recurring charges.

I've always told customers that PayPal is great if you are doing a store/e-commerce. If you're doing anything else, it can be absolute Hell to deal with and you're going to be better off using Stripe or Authorize.Net.

> And we are proffessional developers

In my experience, WordPress is not built for developers or designers. It's built to be simple and extensible from the end-user's point of view. Most end-users don't expect absolute perfection and accept that it will do 90% of what they want. As long as it keeps doing that, no one will care what a "mess" the insides of it are.

> no one will care what a "mess" the insides of it are.

...except the poor bastard who will have to build the website and maintain it.

I agree with you on the Azure vs "nice things". I also think their long-term strategy doesn't rest with the .NET framework.

However, I think they know that if they completely abandoned the .NET framework, there would be a community of very upset devs that have spent their entire careers investing in Microsoft. Instead, they're doing a slow withdrawal and "giving it to the community".

I think that in the long term, they're going to be focusing more on Sharepoint, SQL Server, and Azure; less on .NET. That's just IMHO.