|
GKP1992 wrote: with JS are now avoidable when we use it a certain way.
Which of course works in a day zero startup with two programmers that have been working together for years.
With a 20 year old code base which has been worked on by more than 100 developers, each with their own preferences, it doesn't work out too well.
|
|
|
|
|
GKP1992 wrote: 7 years later I fully agree with him.
Amen brother. IMO the biggest issue with JS is its popularity. You take any language on the planet and make it extremely popular and you're bound to have some people writing stupid code in it. That's not the fault of the language itself though; it's the fault of the "average" coder.
GKP1992 wrote: The callback hell can be avoided with the use of asynchronous programming.
The whole reason callback hell even started (then went onto promise hell) was due to one of JavaScript's strengths. As you mentioned, most people just didn't know about JS's execution model and would rather insult than learn. But, because of the execution model, it's always been extremely hard to lock JS. Granted, people needed to learn how to deal with that or else they'd suffer race conditions, but peeps only had to take the time to learn the language. The same could be said of any language though. I'm not gonna learn Rust overnight.
GKP1992 wrote: As people get more experienced with JS they become more accepting of it's quirks and manage to avoid it's pitfalls while being able to produce robust production ready code.
100%. It's a language that's been evolving and will continue to evolve as it grows up, so to speak.
As it stands now, it's literally the fastest scripting language on the planet. It runs so fast it deserves its own category of scripting language. Sure, compared to C/C++ or Rust it's slower, but compared to Python, etc. none of them hold a candle to JS. And it has to be that way, it's the dynamic language of the Internet so a lot of time has been spent optimizing its execution engines.
Haters gonna hate though. 
Jeremy Falcon
modified yesterday.
|
|
|
|
|
I think part of it is lingering feelings from way, way back when when every browser had their own implementations of certain features which meant that building any sort of platform that was going to work cross-browser was a major headache.
I remember adopting MooTools because it offered cross-browser AJAX support, then obviously jQuery when it came along with it's own solutions. These days most JS functions are normalised (ie. the fetch API) but there's a lot of salt in the wounds that can't be cleaned so easily.
|
|
|
|
|
I'm learning it just now, new job needs it. My biggest gripe is lack of typing of variables. I would like to know what kind of value, object, etc I can pass into a function.
Okay, I do like that they are called functions rather than methods. Cut my teeth on C and then Delphi (which had both functions and procedures) but it rankled me for the 10+ years I worked in Java that I had to say method.
Javascript does have something akin to function pointers, which is a nice throwback to C.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
I’m begging you for the benefit of everyone, don’t be STUPID.
|
|
|
|
|
MarkTJohnson wrote: My biggest gripe is lack of typing of variables.
Typescript to the rescue 
|
|
|
|
|
Erm ... JS has both methods and functions - the former operate on object data (as per C#) the later are procedural and don't (as per C)
The difference in name is important because it tells you what you can do with a bit of code - that's why Java insists on method to differentiate it from the more primitive function you were used to in C.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: that's why Java insists on
Tut tut!
Java ≠ JavaScript. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Quote: ... it rankled me for the 10+ years I worked in Java that I had to say method.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Like I said, learning. Haven't gotten to that stuff yet.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
I’m begging you for the benefit of everyone, don’t be STUPID.
|
|
|
|
|
OriginalGriff wrote: to differentiate it
One thing I disliked about Pascal is that it has Function and Procedure distinguished by keyword -- I prefer that C and its ilk don't, and have no keywords for those concepts.
I can understand why SQL does things more differentlier, and that's OK.
|
|
|
|
|
PIEBALDconsult wrote: differentlier
Word of the day.
|
|
|
|
|
JavaScript is fine - I used in in various incarnations and Typescript definitely helps write cleaner code.
I heard Bob Martin point out that the evolution of programming languages is an evolution in constraining what you can do, each programming language constraining you in a different manner.
JavaScript is perhaps a bit of a exception in that it's fairly loose with its constraints which is why something like TypeScript makes sense as it brings static typing with it.
I still get caught out occasionally with the asynchronous nature of JavaScript but other than that I think it's fine when used well.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Javascript is great!..but I've been using it for 24+ years, so I'm used to it. Combined with CSS and AJAX, and there's not a lot you can't do.
My gripe is that after all this time, it's still a PITA to debug in Visual Studio. (probly cause I use master pages)
I still rely on the tried and true alert(whatami); debugging method.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
kmoorevs wrote: Javascript is great!..but I've been using it for 24+ years, so I'm used to it. Combined with CSS and AJAX, and there's not a lot you can't do.
My gripe is that after all this time, it's still a PITA to debug in Visual Studio. (probly cause I use master pages)
I still rely on the tried and true alert(whatami); debugging method.
I still use alert boxes for testing in JavaScript as well! I've been writing Javascript since about 1996 or so. In the beginning, there was no logging console available, so you really had to use alert boxes to test your code.
I love writing JavaScript. It's become so versatile over time that your imagination is the limit. It does have its strange quirks, but they present no problems if you know how to work with them. Why is it that in JavaScript, null is an object? In terms of conditional statements, that's when it gets really weird. If you compare null to undefined, the condition returns true. When you compare undefined to null, the condition returns false. If I remember correctly, that's how it goes, but I learned this so long ago that my memory is faint and vague. It's something along those lines, but either way, it goes to show how ridiculous JavaScript can be. Either way, I really like it!
|
|
|
|
|
|
I like JavaScript because it is so forgiving.
Error messages like NaN, undefined, are much gentler compared to a bunch of Error messages which come in C# projects on Visual Studio.
|
|
|
|
|
Mainly because it sucks.
Have you noticed that the likeableness of javascript is inversely proportional to a person's age?
CQ de W5ALT
Walt Fair, Jr.PhD P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
One of the things I say to people worried about learning new languages is once you learn the concepts behind one language, you already know most of the concepts behind most other languages. Learning the new language is mostly a matter of semantics and syntax after that.
Javascript, for someone who's always been exposed to strong types, doesn't really lend itself to all of the concepts of our normal languages. It's strongly NOT typed, allowing all kinds of values and free-form stuff assigned to it, including entire functions. It doesn't follow a lot of the concepts you learned in other languages. I think it's this "bucking of the norms" that really throws people off and gives everyone a bad taste.
IMHO, Javascript being a no-typed language really makes the code-writing and debugging experience a pain in the ass. That and the lack of proper debugging tools in browsers. If you really need Typescript to make the experience that much better, the language and execution environment should have been designed with this in mind. Typescript should not have been an external bolt-on.
Once you get used to it, and that's a steep learning curve for noobs, it's not too bad. I just use the tried-and-true old-school techniques of alerts and peppering the code with console.log everywhere.
|
|
|
|
|
I'd upvote your post twice if I could. 
I think another reason it got a bad rep is for years it was strictly functional back in the day... not procedural like C but functional more like F#. Technically you could do procedural in JS, but a lot the solutions to common problems used a functional paradigm. Functional languages and concepts just aren't as popular. So peeps would rather insult than learn. These days that's all changed though as you can do both OOP or functional.
For the types... totes get it. Personally I see value in using a loosely typed language. However, I also see the value in a strongly typed one. Fortunately these days, when you need strong types we have TypeScript and Flow.
Jeremy Falcon
|
|
|
|
|
Haters gonna hate buddy. Everyone who claims to be an expert at JS that hates is lying. It's more ego where they're fooling themselves than them actually being experts. Programmers aren't known for being mature and all.
Jeremy Falcon
modified yesterday.
|
|
|
|
|
Bah. I've been good enough at it to spot obvious idiocy from 'experts'.
It's a bad tech founded on bad principle with more bad practitioners than pretty much any other language you want to pick.
It will die. It may take a bit, but it will be an archaic relic in the dust bin of history and it will be consigned there inside half a decade once the right bits come along.
|
|
|
|
|
I'm absent minded, but I often spend hours debugging stupid things that C# would flag instantly. Also, the VSCode Intellisense and code navigation in JavaScript projects tend to be sub-par when compared to C# projects on Visual Studio.
|
|
|
|
|
Most of those who make their living in the HTML/CSS/JS world span the spectrum of loving it to putting up with it in order to make a living. Like generations of developers before them, change is often resisted. There is nothing wrong with liking JS and wanting to stick with it. In past generations, FORTRAN, COBOL, QuickBasic, Visual Basic, Delphi/Pascal, etc. developers were in their "comfort zone", and did not want to learn new languages, frameworks, and newer ways to design software. What I write is not a criticism of those who like or want to stick with JS. It is an explanation of why many software engineers would like to move past JS to newer, better, technology.
To answer the question, there are several reasons some software engineers do not want to use JS unless they absolutely have to. It is not so much a dislike, but a growing realization that JS is not as suited for 21st century software development as newer, OO, compiled, languages that are designed for broader functionality or extensible to take on new functionality. Many software engineers don't want to be locked into older, less flexible, languages like JS when they can choose from multiple newer, better suited languages.
Here are a few of those reasons.
- JS is not object oriented (OO). OO design and programming has a lot of advantages over procedural languages like JS. Tools like TypeScript try to overlay some OO techniques over JS, but in the end, what is emitted from TypeScript is still non-OO JS.
- JS is a script language. It is not compiled but run by an interpreter. There are some tools that try to approach the benefits of compiling to machine code, or at least byte code for an intermediate just-in-time interpreter/compiler, but the execution speed of JS is slower than compiled languages, especially ahead-of-time compiled (to machine code) languages.
- While JS is supported well in the browser (with inconsistencies between browsers), running JS as a server-side language is slow and not designed for that. Compiled, OO languages work much better server-side.
- JS tends towards being cryptic, not as developer-friendly as modern compiled OO languages.
- JS was never intended to do a lot of what it does. In 1995, the beginning of the dot-com boom, Netscape assigned a programmer, Brendon Eich, to create a language for the Netscape browser to allow dynamic behavior that had Java-like syntax (which is mostly C/C++ syntax), but not derived from Java. Brendan Eich spent 10 days writing a language called LiveScript to do some basic automation in the Netscape browser. Netscape renamed it JavaScript for marketing purposes. Since 1995, JS has been patched and had other functionality hammered into it that is often kludgy and inefficient, since JS was not designed from the ground up to do what it does, or to be efficiently extensible.
There are some reasons why even those who prefer not to use JS will still use it.
- For simple, short, browser functions (e.g. onclick(), onblur(), etc.) involving the DOM, JS is still useful.
- During conversion of large web apps, keeping parts of JS may be useful to get the app converted in stages, until all or most of the JS is gone.
Here is an example of where one will see some of the JS/no-JS tension in software engineering today.
Several years ago, the need for faster-executing browser code was recognized, and the drive to create [^web assembly (wasm)] started by W3C. WASM was created with more careful engineering than JS was (not Brendan Eich's fault, he was under pressure from Netscape). Every major browser has a WASM engine in addition to its JS engine. WASM is byte-code compiled language for the browser, with all the safety protections the browser has in JS. Several modern OO languages compile to WASM as ahead-of-time (AOT) or just-in-time (JIT) implementations. Languages that can be compiled to wasm (not including experimental compilers or little used languages) are:
- C#
- C/C++
- Rust
- Go
- Java
- Kotlin
- Ruby
- Swift
JavaScript, however, due to its design and lack of OO, does not compile to WASM, though some are trying to find a way. However, the WASM engine in browsers does provide for JS interop so the language being used for WASM can call via interop out to execute JS in the JS engine. Keep in mind that interop, regardless of language, is usually noticeably slower than using the compiled code without interop.
Microsoft, for example, has implemented (without changing the W3C standard, for a change) WASM with their Blazor implementation. You write the HTML/CSS, but instead of JS, you can use C#. The HTML code recognizes C# methods and variables, so they are seamlessly integrated into HTML. Microsoft's implementation only replaces the parts of the compiled code that have changed since the last load, to reduce the bytes being sent to the browser. The tiny binaries that are downloaded by the browser on first use, for typical web apps, are about the same size in a lot of cases, as the JS downloaded by the browser on first use. The full .NET environment is not installed by the browser.
Other languages and tools have their own syntax and structure, but you still wind up with wasm in the browser, executing faster, more efficiently, just as safely, than using JS.
A long response, to be sure. But without getting into religious language wars, there are reasons to migrate from JS to a modern browser language like WASM. Apply good software engineering principles, and WASM in the browser is a good choice for small or large web apps. I've been writing WASM browser apps for about 3 years and love it. Change is a part of being a good software engineer over the timespan of a career.
See also [^Wikipedia article on WASM]
|
|
|
|
|
I agree with most of this with the exception of "Not OO". JS is not OO in the Data/Procedure or Data/Procedure/Relational (C++, C#, Java) sense. But it is OO in the Process/Message model. Though none of these are "Object Languages" that confirm to Classical Object Theory. Thus "Object-Oriented" and not "Object".
|
|
|
|
|
I never had much against it until, out of the blue, it was considered a serious programming language.
I mean I like to stick close to the metal as much as sanely possible (I constantly remind people C is a high-level language). That said, I know I'll have to relearn JS at some point in order to load WASM modules (written in whatever: LISP, C, RUST)
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
