Hey! I'm Saul, the founder and CEO of Next Tech. I've been programming since I was a kid and love to share my findings, thoughts, and the occasional rant about the software industry.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
All sorts of things really, from writing tooling for code analysis to virtual filesystems (useless single threaded process spawning ones but still) the appeal for me is one language to dissolve this notion of frontend backend. But once blazor is mature I will be even more confused about C#. Typescript and node offers me the typesafe experience and oop (limited though). Asp.net is the antithesis of JavaScript, batteries are included and I think that's the major difference.
Hey! I'm Saul, the founder and CEO of Next Tech. I've been programming since I was a kid and love to share my findings, thoughts, and the occasional rant about the software industry.
One of the aspects of Node that I've always found appealing as well is the strong community around it.
What types of projects have you used Node for?
All sorts of things really, from writing tooling for code analysis to virtual filesystems (useless single threaded process spawning ones but still) the appeal for me is one language to dissolve this notion of frontend backend. But once blazor is mature I will be even more confused about C#. Typescript and node offers me the typesafe experience and oop (limited though). Asp.net is the antithesis of JavaScript, batteries are included and I think that's the major difference.
The backend/frontend merging in Node has always appealed to me too. Plus the concurrency model is intriguing.
Blazor looks pretty nifty, may add its getting started guide to our queue of courses!