Live data from Hacker News

JavaScript development is not fun for me anymore

medium.com

121–123 of 123 posts

Re: JavaScript development is not fun for me anymore

#121
post #63

Earlier quoted context omitted.

I feel the same way... web development was hard, until I've learned about es6/babel, webpack, redux and react (I'm using morphdom as react replacement, but idea is the same). Now web dev is easy and fun. I have state, components, events and routes. That's it. Update the state and stay calm. The idea to concisely manage the state together with dom diffing, are my personal favorite game changers.

Can you provide some guidance/links to a backend Java developer who wants to learn & use a quality long-term, front-end tech stack? Is there a kickstart example project for your preferred stack? Note that I prefer to avoid nodeJS for any back-end production use but am ok with it as part of the dev toolchain, if required. Thank you.

Try Expo at expo.io. It's similar to create-react-native-app but gives you a nice simple tool to preview your app.

Re: JavaScript development is not fun for me anymore

#122

But JS dev has never been fun. Web dev is fun because the browser is a freaking awesome plateform. However, it is _despite_ of JS. There's not a single characteristic of this language that makes it better than any other mainstream high level language out there. We use it because we have no reasonable alternative on the browser. It has always been a pain to use, requiring: - avoiding part of the language that is badly…

Async is super simple in JS. Yes callback hell can be an issue, and it may be ugly, but there's many a time where I wished for it in Python and ended writing a script in NodeJS.

Python has asynchronous coroutines (the async/await thing) so you don't really need to do callbacks as far as I know. I personally find that syntax much easier to follow than callbacks.

Re: JavaScript development is not fun for me anymore

#123

Earlier quoted context omitted.

Plus more people are familiar with a popular open source framework than OPs. There's 100s of thousands of react devs. But only OP knows OPs framework. Most people need to use an existing framework before they try to write their own, because a lot of people try to write frameworks not knowing what frameworks actually do or what is involved.

I wonder if OP doesn't have a framework at all.

Either way, the code must follow some sort of conventions or use patterns -- and if you invent your own conventions other people are less likely to understand them. Although if no one ever invented their own conventions we'd never innovate. I just think people should at least try out a bunch of frameworks before deciding they want to make one.
Post reply on HN