712 karma · joined March 19, 2009
Libertarian != Anarcho-capitalist
Stop trolling.
Microsoft: screwing you with network effects since before the WWW
Yes, automobiles have many negative externalities but they are distributed and stochastic. Arguably, it is actually the petrol that is directly responsible for these externalities as simply owning a car endangers no one and only has a sunk environmental cost.
In the case of automobiles, we have, as a society, agreed that this is a good trade-off. In the case of industrial accidents, we have, as a society, agreed that the scale of the potential failure should be matched with commensurate concern for safety.
BP clearly has difficulty controlling their risk and they should be held liable for that just as you or I would be held liable for causing an auto accident.
I think you'll see it come together from two separate places.
1. Standardization of browser event subscription by a remote host. This might happen via an HTML5+ ecmascript API in which scripts register user event callbacks. Think ACPI through JS. This requires aware applications but Google could make it a de facto standard.
2. In-browser identity management and single sign-on. This is necessary to achieve the seamless re-authentication to services. This may be in the form of a browser plugin that, like regularfry says, saves to cloud storage. I think we'll see browsers grow web-aware state APIs in the next 5 years as local and remote get blurrier and blurrier.
What do you think?
OCaml (and potentially Haskell, though I haven't used this feature in Haskell) ameliorates this problem by giving the programmer the facility to specify (or generate and edit based on inference) module signatures that are then checked against. With this approach, I would argue that type inference actually makes your large-scale code more robust and easier to modify than without it due to the automatic verification of module signature. If you inadvertently introduce extra type constraints to your module's interface, the type-checker will tell you and save you from releasing a module that is incompatible with previous versions of the same module.
Without type inference, you're either annotating types everywhere (looking at you Java...) or waiting until runtime (or production!) to find out you've made an error (e.g. perl, python, ruby and on and on).
I really don't see how type inference and its associated program analysis and verification is anything but good.
Perhaps if you don't know Haskell, you should learn Haskell to understand what the article is saying.
Edit: This might help: http://www.haskell.org/tutorial/classes.html
Edit: This is probably not useful to them, actually, due to caching. However, it is their prerogative at any time to change their resource behavior and start receiving every request.
Corporations are legal entities and they clearly have socio- and psycho-pathic tendencies. Facebook (and many other corporations) should suffer under at least /some/ legal liability to treat users' data with care.
Remember kids, your privacy is only worth protecting if not having it protected would endanger the nomination of a politically influential person.
Like you say, art vs. science is a false dichotomy. Programming seems like both because it is about design -- the intentional and intense, the passionate blending of art and science.
We do need to come to grips with the social changes that are occurring and the implications of our present and future digital lives. Our man-made environment isn't the problem, it's our evolutionary memory combined with the phenomenal acceleration of information technology.
In conclusion, don't talk on cell phones when you're talking about sensitive things. In some locations (mid east), it has compromised you for years.
Using functions to represent objects like this is rather silly because they are opaque and only support a single operation.
Here are a number of possibly better ways to do it:
- Emulate objects with functions and messages like with scheme or lisp.
- Use structural typing or polymorphic variants like in OCaml.
- Use records with function fields.
- Use a variant union.
- Extend/build a list monad over your class.
Can you think of other or better ways?By 2015.
To be fair, you could probably do it for much less with only a moderately obscenely expensive car like something in the $75k range. Factor in resale, you're looking at driving a freaking sweet car (and getting really amped about it) for only $25,000-40,000/yr! Sweet!
Now if only we had a start-up plan... something to do with life coaches for the rich and famous?
Am I missing something?
So, no, I don't think our apathy will allow the government to be overrun by copyright thugs -- we already have the cure and it's already prevalent.
Now, these are fairly base liberties being totally about the individual: "Copying data doesn't deprive. I want this data. Yay!" "Doing drugs doesn't hurt others. I want to feel different. Yay!"
The trick will be to maintain our loftier ideals like freedom of speech, freedom of press, and the right to privacy which I can very, very easily see being taken away.