2,359 karma · joined May 26, 2013
We already have an extensive infrastructure in place to protect the intellectual property and trade secrets of companies, including NDAs and those clauses assigning ownership of anything you produce to your employer. But the idea that companies can overstep this bound and place restrictions on how you can use your brain and your general knowledge to produce new, creative work that has only a secondary or tertiary relation to their IP is utterly vile.
If the technology existed to erase memories from brains, would these employers insist in their employment clauses that employees who resign must have any professional knowledge acquired on the job erased from existence? This is almost the same thing. If you are an engineer in a niche field, in particular, being barred from that field for a year or more is tantamount to rendering your professional knowledge obsolete.
I don't think Swift is trying to sell itself based on the 'override' modifier, overflow-checked arithmetic, Unicode variable names, or any of the other minor features which people keep on talking about. It has a far more capable type system than Objective-C ever had. Its pattern matching is far more than "C's switch statement, but without automatic fall-through". Except for backwards-compatibility, it de-emphasizes or eschews the many at-runtime dynamic features that Objective-C had (e.g. creating and modifying classes and methods dynamically). It has tuples. It's a huge departure from Objective-C, not just incremental improvements packaged into a new language (not that it invented these new features, of course), so it's doing more than just addressing 'minor qualms'.
Swift also doesn't perform type erasure. You can do something like the following, as I believe is possible in C#:
struct SquareMatrix<T> {
let dimension: Int
var backingArray: Array<T>
init(dimension d: Int, initialValue: T) {
dimension = d
backingArray = T[](count:d*d, repeatedValue:initialValue)
}
subscript(row: Int, col: Int) -> T {
get {
return backingArray[row*dimension + col]
}
set {
backingArray[row*dimension + col] = newValue
}
}
}- I wanted to try out Swift and see how it felt in practice to build a reasonably-sized project in it - and to see if the Xcode Developer Preview was anywhere near up to the task. I also wanted to see how the Cocoa APIs were going to work with Swift.
- I had an existing Objective-C implementation that I could work from. I wanted to see if Swift could make the implementation easier to read, more elegant, etc. While the original is hardly a thing of beauty, I thought it still might be useful to see how business logic to perform the same task might differ between the two languages.
I hope people who take a look, fork the repo, download and play with the code will enjoy reading through it and maybe take it as a taste of how things might be done (or not done) in the future.
At the same time productivity per worker has gone up dramatically in many industrialized and industrializing countries, even as (and in some cases because) of automation becoming more and more widely adopted. On one hand we're having discussions about how to handle large numbers of workers rendered redundant because of automation destroying jobs (e.g. guaranteed minimum income); on the other hand we're predicting that an economy won't have enough workers to fill all the jobs that will be created because of demographic trends. These things are contradictory.
Vernor Vinge's A Fire Upon the Deep tackled this very subject decades ago, and with far greater poise than Mass Effect did. (And I say this as a fan of the series.)
I suspect the author's reference pools are not as deep as they should be, and I say this because a lot of the topics that the author claims ME to be the first to address have in fact been bandied about in science fiction for a long time. Mass Effect is great in lots of ways; it brings together a lot of plot points and concepts from other series and synthesizes them together into a decently coherent whole. But the series is far from original thematically. (minor spoilers) In particular, the third game tries to address the idea of transhumanism in a way reminiscent of Deus Ex: Human Revolution, another game which came out a year before, but does it in a particularly cack-handed way. Even the ending choice in ME3 is thematically similar to the one from the earlier game.
Since I can't learn anything from lectures unless I force myself to pay attention by taking detailed notes, I took detailed notes. You can find them at the link below, although I make no guarantees about their correctness. (Note that they may also spoil the answers to some of the impromptu in-lecture quizzes.)
https://docs.google.com/document/d/1Uk54kbCIKUx8eX2vJsX591ss...
For anyone who needs a refresher on DFA, Stanford's CS143 compilers class course materials are up on Coursera (https://www.coursera.org/course/compilers), and pretty helpful.
If you somehow knew that a hypothetical China in 2040 with all these things would still be pursuing domestic and foreign policy divergent from American interests, would you still be saying this? If so, I applaud your intellectual honesty.
But will it, and why? This is little more than an article of faith. Computers are getting faster according to a given model, a model whose underlying technological process is reaching fundamental (scientific, not engineering) limits. We have no idea if whatever replaces that model will be anywhere as scalable as Moore's Law.
> computer chess
Computers play chess very differently from humans (they do what amounts to a brute force search of the state space and choose the best option). This is basically taking a well-known algorithm and figuring out how fast a computer needs to be in order to solve it in a tractable manner - cryptographers do the same thing when they decide that a cryptosystem can't be brute-force cracked in a reasonable amount of time. There is no well-defined algorithm for passing the Turing test, and given how so many of the 'interesting' problems in AI are outside the domain of highly logical, rules-based algorithms, using the same metric to measure them is not that useful.
2. The most powerful hardware in the world is useless without software. Improvements in AI theory don't follow Moore's law, and there is no reason they should. Maybe your super-fast computer can run machine learning algorithms on a huge dataset, but it's not clear machine learning alone is sufficient to produce something on the scale of the Singularity. Anyways, strong AI is a very difficult problem, but in no case I know of has the limiting factor ever been the power of the hardware (except maybe for neuronal simulations trying to emulate the activity of a human brain).
/* Also, from the blog:
> Nowhere in this code did we ever declare a relationship between MyType and Answer.
"Answer" isn't in the example. Was this something from an earlier draft? */