Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Javascript sucks!

Javascript sucks!

Scheduled Pinned Locked Moved The Lounge
designjavascriptannouncementcomsysadmin
9 Posts 5 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Rutvik Dave
    wrote on last edited by
    #1

    Everything that has javascript is buggy, including AJAX and jQuery. :mad: I hate all the web applications that over-use javascript (I have a huge list). They don't work when you have slow or unreliable (mobile) internet connection. The 'improving the user experience' part becomes really frustrating. And the content-heavy mind-blowing stuff they load on your computer, when you see them in fiddler :omg: , half of the stuff has nothing to do with the user it's just there to make it look pretty. It is awful that developers and companies design their web application for 10 Mbps internet connection. What about the rest of the world? Please allow me to brag about myself... We are working on a major release of our web application, and I am proud to say that even when we are not using fancy coding-patterns and cutting-edge stuff, it works just fine on a 2G connection, with a 10 year old computer. No stupid half rendered pages, No blank popups, No failed requests, No dead logout links, And no more circular loading animations. The current version of our application has started suffering from performance issues as we have started growing, so we fixed it by implementing a custom server side caching and rewriting some of our code base, and not by doing half of the stuff client side and then rendering partial pages. All I am saying is that, we haven't done anything ground-breaking, it's just that we don't want to use broken stuff for the sake of improving UX. Can't wait to release the new version. - bragging and ranting over... for now... :)

    Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

    L B K C 6 Replies Last reply
    0
    • R Rutvik Dave

      Everything that has javascript is buggy, including AJAX and jQuery. :mad: I hate all the web applications that over-use javascript (I have a huge list). They don't work when you have slow or unreliable (mobile) internet connection. The 'improving the user experience' part becomes really frustrating. And the content-heavy mind-blowing stuff they load on your computer, when you see them in fiddler :omg: , half of the stuff has nothing to do with the user it's just there to make it look pretty. It is awful that developers and companies design their web application for 10 Mbps internet connection. What about the rest of the world? Please allow me to brag about myself... We are working on a major release of our web application, and I am proud to say that even when we are not using fancy coding-patterns and cutting-edge stuff, it works just fine on a 2G connection, with a 10 year old computer. No stupid half rendered pages, No blank popups, No failed requests, No dead logout links, And no more circular loading animations. The current version of our application has started suffering from performance issues as we have started growing, so we fixed it by implementing a custom server side caching and rewriting some of our code base, and not by doing half of the stuff client side and then rendering partial pages. All I am saying is that, we haven't done anything ground-breaking, it's just that we don't want to use broken stuff for the sake of improving UX. Can't wait to release the new version. - bragging and ranting over... for now... :)

      Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      At some point the development community made the decision to ignore technologies that make sense so that they'd have the time required to embrace steaming piles of horse shit. That is basically how we got our current HTML stack. It is about assigning oneself importance by being careful to wrap every activity in a very large fog of obscurity and complexity. You'll know who these people are - they're the ones angry that you actually accomplished something.

      1 Reply Last reply
      0
      • R Rutvik Dave

        Everything that has javascript is buggy, including AJAX and jQuery. :mad: I hate all the web applications that over-use javascript (I have a huge list). They don't work when you have slow or unreliable (mobile) internet connection. The 'improving the user experience' part becomes really frustrating. And the content-heavy mind-blowing stuff they load on your computer, when you see them in fiddler :omg: , half of the stuff has nothing to do with the user it's just there to make it look pretty. It is awful that developers and companies design their web application for 10 Mbps internet connection. What about the rest of the world? Please allow me to brag about myself... We are working on a major release of our web application, and I am proud to say that even when we are not using fancy coding-patterns and cutting-edge stuff, it works just fine on a 2G connection, with a 10 year old computer. No stupid half rendered pages, No blank popups, No failed requests, No dead logout links, And no more circular loading animations. The current version of our application has started suffering from performance issues as we have started growing, so we fixed it by implementing a custom server side caching and rewriting some of our code base, and not by doing half of the stuff client side and then rendering partial pages. All I am saying is that, we haven't done anything ground-breaking, it's just that we don't want to use broken stuff for the sake of improving UX. Can't wait to release the new version. - bragging and ranting over... for now... :)

        Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

        B Offline
        B Offline
        BillWoodruff
        wrote on last edited by
        #3

        Good on 'ya !

        If you seek to aid everyone that suffers in the galaxy, you will only weaken yourself … and weaken them. It is the internal struggles, when fought and won on their own, that yield the strongest rewards… If you care for others, then dispense with pity and sacrifice and recognize the value in letting them fight their own battles." Darth Traya

        R 1 Reply Last reply
        0
        • R Rutvik Dave

          Everything that has javascript is buggy, including AJAX and jQuery. :mad: I hate all the web applications that over-use javascript (I have a huge list). They don't work when you have slow or unreliable (mobile) internet connection. The 'improving the user experience' part becomes really frustrating. And the content-heavy mind-blowing stuff they load on your computer, when you see them in fiddler :omg: , half of the stuff has nothing to do with the user it's just there to make it look pretty. It is awful that developers and companies design their web application for 10 Mbps internet connection. What about the rest of the world? Please allow me to brag about myself... We are working on a major release of our web application, and I am proud to say that even when we are not using fancy coding-patterns and cutting-edge stuff, it works just fine on a 2G connection, with a 10 year old computer. No stupid half rendered pages, No blank popups, No failed requests, No dead logout links, And no more circular loading animations. The current version of our application has started suffering from performance issues as we have started growing, so we fixed it by implementing a custom server side caching and rewriting some of our code base, and not by doing half of the stuff client side and then rendering partial pages. All I am saying is that, we haven't done anything ground-breaking, it's just that we don't want to use broken stuff for the sake of improving UX. Can't wait to release the new version. - bragging and ranting over... for now... :)

          Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

          K Offline
          K Offline
          kmoorevs
          wrote on last edited by
          #4

          Part of the reason javascript is unreliable is that 'standards' keep changing. The last two versions of IE (10 and 11) seemed especially prone to breaking older javascript and client-side code. IE 11 doesn't even refer to itself as MSIE 11.0 in the agent string, but instead poses as firefox. (like gecko) Have you ever tried to browse the web with javascript debugging turned on? If so, probably not for long.

          "Go forth into the source" - Neal Morse

          1 Reply Last reply
          0
          • R Rutvik Dave

            Everything that has javascript is buggy, including AJAX and jQuery. :mad: I hate all the web applications that over-use javascript (I have a huge list). They don't work when you have slow or unreliable (mobile) internet connection. The 'improving the user experience' part becomes really frustrating. And the content-heavy mind-blowing stuff they load on your computer, when you see them in fiddler :omg: , half of the stuff has nothing to do with the user it's just there to make it look pretty. It is awful that developers and companies design their web application for 10 Mbps internet connection. What about the rest of the world? Please allow me to brag about myself... We are working on a major release of our web application, and I am proud to say that even when we are not using fancy coding-patterns and cutting-edge stuff, it works just fine on a 2G connection, with a 10 year old computer. No stupid half rendered pages, No blank popups, No failed requests, No dead logout links, And no more circular loading animations. The current version of our application has started suffering from performance issues as we have started growing, so we fixed it by implementing a custom server side caching and rewriting some of our code base, and not by doing half of the stuff client side and then rendering partial pages. All I am saying is that, we haven't done anything ground-breaking, it's just that we don't want to use broken stuff for the sake of improving UX. Can't wait to release the new version. - bragging and ranting over... for now... :)

            Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

            L Offline
            L Offline
            Lost User
            wrote on last edited by
            #5

            Some Javascript is awesome though[^]

            1 Reply Last reply
            0
            • R Rutvik Dave

              Everything that has javascript is buggy, including AJAX and jQuery. :mad: I hate all the web applications that over-use javascript (I have a huge list). They don't work when you have slow or unreliable (mobile) internet connection. The 'improving the user experience' part becomes really frustrating. And the content-heavy mind-blowing stuff they load on your computer, when you see them in fiddler :omg: , half of the stuff has nothing to do with the user it's just there to make it look pretty. It is awful that developers and companies design their web application for 10 Mbps internet connection. What about the rest of the world? Please allow me to brag about myself... We are working on a major release of our web application, and I am proud to say that even when we are not using fancy coding-patterns and cutting-edge stuff, it works just fine on a 2G connection, with a 10 year old computer. No stupid half rendered pages, No blank popups, No failed requests, No dead logout links, And no more circular loading animations. The current version of our application has started suffering from performance issues as we have started growing, so we fixed it by implementing a custom server side caching and rewriting some of our code base, and not by doing half of the stuff client side and then rendering partial pages. All I am saying is that, we haven't done anything ground-breaking, it's just that we don't want to use broken stuff for the sake of improving UX. Can't wait to release the new version. - bragging and ranting over... for now... :)

              Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

              L Offline
              L Offline
              Lost User
              wrote on last edited by
              #6

              It's not the technology; It's the people. To extend it a bit ... I often say to friends and colleagues: We may consider our selves as unlucky because we missed the Golden Age of Pericles but for sure we are cursed because we are living the Golden Age of D!ckhead. It's comforting to know that other people feel it, even if they express it in a totally different way (sometimes like a dogma). Thanks Dave

              1 Reply Last reply
              0
              • R Rutvik Dave

                Everything that has javascript is buggy, including AJAX and jQuery. :mad: I hate all the web applications that over-use javascript (I have a huge list). They don't work when you have slow or unreliable (mobile) internet connection. The 'improving the user experience' part becomes really frustrating. And the content-heavy mind-blowing stuff they load on your computer, when you see them in fiddler :omg: , half of the stuff has nothing to do with the user it's just there to make it look pretty. It is awful that developers and companies design their web application for 10 Mbps internet connection. What about the rest of the world? Please allow me to brag about myself... We are working on a major release of our web application, and I am proud to say that even when we are not using fancy coding-patterns and cutting-edge stuff, it works just fine on a 2G connection, with a 10 year old computer. No stupid half rendered pages, No blank popups, No failed requests, No dead logout links, And no more circular loading animations. The current version of our application has started suffering from performance issues as we have started growing, so we fixed it by implementing a custom server side caching and rewriting some of our code base, and not by doing half of the stuff client side and then rendering partial pages. All I am saying is that, we haven't done anything ground-breaking, it's just that we don't want to use broken stuff for the sake of improving UX. Can't wait to release the new version. - bragging and ranting over... for now... :)

                Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

                C Offline
                C Offline
                Chris Maunder
                wrote on last edited by
                #7

                I could give you just as long a list of applications that are desperately in need of offloading some UI to the client. And then again we've all seen the apps where everything is client side and you just beg them to just render it in one go on the server and just give you the info you want. It's not about the screwdriver. It's about how you hold it while banging in those nails.

                R 1 Reply Last reply
                0
                • C Chris Maunder

                  I could give you just as long a list of applications that are desperately in need of offloading some UI to the client. And then again we've all seen the apps where everything is client side and you just beg them to just render it in one go on the server and just give you the info you want. It's not about the screwdriver. It's about how you hold it while banging in those nails.

                  R Offline
                  R Offline
                  Rutvik Dave
                  wrote on last edited by
                  #8

                  Chris Maunder wrote:

                  It's not about the screwdriver. It's about how you hold it while banging in those nails.

                  I completely agree until it's a screwdriver and not a hammer. My problem is with the people who use hammer everywhere. :)

                  Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

                  1 Reply Last reply
                  0
                  • B BillWoodruff

                    Good on 'ya !

                    If you seek to aid everyone that suffers in the galaxy, you will only weaken yourself … and weaken them. It is the internal struggles, when fought and won on their own, that yield the strongest rewards… If you care for others, then dispense with pity and sacrifice and recognize the value in letting them fight their own battles." Darth Traya

                    R Offline
                    R Offline
                    Rutvik Dave
                    wrote on last edited by
                    #9

                    OK, now I feel good. Thanks Bill. ;)

                    Remind Me This - Manage, Collaborate and Execute your Project in the Cloud

                    1 Reply Last reply
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • World
                    • Users
                    • Groups