FuckItJS: Runs your javascript code whether your compiler likes it or not.

https://github.com/mattdiamond/fuckitjs/

by tomkin • 14 years ago

315 62 14 years ago

github.com

meggar• 14 years ago

Nice.

gfosco• 14 years ago

I love a good tongue-in-cheek git repository... Reminded me of: http://html9responsiveboilerstrapjs.com

michaelbuckbee• 14 years ago

Don't forget to check out the companion Twitter account: https://twitter.com/H9RBSjs

josscrowcroft• 14 years ago

That is the funniest thing I've seen all month!

"2. How do I install this?

Um... are you stupid or something? Just attackclone the grit repo pushmerge, then rubygem the lymphnode js shawarma module – and presto!"

eragnew2• 14 years ago

Groxx• 14 years ago

That's awesome! Try running the JS file - clearly, it should be included in every site. And check out the source of the page.

crazygringo2• 14 years ago

> 1. Include jQuery, because everything requires jQuery

I love it! :P

Great sense of humor.

ericcholis• 14 years ago

Also, "Note: This is ALPHA software and may result in irreversible brain damage."

fferen• 14 years ago

This is ALPHA software and will routinely bully other software to assert its dominance.

Sorry, couldn't resist :)

estebank• 14 years ago

First thing I thought when I see it: Why!?

Second thing: Why not call it OnErrorResumeNext!?

crazygringo2• 14 years ago

Ah... bringing back the memories :)

I think I'll go add an "Option Explicit" to the top of the file I'm working on, right now, just for fun...

Since it's not valid JavaScript, I'm sure FuckItJS will just skip over it.

DougBTX• 14 years ago

You mean, write a script which wraps each line in a js file with try catch? Sounds doable.

modarts• 14 years ago

How would I go about integrating this as a step into my build process?

raverbashing• 14 years ago

this is probably like integrating a car crash into your daily commute

but you can probably integrate into Jenkins for continuous jury-rigging

jackcviers3• 14 years ago

The software license is the best part:

"If you are caught in a dire situation wherein you only have enough time to save one person out of a group, and the Author is a member of that group, you must save the Author."

51Cards• 14 years ago

Brilliant... This is going in every software license and terms agreement I write from here on out. What a tremendous insurance policy if I perhaps hit on the next Facebook. 1/7th of the planet responsible for saving lil ol' me.

kozlovsky• 14 years ago

Just keep in mind: widespread adoption of this license can lead to race conditions, when two concurrent authors of simultaneously used products happen to be in the same group

masklinn• 14 years ago

I don't know, I really liked the `FuckIt.moreConflict()` method, especially when I read the source and realized he actually tested it and ensured `window.location` would not get overwritten (or you'd navigate away from the page)

drivingmenuts• 14 years ago

I dunno. Does this clause require me to save you if I'm in favor of said event happening?

adaml_623• 14 years ago

That's not a 'dire situation' more of a plan coming together.

e1ven• 14 years ago

Interestingly (to me), this is Technically GPL incompatible, since it adds additional restrictions beyond what the GPL requires.

TeMPOraL• 14 years ago

Another reason not to use GPL - it breaks the ability to add something funny to licence.

themstheones• 14 years ago

I realize that this is a joke, but I can't help but wonder if there is a possible valid use for it. I could imagine needing something that fixed bad js for a crawler that needed JS on a poorly coded site, but I can't think of an occasion where discarded bad code would ever be useful. Maybe if a site deliberately injected bad JS to prevent crawling it would be worthwhile.

tyler_ball• 14 years ago

I've used this library for loading horrible, third-party javascript:

https://github.com/gregersrygg/crapLoader

JoeCortopassi• 14 years ago

Dupe: http://news.ycombinator.com/item?id=4148287

tomkin• 14 years ago

My apologies. I submitted, but when it has been submitted before it usually just redirects you to the previously submitted one. Not sure why it didn't do this for me this time!

EDIT: Seems to be "http" vs. "https".

samwillis• 14 years ago

No need to apologise. If something is missed the first time, people see it the second time and it gets voted up to the front page then people want to see it. With the voting system if it truly is a "dupe" it wont get voted up...

wetmore• 14 years ago

> Through a process known as Eval-Rinse-Reload-And-Repeat

ERRAR. I like it.

emiliobumachar• 14 years ago

Intentional or not, that is Portuguese for "to make a mistake".

chc2• 14 years ago

It's also a netspeak spelling of the English word "error." (For some reason it's considered humorous to transform -er and -or into -ar.)

eragnew2• 14 years ago

+1 for creative name

dag11• 14 years ago

I read the source before I read the readme, and was thoroughly mindfucked.

I love it.

cabirum• 14 years ago

For completeness, it should use WTFPL license.

http://en.wikipedia.org/wiki/WTFPL

blasten• 14 years ago

nnq• 14 years ago

...but still, what does `FuckIt.moreConflict()` actually do and when would I use it? (I just desperately feel the need to use a function named `moreConflict`... don't ask!)

samuellevy• 14 years ago

It overwrites ever property on the 'window' object (except for 'location') with FuckIt.

md224• 14 years ago

Original Author here... for reasons I can't fathom, someone has created a Drupal module:

http://drupal.org/project/fuckitjs

mey• 14 years ago

Which contains this gem http://drupal.org/node/1657944

staticshock• 14 years ago

Interestingly, the Bad Judgement module looks like it's a legit check on other non-serious modules:

This module provides an explicit dependency for modules whose usage requires bad judgement. Joke modules often require "bad judgement".

Periodic• 14 years ago

Reminds me of Failure-Oblivious Computing [1]. It takes advantage of the fact that in many programs errors have a short error propagation distance as they are often written as a main event loop and as long as you can get to the next iteration of the loop the error won't corrupt state. For example, if your server crashes on one request, it will probably be fine if it just gets invalid data instead, discards it as invalid, and then waits for the next response.

I'm not sure if this applies well to JavaScript. We might observe that most JavaScript is a set of disjoint event handlers. If one doesn't work right it probably won't break the rest of the site.

I played around with implementing FOP dynamically through DynamoRIO [2] as a class project but only got through a proof of concept and quickly remembered why I hate x86 assembly.

1: http://en.wikipedia.org/wiki/Failure-oblivious_computing

2: https://github.com/periodic/Shady

jberryman• 14 years ago

Clearly this is the future.

saraid216• 14 years ago

So that's where the name comes from. FOC-It.

aboodman• 14 years ago

This is exactly what browsers do already. If one event handler has an error, that event is aborted. But the event loops continues, and js will continue to run.

wsc981• 14 years ago

That reminds me a bit about a 'feature' of VB (LotusScript?) "on error resume next" :)

caster_cp• 14 years ago

//@ TODO: give a shit

epic comment, in an epic app

aklofas• 14 years ago

Yep, the commits are funny too: https://github.com/mattdiamond/fuckitjs/commit/001b146fc9dc6...

pfisch• 14 years ago

I feel terrible for the person who takes a contract job and is handed some code that depends on this. Also I hope it isn't me.

acuity12• 14 years ago

One of the best laughs I've had in a while.

esalman• 14 years ago

Pardon me but I don't get any alert when I run the test script.

FuckItJS: Runs your javascript code whether your compiler likes it or not.

Related Stories