961 karma · joined March 12, 2009
To which the reply was: Yeah, but you knew exactly _who_ knew your business. This new brand of everybody-knows-everybody's-business is entirely different because it's asymmetrical: everybody knows everything about me but I don't know shit about "them", who they are, where they are, how many of them there are, etc...
* My limited understanding of Ocaml is that it supports both, but nobody uses the OO features of the language so I assume there's a reason for that.
(Of course, at >$3000 I'm not actually going to buy one. Just geek out over it.)
I'm not trying to defend the restriction or anything. It's Jobs' right to pull this shit and its everyone else's right to move to Android. I just think it's less about innovation in tools and frameworks and more about keeping the platform isolated for business reasons. This is just an extension of the "no interpreters" rule, which more severely (IMO) hampers language and tool innovation.
This strikes me as a completely reasonable and not deprecating thing to say about any powerful language (such as C) or any advanced tool in any profession for that matter.
The mythical "sufficiently smart complier" can remove these indirections, but no current compiler can do it perfectly, as doing so requires generative the copious amounts of object code that C++ is so roundly criticized for (templates). GHC is pretty good at removing these indirections. I understand C# compilers are as well. I've not used Java much but isn't there some issue where you can't store primitive integers in a collection because they don't inherit from the base Object type and/or the JVM doesn't support unboxed objects?* This is the same kind of annoyance you have to deal with in Haskell to get fast-as-possible performance (i.e. using types which are not polymorphism-friendly thus decreasing code reuse and increasing verbosity) so in that way I think they are equal with regards to the performance/brevity trade-off.
* I'm sure this has probably been fixed in some recent version of Java but it's still illustrative of why garbage collection imposes a real performance impact that C and C++ just don't have to deal with.
While catastrophic insurance is a good deal for young unmarried people, part of me thinks it's not how health insurance is supposed to work. If you're not spreading the cost of caring for old/sick people among young/healthy people then what's the point?
The other part of me thinks it's just a handout to the insurance industry and people such as yourself shouldn't have to pay a dime for someone else's overpriced cholesterol drugs or 3D ultrasound.
So not all gloom and doom for white America. Yeah the children of immigrants were over-represented with respect to their numbers here in the US, but if you step back and look at the global picture, then they are just about proportional. And I think its a good sign that the US is still an attractive place for the worlds intellectual elite to come and raise children.
Also, connecting 1.5 billion to 700 million is a lot more lucrative than connecting, what, 150 million to 50 million? Nevermind the fact that there are existing high-speed networks to connect with in Europe and China. What a fucking bummer it would be to take a 6 hour train trip from NY to LA then a 6 hour bus from LA to SF.
file.cpp:65: error: please have a look at this line and see if anything jumps out at you.
as that is basically all GCC C++ errors are good for.If you don't agree with this kind of macroeconomic reaction then that's the argument you should be making. To disagree with these loans because they can't possibly turn a profit just misses the point.