The website loads in 9 seconds (Chrome 50), the processing of the (peg$parseKeyword) functions takes 4.5 seconds of time during loading which causes the gap in the waterfall.
One look at the function would cause severe ingestion in most people.
(You wanted the word “indigestion”. Ingestion means something quite different. Though I suppose if someone was prone to eating when depressed, it could work.)
I got to see the Saturn V rocket at the Johnson Space Center on Saturday. It is the most incredible piece technology i have ever seen. Luckily I was standing next to a guy whose father worked on the apollo space program; while the astronauts got all the glory. The pride of everyone involved is immense and should be celebrated.
Look up the documentary series "Moon Machines" - it does an amazing job of telling numerous stories of the engineering feats behind the Appllo project, with first-hand accounts and some pretty awesome B-roll from the archives
If the HTTP spec added 2 new VERBS (SHORT, LONG) as a method of shortening and elongating URLs then many things could be done.
1.) The browser could pro-actively lengthening the URL and the same way the server can respond 302/301 now the browser could cache this.
2.) The server could hand-back the final long URL with out needing to redirect the URL multiple times
3.) We could create services that can be integrated into the server software that integrate 3rd parties.
4.) Each domain could create their own shortened URL domains and mask it in a better way.
1) The browser doesn't know the long URL so how can it proactively lengthen it?
2) The server might not know the long URL since all that t.co knows about is the slate.me URL and that only knows about the slate.tribal URL and it only knows the goog.le url and so on and so forth. So this would not be possible unless it was only 1 hop.
3)I am assuming the services you want to integrate into the server software will resolve the shortened URL into a long one or vice versa but in case there are multiple redirects the services would still face the latency of redirects.
> The server might not know the long URL since all that t.co knows about is the slate.me URL
The server at t.co could send a request (HEAD works) to slate.me, and follow up any redirects it gets to resolve the final URL. (This could be done just by following until no more redirects, or only sending requests to known URL shorteners -- there's advantages and disadvantages to both) -- and you don't need any new HTTP verbs to do it.
That assumes that every user gets the same "long" URL for a particular "short" URL (and that every 30x corresponds to a short-to-long redirect). It falls down where a URL depends on geolocation or time sensitivity.
The URL should be under the full control of the domain.
1.) The browser can offer the ability to (right click) and shorten a URL or lengthen it. A HTTP standard would provide this mechanism.
3.) The would not require multiple redirects because everyone should ask the domain. If the URL is already shortened then there is not need to shorten again.
- service like bit.ly, goo.gl can provides services to: 1.) Actually shorten, statistics...
My opinion is there has been a failure of IT to realize that mobile is completely different from everything else and we continue to leverage desktop technology in the mobile world.
Apps work best because they do not carry baggage of the desktop world with them. People have the freedom to build specifically for mobile with mobile tools.
There are no two bigger movements that contribute to this than: Responsive Design and the Mobile first.
Responsive Design implies that mobile is just different from desktop based on the display size and that you can design a single interface that can work for both. Both of these ideas are completely wrong.
Mobile First implies designing for mobile and then desktop is the best approach but this can never work as both platforms will suffer from inferior implementations.
----
Setting the ship back on course would take us building "Mobile Only" with mobile only frameworks, by dropping the ones that were created in the desktop era.
I lived in china for 2.5 years and american's are characterized by its celebrities. In the beginning, i spent most of my lunch time conversations explaining that... No i do not own a gun, but i also explained many times as the men told me they stopped drinking as they prepared to have children.... That is odd; most children in the US are conceived by parents that were drunk.
I have a question that no one i think has asked. Do you think Facebook's "search" capability was born out of their work with the government? When it first came out everyone was talking about how this could be used to violate privacy.
When you are not open about letting people into your market; it is not easy to get out of that market either. i have lived in china for 3 years so i would be cheating to answer this question.
In general, i find the chinese web applications to be a viable alternative to many non-chinese web apps (weibo.com, games...) my new favorite is wechat.com made by tencent.com. it is the best mobile communicator that has been developed.
There is no solution for credit card fraud because the credit card companies do not pay the bulk of the fraud that happens. I have been the subject of fraud both as a merchant and as a consumer and in both cases i was the one that paid.
Two-factor authentication is a good deterrent but is not available everywhere. For my card, for some sites, immediately after clicking "Buy" button, the bank will SMS me an expiring (within minutes) 6 digit code to my mobile phone, and I will have to enter the code to complete the transaction.
Can you elaborate on how you had to pay in the case when you were a consumer and suffered fraud? As a consumer and merchant, I've only ever had to pay when I'm a merchant.
One look at the function would cause severe ingestion in most people.