oh nice php

[Rage9]

You're right though, frameworks are for lazy people. Lazy people don't like to do a whole bunch of extra work to get something done every time they work on a project. So they use boilerplate code to finish shit fast so they can get back to being lazy.

Are you comin to SD next month or what bro? I <3 our programming-method-hating/packers-loving friendship

Haha, that's one perspective on it. Good, I'd counter with good coders don't like to look at half assed ideas when they can write their own solution. An API is not enough of a reason to have a whole third party "framework" devoted to it, as API's are generally very personal things regarding a code base that they are wrote for. It's really abstract layer apon abstract layer, and it's very annoying honestly. Be the shark, not the fish.

As for SD I haven't talked to my bosses about it, chances are there is enough code to be wrote that I can't, but like I mentioned to Uplinked today someone would probably get punched in the face in a heated drunken conversation. Not to say there won't be a meetup by us in the near future where we could all get together.

Erect is really a good guy, not the greatest coder ever, but the guy knows his shit. I will forever respect the guy for it. So while you guys are pussy footing about with your frameworks we are just going out there and putting the pedal to the metal and making cheddar. We do it without OO programming (discounting me typecasting an array to an object for faster coding) or frameworks.

So all those guys that think that these "frameworks" are making their life easier, I'd tell you to really look in the mirror. All the time, and bullshit spent learning this stuff vs writing code is not helping you. All these abstract layers are not helping you. I've known a few of you that want to talk like it is, but when push comes to shove and you have to throw down it's the exact opposite. Being a non OO programmer, and knowing my shit hasn't slowed me down one bit, in fact it's made me more successful because I approached every problem as I can solve it from the ground up and I'm not afraid to get my hands dirty.

But please, coach me on the "natural progression of coding". If you buy in to that garbage all you will ever do is fall farther behind. Stick to the basics, learn your shit, put up with no shit, and you'll be successful beyond your wildest dreams. If you want to be stuck as a tadpole you will be, the sharks know where it's at and they make it happen. We know what's bullshit and what's not. While you dildos are sitting in your framework circle jerks we'll be out there making shit happen, oh wait isn't OO and frameworks suppose to make you code faster?

 

[Rage9]

Did you really just put OO and Frameworks in the same group? Wow you are fucking retarded.

According to lots of coders here, they'd both be categorized as the "natural progression of coding". If it wasn't for OO, you'd probably see less frameworks as it builds on top of the notion that the more you abstract the base code layer the more efficient you get. Allegedly.

Really what is the difference between the two? Both are meant to extent the base code layer. Bother are mean to be more organized. Both are meant to be more efficient. If you can't realize how the two are linked, I'd tell you that you are the retard.

 

[Insomniac]

According to lots of coders here, they'd both be categorized as the "natural progression of coding". If it wasn't for OO, you'd probably see less frameworks as it builds on top of the notion that the more you abstract the base code layer the more efficient you get. Allegedly.

Really what is the difference between the two? Both are meant to extent the base code layer. Bother are mean to be more organized. Both are meant to be more efficient. If you can't realize how the two are linked, I'd tell you that you are the retard.

OO is meant to provide an easy way to do variable namespacing, simple as that. Complex code becomes a serious cunt when you have to mentally keep track of what global functions and variables you've declared. Why else do you think C code these days is written in a pseudo OO way?

Frameworks on the other hand are meant to provide abstraction so different levels of coders can work on the same project. With a framework I can have my css/javascript guy work on my project the same time as anyone else.

 

[mattseh]

I personally find it very upsetting that all webapps aren't written in ANSI C, preferably ASM.

 

[LotsOfZeros]

If it wasn't for OO, you'd probably see less frameworks as it builds on top of the notion that the more you abstract the base code layer the more efficient you get.

This is where I always get hung out to dry in my education. I figure I could learn a framework and advance my programming to the next level but once I start diving in to the code, it looks like something totally different from php thus causing me further confusion. I don't write much and it's all just procedural scripting so far.

 

[WickedWeasel]

Now that's something heavy. Now this php is something that may come handy. Will bookmark the resource. thanks pal

 

[gutterseo]

Oh what do you know, over zealous coders trying to come up with a wacky solution because they can't write their own code. Shocking! (not really)

Hey Rage9 why do you use PHP? Fuck that just write everything in C, you don't need all those inbuilt wacky functions included with PHP.

 

[uplinked]

I had to make my own wheels before they were sold in stores. I own the wheel factory and now I can make as many wheels as I want without having someone giving me the instruction manual.

That might have been cool for the last 10 years, and probably works pretty well for your purposes. You might never wind up needing more than your own wheel factory. But when someone opensources the flying car, won't you and your wheel factory be left out to dry? What about boats and airplanes, can you build those? Without OO, you'd be refitting your whole wheel factory. I simply don't think it's fair to say that your one tiny wheel factory will be able to perform to the top standard of production over the next ten to twenty years.

