So this is going to be a very quick insight into what Twitter are doing in their next update of the public API, so to get straight into it here are some key points:
- All calls to the API must now use the oAuth authentication as all areas of the API will be on lock down
- Desktop based clients that make use of the API will be restricted to 100, 000 unless they receive special permission to continue making API connections
- The display guidelines have changed so any developer making a clone of what the tweet view looks like needs to follow the guide now
So that’s just a very brief overview but the one I really got interested about was the API limit for desktop clients, for a long time now they have given us the freedom of seamlessly going between the website and viewing tweets directly on our desktop by removing a lot of the crud that we didn’t need to see so we got the best experience possible. This has worked for millions of users for a long time but now Twitter want’s to restrict the amount of calls a single application can make to their API regardless of which platform you use the app on, for us as the consumer of the product(s) we might think it doesn’t affect us but you would be wrong. Read more…
Its always a great morning when you find out a fantastic library such as jQuery has been updated to a new version with more benefits and much better performance overall, it offers a lot of handy improvements to help all of us as developers including a re-architected version of the Sizzle engine which drives the most powerful JavaScript selector engine I personally have ever used.
Other features include vendor prefixed properties so no longer do we have to do things like:
$('element').css({
'-webkit-transform' : 'rotate(90deg)',
'-moz-transform' : 'rotate(90deg)',
'-ms-transform' : 'rotate(90deg)',
'-o-transform' : 'rotate(90deg)',
'transform' : 'rotate(90deg)'
});
Now all we need to do is this:
$('element').css('transform', 'rotate(90deg)');
I think this feature alone will make my life easier since now I won’t need to contend with un-needed overhead that otherwise slowed down performance, for a full list of changes, fixes and new features see the following url.
I like many others are always looking towards new ways to improve our workflow habit’s so we can cut down on our development time making our day-to-day job much more enjoyable for us and keeps our clients happy, one new technology that has been a big hit for pretty much the last two years now is preprocessors for CSS which can be explained by the following quote by Wikipedia.
In computer science, a preprocessor is a program that processes its input data to produce output that is used as input to another program. The output is said to be a preprocessed form of the input data, which is often used by some subsequent programs like compilers.
We can take advantage of these preprocessors by making simple and advanced maths that normally we couldn’t if we used a plain old .css file, because of these advantages we can also extend the abilities the compilers can manage allowing for the most efficient style sheet a developer could ever hope for.
Join Me on Treehouse
Become Smarterer
Need a CSS boost to get your day going? Look no further then CSS Tricks!
