@morbiuswilters said:
FTFYmplayer -vo aa $(find vid/ | grep -v '/$' | sed -n "$(($RANDOM * $( find vid/ | grep -v '/$' | wc -l ) / 32768)){p;q;}" -)
This is a console app after all
@morbiuswilters said:
FTFYmplayer -vo aa $(find vid/ | grep -v '/$' | sed -n "$(($RANDOM * $( find vid/ | grep -v '/$' | wc -l ) / 32768)){p;q;}" -)
This is a console app after all
@lpope187 said:
No, it looks more like Epic Fail Guy. Strangely appropriate for Spectate don't you think?I'm pretty sure you just insulted EFG.
I'm reminded of the code I wrote for "Please Name This Feature," which was the official name of the blasted thing right up until beta. Everything related to the feature in the code is labled pntf instead of something more useful. At least it got a good giggle out of the customers that chose to read the source, even if the implementation sucked.
@SpectateSwamp said:
Noodles for spaghetti code. Just one or 2 of these noodles winding its way through the search logic can completely change the results. [...] Let the computer kick out the errors. Make a quick change and jam it again and again. That would always get results fast. And it's a fun way to go about it. When strange data was sent for the first time. Try one data format then the next and the next till you hit the one that worked.
I think I get it now. I understand his code delusion. He's a tinkerer that never grew out of it.
In the mid/late 90s, just as the internets were coming into their own, I became part of a fansite that happened to use good old Matt's WWWBoard. I was curious about how it worked, but the code was incomprehensible to me at the time. I only knew enough HTML to shoot myself in the foot, and not a bit of Perl. Alas, the irresponsible host got their server hacked, and the entire site was basically lost. We switched to newer, niftier, less Matt-tastic software. Unlike WWWBoard though, this one had official support forums, including one for "code hacks." The author encouraged members of the community to modify the software and post their changes.
This piqued my interest, and I dove in head-first. I still didn't know a single bit of Perl, but through reading what others did to the code, and actively tinkering with it myself, I soon figured out the gist of things. I published a dozen or so "hacks" for the code, some tiny one or two liners, some huge paragraphs of code to add some weird feature. I did things that nobody in their right mind would ever consider. (I still have a few of the snippets. They make my blood run cold, they're that awful...)
Two years later, it ended up getting me hired by the company that created the software, to take over development.
It took me years to get out of the tinkerer mindset. Indeed, the cowboy coder, hacker, twiddler, one-line-change-right-before-release, "who needs testing?" side of me ended up causing a huge amount of trouble. There was no mentoring, no software development lifecycle, no specifications process, no code review, minimal concepts of testing and QA. In fact, I only ever got code feedback from the minority of end-users that happened to be code hackers, and none of them raised an eyebrow at some of the WTF-worthy crap I coded over the years. It ended up as a contributing factor in the demise of the product and my job.
Swamp never got past that critical phase. He still lives in the bubble of irresponsible coding. Everything is a quick little hack. Who cares if it doesn't work exactly right the first time the end-user uses it? Worse, he IS the end-user! Who cares about specifications when you have the entire thing in your head? Who cares about code reuse and sanity when you know the whole codebase backwards and forwards?
Without some major situational changes, I doubt that this code outlook on life will never change. He'd basically have to be hired somewhere as a junior dev or an intern or something, and be shown how the real world works. Even then, he'd prolly reject it all as useless, time-wasting fluff, because he thinks he knows exactly what he's doing.
@morbiuswilters said:
Hmm.. never heard this before. Also, you probably mean the PHP folks because Zend has a stake in sticking with their VM as they make money from providing add-ons and tools for it.
You'd think. [url=http://www.technetra.com/writings/archive/2004/01/09/interview-rasmus-lerdorf]Rasmus expressed interest in 2004 though[/url] - see heading "What about PHP 6?" Then again, he works for Yahoo instead of Zend.
The new VM wasn't as batshit insane then as it seems now. There was talk back then by the Zend folks about replacing the Zend Engine with Parrot when it became mature enough. Honestly, that would have been awesome to see, because what I really want is the goodness of perl with the virtual-hosting-friendlyness of mod_php.
Unfortunately the chances of this happening nowadays are about nil, which makes me sad.
@SpectateSwamp said:
At Swamp Shack I could show you the #2 and #3 programs of all time[citation needed]. By Me. Simple and powerful[citation needed]. What any new programmer needs[citation needed]. Will work in any language[citation needed]. Used during 15 years of Telco and cablesystem billing conversions[citation needed]. Then maybe #4 my automation of the Rural gas co-op mapping system. Way ahead of its time[citation needed]. And the lessons learned are easily transferable[citation needed]. The cattle system for the largest feedlot in Western Canada had some high points[citation needed]. Still lots to show and share. Who shares their video, pictures bla bla bla better than Spectate Swamp. Nobody[citation needed]. Some of you just share your opinions and nothing else. Because you don't have this great[citation needed] collaboration tool[citation needed]. Can't do video like me and my swampies do. Can't explore with video. And NetSquared pulls this project. I would have made them lonely at their so called contest. Everybody would be at SwampShack booth[citation needed].
FTFY
It's just a piece of trash blowing in the wind! Do you have any idea how complex your circulatory system is?!
You might wanna look at updating your IE6 with a few security patches. The about: hole was fixed some time in 2003-2004ish at the latest, around the same time as it was fixed in Mozilla.
@medialint said:
I'm thinking of that old gem Ultimate Bulletin Board here ... and the knowledge that huge traffic sites like mp3.com (back in the day) were actually using it. :-)
Small world. I was the maintainer of UBB from 6.0.2 through the bitter, under-specified failure of an end.
I could write epic essays on the WTFery of those flat files and the stuff I had to do to wrangle some semblance of stability out of the things -- and even then, it's still full of WTFs. ubb_lib_pntf, anyone? (I'm so, so, so sorry. I was such a noob...)
Oh yeah, and sorry about the whole plantext password thing. I could write yet another huge essay about that mess. Yay legacy compatability and platform restrictions!
The worst part was keeping the party line about the whole thing, something that I don't care about now that I don't work there any more and the NDA has expired. That code was a rotting piece of crap that wouldn't know how to perform if its life was at stake... and yet I'm still proud of the obscene things I made it do.
@SpectateSwamp said:
... I don't know if he's the most daft idiot ever, or the best troll ever, but somehow we have managed to convince him that posting rocks is topical.
I bow to the offtopicness that has spawned this monstrosity. Truly you are a master of whatever twisted art you practice.
The question they're asking as a requirement:
Can your application run natively in a web browser (Internet Explorer, Firefox, etc) and be remotely accessable by users without the application installed or WITHOUT being installed?
i.e. can you visit a web page like per-se http://google.com/ and enter your search criteria without downloading a program?
Are you so sure that you want to encourage him to make a browser-based SSDS?
I love the month of null. The weather is so beautiful.
@Zecc said:
Ugh, tell me about it. Another part of the application does some rather complex twiddling, and a full quarter of my debugigng effort was making sure that things would fail gracefully if the user entered bogus numbers. Having the entire page grind to a halt because a user entered "lol" into a quantity field is bad.And that goes for the assumption that parseInt would return NaN for an invalid input, too.
I was having a very, very difficult afternoon. After over a year of pondering, we finally had an excuse to wedge a date widget into our web-based intranet app. Unfortunately, the Javascript library that we chose doesn't exactly have a plethora of widget options unless you're also using the underlying platform the library likes. Yes, I'm talking to you, Prototype. Stop that, it's annoying.
The date widget we picked is hardly feature-packed, but it gets the job done well. Well, rather, it gets the job it was designed for done well. It wasn't designed to be a real date widget. It's just a calendar with decent support for doing whatever you want with it, and it even favors YYYY-MM-DD like we already use throughout our app.
Something it didn't do was automatically change its own date when the user manually edits the date field while the widget is active. It was an annoying problem with an easy and straightforward fix. But then I started testing. Whenever I picked a date in August or September, the widget wouldn't update. Every other month worked fine. Deeply confused, I dug in more. The 8th and 9th of the month also wouldn't update the widgets. Confused, I dove back into the code.
var date_bits = element.value.match(/^(\d{4})\-(\d{1,2})\-(\d{1,2})$/);
var new_date = null;
if(date_bits && date_bits.length == 4 && parseInt(date_bits[2]) > 0 && parseInt(date_bits[3]) > 0)
new_date = new Date(parseInt(date_bits[1]), parseInt(date_bits[2]) - 1, parseInt(date_bits[3]));
'2008-09-01' was coming out of that regex as [ '2008-09-01', '2008', '09', '01' ], so no problem there.
parseInt('2008') == 2008, good.
parseInt('09') == ...
If you said 9, you fail. No, it's zero. See, Javascript supports octal numbers. Any number starting with a zero is octal, even if it can't be an actual octal number. In certain languages, like Perl, trying to use a non-octal number as an octal number results in an error. In other languages, like Javascript, it silently fails.
So, thank you Javascript, for teaching me something I didn't know about you... and making me hate your quirks all the more.