Getting annoyed by the framework made by school which we had to use. We werent allowed to use Laravel or other frameworks.

What did I do with a classmate, we expanded on the schools framework. Added a templating engine, improved routing, made a query builder and a few other things before startimg the real project. 4 weeks of building the framework to build the application in a day.
Where others were still using the schools framework were strugglimg and not able to make it.

Gotta love well meaning juniors with completely misplaced intentions.

Nathan: "Hey, do you want a quick 5 minute demo of the code we've changed to move to library version x?"

Almond: "Sure (I wasn't that fussed about moving to library x, but he seemed determined and there's some nice to haves with bumping the version, so we approved it.)"

Nathan: "Cool, so we have this built here, and..."

Almond: "...wait, that's not our CI system!"

Nathan: "Yeah, so I moved to a new CI system too because we couldn't get that working in the old one"

Almond: "...right, we'll need to discuss that, because..."

Nathan: "Sure, we also moved the templating engine as well as there were more examples using this one with library x"

Almond: "...yeah, so I don't think we're looking to switch the templating engine because..."

Nathan: "...and you guys also need to change a bunch of your code as it's all broken since we put the new version in, most of the tests fail..."

Great... so we've got a branch that breaks a bunch of code, switches the templating engine to one we don't want to use, and switches the CI to the one the company is trying to actively migrate away from...

Almond: "We're going to need longer than 5 minutes. I'll put something in the calendar."

🤦‍♂️😬😠

Dear devRant,

I know you will hate me if I do this, so please set me straight,

I have urges...

Urges to create my own, fucked up flavor of markdown....

and worse yet.....

to make it a JavaScript templating engine.................

and publish it to NPM......................

I know you can do it. You can stop me before I commit this atrocity.

Me, starting this project: "im gonna use a templating engine so i can effectively generate files"

Me, now: "this could have been done by a string replace"

This is not a troll q, im gebuinely interested.

What sets spa frameworks (say react) apart from a templating engine and some dom fuckery? To me it seems they are all just syntactic sugar on top of these two very basic things (plus routing), but admittedly im not a frontend dev so im asking more experienced people here.

JavaScript templating libraries are such a joke.

Either they:

