Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Somebody asked on how to get started on Full Stack web application development.
This is how I got started.
Client side Web Application Development:
---------------------------------------------------------------
• Start with basic HTML, CSS and JS, JSON. For quick learning, see W3Schools for these topic or YouTube it.
• Get a local web server. "200 OK!" webserver chrome extension is a good start. (https://chrome.google.com/webstore/...)
• Learn Chrome Dev Tools to debug the pages. YouTube it.
• Get a good IDE. I am very happy with VSCode. You can use it for very serious WebApps.
• Start learning JavaScript language in depth, but just related to Web Browser related topic or you would get sucked in server side too early.
• Install node.js. Learn NPM package manager. Learn basic node commands.
• Learn complexity of JS file referencing, JS modules in browser. Just learn, don't use it yet, to understand the benefits of code bundlers.
• Learn Webpack code bundler.
• Learn how to make you simple site much faster and using in Mobile using "Progressive Web Apps".
• Now learn to make modular UIs. I love React. Focus on getting the UI code modulear. Create Single Page sites. (You are not there yet to create a Web App) “Create-React-App” started kit is a good starting point.
• Learn to create multi-page site using React-router.
• Learn application state management using Redux.
• Learn to create application decision engine using Redux-Saga.
Practice and master each stage.
Along above, learn git / GitHub (to learn from others code), find good web resources like Medium / Smashing magazine, good YouTube channels etc. I subscribed to some popular Udemy courses too.
Server side Web development:
------------------------------------------
:) First learn client side Web Application development. Server side learning is another story.3 -
Dear fellow JS devs, if you make 1 more good damn module loader I swear to god....
Hi - here's a new module bundler named parcel.
FFS3 -
How to kill a laptop in two steps:
1. Run React Native metro bundler
2. Run debugger
and a 16GB core i7 laptop on Ubuntu will leave this life :)2 -
Just created a custom html, css, js bundler to bundle all my files and minify it to a single file.
Development will be a breeze right now.2 -
Theres so many motherfucking command line utilities in web development that I'm surprised there isn't a 128 megabyte NPM install for a leftpad CLI.
God damn people who develop tooling for web development are some navel gazing cunts.
"How can I feel more self important? Lets put a CLI in front of this web bundler!"
Dumbasses.
What happened to the days of purity? Of cleanliness? Of kosher compliant web development, where all you had to do was include a script tag?
Gone are those days. Welcome to Babel(on)!
I put a CLI in your CLI so you can masturbate while you masturbate!3 -
React Native so far today:
1. need external dependency to load svg
2. react-native link doesn't work as it should
3. metro bundler not updating its cache
I wonder if the list will grow or that's it for today... -
I've learned webpack over the past years. It was a tough road.
Then I tried parcel....
.... I hope I'll work on a big project someday, to actually use my hard earned webpack skills again. -
@ everyone who keeps pushing Vue via node
Vue via npm:
- shit
- bundling so you can save 15% on car insurance
- webpack/etc to condense your 50TB node_modules folder
- have to deploy, if you're in the US then it'll probably be in the middle East or maybe North Korea if that falls out
Vue via script tag:
- works awesome
- pretty feckin fast
- can be deployed purely static
- easy debugging from dev console
- easy templating for frontend
- can use existing html/css
- easy to work in teams with people without having everyone install npm
- if you have a designer they will love you for making it easy to style things
- you can cache it and make it offline without any of the new bullshit vuex
- you can use vanilla libraries without a mixin, polyfill, bundler, or etc anus -
The webpack production mode can't even recognize destructuring. It can only naively replace literal occurrence of process.env.NODE_ENV.
What is this? A f'ing template engine?10 -
Didn’t think I would run into issue because I was using Apple Silicon macs - something borked my ruby gems installation, and reinstalling made matter worse by Bundler installing gems that apparently linked to whatever arch they liked. Now if I run bundle exec there was that one f*<king gem that died of mismatching arch until I intervened.
-
How much of a fucking faff is it trying to deploy a rails app to ElasticBeanstalk?!
Brand new instance and it's got no fucking clue what Bundler is, installing gems (looking at you, Nokogiri,) is about as difficult as pissing stones and don't get me fucking started on Webpacker and asset pre-compilation.
DEPLOYMENT SHOULD NOT BE DIFFICULT.2 -
Fuck you XCODE !!! Keeps crashing
Fuck you REACT NATIVE!! Refuses to fucking start metro bundler
Both must burn in hell right now!1 -
Gonna excavate a gem, polish into a Shiny RubyGem! Even if it becomes a shoddy idea later, I'm sure gonna enjoy the bundler. With those adventurous minitests, rake made my life soothing itself!
https://github.com/mash-97/shpg
Top Tags
Weekly Rant
View