1. Google is moving the AOSP away from kernel.org servers to Google servers.
2. The source code for Ice Cream Sandwich will be available "once it’s available on devices".
473 karma · joined March 31, 2011
1. Google is moving the AOSP away from kernel.org servers to Google servers.
2. The source code for Ice Cream Sandwich will be available "once it’s available on devices".
For one, the graphs strike me as confusing. There's too much information trying to be packed into the graphs. It also appears that the various "utilization" measurements are the same on each graph. Furthermore, two completely different types of measurements are used for the "possession" metric, installed base for the U.S. market and quarterly sales for the global market.
Then, there is the questionable "utilization" metrics.
1. Browsing market share: Now, I don't know much about iOs, but on Android there are several different competitive browsers (Opera, Firefox, Dolphin) in addition to the stock browser. Could counting only the stock browser undercount the Android share?
2. Airport/in-flight market share: This is really a measure of what types of phones are used by people who do a lot of flying. Can any conclusions about general smartphone users be drawn from this data? If anything, it just shows that if you are trying to market to the jet-set, iOs is the way to go.
All-in-all it just strikes me a hand-wavy argument that iOs is superior to Android for development. I think there may be a way to make the case, but this certainly isn't it.
As far as becoming another country's citizen, that gets to be fairly complex. Some nations recognize dual citizens, others do not. How that exactly works out depends on the particular circumstances. In any case, the U.S. generally likes to keep its citizens within its grasp.
I don't think the law is necessarily aimed at criminals. The law is primarily sold as targeting people who try to avoid or evade taxation by keeping significant wealth and income overseas.
In any case, the reason for renewed vigour in enforcing the law is clear: the federal government is spending record amounts of money and needs to milk every source of income it can.
edit: fix typos
NOTE! This copyright does *not* cover user programs
that use kernel services by normal system calls -
this is merely considered normal use of the kernel,
and does *not* fall under the heading of "derived
work".
As I read it, the non-Linux part of Android is entirely in user-space, and thus exempt from the terms of the GPL with respect to the kernel. ; Common Lisp
(defun add (x y) (+ x y))
; Scheme
(define (add x y) (+ x y))
; Clojure
(defn add [x y] (+ x y))
Also, Clojure eliminates some parentheses that are used in other Lisps: ; Common Lisp and Scheme
(cond ((> x 0) 1)
((= x 0) 0)
(t -1))
; Clojure
(cond (> x 0) 1
(= x 0) 0
:else -1)I suppose if style is the main consideration when purchasing a computer, Apple is hard to beat.
This is plain wrong. Java was originally developed as a language for embedded devices, not servers. Later, it was targeted for the web (remember applets?).
These days Java may be best known for being "enterprise", but that is hardly its origin.
I am not sure what to think of the wide screen aspect ratio. In some cases it can be good, though sometimes I think it's just a bit extreme.
At this point, I have written significant amounts of code in both languages, and I honestly prefer Clojure. Scala is definitely a big step up from Java, and there is a lot to like in the language. Nonetheless, I think that Clojure is a step up from Scala.
There have been a number of times when writing in Scala that I wish I had some of the features of Clojure, macros in particular. Scala provides many neat features that would be implemented as macros in Clojure, but there are some things that can be done as macros that cannot be done in Scala.
Of course, typing is a big issue. I'll have to admit that when writing client code static typing is very nice, but when writing library code dynamic typing makes things easier. Most importantly, Scala suffers from some of the typing problems that are part of the JVM, most notably: type erasure in generics. Scala provides some means to reify generic types, but it is still a pain to work with. I think that Clojure also contains superior polymorphic dispatch capabilities.
In the end, they are both fine languages. I enjoy coding in Scala and Clojure more than C++ or Java. Still, if I have the choice between the two, I'd go for Clojure.
I disagree. A minimum stipend, at least in the way that you described, would create a perverse incentive. Let's say this stipend is $20,000/year. Why should anyone who makes $5,000/year and get $15,000 free want to work harder to earn the same amount?
A slightly better take on this is to have some sort system were it always pays to earn more. For example, you get 1/3 of the difference between what you earn and $30,000. Under such a system, if you earn $10,000, you would get $6,667 for a total of $16,667. If you earn $15,000, you get $5,000 for a total of $20,000. Thus, it always pays to earn more/work harder.
Personally, I don't like either idea. In my opinion, things like the minimum wage only serve to create unemployment. By making it more expensive to hire workers, companies find other means of being more productive, such as automation or illegal labour.
As analogy (imperfect though it may be), it's like trying to fix a bug in a program that consists of trillions of lines of code, except that you don't have access to the source code or a debugger. Instead, you have just a few high-level variables you can adjust (which may or may not be useful).
In summary, the issue is that there are some problems that have a scale and complexity for which a top-down approach is really beyond human comprehension.
Honestly, I believe that the best dollar spent to get the debt under control is a dollar spent to get a new senator or congressman elected that will actually do something to change things in Washington.
In my opinion, the establishment in Washington consisting of the bureaucracy and life-long politicians is generally pro-government and pro-spending. The Republicans pay a lot of lip service to small government, but it is only the Tea Party types like Ron Paul that actually fight for smaller government.
I am fond of credit unions, simply because they are member-owned and generally are fairly competitive for basic services.
I don't know much about handling merchant services, as that's not the type of business I do. I think warehouse clubs like Costco and Sam's Club also offer those sorts of services of business members.
Announcement: http://www.deepbluelambda.org/programs/baitha/announcing-bai... GitHub: https://github.com/sattvik/baitha
The good news about these two libraries is that there is relatively little overlap, so it'd be great to get the best of both.
If anything, I believe that the biggest boon is not so much in creating device-specific builds, but being able to leave out some things that are unnecessary to keep application sizes low. If you know that a particular package is going to be used only on small, low-resolutions screens, there is no need to include the artwork for tablets.
I'll have to think about your idea to include networking synchronization. The tricky part with that is exactly how to implement it. Off-hand, there are two basic approaches: server/client and peer-to-peer. The problem with server/client is that either I have to choose someone else's platform as a server or provide a server (either as a service or as an included program you can run from a home computer). The alternative is to use something like Bluetooth or NFC to allow synchronization between two devices.
The second issue that I need to figure out is exactly how much material to present. There are some absolutely necessary basics such as activities, services, and resources. Beyond that, there is a question of which platform features are most important. Certainly, something like location is more important than NFC, but deciding on what to include won't be easy.
However, as I understand it, from the perspective of the IRS, it is no restricted as it is an outright stock grant with no vesting or other such provisions.
So, given the above, let me lay out a scenario:
I earn 100 shares of the stock at a rate of $1/share. On the day that I invoice for this stock, it is worth $1.50/share. After six months, when I am able to sell the stock, I sell it at $2/share.
As best I understand it, under section 83(a), I have to report the full $1.50 as income on the day I receive it. Section 83(b) does not apply as it is not restricted stock from the perspective of the IRS. As such, when I sell the stock at $2, it is taxed as capital gains.
Is my understanding correct?
I think I would definitely object to `<-` to be replaced by ←. It's inconvenient to type. On the other hand, as an alias, I am not sure what to make of it.
How this works out in the end may depend on the DHCP server in use. Perhaps the server may discover the broken ARP resolution and invalidate the lease, allowing the Mac to jump in and steal the address while the other device is still trying to figure out what happened.