A friend of mine just came back from a trip to Ecuador. He couldn't get a direct flight, so there was a switch at Miami. Compared to like mostly everywhere, he had to take out his luggage and re-check it in, which is quite senseless IMHO, but hey, security theater. On the way there, there was a note like you said. Coming back, there was no note, but his stuff was completely messed up and his camera missing. Needless to say, he'll try to find a direct flight next time.
The Javascript version of Facebook may have felt unresponsive on an iPhone 4 or 4S, but those days are history.
Nitpicking a bit - the JS engine used in Safari has seen much improvement in the past few years. But if you make a HTML5-based app with something like Cordova, it will use the old JS engine which is markedly slower. Sure, faster processor helps, but it would be nice if Apple would enable the newer JS engine on HTML5-based apps instead of just Safari.
Protip: XBMC + projectM (Milkdrop clone/port, not sure which). Should come built-in with latest versions, requires some GPU but even a lowly ION2 handles 1080p just fine. And yes, it reduces the need for acid;)
Thanks, that makes sense. (FWIW, sftp support is included with OpenSSH, which I guess is the most popular implementation, but there are probably some admins that disable the functionality)
Somewhat off-topic, but I figured there'd be some KDE users reading this - I've always wondered what's the difference between using fish:// and sftp://. I always use the latter, and in my experience it is somewhat reasonably fast, once it's able to negotiate a connection. Initially, when opening a remote location or doing something after a long period of inactivity, it can take some seconds.
I don't know which distribution you are using - but at least on my laptop (which runs Arch and KDE SC 4.10), I just tried to open/usr/lib (Arch recently moved everything to/usr/bin and/usr/lib, everything in the "old" locations are symlinked there) - according to Dolphin, 3491 files and 169 folders totaling 1.8GB. It opened instantly. Granted, this is on an SSD, but I've never seen Dolphin take that long (apart from opening folders via SFTP, for obvious reasons). Also granted, many distros do a really half-assed job with KDE (keep it vanilla, let the user configure it).
I don't mean the browser would actually execute the code, that would be both dangerous and stupid. But the browser has complete control of the JS runtime, so I guess Firebug executes the code, checks the return value and returns the state of the runtime to what it was before. Obviously no XHRs are sent when doing this. As a fellow poster noted above, this is very handy with ExtJS.
It was a contrived example because I was trying to be general, but let us be specific then: "Ext.getStore('myStore').getById('someId').get('property');". In Chrome, tab completion ends at Ext.getStore - I'm guessing Firebug tries to execute the code in the background as you type because it works all the way.
Wake me up when the Chrom(e/ium) console is better. Yes, both allow tab-completion of properties of an object. However (as a contrieved example), say you have an object "foo" that has a method "bar" that returns an object of type "baz". In both, I can type "foo.b" and select the "bar" method. But in Firebug, I'm able to write "foo.bar()." and autocomplete properties of "baz". If you're working with something like ExtJS it's godsend. Also the network tab is much more useful in Firebug - in Chrom(e/ium) one can sort by type, but there's no way to show only requests of a certain type.
I also keep using FF because of Firebug (and AdBlock+) - but in my experience, with many tabs open, Chromium takes much more memory. This is on x64/Linux, YMMV.
Anecdotally (having worked with node.js for the past year or so), whenever I've needed to do something not available in the core libraries, there has been an npm for it, usually several. But - and this is a rather big but - their maturity can vary quite a bit. The biggest issue really is documentation, that can be incorrect or completely out of date. Yes, there always is the source, but that's hardly ideal.
Having said that, in general I do like node.js. It takes some time getting used to and you have grasp Javascript well in order to use it efficiently, but if you're working with JSON data (we use CouchDB) it's quite a natural fit.
Isn't the Daily Show and Colbert available for free off Comedy Central's website?
They are, and they are not. They're blocked by IP to some countries, and depending on your location you can get them in most places here, and not get them on some hotels for instance. I guess geolocating isn't an exact science. Also, I don't know what they do with their flash player but it's the most unreliable I've met. It can skip to the next segment seemingly at random which is very irritating.
Here in.fi, some operators were ordered to block thepiratebay.org and associated domains. The blocks ranged from simple DNS blocks, trivial to get past, to blocking actual connections to certain IP adresses, depending on the ISP.
Among the blocked domains was piraattilahti.org (that would translate to "pirate bay") - but at the time being, it forwarded to effi.org (local EFF). The block on piraattilahti.org was lifter after a while. Now, when you visit piraattilahti.org, it functions as a proxy to thepiratebay.org, so you can get there no matter what ISP you use.
The point being, these kinds of blocks are completely futile. Those interested in pirating content will continue to do so (and while TPB is undoubtedly a large tracker, it is hardly the only one), and ISPs will not certainly implement such blocks out of charity, so ultimately the costs will be paid by the subscribers. The only way to reduce piracy is to offer legal (and reasonable) alternatives. Currently, between subscriptions to Netflix/HBO Nordic/Spotify, I personally pirate very little - I do like to pay the content producers, if I'm able. But if I'm not, arrrrrr it is (Comedy Central, should you be listening, I'd gladly pay for Daily Show and Colbert).
We're currently using Sencha Touch - there are some downsides, the documentation can be woefully incomplete or wrong even (be sure to use the online docs so you get the user comments as well), we've had some issues with migrating between very minor revisions, up until recently it only supported Webkit (2.2 added support for mobile IE as well, I think mobile FF is still not supported) and programming for it is quite different than traditional web programming - Sencha Touch is very much a "my way or the highway"-type of framework, if you try to work outside the conventions you're just asking for it.
OTOH, if you're familiar with MVC-based frameworks and GUI programming with something like Swing (or any modern GUI toolkit really), you should be able to pick it up fairly quickly, and it offers a quite rich selection of GUI elements one would expect in a mobile device. You can use traditional OOP with subclasses and so on, which can help to make your code more maintainable. And theming with Compass is just great. HTH, HAND.
While I appreciate efforts to improve Javascript ($DEITY knows there's a lot of built-in retardness, although personally I'd appreciate most if ECMA Harmony would finally be implemented - not holding my breath though as I like living), I'm not sure I really asm.js is the way to go. However, their typing system is "interesting" - but it doesn't go far enough. I mean, it's great that you can have "intish" and "doublish" values, but why stop there? Print stringish stuff to the console, define your own objectish values in an arrayish structure, manipulate them with functionish methods - the possiblities are endless(ish)!
Actually, trying your example query, the first response I get is a "card" as well. Perhaps my queries are usually so obscure / I use bookmarks too much that these don't appear? But... it's a single "card". One flick of the thumb and it's out of the view, the "card" doesn't show in subsequent result pages. This really is your issue? I'd be infinitely pissed if those were all the search results, but as such... really, not such a big deal, in my opinion.
It sounds really annoying, and I'm sorry I'm not able to help you. Perhaps Google offers a different Google "experience" on Nexus devices? On a totally unrelated note - boy does the new Slashdot mobile site suck. I never read this via my mobile due to the "competence" of/. web devs, just occasionally check responses to comments. It seems to go into an infinite loop of replies, I'm able to see our discussion repeated ad infinitum. *golf clap*
Granted, I don't run vanilla Android anywhere at the moment - but this is what happens both on a stock S3 and Transformer Infinity, running "Browser", i.e. some-webkit-based-browser-that's-not-Chrome. I'm sorry if this is a WORKSFORME-type of response.
Slashdot Mirror
It isn't the right wing saying that. It's certain anti-corporation types with a weak understanding of global business law.
What, like this guy?
A friend of mine just came back from a trip to Ecuador. He couldn't get a direct flight, so there was a switch at Miami. Compared to like mostly everywhere, he had to take out his luggage and re-check it in, which is quite senseless IMHO, but hey, security theater. On the way there, there was a note like you said. Coming back, there was no note, but his stuff was completely messed up and his camera missing. Needless to say, he'll try to find a direct flight next time.
The Javascript version of Facebook may have felt unresponsive on an iPhone 4 or 4S, but those days are history.
Nitpicking a bit - the JS engine used in Safari has seen much improvement in the past few years. But if you make a HTML5-based app with something like Cordova, it will use the old JS engine which is markedly slower. Sure, faster processor helps, but it would be nice if Apple would enable the newer JS engine on HTML5-based apps instead of just Safari.
Actually you will feel something. It'll be like boiling a frog.
No, it won't.
You are aware there are waterproof phones (well, 30mins @ 1 meter anyway, see Galaxy S4 Active for example) with microUSB ports?
Protip: XBMC + projectM (Milkdrop clone/port, not sure which). Should come built-in with latest versions, requires some GPU but even a lowly ION2 handles 1080p just fine. And yes, it reduces the need for acid ;)
Thanks, that makes sense. (FWIW, sftp support is included with OpenSSH, which I guess is the most popular implementation, but there are probably some admins that disable the functionality)
Somewhat off-topic, but I figured there'd be some KDE users reading this - I've always wondered what's the difference between using fish:// and sftp://. I always use the latter, and in my experience it is somewhat reasonably fast, once it's able to negotiate a connection. Initially, when opening a remote location or doing something after a long period of inactivity, it can take some seconds.
I don't know which distribution you are using - but at least on my laptop (which runs Arch and KDE SC 4.10), I just tried to open /usr/lib (Arch recently moved everything to /usr/bin and /usr/lib, everything in the "old" locations are symlinked there) - according to Dolphin, 3491 files and 169 folders totaling 1.8GB. It opened instantly. Granted, this is on an SSD, but I've never seen Dolphin take that long (apart from opening folders via SFTP, for obvious reasons). Also granted, many distros do a really half-assed job with KDE (keep it vanilla, let the user configure it).
The fact that linux does not do this is a downside.
Uhh, what?
I don't mean the browser would actually execute the code, that would be both dangerous and stupid. But the browser has complete control of the JS runtime, so I guess Firebug executes the code, checks the return value and returns the state of the runtime to what it was before. Obviously no XHRs are sent when doing this. As a fellow poster noted above, this is very handy with ExtJS.
It was a contrived example because I was trying to be general, but let us be specific then: "Ext.getStore('myStore').getById('someId').get('property');". In Chrome, tab completion ends at Ext.getStore - I'm guessing Firebug tries to execute the code in the background as you type because it works all the way.
Wake me up when the Chrom(e/ium) console is better. Yes, both allow tab-completion of properties of an object. However (as a contrieved example), say you have an object "foo" that has a method "bar" that returns an object of type "baz". In both, I can type "foo.b" and select the "bar" method. But in Firebug, I'm able to write "foo.bar()." and autocomplete properties of "baz". If you're working with something like ExtJS it's godsend. Also the network tab is much more useful in Firebug - in Chrom(e/ium) one can sort by type, but there's no way to show only requests of a certain type.
I also keep using FF because of Firebug (and AdBlock+) - but in my experience, with many tabs open, Chromium takes much more memory. This is on x64/Linux, YMMV.
Anecdotally (having worked with node.js for the past year or so), whenever I've needed to do something not available in the core libraries, there has been an npm for it, usually several. But - and this is a rather big but - their maturity can vary quite a bit. The biggest issue really is documentation, that can be incorrect or completely out of date. Yes, there always is the source, but that's hardly ideal.
Having said that, in general I do like node.js. It takes some time getting used to and you have grasp Javascript well in order to use it efficiently, but if you're working with JSON data (we use CouchDB) it's quite a natural fit.
For them to be a tracker, they would have to host torrent files, and they haven't in years.
OK, "distributor of magnet links" then. Using magnets is so transparent that it's hard to tell the difference.
Isn't the Daily Show and Colbert available for free off Comedy Central's website?
They are, and they are not. They're blocked by IP to some countries, and depending on your location you can get them in most places here, and not get them on some hotels for instance. I guess geolocating isn't an exact science. Also, I don't know what they do with their flash player but it's the most unreliable I've met. It can skip to the next segment seemingly at random which is very irritating.
Here in .fi, some operators were ordered to block thepiratebay.org and associated domains. The blocks ranged from simple DNS blocks, trivial to get past, to blocking actual connections to certain IP adresses, depending on the ISP.
Among the blocked domains was piraattilahti.org (that would translate to "pirate bay") - but at the time being, it forwarded to effi.org (local EFF). The block on piraattilahti.org was lifter after a while. Now, when you visit piraattilahti.org, it functions as a proxy to thepiratebay.org, so you can get there no matter what ISP you use.
The point being, these kinds of blocks are completely futile. Those interested in pirating content will continue to do so (and while TPB is undoubtedly a large tracker, it is hardly the only one), and ISPs will not certainly implement such blocks out of charity, so ultimately the costs will be paid by the subscribers. The only way to reduce piracy is to offer legal (and reasonable) alternatives. Currently, between subscriptions to Netflix/HBO Nordic/Spotify, I personally pirate very little - I do like to pay the content producers, if I'm able. But if I'm not, arrrrrr it is (Comedy Central, should you be listening, I'd gladly pay for Daily Show and Colbert).
We're currently using Sencha Touch - there are some downsides, the documentation can be woefully incomplete or wrong even (be sure to use the online docs so you get the user comments as well), we've had some issues with migrating between very minor revisions, up until recently it only supported Webkit (2.2 added support for mobile IE as well, I think mobile FF is still not supported) and programming for it is quite different than traditional web programming - Sencha Touch is very much a "my way or the highway"-type of framework, if you try to work outside the conventions you're just asking for it.
OTOH, if you're familiar with MVC-based frameworks and GUI programming with something like Swing (or any modern GUI toolkit really), you should be able to pick it up fairly quickly, and it offers a quite rich selection of GUI elements one would expect in a mobile device. You can use traditional OOP with subclasses and so on, which can help to make your code more maintainable. And theming with Compass is just great. HTH, HAND.
I think the word you're looking for is "condone". Condoming an island country could prove to be extraordinarily difficult.
While I appreciate efforts to improve Javascript ($DEITY knows there's a lot of built-in retardness, although personally I'd appreciate most if ECMA Harmony would finally be implemented - not holding my breath though as I like living), I'm not sure I really asm.js is the way to go. However, their typing system is "interesting" - but it doesn't go far enough. I mean, it's great that you can have "intish" and "doublish" values, but why stop there? Print stringish stuff to the console, define your own objectish values in an arrayish structure, manipulate them with functionish methods - the possiblities are endless(ish)!
I have mod points... but there's no "-1, Lame" option. Really, you have to put some effort into it.
Actually, trying your example query, the first response I get is a "card" as well. Perhaps my queries are usually so obscure / I use bookmarks too much that these don't appear? But... it's a single "card". One flick of the thumb and it's out of the view, the "card" doesn't show in subsequent result pages. This really is your issue? I'd be infinitely pissed if those were all the search results, but as such... really, not such a big deal, in my opinion.
It sounds really annoying, and I'm sorry I'm not able to help you. Perhaps Google offers a different Google "experience" on Nexus devices? On a totally unrelated note - boy does the new Slashdot mobile site suck. I never read this via my mobile due to the "competence" of /. web devs, just occasionally check responses to comments. It seems to go into an infinite loop of replies, I'm able to see our discussion repeated ad infinitum. *golf clap*
Granted, I don't run vanilla Android anywhere at the moment - but this is what happens both on a stock S3 and Transformer Infinity, running "Browser", i.e. some-webkit-based-browser-that's-not-Chrome. I'm sorry if this is a WORKSFORME-type of response.