Galang: Funny how we’re stuck writing applications using a glue language.

Lovett: I thought for a second “a lot of people use it, it can’t be bad”, but then I remember that PHP is also the most widely used backend language, so heh

Steffen: A lot of really popular things are ****

Orlow: When I hit a button in FF and a javascript function is triggered, can I check which one is triggered ?

Steffen: Not just in programming, but in general

Lovett: Well, 90% of everything ****s

Gerberich: Lovett, Angular is decent enough, but read up on the difference between Angular 1 current and the upcoming Angular 2.

Nault: Doing: in the Inspector, click the ev next to the element

Gail: Or just get onto npm and start writing code because you’ll spend a week figuring out the specifics to the framework you choose to adopt

Gerberich: You can write so that your Angular 1 app will be easy to convert, or you could use ng-controller.

Beckum: Nault: oeh let me check

Gail: And then when something goes wrong you’ll come here asking for help and nobody will really know how to help you

Lovett: I expected the front-end world to be smaller than the back-end world. You guys also have tons of tools I’m going to have to learn about :

Gerberich: But yeah, you don’t really need a framework.

Gerberich: Lovett, Get familiar with Gulp and S***. They will be some of your best friends.

Lovett: Gerberich: so why do people use them?

Gail: Prototype, add rigidity as you go, modularize as things grow out of control

Galang: Lovett: Frontend is a difficult and sometimes more than a lot of backends.

Gail: Lovett: the benefit of a framework is when you already know your specific needs, and the framework aligns with those needs

Galang: Any monkey can write backend CRUD apps.

Lovett: Well I’m aiming for a dumb backend

Hunsberger: Nault: thanks my friend!

Kimmons: Now I need to kiss you

Gail: Lovett: by standardizing on a frameowrk that aligns with your goals you can hire new developers on that are familiar with this framework and they’ll, in theory, have less of a learning curve

Lovett: Gail: I don’t know what I need

Gerberich: Lovett, Many people use frameworks because they were buzzword that they got their job with.

Lovett: I won’t until I write the whole app

Gail: But if you don’t know your goals, a framework chosen at random is generally just going to be a lot of technical debt that you need to pay off later

Nault: Doing: you’re welcome

Pageau: Gail: paying off debt as late as possible is how you manage debt

Galang: Gail: It’s a lot worse if you try to build your own thing without having good frontend foundations.

Gail: Which is why I suggest just starting simple, start writing pieces you need, pull in modules that make your life easier. npm has hundreds of thousands of modules that help solve all sorts of differnet problems

Gail: Rcyr: If you don’t know which foundations you need, that just makes no sense

Gail: Dunk: unnecssary extra debt is what I was talking about

Steffen: I think i agree with Gail but i think even small modules are also technical debt you should avoid where possible

Gerberich: Tcsc, Even moment.js?

Gail: No dates in JS ****. you should pretty much always moment.js haha

Lovett: Dates **** on every single language I’ve tried

Steffen: Gerberich: never had to use it

Knoepfler: We should stop using dates

Steffen: I also like, never deal with dates really

Mccurtis: Dates are technical debt we should avoid

Elsasser: Well, dates **** even outside of programming, really

Mantis: Calendars are hard and no one has ever gotten them right