accatyyc

I hope this is very ironic (?)

edit removed unnecessary comment. What I mean is that you can already do this with git, nothing else required.

git remote add fork fork@github.com && git merge fork/pr-branch

That is beautiful. Perfectly expresses how I feel about the web today...

YES! Everyone should try this. Sometimes I can get lost in it for hours, just floating around the galaxies...

It's so cool that everything you see, every little star in each Galaxy you can zoom into and check out. Check the simulated atmosphere of every planet, check the rough surfaces of every little asteroid. All procedurally generated and very mind blowing.

Neat looking code! I've been looking for something like this. Will try it! I find it a lot more readable than the usual "header-libs"

This is kind of system wide on iOS. Almost all apps that support zoom supports double tapping to zoom in. Safari zooms into the HTML element you double tapped on and fits it nicely on the screen.

That's an entirely different problem I'd say, and the perfect use case for these libraries on a client! If you'd do it server side it would be like a local IDE sending the code to be lexed remotely...

My rantiness (I apologize for that) targets programming blogs/static pages.

Sure, the energy argument is probably the least interesting of the ones listed above. Don't ignore the rest of them!

That's a good idea! I should make a blog post about it. And maybe be less ranty. ;)

In my opinion it's irresponsible to use highlighters like these. At least when you use them like advertised. Why does no one bat an eyelid at letting the clients handle the highlighting?

The highlighting (lexing) could (and should) be done ONCE at the server. Imagine some high traffic blogs with hundreds of millions of hits combined - all these clients downloading the highlighting libs + lexers for 50 different languages that will never be used on the blog anyway. The wasted energy here is probably even measurable.

Cons when letting the clients handle syntax highlighting:

- Much slower load times

- Wasted energy

- Can fail because of JS crashing

- Noscript users won't get any highlighting (and your blog targets technical users, right? They are more likely to use no script)

- Slow mobile devices will have a harder time loading the site (or depending on javascript engine - failing highlight)

- (if no site optimization is made) the client will download lexers for languages not used on the blog

Cons when the server do the lexing ONCE:

- NOTHING

Note that this rant isn't targeted at Highlight.js. It's a good highlighter - I use it myself at my blog. Except I use it on the server via a CGI script. It took me no more than 2 minutes to set up.

Actually, the UITabBarController supports more than 5 items perfectly well. It automatically adds a "More" button if you add more than 5 items. There you can cram everything in that you would otherwise have put in your hamburger-menu.

Also, if you enable it, it automatically allows users to choose which tabs that goes where, just like in the music app :)

I really like the looks of this! Great work! Might start using it instead of/together with wee chat for the ease of use.

A suggestion - (I know I can just use my own CSS but,) there are low contrasts in the default theme. I usually have very good vision but for me it's pretty hard to distinguish the green from the white background. Maybe you could edit the default colors a bit?

I thought exactly the same thing... I was expecting to read something like "rides the currents back to signal to other jellyfish that this is a bad current", but right now I can't really see the algorithm here.

My interpretation is that OP means that there could be some dislike function on Github, to hide uninteresting projects when browsing... maybe?

You use another delimiter if you need commas. CSV isn't comma only (contrary to what the name implies), you could use '!' or anything else.

Wow! Thank you for this. In 5 minutes I found 5 plugins I had no idea existed but truly brightens my day. Keep up the good work!

I have some problems with this post.

#1 is saying that you're restricted to point based UI's in interface builder. This is absolutely not true. Wether you do you UI's in interface builder or code - use auto layout!

This way you get dynamic, resolution-independent UI's that can even work automatically with right-to-left text (realigning other elements according to text alignment).

The way the author is doing it is still point-based (just a bit more dynamic since he does some calculations) while auto layout has all this built in.

Yes, it is harder to get started with auto layout, but once you learn it, it is worth it.

#2, using things like UIView+Positioning still sets your frames. And it does so for each property you set. This means that the frame might be set 5 times instead of one (just for slightly cleaner code). This is not good since it might cause 5 calls to layoutSubviews instead of one (performance issue) and also it will ruin animations (dependent on a source and target frame).

Candy Crush may have different sprites from Bejeweled, but they play exactly the same. Special matches even give the exact same special powers in Candy Crush... I think they deserve the "candy swap" ripoff. They just got what they did themselves. And it's worse that they also made Papa Pear which copies Peggle (also made by PopCap, creators of Bejeweled)

That's a weird argument. Bejeweled and Peggle (two VERY polished games, both made by PopCap games) were blatantly ripped off. (Candy Crush and Papa Pear by King are almost identical ripoffs, save for sprites).

How are the games by PopCap not polished? It irritates me even more that King copies TWO games from the same company... They truly are the new Zynga.

It will likely stay the same. I can't see what in the Apple TV app would use WebKit since it uses the exact same controls as the rest of the Apple TV. And honestly, I hope it stays the same because I think the ATV app is so much better than the Xbox/PS3/iPad apps... It's simple, doesn't bother me by autoplaying the next episode etc.

I really like this. Thanks! For some reason I'm fascinated by palettes (I never use them for anything though) and simple pages like this is nice because it's easy to save them. (I never remember them otherwise)

edit this may not be the right place for feedback, but I see no e-mail and won't bother with twitter: The "Starred x times" text does not update when I press random. Also, in Chrome it seems that the star button works but it has no feedback at all which seems buggy. Also I can't understand the rightmost column since the box at the top is totally empty which also looks like a bug to me. Otherwise, great service!

I wonder the same thing. How can 7 random passes be any more secure than 1 pass with random 0's? This must be one of the IT worlds biggest (false) myths.

I mean, If there are (recoverable) traces of the previous data after one pass, how can I be sure that my newly written data isn't corrupt? 1 bit should be 1 bit, right?

Please, can anyone demystify this myth, or is it just something everyone accepts?

This is awesome. Very well done, and very nice looking examples. Simplistic and stylish. Props for the spider!

That is true, but it still conflicts with the purpose of this file, which is to "Make the internet suck less", while it instead, in the long term, may make the internet suck more. I don't see how blocking them makes it sucks less anyhow?

Be aware that this blocks Google Analytics and similar services. IMO it's a really bad idea to encourage users to block these services. For example, they are used by pretty much every software company to IMPROVE the product, and if they can't get data on what people use the most in their product, it may not get the attention it needs.