Ctrl-x e in zsh is '_expand_word'. The function you are talking about is 'edit-command-line', which is not loaded or bound to any key by default in zsh. You have to load it manually.
The OpenSSH model implies that you check the fingerprint of the public key before you send encrypted data using that key. That is why SSH shows you the fingerprint of the server key when you first connect, and you have to answer "yes" in order to accept the key and add it to your keyring. You are supposed to have talked to the person managing the system and that person should have given you the fingerprint of the key.
It is virtually impossible for the ISP to intercept and sniff the stream without changing the fingerprint.
"Wrong! Random people will totally verify key fingerprints when they're logging into Google Mail at Starbucks! After all, that's what every sysadmin does with SSH, right!"
I have no idea what you are trying to express here. "Trust On First Use" is a synonym for key continuity. The fact that you have to type "yes" when SSH does it and click a series of buttons when a browser does it doesn't change anything.
I think you think that "Trust On First Use" means "automatically accept keys the first time you hit a site". In fact, that's only true in practice. Presumably everyone's going to get the "Watch Out! This Could Be Iran!" dialog from their browser, too.
There isn't any non-Internet communication channel that users could use to find Google's fingerprint. Google won't give their fingerprints on the phone for billions of web users.
Theoretical models that have no practicality in a given real life context aren't worth discussing as a solution.
Calendar does have a custom view, which defaults to showing the next "4 Days" (hint), available in the bar at the top of the calendar view. You can change it to 7 days if you like in the settings (gear -> Calendar settings -> General -> Custom view).
For the users, it is either this or no movie player for them. No movie player means a big product disadvantage compared to competitors, which is very bad for Google as a company.
> I'd rather have no movies and no music than to have our technology become increasingly hobbled by the entertainment industry.
Unfortunately, whilst you're not alone in your sentiment, the majority of users to whom Android devices are sold don't care either way, and those are the same users that make Google the most money.
Not sure if that's the case. The company makes the most money from online ads, so is it better to foster long-term technology growth or to convince more people to use Android?
> Not sure if that's the case. The company makes the most money from online ads, so is it better to foster long-term technology growth or to convince more people to use Android?
Getting more Android devices into the hands of users now is important to Google: it increases developer appeal (growing the platform), which draws even more users (increasing advertising revenue). Having competitive, consumer-orientated features like this—that stack up against Apple (and Amazon)—are far more important to these goals than things like whether a device is rootable, themeable and/or side-loadable.
Consumers will become very discouraged quickly when they try to add a skin, or theme, or any customization, and all of a sudden certain applications will no longer work.
I feel this is akin to having a Windows PC that would disable Netflix streaming if you wanted to dual-boot your PC.
Android devices are the current generation of the previous Windows-era ecosystem. A bunch of clone hardware running slightly tweaked OEM versions of an OS.
The biggest difference, which consumers will really start to have issues with, is tying a software OS update to a hardware revision (If Dell prevented you from upgrading a Windows 98 machine to a Windows 2000 machine, not because of hardware limitations, but simply to generate more device sales).
> I feel this is akin to having a Windows PC that would disable Netflix streaming if you wanted to dual-boot your PC.
It's more akin to having a Windows PC that would disable Windows Media DRM files if you had unsigned drivers loaded into the kernel. Which it does. This isn't without precedent, by any means.
I don't see "our technology" becoming "increasingly hobbled" just because there's one Android app out there that doesn't want to cooperate with a rooted phone. If anything this is positive since it probably acknowledges that anyone with a rooted phone is going to be able to capture the contents of the movie in an unencrypted format.
Most, if not all, of his arguments were already beaten to death. The rebuttal should be floating around somewhere on the Internet, but I couldn't find it with a quick search right now.
Anyways, right at the beginning of the presentation you see the quality of his arguments as he uses a very known problem of a particular compiler (GCC) to bash the language. Sort of a straw man fallacy.
His argument is that C++ is so complex that it's extremely hard to write a fast, reliable compiler that generates good error messages.
The fact that it took gcc programmers 10 years to get to a point where gcc doesn't use ridiculous amounts of memory when compiling few lines of tricky code is a fact in favor of the argument, not against it. Gcc programmers are smarter than an average programmer. If it was easy, they would have gotten it right on the first try. Accordingly, C or Java or C# or Go compilers didn't have such problems so C++ is more complex for compiler writers than pretty much every other known language.
The same goes for error messages. In the past decades we've had tens of C++ compilers. If clang is the first one that is able to generate decent error messages for templates, then it means it was a hard problem to solve.
None of that got any easier: if you want to write another C++ compiler, it'll still be hard for you to generate decent error messages or compile tricky C++ code reasonably.
A possible counterargument: it took gcc programmers 10 years to get to a point where gcc doesn't use ridiculous amounts of memory when compiling few lines of tricky code _in_C_.
Clang, written in C++, is faster, uses less memory, produces better error messages, and, I brink, took less calendar time and man hours to write.
Yes, it is a hard problem to solve, but from these two anecdotes, it seems solving it in C++ is easier than solving it in C.
And yes, I know the above probably is a fallacy; gcc hackers probably spent most of their time working on CPU ports and on getting gcc to produce better code. Begin hackers, and not having a C++ code base themselves, getting good C++ error messages just wasn't important enough for them.
I could use your argument to describe pretty much any modern compiler or framework. "It is extremely hard to write a fast, reliable Java SDK that generates good error messages.", for example.
It took years to GCC to arrive where it is because it contained A LOT of legacy code that have been accumulating since its first versions with C++ support. GCC is a compiler that evolved little by little through long years, and many features were added with little design, to fix punctual problems, which made it difficult to converge to a clean implementation.
Clang, on the other hand, had a good deal of proper design to write a clean, robust compiler. The fact that clang reached where it is in such a short time compared with GCC is a good evidence that it is possible to write a good C++ compiler with nice performance and error reporting if you employ good engineering efforts.
No Java compiler has ever generated the kinds of error messages that every single C++ compiler did for template errors. Feel free to give me an example of Java compiler error message that takes 2 screens and fails to give you useful information.
If you compared the complexity of clang C++ front-end with complexity of any Java compiler front-end, you would see a huge difference in complexity (size of the code, time it took to develop).
The first checkin in clang code base was in 2006-06-17. It took almost 5 years and more than 31 thousand checkins to get to current state which is: not done (http://clang.llvm.org/cxx_status.html).
A fully functional, fully compliant Java compilers have been written in fraction of this time by much smaller dev teams.
The facts do not support your claim that "proper design" is enough to write fully compliant C++ front-end in a reasonable amount of time. 5 years of effort of top-notch, highly paid developers to not achieve the goal is not reasonable and it's fully the result of C++ complexity.
Except that the problem of understandable error messages for C++ is not solved. That was the whole objective of the proposal of concepts, which were not included due to last minute problems.
> The bitching about bad compile time errors has been mostly fixed in clang.
Yes, IOW, it is a compiler problem, not a language problem. Because one particular compiler is horrible on error presentation doesn't mean that the language is bad.
> declared somewhere with static linkage, it can be hard to pin down exactly _when_ that constructor will be called.
The language doesn't define it on purpose. The language leaves it to be defined by the implementation because it goes a little beyond the purpose of the compiler. The compiler transforms C++ source into object code. You can have multiple objects linked together into a single binary, and this linkage is very platform and operating-system dependent. C++ is already horribly difficult to implement correctly; if the language were to define an order for static initialization, it would be stepping on the operating system domain, and make it even more difficult to implement on some systems.
This is not the expected transition plan to IPv6. You do not turn IPv4 off. During the first phase of the transition period, new users are supposed to run IPv4 and IPv6 side-by-side, so they can reach both parts of the Internet without issues.
You just jumped to the third phase of the transition plan while the rest of the world is busy doing the first one. That ain't gonna work.
The site will tell if your Internet access will be fine on World IPv6 day. A positive answer means that you either have IPv4 only connection (no broken IPv6 DNS responses or routes), or have a fully operational IPv6 nameserver and route to the Internet. A negative answer means that your computer was tricked into using IPv6 while no actual IPv6 connectivity exists (and thus you are going to have problems on June 8th).
I get different results from those sites. The first says that everything will be fine because my setup only does IPv4[1]. The second says everything will be fine because my setup fully implements IPv6[2].
This seems somehow strange.
1 - This web browser (at this location) looks safe. You'll just keep using IPv4.
2 - Congratulations! You appear to have both IPv4 and IPv6 internet working.
I've run that on all manner of devices and infrastructures and it has never told me I will have any problems on World IPv6 Day. That's not because it is inacurate, it's because the vast majority of setups will continue to work perfectly on June 8th.
The more out-of-the-box your setup is, the more likely it'll work (modulo a few broken OS/browser combos listed in the ARIN wiki).
You might experience problems in environments where someone has been playing with IPv6 and left it half-broken (or, in my case, tried to be too smart and used DNS server on Cisco router ;)
From what I remember, the instructions were that ISPs receive no less than /32, which should provide end-users either /48 or /56. End users use the remaining 8-16 bits to partition their networks in /64 subnets. /64 is the minimum routeable prefix, and is the prefix used for automatic configuration.
Linode offering /128 for free and /64 at a cost is ridiculous. Users will have problems to forward since that would require breaking the /64 into smaller networks (to have at least one distinct subnet at each end of the tunnel), which is not possible for radvd.