HTML markup of the whole template

Toby

neptronix Not to revive this discussion which I think has taken its course... but just a note for interest:

I was just nostalgia-reading through the old esoTalk blog and it seems back in 2011 I said almost the exact same thing as you:

I'm not a big fan of dependencies. When I make software, I like to have complete control and understanding over everything I'm working with—that's just the way I work as a programmer, I guess. Perhaps it's a flaw. Perhaps not. But for this reason, I chose not to use an existing PHP framework.

And then a short time later, as the sole maintainer of a piece of software powered by a custom pseudoframework, I wrote this:

So, what did I do wrong? To summarise it in a few words: I reinvented the wheel. Many times.

When I rewrote esoTalk, I wrote it from scratch, using no frameworks and no libraries. I wrote all of my own code to do things—database, MVC, session, JavaScript, etc.—when there was already code out there that was free, open-source, actively maintained, and most importantly, better.

Why did I do this? I had some kind of prejudice or bias against frameworks and code that other people wrote. I shallowly assumed that all PHP frameworks were big and clunky like CakePHP, and I didn't want to have anything to do with them.

Pirat

Toby Toby, why is the white screen loading in my mobile version?
Another second question. Maybe it is better to use template building via html instead of javascript.
I mean, this code is not convenient.

todo.view = function() {
    return m("html", [
        m("body", [
            m("input"),
            m("button", "Add"),
            m("table", [
                m("tr", [
                    m("td", [
                        m("input[type=checkbox]")
                    ]),
                    m("td", "task description"),
                ])
            ])
        ])
    ]);
};

it's just tear your eyes out

Happy New Year!

neptronix

Toby Thanks for getting back to me.

Interesting that you went full circle. Since this conversation, i read 'php the right way' in full, but i still have some objections to certain practices in modern php development. It may be due to a lack of experience with say, working in a team; thus not understanding the value of them.

My framework has not bitten me yet, but then again i am a single programmer working on a very large project.

I think the conclusion is that i don't understand working in a team, and should get to working with one ASAP if i want to continue to write code in PHP that others understand.

As for my choice of forum software for my big project, i've ruled out flarum for the time being, due to what it would require to patch on the functionality the community needs. But am still keeping an eye out on the project.

luceos

I think every developer reinvents the wheel at some point in his career. Whether that's a complete framework or pieces. We all believe depending on the code of someone else has more drawbacks than benefits. In fact my multi tenancy package way back was a custom php framework too and now it's "just" a package for Laravel. More powerful, more secure, less bugs, less maintenance and not reinventing the wheel, engine, fuel and car.

« Previous Page