|
I agree that Javascript does what it is supposed to, but sometimes following its logic becomes a little difficult. And then it snowballs from there. Gets worse every hour, and leaves you with frustration.
The lack of coding practices in javascript or the lack of people willing to follow is also to blame. These are the same problems "daddy languages" have faced and tried to resolve over the years.
But in the end, everything has its goods and bads. I just wish that it learned from other language's mistakes/flaws.
Anyways CP makes working a lot easier. I just had to rant somewhere, but here I also get some feedback which is always nice. 
I just might finish this today.
I am not the one who knocks. I never knock.
In fact, I hate knocking. Just barge in will'Ya?
|
|
|
|
|
It boosts IT employment, shortens the life of those same people,
and as a side effect keeps thousands of coffee farm workers busy in far flung places like Kenya and Brazil (even if they only earn a dollar a week.)
Think of the horror if they fixed that sort of stuff... hundreds of IT folks out in public... think of the children!
Sin tack
the any key okay
|
|
|
|
|
Undefined reference error - you are speaking about Java, not JavaScript.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
u seem to have a point there..also see below..
That paradigm will be defined by three key characteristics, Nadella explained: Every computing task and experience will be "multi-device, multi-sense" with multiple means of input and output; artificial intelligence will be built into every application and device; and there will be an increased use of containers, microservices and server-less technologies that provide new ways to develop, distribute and manage applications.
|
|
|
|
|
|
If you're really desperate you can always give Elm a try...
Strongly-typed with type inference. Compiles to JavaScript. Can introduce incrementally, i.e., no need to rewrite everything. No runtime exceptions.
(Disclaimer, I've only had a brief look.)
Kevin
|
|
|
|
|
JavaScript to my experience is like root beer. First taste is bad and saying who would drink such a foul taste drink. But you know what, the more you drink it, you grew to like more and more. Pretty soon you preferred it to other drinks, even genuine draft beer.
I'm having second thought about how bad skunk smell. If you get just a fainted smell, it actually no bad at all. People paid good money for the scent. 
|
|
|
|
|
I'm closing on 20 years of JavaScript. You have to accept it as JavaScript, it will solve 99% of your problems. As long as you try to bend it to be C# (or like) you will fail in so many ways...
If you want to feel good with the tools, try using Notepad as editor and never hit F12 while you are in the browser...
After two weeks you will see the benefits of the built in debugger... 
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I'm not the biggest fan of the language either but it is quite useful. Some of those frustrating bits also give you the ability to do things that simply aren't possible in other languages. That being said, I've really started to like Typescript[^]. It's a superset of JS so you basically just have to read up on how the type system works then you're good to go.
|
|
|
|
|
GKP1992 wrote: if people had the choice of using a friendlier language like C# or Java, javascript would have been in the dumpster by now.
Come on, That is why we gave you Applets, Active-X, etc right? 
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
debugging Javascript in a browser is bad. Which browser and what JS debugging tools did you use if at all?
Some browsers have excellent debugging tools including step by step execution.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
|
JavaScript is around for one reason: To stick it to Microsoft.
There was a time when types mattered (remember why "smart" people hated VB?). There was a time when performance mattered (remember when C++ was cool?). There was a time when user interface standards mattered (Anyone remember UI guidelines?). Now all that matters is having your code - however much of a mess it may be - run in a browser even though if it's a browser running on a PC, 98% of the time it will be running on Windows. But I guess we have to worry about that 2% because it could be Linux! Or, a Mac! Two percent of the market is only a failure if it's Windows phone.
Why don't we write apps for PCs? That only is a smashing success for mobile. It would never work for a PC because....Microsoft owns the PC, and we can't have that. No, let's beat our heads against the wall trying to get some hacked together language to do even the most basic things. <sigh>
|
|
|
|
|
This. Pretty much this. I hate having to do everything on the browser. So much of the last 10 years have just been "not-microsoft", which is a sentiment I understand and get behind (monopolies are bad, but the 1990's are over).Do we really have to go back to the dark ages just to "stick it to the man" ? I hate modern "app" which are glorified browser tabs, taking 1 GB of Ram for a chat app (oh Hi Slack !) and completely failing to integrate into the OS (chromium apps leave pop-up messages open, regardless if you change focus.).
Do we really need 8GB just to browse facebook? Remember the time when your apps would keep 60fps render at all times? Remember when you could use alt-tab ? Good times.
|
|
|
|
|
Have you considered using TypeScript? Several developers I know shifted from JS to TypeScript to better align their OO C# experience with generating JS.
|
|
|
|
|
MSBassSinger wrote: Have you considered using TypeScript?
I have actually, but I'm just a poor developer. However, I have initiated the decision process and now it rests with the managers.
I hope they don't find it too "expensive".
I am not the one who knocks. I never knock.
In fact, I hate knocking. Just barge in will'Ya?
|
|
|
|
|
Yeah it has flaws. Every language and every environment does.
Remember in Cobol, you had to IDENTIFY the target environment!
In ForTran, God was REAL.... Unless you declared it otherwise.
The biggest issue I ran into was some code declared a variable with the same name as a global IE object, and that JavaScript variable did not really work, but the code failed in IE, and worked okay in Chrome.
That took me a while to debug.
But the little I do with HTML, I would honestly die a thousand deaths without JavaScript!
|
|
|
|
|
I'm kind of surprised at the lacks of specifics on this thread. So far no one, including the OP, has indicated specifically what they like or don't like about Javascript or the tools and ecosystem that surrounds it.
One of the things I find most amazing about Javascript is how chameleon-like it is. Folks have created TypeScript, to provide strong typing and a more traditional OO flavor. React and other frameworks rely more on its Functional Programming flavor. Other people have compiled Javascript source into such compact code that the recently released WebAssembly standard is only a minor improvement. People have even made Javascript look like the granddaddy of OO languages, Smalltalk (Amber Smalltalk[^]).
Tools around Javascript also make the language extremely powerful. Flow allows you to find flaws in your code without requiring the explicit type declarations that TypeScript utilizes. WebPack and its many plugins allows you to not only minimize your production code, but you can even create hot-loaded modules so that your enormous web app doesn't have to all be loaded when the user accesses the first page. And if you're generating minimized code, make sure you also generate source maps, so you can debug it so much more easily. Chrome's built-in developer tools are powerful, and I rely on them every day, but occasional glances at FireFox and Edge make me think they have pretty strong debugging tools as well.
There's no way to tell from your post what it is about Javascript you don't like, or how much experience you have with the language, and so its impossible to suggest approaches that might help you deal with your issues. And there's no doubt that Javascript continues to have its limitations. But it still seems to me that Javascript survives not only because it is the only game in town for front-end web programming, but because it is a remarkably adaptable tool that enjoys strong support from a large, vibrant developer community.
|
|
|
|
|
Type safety (aka compile time errors instead of runtime ones). No standardized web bytecode it compiles to like HLSL, Vulkan shaders, .NET, Java, etc, etc leaving huge gaps in a standardized lang and API. Maybe webasm will fix that. O and crap like this: Javascript: the weird parts -- Charlie Harvey[^]
|
|
|
|
|
Who needs type safety, when you have Strings for everything, AMIRITE??? /s
|
|
|
|
|
I think you had a runtime error stringing that together.
|
|
|
|
|
Yes, but only on Firefox, Chrome works so that's all that matters. Edge what?... /s
|
|
|
|
|
The problem is not its limitations. It's the lack of limitations and lack of proper enforcing of a set of rules to ensure behaviour of code. In the web world, they call it Chromium V8, in the rest of the world they call that a compiler.
|
|
|
|
|
|
Message Removed
modified 3-Aug-17 5:52am.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
I think it's unanimous that most of us hate JS...especially the part where you get it working in one browser 
, then find that it fails in another! 
