Though, I think a lot of these people might get a rude awakening when they realize what they actually dislike is the DOM and CSS, not js itself. It just allows people to re-use their knowledge to develop for the web. Projects like Blazor allow devs who are already productive with one stack be productive elsewhere. Webasm has some advantages native JS will probably never have, like being in a binary format and streaming compilation.
Reactxp peer dependencies code#
For example, what do you think this code will do?. Javascript also has some quirky parts of it, that, much like PHP, make code unpredictable if you're used to programming in another language. They've probably interacted most with legacy es3/5 with callback hell and such, which doesn't leave a good impression. Most of these developers also aren't aware of what modern js looks like and how nice things like es6 modules are. You can see this pretty clearly with people who felt forced to use coffeescript, typescript, etc. If a developer does not like javascript (for whatever reason) and is still yet forced to work in it, they will end up resenting it. And because it's a spectrum where a lot of the former group gradually tries to grow into the latter, it can sometimes be difficult to tell who you're talking to. it's hard to filter out either category of people and because of the easier on-ramp to being a "script-kiddie" the former group tends to be larger, so it can be easy to see all of these people who are using the language in tiny ways and with bad practices as a reflection of the community or the language's actual capabilities, even though that's not the case. When you're looking for books, tutorials, scripts, advice, libraries, etc. They can engage with JavaScript in a rigorous, scalable way.
Reactxp peer dependencies software#
Other people are programmers who write large programs and have experience and education in software engineering, algorithms, programming paradigms, security, the DOM, HTTP, etc. They might not think twice about bloated libraries from untrusted sources or pervasive bad practices that are prone to errors or poor scaling. For these people, they might be doing dumb things without really understanding them and they do engage with the language a lot more like a "toy" language. Some people are non-programmers who mainly work with HTML and CSS and they are looking for quick and easy one-liners or things that they can copy and paste to let them do a few things that are just out of their reach. I think part of what explains what you're saying here is that JavaScript is a language that can be engaged with on many levels. Now adding HTML, CSS, and JavaScript to my arsenal has been an experience and to be frank learning these three has made me more proficient in the other languages.īut everyday I am learning that there is a purpose and tool for everything and picking the right tool even if you have to learn a little bit is always best. So the languages I used were: Python, Bash, Awk & Sed (I count them as languages haha), SPL, SQL. It use to be all cli, scripts, automation, queries, etc. The big thing was I never did things with a UI before this. About a year ago I got a job that has me kind of wearing many hats, so I picked up React for a front end project, found out i really needed to learn JS and ended up kind of falling in love haha. I started learning with python a while back and could never get the hang of JavaScript, the syntax felt unnatural and initially I would try applying what I learned with JavaScript but frequently found myself going right back to python to do the project.
0 kommentar(er)
