waddup my brudda

Hey! It's Steve Terry!

How are the kids?

I did, too, which is why I started doing it again. Ignoring responsibilities leads to greatness!

... and if I end up in a ditch somewhere, you can thank anto80 and all the cool stuff he's been doing.

Yes! Actually he does now! He just briefly mentioned it a few weeks ago but never elaborated.

Same here. But I'm working in Rails now (living in Toronto). I'm only about a year out from getting PR in Canada :tada:. Have also been working on RESTful stuff, but I'm purely backend, which is really nice actually

Wow! My hometown is Ponca City, which was only a few miles from the epicenter.

Heya Steve! Sounds like we're working on similar projects.

I'm developing a web based app for our existing software. We already have iOS and Android apps (built using C# and Xamarin). It's basically a niche market CRM with extensive payroll/billing/scheduling/hr/etc components. The backend is primarily stored procedures in SQL, so I have a C#/MVC application for the backend, but I find I'm primarily making REST requests and living every day in JavaScript... if a person can even call that really living.

We've shy'd away from the Angular2 components of the framework we're using because when we first started the project it was in too early of a stage.

I'd have started in TypeScript instead, and plan to switch to it, but I don't know it yet.

JavaScript is actually a really cool language. You just need to familiarize yourself with it's strengths and cool features, and learn it's "gotchas" and define styling and code standards (your own or company level) to avoid the gotchas. That said, I highly recommend you avoid developing a JavaScript-heavy site. For one thing, it's more difficult to debug JavaScript, and because it runs on the client you have anywhere from 3-n clients to test it with to ensure it works (unless it's an Intranet site and you can define a single standard). For another thing, overly complex JavaScript applications are usually so complex because you're trying to do multiple things on one page without reloading. This gets complicated because many parts of the system may interact in weird ways. Also, without reloading the page, the browser doesn't get an opportunity to reclaim leaked memory from it (circular references and the like can lead to memory leaks, not to mention browser bugs and the like). In general, using pure hyperlinks and <form> tags more traditionally ends up being far easier than a JS-heavy site. Less code == less bugs.

/2cents

Good to see you, Steve.