|
Lumpy posted:Welcome to front end development! Eh, it's not new to me, it's just can you call something dead when a ton of people still use it?
|
#
?
Jun 10, 2016 20:53
|
|
|
|
| # ? May 15, 2024 20:41 |
|
|
Noam Chomsky posted:Eh, it's not new to me, it's just can you call something dead when a ton of people still use it? Is dying better?
|
|
#
?
Jun 10, 2016 21:24
|
|
|
Skandranon posted:Is dying better? Well, what is dead may never die, so.... Bower for King of the Iron Islands?
|
|
#
?
Jun 10, 2016 21:50
|
|
|
Pollyanna posted:Speaking of yeoman generators, what's the most accepted way to start up a new React SPA project? This would be something that only interacts with an API, so it won't require a back-end like Express or anything. Something that just compiles to static HTML/ES6/CSS and that I can just publish onto a lovely intranet Windows server or something (it's complicated). I kinda feel like starting a new react site is so simple you don't really need anything to do it for you and if it wasn't quite so simple I'd rather not have someone else's idea of a good site structure. Though, I also think that about most of the boilerplate/generators I see...
|
|
#
?
Jun 11, 2016 01:02
|
|
|
Professional development question: I sorta fell into web dev, but I'm sticking with it, and it's time to start moving on, but I know I have some holes. The site I inherited is php/mysql/jquery and I've since added angular 1&2 stuff. But the site was made by non-webdevs so it uses no frameworks, build tools, testing, etc. I've been burned before in interviews by that (why I picked up angular), so if I want to fill those gaps, what sorts of things would you guys recommend I look into?
|
|
#
?
Jun 11, 2016 04:45
|
|
|
dupersaurus posted:Professional development question: Angular 2 / React Webpack Gulp Rails or Node for server side maybe
|
|
#
?
Jun 11, 2016 04:50
|
|
|
dupersaurus posted:Professional development question: React Redux SaSS Webpack ES6/2015 Django Angular 2
|
|
#
?
Jun 11, 2016 15:11
|
|
|
Noam Chomsky posted:Angular 2 / React Don't do Rails, it is on it's way out and having "some" Rails will never get you a Rails job. C# or NodeJS are much more likely to benefit you for backend stuff. The first 3 are spot on though.
|
|
#
?
Jun 11, 2016 16:28
|
|
|
Skandranon posted:Don't do Rails, it is on it's way out and having "some" Rails will never get you a Rails job. C# or NodeJS are much more likely to benefit you for backend stuff. The first 3 are spot on though. I don't think Rails is on it's way out just because Node is currently more popular. And a ton of people will tell you not to use Node because it's just a toy and has a lot of issues. As someone who knows Ruby, Rails, and JS, and some Node, it's very difficult to decide which advice is worth following. Huzanko fucked around with this message at 19:42 on Jun 11, 2016 |
|
#
?
Jun 11, 2016 19:36
|
|
|
Didn't twitter move completely away from rails? No big companies behind it means a loss of momentum and eventual death.
|
|
#
?
Jun 11, 2016 20:58
|
|
|
I doubt Rails will completely vanish, for a lot of people it still is the fastest way to get something sellable working and migrating from it only happens if it's actually needed (SoundCloud is migrating to microservices with Scala for example, but I doubt your local business has the same needs). I would recommend learning the basics of ruby/rails just in case and then focus on something else. EDIT: Basically you don't want to be a Rails developer, but knowing how to use it will definitely help. At least around here knowing how to use the asset pipeline and other miscellaneous rails stuff is a requisite for a lot of otherwise pure frontend jobs. lunar detritus fucked around with this message at 21:11 on Jun 11, 2016 |
|
#
?
Jun 11, 2016 21:08
|
|
|
Gildiss posted:Didn't twitter move completely away from rails? No big companies behind it means a loss of momentum and eventual death. https://www.quora.com/Why-did-twitter-move-away-from-Ruby-on-Rails quote:RoR is not hard to scale. However, Scala tends to be more efficient than Ruby which translates into smaller hardware costs and lower latencies. For these reasons Twitter is moving most if not all of its backend services into Scala and/or Java. However, they still use RoR for their front end as it is easier to iterate with RoR and front end servers are typically easier to scale than backend services. quote:It's not that Rails doesn't scale, but rather, requests for "live" data in Ruby (or any interpreted language) do not scale, as they are comparatively far more expensive both in terms of CPU & memory utilization than their compiled language counterparts. Twitter's reasoning for moving away from Rails does not apply to anyone just getting started or really any app that isn't as highly used as Twitter. Huzanko fucked around with this message at 22:54 on Jun 11, 2016 |
|
#
?
Jun 11, 2016 21:44
|
|
|
Noam Chomsky posted:https://www.quora.com/Why-did-twitter-move-away-from-Ruby-on-Rails Yes, but most places that are hiring wont be picking it up nearly as much these days without a big name behind the tech. And that leads to less positions, less overall support and new developments, etc. Angular - Google, React - Facebook, Everything soul crushing enterprise places love - Microsoft. https://www.youtube.com/watch?v=a5dpBpaFiMo It's basically this, but the ending is different.
|
|
#
?
Jun 12, 2016 02:02
|
|
|
ember doesn't have any one big company behind it but still has plenty of small shops and mid-sized mature companies using it, idk (twitch, digitalocean just moved back to ember after trying react for a while, etc)
|
|
#
?
Jun 12, 2016 02:16
|
|
|
Gildiss posted:Yes, but most places that are hiring wont be picking it up nearly as much these days without a big name behind the tech. And that leads to less positions, less overall support and new developments, etc. Fwiw airbnb uses rails. Stitch fix as well. I get a couple rails job leads each week. Lots of hospital systems are using it.
|
|
#
?
Jun 12, 2016 02:24
|
|
|
Noam Chomsky posted:Fwiw airbnb uses rails. Stitch fix as well. I get a couple rails job leads each week. Lots of hospital systems are using it. Hospitals? Are you trying to scare people away?
|
|
#
?
Jun 12, 2016 02:32
|
|
|
abraham linksys posted:ember doesn't have any one big company behind it but still has plenty of small shops and mid-sized mature companies using it, idk (twitch, digitalocean just moved back to ember after trying react for a while, etc) i can't find anything about twitch trying react at all. in fact, the only mention of react is a job posting suggesting they do use react: https://jobs.lever.co/twitch/888a6a8b-3cff-4c90-b490-33852910713e
|
|
#
?
Jun 12, 2016 02:32
|
|
|
Suspicious Dish posted:i can't find anything about twitch trying react at all. in fact, the only mention of react is a job posting suggesting they do use react: twitch uses ember. digitialocean used ember, moved to react, and are moving back to ember the closest thing ember has ever had to a big company backing it is yahoo, and there's no one in 2016 going hell yeah, yahoo trusts it!! but ember still manages to do very well without big co support
|
|
#
?
Jun 12, 2016 02:38
|
|
|
Thanks for the help. Now just to think of a personal project that could make use of it...
|
|
#
?
Jun 12, 2016 03:58
|
|
|
abraham linksys posted:ember still manages to do very well without big co support how can a framework "do well" if practically nobody uses it for anything outside of pet projects?
|
|
#
?
Jun 12, 2016 04:04
|
|
|
zorch posted:how can a framework "do well" if practically nobody uses it for anything outside of pet projects? It's entirely possible for ember to be used in thousands of projects of a decent size and still not be used by the big companies...
|
|
#
?
Jun 12, 2016 05:51
|
|
|
Thermopyle posted:It's entirely possible for ember to be used in thousands of projects of a decent size and still not be used by the big companies... Nah, man, you should only use things used to build the most popular apps that have ever existed, otherwise you're a scrub, also when they switch stacks, you should definitely switch stacks, or you're a scrub. Context doesn't matter; only hype.
|
|
#
?
Jun 12, 2016 08:00
|
|
|
Skandranon posted:Hospitals? Are you trying to scare people away? I currently work in enterprise consulting in the portal space. Nothing scares me anymore.
|
|
#
?
Jun 12, 2016 08:01
|
|
|
Noam Chomsky posted:Nah, man, you should only use things used to build the most popular apps that have ever existed, otherwise you're a scrub, also when they switch stacks, you should definitely switch stacks, or you're a scrub. Context doesn't matter; only hype. my favorite part of the people who adopt this awful strategy is when they don't even stop to consider that massive enterprises have different engineering needs than new startups or small client projects. For example, Relay/GraphQL is something that made sense for Facebook because they had the resources to write their own backend to implement their own query language. It will not make sense for your tiny three-man engineering team. Heck, even Flux is boilerplate-heavy in nature because the teams at Facebook who make apps with Flux can afford to trade coding speed for the explicit nature of Flux makes.
|
|
#
?
Jun 12, 2016 08:15
|
|
|
Noam Chomsky posted:Nah, man, you should only use things used to build the most popular apps that have ever existed, otherwise you're a scrub, also when they switch stacks, you should definitely switch stacks, or you're a scrub. Context doesn't matter; only hype. Google Web Toolkit, got it!
|
|
#
?
Jun 12, 2016 14:28
|
|
|
Can someone explain why I'd want to use Gulp/Grunt/Webpack/ thing on github only installable via npm? I can't tell if it's just beyond my comprehension or just not my use case. I work on a good sized ecommerce (I don't touch the actual checkout logic aside from basic CSS). EDIT: I should mention that if using these would require a site-wide rewrite, then lol at it ever happening for where I work.
|
|
#
?
Jun 12, 2016 15:46
|
|
|
It's seriously all about what kind of environment you would like to be working in. I much prefer working with small teams and projects that are relatively quick where there's no 'but does it scale?' meetings because it's like a small internal tool for a client that appreciates finally having this tool that solves X problem for them. So my main focus is JS, JS frameworks (like ember, meteor even, Im not an angular fan really, React and Node), PHP and WordPress/Laravel. hosed with Rails a little. I want nothing to do with enterprise so I don't really look at stuff like Scala, Java, .NET, etc. edit: Basically a bunch of nerds will argue on Quora forever about what you should learn but just look at areas/companies your interested in and see what they use!
|
|
#
?
Jun 12, 2016 15:58
|
|
|
I'm currently employed as a contract front-end dev. I'm looking to improve my resume/employability in the future, and right now I'm focusing on improving the projects content on my resume. As I've mentioned in this and other coding threads I'm a bootcamp graduate, so I have 3 projects that I built myself during that particular bootcamp. One of my projects is a clone of Trello which I'm very proud of and always gets compliments during interviews. But if I were to revisit it there are tons of things I would change, such as 1) switch from flux to redux 2) refactor all ES5 to ES6 3) rewrite the CSS and use a CSS pre-processor, 4) use flexbox, 5) make it mobile responsive, etc. My question is this: is it worthwhile to put a lot of work into a past project? Now that I'm employed and have experience on my resume (also will have a site to add to my portfolio from this job), I just wonder how much it will help the next time I'm interviewing.
|
|
#
?
Jun 12, 2016 22:47
|
|
|
Gildiss posted:Angular - Google, React - Facebook, Everything soul crushing enterprise places love - Microsoft. 
|
|
#
?
Jun 12, 2016 23:45
|
|
|
n4 posted:My question is this: is it worthwhile to put a lot of work into a past project? Now that I'm employed and have experience on my resume (also will have a site to add to my portfolio from this job), I just wonder how much it will help the next time I'm interviewing. You'll want to update it occasionally, though, before you get to the point of showing off something built around jQuery in 2016.
|
|
#
?
Jun 12, 2016 23:56
|
|
|
Doing front-end development got my foot in the door to doing web development professionally, but after having worked in front-end land for ~2 years I'm glad to be moving away from it to focus more and more on the back-end. Are there there any veteran front end devs here which have stuck with it for longer than a couple of years? Any reason you keep coming back to it?
|
|
#
?
Jun 13, 2016 02:46
|
|
|
abraham linksys posted:twitch uses ember. digitialocean used ember, moved to react, and are moving back to ember I know Target is doing a bunch of new stuff in Ember. Yeah, yeah, not a big tech company whatever
|
|
#
?
Jun 13, 2016 15:46
|
|
|
I guess this is the thread to ask if anyone has tried Aurelia? At my company we're going to start a long term web project, and after assuming we were gonna go with Angular 2 we learned about Aurelia recently and thought it looked somewhat interesting. The backend will be .NET, if that makes a difference.
|
|
#
?
Jun 14, 2016 12:05
|
|
|
LOOK I AM A TURTLE posted:I guess this is the thread to ask if anyone has tried Aurelia? At my company we're going to start a long term web project, and after assuming we were gonna go with Angular 2 we learned about Aurelia recently and thought it looked somewhat interesting. The backend will be .NET, if that makes a difference. We're using Aurelia for our new enterprise product on the frontend with a .NET MVC backend. I am the lead on the client-side part of the project and it was my call. I evaluated a bunch of frameworks and did decent sized prototypes in Angular1 and 2 but bailed in favour of Aurelia. Long list of reasons, but the primary one was that you don't end up teaching other team-members a language, they're just using pure ES6 javascript. They don't have to "learn angular", or take a course on Angular 2 nomleclature. They just need to know standards. That's incredibly important for us as the team grows as it means you don't have to uptrain people, they can use what they already know. For our project (we're starting with a small core and building up progressively), this is perfect as we don't have to hunt developers who know React or Ember, but just know JavaScript. There are a bunch of other reasons like speed, efficiency, clarity and the like, but being pure javascript and html standards was what sold my technical architect from day one. When you're building enterprise poo poo (as we've found building for SharePoint) getting new developers who speak whatever crazy language you chose 10 years ago is a terribly difficult chore most of the time. You end up getting someone who knows something similar, but that's about it. Training is a huge factor and Aurelia takes a lot of those headaches out of the way.
|
|
#
?
Jun 14, 2016 22:39
|
|
|
Plavski posted:we don't have to hunt developers who know React or Ember, but just know JavaScript. Just using React without the typical surrounding ecosystem isn't much of a learning curve. We just brought on a junior dev that was pretty much up to speed with it in a week.
|
|
#
?
Jun 15, 2016 02:41
|
|
|
Yeah I consider the fact that react is almost completely vanilla JavaScript to be one of its major selling points, especially for a small team like mine.
|
|
#
?
Jun 15, 2016 05:14
|
|
|
Chenghiz posted:Yeah I consider the fact that react is almost completely vanilla JavaScript to be one of its major selling points, especially for a small team like mine.  BUT JSX!!!
|
|
#
?
Jun 15, 2016 14:45
|
|
|
JSX looks enough like ES6 that if you can't just pick it up, you're probably not going to be able to get up to speed with anything outside your comfort zone in reasonable time but that's 
|
|
#
?
Jun 15, 2016 16:11
|
|
|
Munkeymon posted:JSX looks enough like ES6  Except that it doesn't look like JS at all and isn't supposed to.
|
|
#
?
Jun 15, 2016 20:30
|
|
|
|
| # ? May 15, 2024 20:41 |
|
|
Maybe he's thinking of the lesser known JSX? http://jsx.github.io
|
|
#
?
Jun 15, 2016 21:14
|
|