4 ms·
about JavaScript, CSS, and HTML basics ...and this is where it goes off the rails; teaching JS before HTML is how we will continue to have the ridiculous proli
by userbinator 5y ago
about JavaScript, CSS, and HTML basics
...and this is where it goes off the rails; teaching JS before HTML is how we will continue to have the ridiculous proliferation of app-sites that shouldn't require a single line of JS instead needing the latest version of $browser (you have a choice of browser - pick one ...) to even show any content at all. Forms don't need any JS to work, yet the impression this gives to beginners is that they do.
https://news.ycombinator.com/item?id=25915313 https://news.ycombinator.com/item?id=25915313
But then again, this is Microsoft, which is now firmly in bed with Google in contributing to the Big Browser monopoly, so I suppose I shouldn't have expected anything else. The agenda is obvious to anyone who cares to look.
- davidelettieri 5y agoLooks like the first few lessons use Javascript to give an introduction to programming and not to web development in general. I don't see any agenda. Just teach programming on the language a web developer will happen to use later.
- KronisLV 5y ago> The agenda is obvious to anyone who cares to look. Alternatively: it's just teaching whatever is popular in the industry, for better or worse (similarly to how DevOps people would be taught Kubernetes, even if it can be horrible in certain cases and for smaller projects). Many sites out there don't need JS. Server side rendering would suffice. And many other sites out there would be well served with minimal JS for enriching a few forms. Yet, that's not the reality that we live in. The reality is that the majority of the developers out there will simply have to deal with lots of JavaScript, TypeScript and frameworks like Vue, React, Angular (i'm using the term "framework" here because they change the entire direction of the development of your front end, not that it matters at all). So, that's what curriculums will focus on, since clearly people want to have good employment prospects. It doesn't seem like the linked one gets too caught up with the frameworks, though.
- dgb23 5y agoBut to master JS tools you want rock solid fundamentals and know about default behavior, writing clean HTML and CSS. I even teach more about networking and HTTP than JS. They actually want to know: what happens when I type an url into the browser?
- serial_dev 5y agoWhile I agree with you that knowing the basics is obviously helpful and desired, in the end what gets you your first job isn't "what happens when I type a URL into the browser". What gets you your first job is you knowing how to use the tools that the companies already use to ship software solutions on the web. If they use react, webpack, graphql, then your best bet at getting your first job is learning enough about those to be productive in a couple of days at the company, and not what happens after you hit enter in the URL bar. 95% of my work as a regular web/mobile dev was about being able to fetch some data, massage it, display it, then handle user interactions to send something back to the server. Some software dev jobs are more complicated than that, but to be honest, most of what we do it not rocket science. Once you get your first job, you can work "backwards", and learn the basics. This approach also helps you learn what is important as you see it firsthand that it's important. Your team is there to help you learn, you earn money in the process, you make your customers' life easier, and you build your portfolio and gain experience to get your next job (that will hopefully be more challenging than a CRUD app). I'm not saying that it's great that you learn the tools before the basics, I'm just saying it makes sense if you want to get a job and pay your bills (and set yourself up for long term success as you learn on someone else's dime.
- bhobs 5y agoThis view that you don’t need JS and can do most things natively is tired and screams of old timers trying to cling on to the past, when web pages didn’t have rich user interactions and good UX. Sure, you can build forms that perform full page refreshes, but ajax requests offer a better user experience.
- uallo 5y agoNative dropdowns have much (much!) better UX and accessibility than most custom dropdowns built with JavaScript. Same goes for native form validation. And there are many more examples. Using JavaScript does not necessarily improve UX. Use the platform where it makes sense. Extend it with JavaScript where needed. Make it work for everybody and make it better for capable browsers. That is called progressive enhancement. OP did not say that you may never use JavaScript. Just be mindful about it when you do.
- amelius 5y agoYou can say the same about computers in general. No computer is preferable over having to use one.
- krono 5y agoWhen someone has just barely crossed the "hello world" stage, I don't think they should be thinking about asynchronous XHR requests, or be pulling up user experience research to find the optimal shade of red for making input validation errors appear less aggressive to middle aged women with a bachelor degree in communications who are part-time employed in marketing. Let's start with getting data from the form to your back-end, and once we've got those must-have basics down, then we can start introducing the nice-to-have bits.
- bigDinosaur 5y agoI consistently have a more pleasant time with the well-designed, minimal JS websites (which are now a rarity) than even the better designed websites which heavily use JS. And my job is allegedly to 'improve' the internet with more JS.
- 5y ago
- legopeice 5y agoPlease could you inform me how you would build a form that creates, lets say a secondary loan for a company with attached assets. The assets could be zero, or many. How would you create this form without Javascript? Would you require a user to create the assets before the loan? Saying that HTML provides everything a developer needs to provide an application to client is so ridiculous, I have no idea why this sentiment is so popular. the vitriol expressed for front end devs from the community seems out of place. Forms work without JS for the most basic baby forms. the moment you go enterprise, more is needed. which is where JS steps in, What am I missing here?
- e12e 5y agoYou would make multiple form, and track state on the server side (user createdvempty/wip loan, user added assets, user reviewed and confirm loan). Probably share state between client and server via a session token (cookie). Optionally share some state via REST - eg loan ID and asset IDs in path). That said - complex forms is a typical example of when you might want to move from a web "page" to an "app".
- legopeice 5y agoShare state? I disagree heavily. There is no reason for the backend to know how many assets a user is trying to add to a loan, or delete, or accidentally load, or add but realize mid-way that it doesn't apply. Do you belive the backend should know about human incorrect input and track state? What if a cat steps on a keyboard? every addition to a form is a page reload and a query to the server. then the server sends a response. Which is exactly the bloat everyone seems to go on about. Im sorry but living in a world of enterprise apps, the sentiment that JS is a poor language and a bad choice is both out of place and highly de-coupled from real-world usage.
- e12e 5y agoYou need to share state. You might only store finished loan applications server side, but often it's nice to allow a user to pick up where they left off. Or keep a list of started, not finished applications, to hand over to sales. Etc. But sure, application state might not go in the same db/schema as completed transactions.
- escape_goat 5y agoIf one wishes to teach web development, one teaches JavaScript. That's the end of the story.