- Totally change the syntax of HTML (Which? would make them? Not a templating engine? But their own shitty markup language?)
- Are already deprecated (And the new version isn't done yet!)
- Both

After creating my own PHP MVC framework with Twig as templating engine, everything is now so simple and so fast, I juat cant belive how much I understand now. The development is just so smooth, you know exactly what to do all the time... And for my simple project, it does not even hurt that much to use PHP (and its even strictly typed 7.2, so not that bad). I think that I am in love. ❤

Why the fuck nobody talks about Multi-page apps?! We went from a Web where everything was Multi-page server-rendered, and now everything for Web developers is "Single-page apps".

What about websites who can't do that? Not everything can be a single-page app. Only my uncle's restaurant website, or something which is TRULY a full app. No half choices.
If your website is a multi-page app/portal which actually PRELOADS data, instead of doing 100 fetch to an API within a page that is full of loading bars, well, your life is a pain.
When you want a first contentful paint which isn't a white page, well, your life is a pain.
What are React, Vue, Ember, Angular (let's exclude Svelte and Marko) going to do about Multi-page apps and SSR?

React-router sucks to me. It's performance is weak and it's useful only when you have an SPA with multiple sections which can be treated as pages (e.g. A single SPA divided in tabs).
Server-side rendering is the worst pain ever made by humanity, in React (and prob Vue, I didn't try but I can bet). And even when made easier from libs like Svelte and Marko, I (personally) can't get it to be faster enough compared to a traditional website without a JS framework and with a templating engine.
Anyways, if there's anything that I learnt from React, is to stay away from Next.js. Perfect, beautiful, mess.

All JS frameworks just seem to bloat the code and make it worse and slower, even though they're REALLY helpful.

Why? Why everyone loves them if their downsides are so clear? Why 3 projects out of 3 I made (1 React SSR, 1 Vue, 1 Marko SSR) are and will stay painfully slow and bloated, full of shit, even if in 2020 we should have evolved with the famous three shaking, with the famous lazy loading, etc.?

I am just frustrated.
And let's not even talk about Webpack, Rollup, Lasso, those module bundlers shit which are harder to configure and understand than finding a needle in a haystack.
Lasso was the easiest to configure but I anyways can't understand it. Webpack seems it was made to handle SPAs, as any tool in this freaking world, and not even considering an easy way to integrate multiple bundles for multiple pages (I know it's pretty easy, but with component sharing between pages and big unique bundles Next.js handles it soooo bad it feels like hell).

Am I the only one?

Sorry for the long rant. I just needed to rant right now.

Jinja2 is so awful compared to simple and elegant erb, but you can't go over python whitespace limitations.

To the guys that develop any form of hybrid applications, is there literally no js templating engine that accepts template files as its base? I could write probably a single file that just returns the template and then all the others request it before templating, but seriously, is there no ready to go solution?

When I wrote a templating engine (great overstatement) just for myself to learn, I had this bug in php5 and regex that would crash the whole apache server.
Literally nothing worked and I didn't know why. After rebuilding everything I tried with regex using only simple string manipulation all of a sudden everything worked fine.

I nearly never actually had to code for an interview, since I decided not to work in the gaming industry. Only ever I can recall was them asking me to define a templating engine / Syntax of my dreams.

What's the general Software Engineering rule of thumb again for frontend templating code?

If I look at certain websites, I notice some code smells in PHP such as:
$.modal = <?php echo $(base)["username"] != 'me' ?' ': echo 'style="display=none"' ?>

or just in general places in the code where PHP gets used as a templating engine for gluing together pieces of HTML code based on conditionals spread out over the codebase and the database itself too. To make things worse, this carries over to JavaScript ajax functions. As a developer, this to me just seems like spaghetticode.

On the other hand, many popular frameworks properly do templating, such as EJS, containing templating in one place and not mixing it with logic too much but just having simple output like <%= %>.

I know I've seen frameworks like Angular 1 contain pieces of HTML into directives, but maybe that's something different, more 'OO'-simulating or cleaner.

Need to create an internship portal for students and companies to register, sign in, post internships, apply for internships, browse internships and a minimal admin panel, for the entrepreneurship cell I'm college
(cuz the guy who was supposed to do didn't do jack shit in three months, so I have to make a quick one in three days)

Any suggestions on what should I use?
My current options are PHP and Node-Express, but I'm not fixated on either, and the minor details like the templating engine, how to store data, how to implement authentication etc...

Recently attended an interview. The guy was some random company consultant. Job description was for spring-boot (also required templating engine experience). He was asking me whether I know angular and JEE (completely different and kinda opposite of the job desc). That's a bummer but good thing I've messed around with these once or twice so I know whatsup.

Also, who the fuck has already got 7 programmers and wants to double up to 14 by only adding university students to the team (after teaching them angular and jee for a month, but whatever, its only a fucking month), in order to complete a new project with tight deadlines?

I don't think I'm sticking with this one...

I love laravel. But I hate blade as it's templating engine. Why didn't they choose pug. Its so much more readable. I know I can have it by packages. But I would rather see it as the default.

HTML: Tags. I fucking hate them. Yes, Emmet makes it fast and simple to create them, but when restructuring or deleting things it becomes a mess every time. And I cant use a templating engine (i think it's called) at work, also I havent found one that I like.

CSS: Trying to apply CSS to Angular Bootrap Components. Everything has a shadow dom + a lot of things are ! important for some fucking reason.

Hi guys i m new to js, could u guys suggest me templating engine which i can learn quickly.

Undocumented thymeleaf secrets fuck you.

Its a templating engine