400 karma · joined May 6, 2014
[1] http://www.nytimes.com/politics/first-draft/2015/12/23/which...
Can you reference the source for this? I ask because much of what I've seen between what WikiLeaks tweets and what's actually contained within the email messages is severely taken out of context. (e.g. not understanding what news embargos are [1]) The New York Times were also the ones who originally broke the story of the private email server.
In the US, this could easily be mitigated with shorter campaign cycles.
[1] http://www.politifact.com/truth-o-meter/statements/2016/jun/...
I think naming and shaming would have little impact and whatever impact it did have would be short lived. Consumers tend to have short attention spans and zero long term memory. Take the banking/finance industry for example, were egregious, predatory and at times criminal tactics are par for the course. Banking institutions are named and shamed all the time, yet the Bank of Americas, Wells Fargos and Goldman Sachs of the world still exist.
Is this not the basis for The Myth of Sisyphus? If I recall correctly, Camus rejects both religion and suicide as ultimately absurd.
..two lobbyists who managed to find their way onto the five-person panel testifying. They represented the interests of traditional IT contractors, who seem to believe it is their right to overcharge taxpayers for complex computer systems that don’t work. Even though, as one congressperson at the hearing put it, those special interests are likely to view the USDS and 18F “with a jaundiced eye,” they were given the opportunity to seize on the authority issue as a way to cast doubts on the Obama tech surge.
From a data standpoint, yes, WP is bad. Really bad. The poor quality code base of WP is only one half of the equation. The other half is the downright awful, novice database schema that ships with it. I've never seen a database schema that is so tightly coupled with the parent application that it essentially hijacks your data into always needing itself simply to extract and render data. WP takes the "relational" out of relational database and flushes it down the toilet. To add to the mess, instead of fixing the rot of its database schema and data handling functionality, WP developers, in their infinite wisdom, merge a woefully incomplete, faux-API system into WP's core, thereby further sealing the door of ever having a clean, thoughtfully designed database that one can access outside of WP and PHP.
In the US, we could already make great strides with removing the hard floor by simply implementing universal, primary health care coverage, free/low-cost higher education and wages that keep up with inflation. I feel that BI in some form is inevitable and the next logical step of civilized society, however, given the incredible resistance to providing universal health care, I do not see BI happening in my lifetime.
As with anything in life, things are never black and white but filled with grays. For example, I'd much rather my banking software or the avionics of a plane that I am about to board be designed and built by committee rather than the local hotshot cowboy coder who wants to rebuild everything from scratch with whatever happens to be the tech stack-of-the-month. Great software is often boring and un-sexy and not everything can be built by two developers in a bedroom.
I don't and the very first thing I mentioned is that content management is a very domain specific problem. In some cases, WP may fit the bill, in many cases it does not.
> This leads one to your conclusion that because they aren't doing some parts of their job particularly good, they shouldn't be considered.
When it comes to content, your data layer is not just "some part". It is a fundamental component and critical aspect to get correct for sound, scalable content management. WP's database schema and abstraction layers fail miserably at anything beyond the context of a basic blog. I understand WP bills itself as a CMS, but its data handling and architecture says otherwise.
> The risks of being technologiclly dependent on the few people that wrote your custom CMS just arent worth it for the customer.
If your CMS is written in Django, RoR, Spring, etc, you aren't anymore dependent than when you are leveraging Wordpress. No WP installation is without heavy customizations to finagle it to become a poor man's CMS and some group will still have to manage/maintain the mountain of technical debt you've left behind by deploying WP in the first place. Furthermore, the landscape of quality software developers in WP land is bleak to say the least.