Learning to use other peoples code is a skill. IMO, it's my most important skill, and the one I try to hone most regularly. I build up my own library of functions so I can move quickly, sure, but the very instant there are better components available in the f/oss space, you'd better believe I'm already leveraging them.

 

[erect]

Which is exactly why I'm paying you to build my airplanes, it's outside the scope of what my wheel factory can produce and really isn't part of my core business.

 

[uplinked]

Which is exactly why I'm paying you to build my airplanes, it's outside the scope of what my wheel factory can produce and really isn't part of my core business.

Touche, sir.
Your thrusters are almost complete.

 

[Rexibit]

I prefer the teleportation pad factory. Once they're all in everyone's homes, people can get in and out and focus their lives instead of shooting up people's cars because someone cut them off in traffic or having their plane crash because a pterodactyl was reading the paper while flying and didn't see the plane's engine coming at it.

OO coding works like a teleportation pad because you build working objects. Once one's working and can accept parameters, you don't need additional parts or have to replace everything if a road gets congested or an airport terminal isn't accepting new flights. You just plug your coordinates in and BLAM!, you're there and can move on with your life.

 

[Rage9]

Hey Rage9 why do you use PHP? Fuck that just write everything in C, you don't need all those inbuilt wacky functions included with PHP.

The problem is that everything is moving to the web, and the web is much much more lucrative. I heart C. C was the perfection of languages, agile, fast, pointers, compiles perfectly to asm then to binary, ah man it gives me a hard on. It didn't really need to go any farther than that, and if that's all we had I would have died a very happy man.

 

[mattseh]

The problem is that everything is moving to the web, and the web is much much more lucrative. I heart C. C was the perfection of languages, agile, fast, pointers, compiles perfectly to asm then to binary, ah man it gives me a hard on. It didn't really need to go any farther than that, and if that's all we had I would have died a very happy man.

No reason you couldn't build a webapp in C. I argue that PHP is pretty much a web framework for C.

 

[eliquid]

why why why feed the trolls?

 

[Rexibit]

No reason you couldn't build a webapp in C. I argue that PHP is pretty much a web framework for C.

I would argue that C is just a framework of assembly. Given that PHP is just a framework of C and C is just a framework of assembly, just save yourself the trouble and build your shit in assembly.

Super fast. You'll be getting Rank 1 since your site loads in .0000000000001ms. Google will love you.

 

[uplinked]

ohai

some days, i enjoy chocolate bars, but more recently i enjoy raspberry truffles more

if you poop off the empire state building in the rain, are you causing a "shit storm"?

i wish i were two inches taller

this is a good thread

 

[DKPMO]

I think you have that backwards? most people agree cake is too fat and codeigniter is the nice lean framework.

What exactly makes CakePHP "fat"? If you need lots of different logic in your app it seems too thin rather than too fat...

Are you comparing them for building two-page sites or actual webapps with lots of functionality?

 

[Rage9]

I would argue that C is just a framework of assembly. Given that PHP is just a framework of C and C is just a framework of assembly, just save yourself the trouble and build your shit in assembly.

Super fast. You'll be getting Rank 1 since your site loads in .0000000000001ms. Google will love you.

Actually no, I wouldn't classify C as a framework from assembly. With C you get all the joys of assembly in a much easier to read fashion, there is a very direct coloration between the two. And PHP isn't a framework for C because it's interpreted and doesn't compile, although could be classified as a C framework because if you're thinking of it on that level then it's been bastardized to hell which would make it a perfect framework!

Then again I just did stumble onto this today, and I got hard, really hard.

Home - Snorkel Embedded Web Server

 

[crackp0t]

Actually no, I wouldn't classify C as a framework from assembly. With C you get all the joys of assembly in a much easier to read fashion, there is a very direct coloration between the two. And PHP isn't a framework for C because it's interpreted and doesn't compile, although could be classified as a C framework because if you're thinking of it on that level then it's been bastardized to hell which would make it a perfect framework!

Then again I just did stumble onto this today, and I got hard, really hard.

Home - Snorkel Embedded Web Server

woah thank you! almost exactly what I was looking for +rep

 

[DKPMO]

Actually no, I wouldn't classify C as a framework from assembly. With C you get all the joys of assembly in a much easier to read fashion, there is a very direct coloration between the two. And PHP isn't a framework for C because it's interpreted and doesn't compile, although could be classified as a C framework because if you're thinking of it on that level then it's been bastardized to hell which would make it a perfect framework!

Then again I just did stumble onto this today, and I got hard, really hard.

Home - Snorkel Embedded Web Server

Why not use Apache?

On the other hand maybe you should write a web server in assembly and design your own chips to have your own instruction set. Do not settle for these stupid frameworks!