cmccabe
Joined 14 years ago
Joined 14 years ago
The three-strikes law significantly increases the prison sentences of persons convicted of a felony who have been previously convicted of two or more violent crimes or serious felonies, and limits the ability of these offenders to receive a punishment other than a life sentence. Violent and serious felonies are specifically listed in state laws. Violent offenses include murder, robbery of a residence in which a deadly or dangerous weapon is used, rape and other sex offenses; serious offenses include the same offenses defined as violent offenses, but also include other crimes such as burglary of a residence and assault with intent to commit a robbery or murder.
So, since speeding is not a felony, it has no relevance here. Shoplifting might be a felony, but it would only invoke three strikes if you already had two prior felonies which also happened to be violent.
By the way, I'm not defending three-strikes laws, just describing them. I think they are a bad idea. I also think the ACLU is whitewashing the records of a lot of the people involved here.
Because evidence might come up later that proves them innocent. Because killing someone deprives them of all of the rest of their life, whereas life imprisonment offers them some fraction of it.
I actually do think there are some people we should just hang-- after due process, of course-- but definitely not everyone who has a long sentence.
Also, a "life" sentence usually just means 20 years in the US, for whatever reason.
If it's "cumbersome" to acquire the state you need for testing, then that sounds like a design problem that you should fix. The best kind of tests are reproducible and part of a test suite anyway.
I actually kind of like Go's scheme here. One thing I never quite liked in C/C++ was huge directories full of source files where it wasn't clear what code was part of what binaries. If something is only part of one binary, why not make that obvious by putting it in another package?
Windows RT machines are usually between $300-$600, and were marketed as "Windows" machines, which brought with it a set of expectations that Windows RT machines were not able to meet. People assumed that "it runs Windows" meant that it ran their apps, but that just wasn't true in this case.
I am aware that there are some ChromeBooks that are really expensive, and Microsoft introduced desperation price cuts at certain points, but that's the basic story.
git does this: it has "man gittutorial" and "gitcvs-migration", as well as man pages for each command. It makes a lot of sense and avoids the "giant wall of irrelevant text" approach.
Bash, on the other hand... yeah. Just try finding anything in there.
True. But the documentation for GNU programs, both man and info, is often also "of unknown provenance, authorship, datedness, accuracy, and comprehensibility." You even said yourself that the man pages for many of these GNU programs are years out of date on some systems. Official status is not guaranteed either, since anyone can fork an open source program and produce a clone.
Somehow, despite all that, we manage to muddle on. Probably, it's because we're humans, with the ability to filter out bad information and incomprehensible explanations, and find the real information. And in my experience, this is much easier to do with a man page, which usually simply gets to the point, than with a long, meandering info page which treats me like an idiot and yet often fails to mention vital information.
Thank you for the clarification that info pages can support images. Since I have only ever used info in a terminal, I was not aware of this.
In a lot of ways, info reminds me of Microsoft's CHM format, another HTML workalike with limited abilities. CHM can also support images.
Web usage may be monitored, but I suspect that searching for information about open source programs won't reveal anything about me that downloading Linux did not.
Impala was about creating a low-latency SQL engine for Hadoop, so that queries could be done interactively by a human at a keyboard. This is something that you don't really get with Hive (despite all the recent hype) because it simply is too slow, and has high startup costs. That's unlikely to change in the future because of the overhead of spinning up JVMs, starting MapReduce jobs, etc.
It seems like you are trying to target the OLTP market. That's a difficult market to crack. A lot of the value of things like Oracle and Microsoft SQL server is not in the database itself, but in the surrounding software. Performance is nice, but unless you can get orders of magnitude, it's very difficult to compete.
Will anybody ever bridge OLTP and OLAP? The last people who claimed to be trying to do that were Drawn to Scale, and we all know how that turned out. I think it's better to focus on doing one thing well.
Good luck.