Gildiss posted:

We almost had to develop exclusively on IE at Bank of America after an IT director saw a dev change a dollar amount using the dev console. He issued an order to force all devs to remove Chrome.
There was obviously push back but I don't think he got called a retard which is unfortunate.

Gildiss posted:

We almost had to develop exclusively on IE at Bank of America after an IT director saw a dev change a dollar amount using the dev console. He issued an order to force all devs to remove Chrome.
There was obviously push back but I don't think he got called a retard which is unfortunate.

Gildiss posted:

We almost had to develop exclusively on IE at Bank of America after an IT director saw a dev change a dollar amount using the dev console. He issued an order to force all devs to remove Chrome.
There was obviously push back but I don't think he got called a retard which is unfortunate.

ROFLburger posted:

I don't get it. Could you not demonstrate to that person that you could do the exact same with with the IE dev tools? Or was this at a much earlier time

fletcher posted:

I was following this tutorial for Django + Webpack: http://owaislone.org/blog/webpack-plus-reactjs-and-django/

Things seem to be working well but I've got a ton of ./assets/bundles/main-[hash].js files accumulating now as I'm making changes. Is there something that is supposed to be cleaning this up?

Helicity posted:

Your build script should have a clean step to start with a pristine, empty dist directory.

Sample package.json:

code:

"scripts": {
    "build": "npm run clean && npm run copy-assets && NODE_ENV=production webpack",
    "clean": "rm -rf ./dist",
    "copy-assets": ". ./build_scripts/copy_assets.sh",
    "dev": "npm run clean && npm run copy-assets && NODE_ENV=development webpack-dev-server",
    "test": "mocha -r preMocha.js 'src/**/*.test.ts'",
    "test:coverage": "nyc npm test"
  },

fletcher posted:

But if I have webpack in watch mode while I'm developing and it's recompiling every time I make a change, am I just supposed to run the clean command periodically?

ROFLburger posted:

I don't get it. Could you not demonstrate to that person that you could do the exact same with with the IE dev tools? Or was this at a much earlier time

COOL CORN posted:

Another question. If I'm separating my concerns, and having Nginx serve the frontend portion of the site, and Node running the backend of the site, how would I handle something like page login? If Node isn't dynamically generating the pages, I'm not sure how to check for login status.

Skandranon posted:

Usually, you do some sort of REST request to perform the login, and this returns a token. The token is then passed into subsequent REST requests that require authentication. You can also have the login request return some sort of user object that the UI can use to enforce things on the UI side for the sake of better UX.

geeves posted:

Is there a stand alone library that's similar to Angular Translate? Like how axios is a stand alone version of $http?

COOL CORN posted:

Ah, thanks. I'm used to Django which takes care of all that itself, so I have some reading up to do

Maluco Marinero posted:

http://i18next.com/ is my port of call for Javascript translation.

porksmash posted:

I'm using json web tokens: http://www.django-rest-framework.org/api-guide/authentication/#json-web-token-authentication

Kekekela posted:

I was taking another look at Vue today for a small project that I want to knock out this weekend. Every time I come back to checking out a framework like this however, I'm kind of struck by one big thing:

Now that React has happened, I pretty much feel like having a programming language handle templating is superior to having a templating language handle programming, if that makes sense.

Anyone else have an opinion one way or the other on this?

Helicity posted:

Speaking of, I've been asked which books I consider essential for any fullstack developer. I've come up with the following list, and would love to hear feedback:

Helicity posted:

Pro-tier: use the nginx http_auth_request module to talk to an LDAP or similar service, or use an oauth proxy like https://github.com/jirutka/ngx-oauth. Then your app doesn't care about authn/authz - it's all offloaded so you can put multiple sites/APIs under its aegis and don't have to duplicate auth logic, and allows you to squeak out more performance from your apps.

Helicity posted:

Yes, anytime you can leverage an extensively used/tested/proofed piece of hardware/OS/stack/library to provide automation and guarantees, you are practicing the informal art of design by guarantee and making your code better and your life easier. You just discovered the beauty of code generation, as React is essentially a code generator that transforms in-memory objects to HTML that is spit out onto a page. I'd highly recommend this book to touch on these concepts more: https://pragprog.com/book/tpp/the-pragmatic-programmer

Speaking of, I've been asked which books I consider essential for any fullstack developer. I've come up with the following list, and would love to hear feedback:

• The Pragmatic Programmer - helps you think about how to write software in a more maintainable way and prevent headaches.
  
• Clean Code - If you struggle with how to organize code, name variables and classes, when to write comments, how to style your code, this is your book.
  
• The Art of Unit Testing - If you aren't writing unit tests and writing them *well*, your code is already legacy.
  
• Patterns of Enterprise Application Architecture - A small section on when/why to use patterns, and then a huge reference section on each pattern.
  
• Service Design Patterns - Most full stack devs need to write services/APIs, this is the bible for that.
  

edit: the top three apply to pretty much any developer, including people that only stay on the front-end

porksmash posted:

That's neat, but Django is my auth service and I'm assuming that other guy's too.

Kekekela posted:

I was taking another look at Vue today for a small project that I want to knock out this weekend. Every time I come back to checking out a framework like this however, I'm kind of struck by one big thing:

Now that React has happened, I pretty much feel like having a programming language handle templating is superior to having a templating language handle programming, if that makes sense.

Anyone else have an opinion one way or the other on this?

ROFLburger posted:

All languages are bad

PlaneGuy posted:

all languages are ok. all programmers are bad.

PlaneGuy posted:

all languages are ok. all programmers are bad.

Lumpy posted:

All languages are bad because they were written by programmers, who are all bad.

Rasmus Lerdorf posted:

I'm not a real programmer.

Munkeymon posted:

Munkeymon posted:

Helicity posted:

I want to agree with languages being good and programmers being bad, but I've never seen good PHP or VB. Sometimes language decisions are just so garbage, you can't escape

(programmers are still bad)