Echo JS 0.11.0

<~>
nydkim 1599 days ago. 
Hi people, I'm Nak. 
I've been coding for around half a year now, and built some projects too. 

And for the past 5 weeks, I've been working on an open source project, and it's been quite a journey. This was my first time coding in TypeScript, and it was a lot of hitting blocks and learning. Through this project, I have become more familiar with typing, which for me who started coding in plain javascript, was very foreign. 
But i definitely saw the benefits of typing even though everything was so much of hassle and error-throwing(T.T) as the compile time errors prevented runtime errors! 

If anyone would like to take a look at it, and give me a comment, I would really appreciate it, since I am still in the learning phase. Also I would really be grateful for a star (wink)!

https://github.com/oslabs-beta/Kafka-Sprout

ntyti 1599 days ago. link 2 points ▲ ▼
Hey, this looks really cool. Though I'm not familiar with Kafka, I've been trying to learn TypeScript and it's cool to see how it's growing and being implemented (instead of using JavaScript) into projects.
nydkim 1599 days ago. link 2 points ▲ ▼
@ntyti thank you so much! it's really nice that you gave a compliment as my team and I spent a lot of time into the project. I've learned a lot, but still not sure if we have implemented best practices. I'm glad we are on the same boat in learning TypeScript!!!
Neonsquare 1598 days ago. link 0 point ▲ ▼
Hm... just a quick glance... it doesn't seem to make much use of typing and without strictNullChecks you miss one of the most important typing aspects in TS.
asmyshlyaev177 1599 days ago. link 0 point ▲ ▼
Typescript gives you false sense of protection from errors and bad code.
It's prevents simple errors, but it makes code more messy and require spend time on learning and debugging TS itself.
When you learn further better to know specific of JS(or any language you coding on) and plan better architecture it will bring more benefits.
Simple stuff like SOLID principles, tests and experience more important.

But it make sense for many companies those hire juniors and replace them often, in that case better to have at least some guarantee that code works.
badsyntax 1598 days ago. link 0 point ▲ ▼
I agree there will be extra time required to learn TypeScript and construct your types correctly. Saying that, I find the TypeScript type system _not that hard_ to learn. Yes there will be an initial learning curve but it's easier to learn than other type systems (eg flow). 

Once you've setup your types correctly you can argue it saves you time in the long run, especially when it come to refactoring. Also consuming typed packages is easier, you don't need to refer to the docs to understand expected data types or parameters, the IDE will tell you how to consume 3rd party code. 

TypeScript should complement and not replace existing good practises.
asmyshlyaev177 1598 days ago. link 1 point ▲ ▼
"Yes there will be an initial learning curve but it's easier to learn than other type systems (eg flow)."
Flow is terrible, i remember my experience with it. Learn 1 unnecessary thing to easier learn even more useless stuff, strange idea.

I have pet project on TS, at first it was fine. But after some time code become too complex, and TS only makes it more complicated.
Instead of spending time on code design and proper tests, i spent it to fight with TS.

Can keep only limited amount of things in mind, there already too many stuff to know, remember and learn in JS ecosystem. 
At first TS protects you from simplest errors, but consumes too much attention for it. This time can be spent much more efficiently.
it is simply not worth it.

For simple errors i have unit and integration tests, no replacement for it anyway, and tests also helps to see big picture and what can improve in code design.
80% of problems is bad architecture, not knowing specific of language or misuse of other libraries. TS can't help with it at all, only add another thing that i should worry instead of code.