Sooo, back to our trick. Ever launched the terminal and noticed that it may take a good 2 to 5 seconds to open? Even on your stellar 16-core Mac Pro? Fear no more. There’s a trick that will bring that benchmark down to well, hmm… a split second!

Open the Terminal (Cmd + Space, then type “Terminal”, then press “Enter”). Are we there yet? Good.

Now paste in the following excerpt and press “Enter (or Return)”:
touch ~/.hushlogin

Quit the Terminal (Cmd + Q) and relaunch. Be proud.

Credits: User “thought_alarm” on Hacker News – Source

* EDIT *
Sorahn, an awesome user from the Reddit community contributed this little gem to us:
Dumping the *.asl logs seems to speed up login even more. If like me, you’re after every millisecond you can get and don’t mind spending an extra 5 seconds to make it happen, then here’s the command you need to run:
sudo rm -rf /private/var/log/asl/*.asl

Full Credits here.

Remember Spotlight?

Well, it seems like Mark Shuttleworth and his team at Canonical took a shot at it and hit the Apple straight in the seeds!

For those of us less familiar with OS X, Spotlight enables you to quickly access files or applications. Just start typing a keyword and your app or file’s name will show up as an option that you can select to access, much like Google’s Instant Search or the Windows Start Menu Search.

… And then there is HUD.

In Ubuntu 12.04 (Precise Pangolin), HUD takes the Spotlight premise and extends it to your current context.

You’re in a browser? Type a URL in HUD and there goes your browser making good on fetching your website! Search help, history, option menus. It’s ALL in HUD!

In an Image Editor? Same principle. Apply filters, resize, add layers, change colors all from the HUD. HUD is like the best friend you’ve never had, always listening and ready to help, no matter what the context!

As the great Ed DJ once said:

Now, Ubuntu users can swear by the HUD! More about it in this video:

You’re still here! Great, that means you, me, and a plethora of other devs have endured the same issue on OS X Lion, specifically.

While it may not be the only source of the slowdowns in your local stack the following trick might prove invaluable to you, as it was to us:

Open your /etc/hosts file, locate the 127.0.0.1 lines, and merge them into one line!

Go from:

To this:

Good Hack is Good

We all owe a big thanks to our friend Joey for the sweet hack!

If you are mildly proficient with a terminal (even the Windows Command Prompt!), chance is you can watch Star Wars Episode IV: A New Hope all made of ASCII art!

It’s a tremendous job by Simon Jansen ( http://www.asciimation.co.nz ) ported to Telnet (with some Terminal tricks) by Mike Edwards (pf-asciimation@mirkwood.net ) and Sten Spans ( http://blinkenlights.nl ).

To enjoy the movie, just open a new terminal window and type:
telnet towel.blinkenlights.nl

More pics below:

Ever wanted to annoy the hell out of your users?

Look no further. Pepper Spray will drive 99% of your traffic away, thanks to its amazing features:

Disable Right-Click

That’s right! Right Mouse Clicks can be so dangerous we made it simple
to disable it with a single call to:
$.pepperspray("disableRightClick", true);

Disable Text Highlighting (and yes, Images too!)

Don’t allow other suckers to steal your content. You’ve worked so hard copying it from somewhere else!
Here, one shot of pepper spray and look at them poor villagers, with their menacing pitchforks, all up-in-arms! But who cares? No subject shall walk off with her majesty’s property!
$.pepperspray("disableHighlighting", true);

Disable the Back Button Functionality

The world is a prison. Let your users feel it. Oh, one squirt of this pepperspray wonder suffices to piss them off! Ain’t nobody goin’ nowhere!
$.pepperspray("disableBackButton", true);

To download, contribute, or read the documentation, click on the link below:
https://github.com/jonaphin/pepperspray

As you may know, a typical jCarouselLite plugin is instantiated as such:
$(function() { $(".anyClass").jCarouselLite({ btnNext: ".next", btnPrev: ".prev"}); });

where “.anyClass” is the name of your gallery container, “.prev” and “.next” are the gallery’s previous and next navigation links, respectively.

Removing the plugin at runtime is fairly simple once you understand what is involved:
$('.anyClass').jCarouselLite = null;
$('.prev').unbind('click');
$('.next').unbind('click');


These 3 lines allow you to re-initialize jCarouselLite later on within the same page. Pretty simple and neat, isn’t it?
Let’s decompose what just happened so you may get a better understanding.
$('.anyClass').jCarouselLite = null; removes the jCarouselLite instance from our gallery. In other words, you will have to reinitialize jCarouselLite if you want to reuse it on this page for this gallery.
This isn’t all, however. When jCarouselLite is initialized, it creates what we call event bindings.
Whenever you destroy the jCarouselLite instance the bindings are still lingering and problems will start occurring if you re-initialize jCarouselLite on the same page, for the same gallery, as the click events on the navigation links will have been bound twice.
To prevent this issue from occurring, we add the two following lines:
$('.prev').unbind('click');
$('.next').unbind('click');


Which brings me to one last pro-tip about dealing with groups and bindings.
There are two main ways to deal with group bindings in jQuery:
- The first one is fairly common. It consists of using a common class to all elements of a similar group.
$('.clickable').bind('click', function(){ alert("Hi, I'm clickable!"); });
$('.clickable').unbind('click');

In the code above, all elements of the class “clickable” will have the mouse click event bound (then unbound) to them.

There is however a second, more mystical way to do this in jQuery: Namespacing.
Let’s say you create an instant link preview feature that you want to disable and re-enable at will on your page. We will call our namespace “linkPreview”.
Here’s the event binding to our namespace:
$('a').bind('mouseover.linkPreview', myPreviewFunction);

And the event unbinding, just as easily:
$('a').unbind('mouseover.linkPreview');


This makes it easy to unbind only specific events from our elements. In this case, all other mouseover events would still be bound to our page links. Isn’t this amazing?

So what is this revolution we will soon be dealing with? Well, your guess is as good as mine but I have a feeling we are talking about an app store for OS X.

OS X has been missing an official package manager for the longest time, and a common place to buy/download/find new packages or “apps” makes sense in that regard.

Also, Apple, great as they are at finding the honey pots, must definitely drool at the idea of recreating the app store craze, only this time on the desktop/laptop OS market.

What thinks you?

For the modest price of $3.99, allow your users to play music from their iPod Library directly from your game!
This is a must-have for all developers who want to provide their users with a premium experience.

As is usual with our plugins, we will support this plugin long term and keep adding features as we go, at no extra charge all throughout the v1.x series.

Purchase the iPod Controls plugin for USD 3.99

Item no longer on sale

Easy iPod Controls Setup

Playing my own music in-game

GenesX is proud to announce the release of our latest Unity Plugin. iAd for Unity on the iPhone and iPod Touch platforms is the iAd solution we have all been waiting for.

Features

• “Zero Coding” skills required.
• Full Integration with XCode. Press “Build” from the Unity Editor and let the magic take over.
• iAd for Unity will detect the orientation of your game automatically
• Choose a “Bottom” or “Top” banner position and you’re ready to go.
• Available API methods for more control over the ad banner
• Read the plugin’s documentation for more details

For the unique price of $3.99 all your Unity-Based iPhone & iPod Touch games can now implement iAd without the hassles, and more importantly, seamlessly.

Item no longer on sale

NOTICE:  This is copyrighted material. By purchasing the product, you are granted a single, non-transferable license for the program. No refunds will be given.

Instructions

- Unzip the package downloaded from the payment confirmation link and import the .unitypackage into your Unity project
- There is a PostProcessBuildPlayer file that will help with the magic. Please make sure it isn’t overwriting another file of the same name, in which case it will clobber some of the other magic you might be already running for your project.
- For now, please use “File” > “Build Settings” > “Build” from Unity. The code in charge of code injection is not 100% accurate all the time, it seems.
- As a precaution, make sure no other Xcode project is open at the same time you do press “Build”, so as to ensure the right Xcode project is being patched.
- If all went well, you should now see “CoreGraphics.h”, “iAd.h” added to your Xcode project’s ‘Frameworks’ group.
- The library was compiled using the iPhone SDK 4.0, so if you have problems, check that you’re up to date with the SDK.
- Building for iPod Touch 2nd Generation or other ARM6 processor-based device? Unity’s Xcode project has a known little problem with the iPhone SDK 4.0. The fix is easy to implement and listed here.

Notice: The current version of the plugin only works with the iOS 4.0 SDK. It is being updated to iOS 4.1 SDK and should be released very soon.

The more we bore witness to this ever-evil fight the more we lost focus on Google and the brews that were coming to maturity inside their busy labs.

In a most shock-and-awe fashion, the world received last week an open-sourced gift from Google. A gift most of us would not know what to do with, but a gift all of us will eventually benefit from. I am talking about Native Client.

How can this resolve the Apple vs. Adobe issue, you ask?
Native Client’s premise is that native code would run on any browser that is compatible with native client on any OS.

How it does this translate into our world? In theory, any web tool such as the flash player or Unity Web Player could potentially run on a Native Client compatible browser without the need for any plugin. Unity showed us the way by demoing Lego Star Wars running on the chrome browser in Linux, plugin-free.

Google offered us a first-class look at the future of the web, a plugin-less future; a future where the line between browser and native applications is blurred to the point where the browser becomes a virtual OS that can run code on any platform, regardless of their desktop OS.

While Adobe fights for the life of its plugin and Apple fights for the death of Flash, Google demonstrated a true act of peace-making. In this very instance, Google’s fight seems to be focused on a better web.

Due to the open-source nature of its technology, native client will certainly make its way into all major browsers. There is no doubt about that. Adobe has the best opportunity of all to get out of Steve Jobs’ deadlock by integrating the native client API into their flash technology.

Apple, via pressure, will reluctantly have to integrate Native Client into Safari, short of rendering their web browser obsolete.

The next question is: How long will Apple be able to keep Native Client out of Safari mobile? It seems to me that Section 3.3.1 of the iPhone OS 4.0 ToS is dead before it is even born.