Live data from Hacker News

Tell HN: I spend so much time solving problems I feel like giving up

news.ycombinator.com

51–60 of 60 posts

Re: Tell HN: I spend so much time solving problems I feel like giving up

#51
The JS/React ecosystem is moving rapidly right now. I got caught in the middle of a storm when I updated my toolchain from Backbone/Sprockets to React/Redux/Webpack. There was Flux, then a bunch of Flux implementations, then Redux took the crown - a library which didn't exist a few months back. But as Redux has taken the crown, Relay has emerged along with it's own alternatives such as Falcor. Then there is Angular 2 on the horizon. Back in the day it was Knockout vs. Backbone which made things a lot simpler.

There is a proliferation of [boilerplate projects](https://github.com/xgrommx/awesome-redux#boilerplate) out there at the moment but they are quite heavy and all do things a little differently.

I think what is lacking and will emerge eventually is some glue to fill the gaps that everyone is identifying. I think it will be a few small core libraries with some conventions about project structure, toolchain, and modularity.

Re: Tell HN: I spend so much time solving problems I feel like giving up

#52
post #40

I call this 'feeding the machine'. There's the thing you want to do, the interesting, valuable, real-world problem you're trying to solve. But you're using a library, that has a dependency, that doesn't build on your machine, because of your version of the compiler, and the new version isn't in your package repository, so you have to download and build it, but your version of readline is wrong and so on and so on. Yo…

also known as Yak Shaving - http://www.hanselman.com/blog/YakShavingDefinedIllGetThatDon...

Re: Tell HN: I spend so much time solving problems I feel like giving up

#53
I get the impression you are learning, if you're not, I suggest you think again, because actually you are. :D

Programming is much about learning and it never gets easy when you need to pick something new. I suggest you find a mentor if you don't like experimenting alone, somebody who can give you some guidance.

After you learn something, it gets easier, and very rewarding.

On the subject of "not having what it takes", I disagree. Find a friend who draws, sings, plays an instrument or whatever, and ask them to tell you how much effort they had to put to learn their craft.

"Computers" are probably a lot easier, at least in comparison, since you have to use them anyways.

Re: Tell HN: I spend so much time solving problems I feel like giving up

#54
post #47

Earlier quoted context omitted.

Writing JavaScript and feeling you're surrounded by errors is pretty normal. It's a hastily-designed language. There's no getting away from the fact that everything is going to feel a little bit fragile. Just accept it and don't expect perfection.

Hastily designed for version 0.0.1, this is simply not the case if you are using modern EMCAScript

Is equality still broken? Are maps still broken? Is it still a sporadically whitespace-sensitive language?

Re: Tell HN: I spend so much time solving problems I feel like giving up

#55
Pick a language. Write some code. I recommend one that requires minimal building. Maybe python. If you need a build tool, use make. Use a text editor, like nano, gedit, or notepad++. Not a complex one like vim or emacs. Keep it simple. Now - And this is the important part - WRITE SOME CODE. It doesn't have to be complicated, It could just implement cat or something. But the important thing is to write it. Don't bother trying to find the "right way." If you need libraries, go for the path of least resistance.

EDIT: This is important, so I want to say it as clearly as possible. FUCK. ES. 2015. ES5 is actually pretty good. Learn prototypical inheritance, or just don't use OO. People have built real apps in ES5, you'll live. It might be hard at times, and you might have trouble learning, but the important thing is that you'll be writing code, not fixing your toolkit.

Re: Tell HN: I spend so much time solving problems I feel like giving up

#56
post #47

Earlier quoted context omitted.

Hastily designed for version 0.0.1, this is simply not the case if you are using modern EMCAScript

Is equality still broken? Are maps still broken? Is it still a sporadically whitespace-sensitive language?

not AFAIK, but I am not an expert.

Re: Tell HN: I spend so much time solving problems I feel like giving up

#57

Earlier quoted context omitted.

Is equality still broken? Are maps still broken? Is it still a sporadically whitespace-sensitive language?

not AFAIK, but I am not an expert.

Leading questions, I'm afraid. Yes, equality is still broken, maps are broken (and in new & interesting ways in EMCAScript 6), and the language is occasionally whitespace-sensitive.

JavaScript was hastily designed, has never recovered, and shows no sign of ever fixing the fundamental problems. :-(

Re: Tell HN: I spend so much time solving problems I feel like giving up

#58
No one gets the perfect start, and there are gonna be painful change as you progress and realize past mistakes. That's part of the learning process. Regardless of the changes you're still improving and gaining experience, and that's never a bad thing. Try to look more on the positive side of things. Take small steps and satisfaction once u get it, then move forward.

Re: Tell HN: I spend so much time solving problems I feel like giving up

#59

Earlier quoted context omitted.

not AFAIK, but I am not an expert.

Leading questions, I'm afraid. Yes, equality is still broken, maps are broken (and in new & interesting ways in EMCAScript 6), and the language is occasionally whitespace-sensitive. JavaScript was hastily designed, has never recovered, and shows no sign of ever fixing the fundamental problems. :-(

Equality isn't really as broken as people seem to think. And if it bothers you that much, use ===. Yes, it can be annoying, but it works.

What do you mean about maps, and whitespace sensitivity? I've never heard anything about that.

Re: Tell HN: I spend so much time solving problems I feel like giving up

#60

Earlier quoted context omitted.

not AFAIK, but I am not an expert.

Leading questions, I'm afraid. Yes, equality is still broken, maps are broken (and in new & interesting ways in EMCAScript 6), and the language is occasionally whitespace-sensitive. JavaScript was hastily designed, has never recovered, and shows no sign of ever fixing the fundamental problems. :-(

Case sensitivity i'm assuming you mean the automatic semi-colon insertion due to a line break after a return statement? I have a hard time seeing this as being a reason to dislike an entire language.

Most languages have features to avoid, JavaScript is no different. Many JavaScript developers use linters to avoid the poor `==` feature. I'm unfamiliar with the argument of the `Map` datastructure implementation being broken. Do you have a reference to that claim?

Post reply on HN