4 ms·
Well, I think that compared to other fields, it's quite hard to get on board - there is so much tooling that it's really hard to catch up. There is node, npm/ya
by iansowinski 9y ago
Well, I think that compared to other fields, it's quite hard to get on board - there is so much tooling that it's really hard to catch up. There is node, npm/yarn, webpack, gulp, scss/sass. If you're back-end dev coding in ruby, you just pick rails and you're done if you're python webdeveloper, you pick django, and so on.
With front-end? After hours of fighting with Babel and Webpack, you can pick Angular, React or Vue. And it's hard to know witch one to choose if you're some beginner who just want to code efficiently.
- shados 9y agoif you make a simple backend thing, pick up rail and you're done, but you're essentially building something that's a solved problem. The frontend equivalent is dropping a script tag on a page and uploading it by FTP. But there's a reason backend communities accepted devops long before frontend. Between all of the various BE platforms, all with their own dependency management intricacy, all the various databases, big data stores, queues, streams, object stores, cache systems, containers (docker, VMs, etc), the OS (for FE you can just drop your stuff on S3 and stick a CDN in front and it will scale to near infinity...try to scale your rails app like that for giggles). BE is 100x worse.
- iansowinski 9y agoYes, but STARGING in backend is easier. I don't try to say that FE is harder, just that this wall between beginner and modern standards is higher here. After this wall it's probably harder in BE that in FE, but I think this wall is higher for FE devs.
- deleted 9y ago[deleted]