Subject: Re: So chrome wont show you the url of the site you are visiting soon...
Thu May 01 2014 18:42:29 EDTfrom IGnatius T Foobar Subject: Re: So chrome wont show you the url of the site you are visiting soon...Kind of difficult to bury it completely, as it's needed for things to work ... I suppose it will be kind of like WordPerfect's "reveal codes"
How will bookmarking work?
Subject: Re: So chrome wont show you the url of the site you are visiting soon...
I'm assuming that it might not show you the URL on the title bar, but if you poke around it's bound to show you it somewhere, right?
Subject: Re: So chrome wont show you the url of the site you are visiting soon...
The article notes that this was an experiment, nothing more.
I don't think they'll actually get rid of it. It powers the internet.
Unlike tubes.
as soon as you type in it it goes up to the omnibar. I hate searching from the address bar.
"the URL will move out of the field entirely, to a tidy little button that many users will never even realize is
clickable."
You could always use the super-low-bandwidth search screen I built for myself...
http://www.citadel.org/google.html
I
ve got that in my bookmark button bar. Simple and effective.
To be honest I really did prefer when URL and Search were in different boxes.
But I'm a "computer person" and we really do think differently from most users.
Even with separate bars, some browsers instantly opened a search for single words such as "dork" instead of first checking if it was a hostname that was resolvable via dns/netbios. Even prepending http:// did not help at times. Same goes for lan ips. For fucks sake, why should I google search 192.168.52.43?!?!?!?! I could understand it for the 10.x.x.x, but for 192.168x.x?!
There should be at least an environment variable such as PANTS=ON or USERLEVEL=SHIBOLEET in order to get browsers to behave sane again.
but wait... this is from CNN so Ignat will tell us it can't be true.
[ http://tinyurl.com/mzqnovz ]
Let's remember, however, that "brand value" does not necessarily translate directly to revenue. Vision and execution are two very different things.
Once is not enough; plant a porkchop today.
zooer will be very happy today -- I am about to complain about Google.
fucking googtards and their we-know-best attitude ... I got upgraded to Chrome 35 and now my Java doesn't work. They just unilaterally decided that it's time for NPAPI to die, so I can't run my plugins.
Oh, yeah, speaking of...
Yesterday, I thought I'd try using Google Play on my phone to play a collection of Beatles tunes I have stored on the thing. I told it to make a quick-mix of the Beatles, then start my long commute to work.
For the next 1 hour 30 minutes, it played almost anything in my music collection *except* the Beatles. It avoided the classical music, but it did go so far as to delve a little bit into my Zappa collection... which doesn't really strike me as being anything like the Beatles.
So... yeah... WTF? I didn't hear a single Beatles tune in the mix it made based off The Beatles. Fucking brilliant.
to Chrome 35 and now my Java doesn't work. They just unilaterally
java not working is probably a good thing... of course it will be a long time before there is a ppapi port of JVM, if it ever happens at all.
EMC Unisphere. Requires a browser with Java. Everything else I can get around by downloading JNLP's and running them from the command line ... but Unisphere insists on running inside the browser.
sure, use firefox. my investment-banking apps are the same way.
os x chrome has had no java for a while now, even though it supports npapi for the time being, because it is a 32-bit process and mac java is moving towards 64-bitness.
anyway, here's an interesting read on what the goog-droids want to replace npapi with. http://blog.leafsr.com/2012/08/03/google-native-client-part-1/
J3/vmkit seems to be moving towards a NaCl port: http://reviews.llvm.org/rL200856
ppapi is a nice innovative approach, it is really too bad that the firefox guys are whining now that they have some competition to their stagnant technology
HTML5 is now sufficiently powerful that it no longer makes sense to write web applications which require client-side Java in most cases. At the very least, EMC and others should be moving to Web Start (JNLP) so it doesn't have to plug into the browser as an extension. In the meantime however, this is kind of an abrupt stop.