I Do Not Agree

Going to shit

2015 is when web development went to shit. Web development used to be nice. You could fire up a text editor and start creating JS and CSS files. You can absolutely still do this. That has not changed. So yes, everything I’m about to say can be invalidated by saying that.

Read “The Sad State of Web Development” >

Advertisement

Author: Bruce Elgort

You’ll find this technology professor – an award-winning instructor at Clark College – working hard to inspire and challenge his students with meaningful web development and programming experiences. With a skinny vanilla latte (no foam) in hand, Bruce loves to tinker and test the boundaries of existing and emerging technologies, to then guide hungry minds through memorable, educational journeys to showcase with passion the ever-evolving innovations of society. An industry leader, Bruce is known for co-developing Elguji’s IdeaJam software, and is recognized by IBM as an ‘IBM Champion’ for being an innovative thought leader in cloud technologies.

8 thoughts on “I Do Not Agree”

  2. Am with Chris, he has a point. Companies are “looking” at this closely. Remember VBscript not working after updates…. its really coming back.

    1. Am part of a group at my company that work closely with companies during there analytic design and layouts , this has been brought up few times from developers that use Node and others frameworks. We have to pick the framework carefully that suites the 3 – 4 years lifespan of the app.

    2. @Bruce: I was speaking more specifically to the author’s point in that paragraph that SPAs aren’t the End All Be All when it comes to a project.

      As for how many Node.js projects I’ve written, I’ve only had the chance so far to use it 8 times (with 2 of those projects being demos).

    3. @Bruce, I think the proper question is “what is the LARGEST node app you’ve ever written. 🙂

  4. JS Frameworks seem similar to the sheer number of slightly different types of churches in US. Some in the congregation get upset, they split, they form, they split again. All you end up with is a smaller and smaller congregation. Eventually the congregation moves to another round of different churches and each goes their own way.

    I think the author hits the nail on the head. Yes, server-side JS sucks, just in more obvious ways than other languages. The early days of Java has the same issue. Those issues mostly went away when Apache (the foundation, not the web server) codified the “projects” in a somewhat understandable way. JS frameworks could do with something similar, but SSJS will still suck 😉

    Just my $0.02

  5. Well that was an interesting article. First, as most of you know, we use Dojo as the basis of our framework, and I am so glad I did, because of its structure programming and patterning. We have been supporting our framework for 5 years now and our clients expects it to be supported another 5 to 10 years. It is consistence and old stuff can be migrated to newer versions and is built for enterprise. The main problem with Node is not Node itself, the ecosystem where everyone including novice developers with basic JavaScript skills can publish modules. The barrier of entry is too low good and bad. There is really no required structure and venting of the code thus creating a total mess.

Comments are closed.

%d bloggers like this: