I'm not sure how you can say hierarchical organizations that use violence/coercion are in any way anarchist. Anarcho-capitalism requires voluntary engagement in a system of contracts and so forth. (Whether that could actually work in the real world is debatable but beside the point.)
I'm not saying the organization exists in anarchy -- we completely agree there.
I'm suggesting that a corrupt state, which cannot prevent the rise of a counter-state power like the cartels, and the evolution of anarcho-capitalism are similar.
The flaw I see with AC is that once the private police force and the private court system in an anarcho-capitalist state combine, there is nothing to prevent them from coercing the organization's will on all around. This is a de facto state. Given that this state may not have primacy, other groups may oppose -- civil war in a supposedly stateless society.
My thought here is that the cartel is the counter-state to Mexico, a state-in-waiting/hierarchical body capable of providing similar "services" that the state typically provides -- defense, mission-definition, communication access, as so on. Whether or not the people under their thumb agreed to this transfer of power is not really necessary to consider, as it is the circumstances at play.
You're using different meanings of the word 'anarchy':
2. (uncountable) Anarchism; the political theory that a community is best organized by the voluntary cooperation of individuals, rather than by a government, which is regarded as being coercive by nature.
3. (countable) A chaotic and confusing absence of any form of political authority or government.
In general, sure, but the context of this thread is drug cartels.
Their unregulated businesses use capital to aggressively expand into other markets, destroy competition, and oppose democratic regulations - behaving similarly to legal capitalist corporations. Though, granted, they conquer with guns and gangsters instead of legal loopholes and lawyers.
I think they suggest that people can be made aware of their incompetence after feedback, but the right kind of feedback often isn't given because of cultural factors that make it unacceptable to give "negative" feedback and also hard for people to accept "negative" feedback.
That idea seems positive to me. If we could change our feedback mechanisms (via education and so forth), we could increase self-awareness and reduce incompetence.
Also, we tend to think of "incompetence" as extremely negative, but they use it in a specific way that is meant to be descriptive and not an insult.
Anecdotal, but PostGIS is the reason I started using Postgres several years ago in some of my own projects, which later came in handy at different jobs. At one place, we standardized on Postgres partly because of PostGIS.
I think Django has had some influence too, since they've always recommended Postgres.
I selected PostgreSQL for a geo project recently. Still haven't got my head around tuning, but apart from that I've found it great to use. I use psycopg2 to connect from Python. No nasty surprises in use, and found that all my pidgin SQL translated easily. Also worth knowing that ogr2ogr supports PostgreSQL and is an awesome tool.
Building your own is educational and maybe even fun (to a point), but it's not going to magically fix these kinds of issues. Most if not all frameworks support navigation and custom framework XYZ probably isn't going to do a better job.
The fact that some sites do a bad job at navigation, performance, or whatever really seems orthogonal to me. We can also come up with numerous examples of "classic" sites that are slow, bloated, and have a bad UX.
I think the argument is something along the lines of: the public hears that an engineer is making certain claims and then push for the laws to be changed. Running of yellow/red lights ends up killing a lot of people. Perhaps without this passive enforcement, more people would die.
Having read some local news about the incident, it sounds like his wife blatantly ran a light according to the laws of Oregon and he attempted to get it thrown out using a dubious technical argument.
I think the argument is something along the lines of: the public hears that an engineer is making certain claims and then push for the laws to be changed
If laws are passed based only on the claims of any person (regardless of his engineering certifications) and without any independent validation that's not the fault of the person making the claim.
His arguments actually were very good. Response time is never instantaneous. Oregon's yellow light law is incredibly dangerous. No one knows when it will end, stopping in the middle of an intersection can create an accident too.
This perfectly articulates something I tried to get across to upper management last time we hired a manager for our team. It seems so obvious and reasonable, but they wouldn't hear it. So, we ended up hiring someone who not only had no real management experience but who also didn't particularly _want_ to be a manager, instead preferring to write code.
This created conflict exactly as you'd expect and team morale fell apart, projects slipped, etc. Of course, management takes no responsibility for this, instead diffusing blame to employees via suck-it-up type platitudes (couched in "nicer" language but with that essential meaning).
> selecting CSS colors in other colorspace (eg. RGBA) as oppose to just hex
I'm not sure if this is what you mean, but you can go into the dev tools config and change the default color unit under Inspector. The eyedropper will show values using the selected unit and style rules will be converted to that unit.
Go is still a pile of abstractions built on top of another pile of abstractions that almost no one fully groks. It doesn't seem significantly less "magical" than any other commonly-used language, especially from the perspective of non-wizards, even if it might be a better tool for casting certain spells.
