990 karma · joined September 27, 2009
(Also, it doesn't help that the wiki is crufty and out of date, and boot menu, last time I rebooted, was still on CentOS 5.)
Harmony didn't die per se - It was killed by Oracle. Google's rationale for engineering a Java-ish VM with Java APIs was only legal up until Java 6.
> Similarly, there’s a logic to giving Paper some more features, or “bloat,” as engineers derisively call such additions. Although it’s awkward to cram more information into a hidden tab on Paper — if birthdays are so important, why aren’t they in Paper’s main news feed? — the additional information also helps Paper live up to its billing as a place for news and stories from your social graph. For some people, birthdays and invitations are a vital part of that news stream, even if, for others, such information is trivial or better placed in the core Facebook app.
1. The Events and Birthday features were planned before Paper was announced. It's not feature bloat, it's a "second release" feature planned ahead of time.
2. Paper is optimized for a high-quality reading experience, especially longer content, as evidenced by the meticulous attention to detail in the text rendering and the horizontal scrolling. Birthdays would take up a lot of space in the story stream for relatively little content (and how would you order it within the feed, anyway?). Look at the birthday indicator on Facebook WWW, and tell me a name and three words are worth a screen-sized card in the stream. I would be very skeptical.
3. Birthdays arrive regularly and in chronological order. The Notifications jewel is the best place for these things - people also visit it regularly and there's a chronological ordering to it.
As for Nearby, the argument is flimsy. Changing strategy doesn't have to mean sabotaging in-flight development. Perhaps Nearby was developed before or during planning for the shift to the new strategy.
I was on the Paper team, but besides iOS, I am very handy when it comes to backend or system administration tasks.
(email: andy+yc@atoulou.se)
No, the point of source control is to record incremental improvements in a codebase. This is a subtle difference, but critical: the history of how codebase got from point A to point B isn't valuable in itself - the logical changes that altered the behavior of the project are.
A series of broken commits might show the developer's journey from zero to 100%, but the idea that each commit is a non-broken incremental addition enables powerful automated workflows for regression testing.
This is more of a strategic move to make Oracle Linux and the other RHEL copies and CentOS-wannabes less compelling: many enterprises that are evaluating Oracle vs. Red Hat will stick to the single-vendor option, and many enterprises that are evaluating Ubuntu vs. CentOS can finally check both checkboxes for "corporate backed and officially endorsed" and "$0 to get started".
My anecdata tells me that Go's types are sufficient (and sometimes even handy), error handling everywhere helps more than it hurts (and is easily ignored if you want to), and is very much not a functional language. And I would disagree with the notion that C is, on average, well-understood given how widely available it is (a nicer way of saying that C is an easy language for anyone to misunderstand). Go is comparatively simpler to 'get right' -- in my experience
Again, this is all very subjective. Still, I don't see how flaming Go alone helps highlight OCaml's advantages and contrast their tradeoffs.
Sad, to be sure, but there's no kind of critical document storage that doesn't need a backup.
I want to like DDG and I've switched to it from time to time, but the thing that always gets me is that I loathe the branding. I'm really, really sorry, about that and I appreciate what you're doing with DDG, and wish the branding didn't turn me off to a peculiar degree, but Google is such an easy choice and it doesn't get on my nerves.
I know that I'm an outlier in this, but I don't think it's altogether a completely impossible or uncommon reaction to be turned off by the name.
Well, since you're foregoing certification, even if you're deriving substantially from the OpenJDK, you're also foregoing the automatic patent grants. And since it's GPLv2, not GPLv3, Oracle or any of the companies who collaborated in the patent licensing scheme, is now free to sue you for billions or trillions.
So no, OpenJDK has a field-of-use restriction in that the only way for a company to build a successful product (or even a failed one) based on it and not get sued into oblivion is to license and pass the TCK to get the license for trademarks and protection for patents.
Here's a link which should prove informative: http://dirkriehle.com/2011/06/30/the-java-ip-story/
Additionally, Dalvik didn't have JIT until late in its maturity, so besides the normal slowdown from Java->Scala, expect it to slow down further by the less-efficient VM.
It might be viable on newer devices, but it'll definitely have problems on older ones. Other than that, it does seem very feasible to write and deploy a Scala Android app.
Given huge effort to implement Dalvik in such a way that the end result could not be called Java, they had to be able to make the argument that Dalvik was a cleanroom implementation of Java. They worked from open specifications; Java 6's specification was open-source, whereas Java 7+ was locked down. There is no Java 7 implementation that could be made without violating the license terms of the specification, as it was no longer open.
It's also clear that they could never have worked with Apache, as any developers who had seen substantial Java 7 implementation code or the specification could be considered "contaminated", and thus any work on Dalvik or any other non-FOU-restricted JVM could be in violation of the license terms. Whether or not this would actually be true, it would be a huge, huge legal vulnerability.
Google and Apache had to avoid each other out of legal necessity to ensure Dalvik's survival. Oracle v. Google could never have worked had they not implemented a very strict (and well-implemented, albeit slightly imperfect) isolation between "Android Java" and "Actual Java". Android technically can't (and doesn't) call what runs on Android devices "Java" - because it's not a compliant VM, they don't have the trademark to use it as such. That said, because of the process they use in which the code is compiled to Java bytecode before it's compiled to Dalvik bytecode, they can make reference to it in terms of the tools - just not in terms of Android actually running it.
I also find the suggestion that there aren't enough smart people to be able to do programming highly questionable. There are far more people who are capable but not able to pursue programming than there are people are who are not "fit" mentally.
With DCIntrospect (https://github.com/domesticcatsoftware/DCIntrospect), positioning in code actually becomes easier than nibs. You can print out the view properties, tweak positioning, then once it looks right you can get the values you need to tweak your code.
Additionally, getting to know UIAppearance and adding categories to UIColor and UIFont that return your app's standard fonts let you create a styleable application with consistent typography and color palette.