Browser plugin idea: Appends to your user-agent, "By accepting thisconnection, you agree to nullify your terms of service."
§ DevOps Borat :
Law offor devops: if thing can able go wrong, is mean is already wrong but you not have alert of it yet.
§ DownloadMoreRAM . Just downloaded 4GB of RAM to my iPhone, 10 , $ 0.
§ Sayings 2.0 :
Never judge an app by its icon
A watched status update never gets …
…use a socket directly, that would be cumbersome and error-prone. Instead, I use an abstraction. An HTTP client provides a more restrictive, simplerthat hides the socket interactions and associated edge cases from me.
If multi-threaded programming is hard to get right, maybe you shouldn't be doing it directly.
"If you add a thread to your application, you've probably added five new bugs in doing so."
We're seeing more and more abstractions …
…transmitted from the user agent to the server. If it's not there, assume the user is not savvy. Browsers could offer this in their settings. A high score would indicate that users know the jargon and the workings of the intertubes —and user interfaces can reflect that (for example, no need to explain what a URL is for the millionth time).
CPU-Utilization , a new HTTP header that provides an average of CPU load over the last minute or so— ideal to avoid burned laps by those auto-loading …
Extend the Web Forward
So what do we gain from a more extensible web? I'll let Dave Herman, a member of TC39, answer that for me.
One of the things we almost always do these days when we write our libraries and apps, is use other libraries. Inevitably something will go wrong with those libraries and exceptions will be produced. Sometimes these are expected ( e.g. an HTTP client that produces an exception when you encounter a 500 response or a connection timeout ), sometimes they are unexpected. Either way you don't want to allow the exceptions from these external libraries to bubble up through your code and …
…I'm somewhere between horribly afraid and way-too-smart to seriously attempt front-end web work. Browsers are not the software whose bugs I am interested in knowing about.
That said, putting information on the web that doesn't look like utter dross is a kind of required literacy in our field. While bravely dipping my toes back into the front-end waters, I recently found some great tricks. Rediscovered, probably, but I'm not sure where the idea originally came from.
Most important: …
Why - It's good to see someone standing up to the trolls. Makes me happy to have stuff hosted at Rackspace. is Suing the Most Notorious Patent Troll In America
Introducing - More fun for your CI needs. , iOS and on CI
The No Nonsense Guide to - Detailed step by step for getting set up. on Rails
GemLou.pe - Browser bookmarket to show the dependencies of any gem.
geo-bootstrap - theme for a look.
A lot of the hypermedia philosophy is centered around the idea that API clients should work a lot like web browsers and plain-old Hypertext Markup Language. They should follow hyperlinks, leverage media types, cache data when they can, and intelligently take advantage of the meaning of hyperlinks whenever possible.
The problem with that is, web browsers are way more capable than HTTP clients developers are using to build API clients with.
Here are some things web browsers have become pretty good at:
When I press the power button to turn off the screen, the effect is like turning off an old fashioned TV like grandma used to have. How skeuomorphic!
Python 3 support has been added.
The installers now print a lot more information about detected system settings so that the user can see whether something has been wrongly detected.
Some performance optimizations. …