3 ms·

Different areas of the dev world appeal to different people, naturally, but as a web dev since that became a thing (1995), I take a contrasting view. The web i

Different areas of the dev world appeal to different people, naturally, but as a web dev since that became a thing (1995), I take a contrasting view. The web is the most dynamic, most exciting space in software development right now and is likely to be so for the foreseeable future. It touches everyone, in every industry. Web interfaces and technologies are the most used languages on the planet, giving your work huge impact. Have there been changes in this newest area of computing? Of course! Typescript isn't "controlled" by MS. It's just the future version of JS, available today. It's tremendously exciting for anyone who works with big JS codebases. Electron and other ways of building desktop apps out of the same tools is also a huge leap forward and let's web devs make stuff that's as beautiful and exciting as traditional desktop apps, all of which are incompatible with each other and have huge proprietary libraries. Bare metal web components and Lit are able to replace outdated frameworks like Angular and React and this is a huge improvement, too. Finally, web sockets gives us an open two-way pipeline to communicate with multiple servers or clients without http. Taken together, these elements represent an exciting time in web development when we can deliver apps that are beautiful, well written, and easy to maintain. The time for web dev has never been better! But it might not be a good match for you if you prefer working on other kinds of code.

kayodelycaon 4y ago
Calling the single most popular framework for front end outdated and saying $newFramework is the way front is exactly the kind of thing OP is frustrated with.
- dtagames 4y ago
  Everything is outdated eventually. It's the nature of our work. React was a reaction to Angular (because FB couldn't be seen using a Google framework). Google itself has seen beyond Angular now that web components are part of the browser. Other than as a convenience library, their overhead and rules are outdated. #sorry
textninja 4y ago
While I do think it’s here to stay, I don’t consider TypeScript to be “the future of JavaScript”. Given the choice, I’d much rather use JavaScript, and that applies to large codebases as well. TypeScript just gets too verbose and adds way too much ceremony for my taste, the implied safety is skin deep, and I far prefer metaprogramming and reflection to compile time IDE hints. Type systems are not for everyone. See also, Haskell vs Lisp. Also, I disagree completely with your claim that React is outdated. Plenty of existing projects use it, plenty of new projects are starting with it, it still has a huge community, it’s actively maintained, and this is a subjective point, but the developer experience outclasses pure web components by a lot.

kayodelycaon 4y ago

Calling the single most popular framework for front end outdated and saying $newFramework is the way front is exactly the kind of thing OP is frustrated with.

dtagames 4y ago
Everything is outdated eventually. It's the nature of our work. React was a reaction to Angular (because FB couldn't be seen using a Google framework). Google itself has seen beyond Angular now that web components are part of the browser. Other than as a convenience library, their overhead and rules are outdated. #sorry

textninja 4y ago

While I do think it’s here to stay, I don’t consider TypeScript to be “the future of JavaScript”. Given the choice, I’d much rather use JavaScript, and that applies to large codebases as well. TypeScript just gets too verbose and adds way too much ceremony for my taste, the implied safety is skin deep, and I far prefer metaprogramming and reflection to compile time IDE hints. Type systems are not for everyone. See also, Haskell vs Lisp. Also, I disagree completely with your claim that React is outdated. Plenty of existing projects use it, plenty of new projects are starting with it, it still has a huge community, it’s actively maintained, and this is a subjective point, but the developer experience outclasses pure web components by a lot.