990 karma · joined September 27, 2009
Android generally monetizes/converts worse than iOS, so those who want a presence on Android can't afford to take advantage of any of the new stuff until old devices are retired sufficiently to make the tradeoff really worth it. It's been really tough to see all of the improvements, because Google is addressing user upgrades so poorly (even though the fault lies mostly with the manufacturers) that the upgrade problem is such a big deal for developers.
The protest, by some accounts, was for the most part not violent. The violence that did happen was a planned and targeted action perpetrated by a highly trained militia exploiting the cover of the protests.
Reinforcements were delayed intentionally, and the second attack clearly accounted for the contingency of a saferoom escape by smoking them out. Indeed, several hours before the attack occurred, it's possible that the area was being scoped out, and pictures taken.
Furthermore, the group that is apparently responsible has been identified, and is being pursued.
If you want to know more, the middle-eastern thread at SomethingAwful is tracking developments.
You can even add to /etc/hosts and the computers using it as their DNS will resolve it. Depending on how much control you have, DNSMasq will also function as a DHCP server and TFTP server from which you can netboot other servers and do such nifty thing as automatic reinstalls. Useful if you have a separate, internal network and want to set internal IPs, too.
There's a social factor to being a professional too; it's not just raw programming skill or experience.
I hope this drives developers towards using and improving Postgres, but, well, who knows. One can dream!
More likely is that it may drive people towards Percona, which I have on good word is a solid professional MySQL branch...or, like Java, people will just stick with the brand. :/
EDIT: adding links for the curious.
Percona: http://www.percona.com/
Background on the Java stuff: http://arstechnica.com/information-technology/2010/12/apache... (the difference is that MySQL never did have open governance, so there was nobody to quit in a justified huff)
[citation needed]
I know someone who works on processor stuff at Apple. More detail would obviously be bad for him, but they have digital design expertise which they are actively using to design (presumably) their future generations of chips.
Maven lets you keep different library versions around for different applications. This is actually a fundamental thing I've noticed everywhere I've personally seen it used: specify the versions. However you use Maven is evil. Your usage pattern needs to be improved.
In practice, as far as I've seen, one should specify the exact versions of the library you're pulling. This is done explicitly in the name of build reproducibility. The "main" repositories should be preferred unless something really custom is needed - in which case, you should be running your own package repository with the libraries you need.
So I guess more tips for maven:
1) Prefer releases over snapshots of libraries whenever possible.
2) Consider running an artifact repository if you're working with a large enough team. It's simple enough that it'd speed you up nicely even if your entire project lives on one laptop, if you're comfortable with a few details of running it. This is strictly optional but will make certain team-based workflows smoother.
3) Always specify versions manually! Don't set it to use the latest automatically. Is this ever a good idea?
4) Try not to include too many third-party repositories if you can.
It's not hard to get Maven dependencies under control. The dependencies are also cached locally, so Maven builds should depend on the internet only the very first time their dependency is included, and thereafter, every time they are updated, only for the package that was updated. Maven is actually -very- good at repeatable builds by default.
Things like the Play! Framework can get away with it because the framework is basically an exoskeleton around the Java code rather than a traditional container.
Maven requires a standard directory layout. Maven chose that hierarchy, because:
1) Namespacing. With tens or hundreds of thousands of packages out there, there needs to be an unambiguous way to refer to them separately.
2) Multiple language support. Maven can do Java, Scala, Clojure, Groovy, and so on - in the same project, even. It can even do Javascript, which isn't a JVM language, in certain cases. For the JVM languages, if you want a multi-lamguage project, there has to be an easy way to interoperate (this is enabled by namespacing).
3) Separation of test code and program code. Don't ship tests with your binary package.
4) Separation of code from data.
5) Automation - of packaging, IDE support, etc. This has to do with all of the previous ones. You want to produce a JAR, but don't want to include the default log configuration. So you package the project up. It just happens. You want to edit the code in your IDE. So you add the project. All libraries are downloaded and on your classpath. Add a few lines to your config (as a per-system-user setting or per-project setting, take your pick). Java documentation and source code for those libraries is automatically downloaded. Eclipse hooks it up for you.
Suddenly, this:
src/main/java
src/main/scala
src/main/resources
src/test/java
src/test/scala
src/test/resources
...makes a lot more sense. It's hardly overengineering, but even then, the engineer isn't the one engineering the build system; these are details Maven takes care of.
[Aside: I am appalled and flabbergasted by the ignorance typically leveled at Java by people who don't understand it✝. It has real flaws, don't get me wrong, but making dependency resolution and installation ridiculously straightforward, multi-language builds dead simple, and unit testing a core feature - these are good things.]
Take a look at ant and compare it to maven and you'll see which one makes your life easier✝✝.
✝ I have worn many hats, and have experience with Python, Ruby, PHP, C, Java, and a little bit of Scala in real world contexts, among others. So I'm not a noob who hasn't experienced elegance or conciseness or performance. Java is actually an amazing language that many people don't give it credit for. Though the syntax can be pretty ugly even when the code is conceptually solid.
✝✝ Losing a bit of nuance here - ant gives you configuration. maven gives you convention. Ant is good for very custom; maven is good for straightforward processes.
Because of this, I think there should be a meta-HN so rather than shutting down discussion and causing it to bubble up and eventually boil over, it can be openly ignored until a fantastic idea comes along (or refused nonetheless), instead of total silence or a constant buzzing noise like my post and the parent which, honestly, detracts from the overall quality of HN proper.
That is beside the point, however, as the questions of jurisdiction with respect to copyright are somewhat more well-established than that.
Jaywalking, doing drugs, and underage drinking are fundamentally acts against rules, not acts against entities. A risk is being taken and the burden of failure is on the risk-taker.
Selling alcohol to minors is unethical. Do I need to get into that? Acquiring media in an unauthorized fashion is an act against the creator and their licensed distributor. That makes it unethical.
You can separate whether an action is justified, and whether it's ethical. There are clearly reasons to pirate - valid or not^, the act itself is not ethical. And I think it's clearly so.
^ personal opinion: mostly not
There's also the separate but related issue that many believe that entertainment is a right, or that it should be available in all mediums. While I do believe that it should be available anywhere at any time, pirating should not at all be considered an ethical recourse to acquiring it through other means. Art doesn't exist absent the influence of money. Entertainment is commercial art but that doesn't mean that its artistic value excuses the viewer from participating in the artist's (creator's) intentions for distribution.
That's half the story. Piracy is a hard habit to break - even when it does get easy to get content cheaply, some people take a while to come around.
Most consumers of online video services (I work at a company that streams video):
* Can easily mistake 480p for 720p and above
* Don't know or care how much bandwidth they are using
* Value content availability
So if Comcast wants to compete, licensing the best content, which can become really, really expensive, is going to be key. Even so, though, production companies may find it most profitable to license to multiple outlets to maximize profits. So even though Comcast owns NBC, it's probably best for NBC's shows to be on Netflix, Hulu, etc.
I think that a successful Comcast app might be a very good thing because ratings measurements will shift from Nielsen ratings (which can undercount certain kinds of shows) to better data (how many and what kind of people really watched the show). Better data means better analysis and targeting, so, for example ads can fund the shows much more effectively - and thus make shows that were previously niche more viable, or shows that were quirky and constantly teetering on cancellation more secure.
So this means that any website could embed Ruby code (more strictly speaking, it could embed a Ruby interpreter) to be executed client-side on a browser supporting NaCl.
The administration of subreddits has problems, in which some mods (i.e. of SRS) got death threats. Subreddit splits are typically unsuccessful. Exposition and discovery of subreddits is hard. Insightful, rational, two-way discussions are now exceedingly rare, and offensive/tasteless comments are nothing unusual. Popular subreddits tend towards "pop" topics rather than depth.
I am subscribed to DepthHub and TrueReddit but still, neither fully scratch my itch. I think that drawing a firm, clear line and being dedicated to squelching those who step over it will help build and preserve a community. See SomethingAwful, where there's an incentive to stay on-topic and a penalty for being creepy or overly offensive (beyond being just provocative) outside of the forums in which that is allowed.