5 ms·
> seasoned JavaScript developer you simply know to ignore those corners I'm sorry, but how does a seasoned Javascript developer ignores the absence of compile-
by golergka 10y ago
> seasoned JavaScript developer you simply know to ignore those corners
I'm sorry, but how does a seasoned Javascript developer ignores the absence of compile-time type checks? Aside from switching to a language that compiles to Javascript.
- jcao219 10y agoI've always thought that Javascript makes up for its lack of compile-time guarantees with compensating tooling. For example, it's common to use Flow with Javascript to enable static type checking before actually running it. The language itself doesn't guarantee type safety, but when used with peripheral tooling, the developer isn't missing too much.
- bruce_one 10y agoThere are many popular dynamically typed languages. Why is it suddenly a foregone conclusion that seasoned Javascript developers all want compiled statically typed languages?
- golergka 10y agoI know that it's a very old argument that I'm not going to win. But I would like to provoke you to it because I'm really trying to change my mindset, coming from a static language to Javascript - and I still just don't see, where are the wins. Please argue with me, because I _want_ to be convinced. I'm trying. It may be because of the habits I developed, writing compiled code. I always would first concentrate on my concepts, things that I want the code to do, data and flow structure - while keeping all errors (even syntax) silent. And only when I got everything I wanted implemented and consistent, I would turn to a compiler to quickly fix all mismatches in API, all wrong method names and other trivial blunders. Now I stumble, feeling that I'm a blind man going through a minefield. Every line I write, I have to think about the things that I want to express and the mechanics of language and API simultaneously - because nothing's got my back. (Yes, I know that I should write unit tests, but not all of us have the luxury of working on perfect projects, starting perfect projects from scratch, or having the resources of putting good practices into legacy code). Every time I discover that I mistyped the name of the function or variable, forgot to use "this" when referring to an object property (C# habit), forgot that external API function returns a custom type and not a string - I do it too late. Instead of quickly fixing the thing that I've only typed right now, I have to go back, and spend time reading and understanding relevant code again. All I'm trying to understand is, where are the trade-offs? Where are all the awesome dynamic things that make all that worth it?
- bruce_one 10y agoIt's alright, I have no interest in an argument :-) I like Javascript, and that's enough for me - and I (in _most_ situations) find dynamic typing more of a benefit than hindrance; but I don't mean to purport that my perspective is everyone's perspective :-) IMO it's very plausible that dynamic typing will never be better for you; because we're all different and we don't all like the same thing. If you've come to learn that dynamic typing doesn't suit you, act accordingly, don't just try to change yourself because something else works for others. If you're interested in static typing, maybe try moving to Typescript? AFAIU it also integrates fairly well with normal Javascript, and hence maybe it's more to your taste? And if there are other people feeling the same way you are on your projects, it mightn't be too difficult to move new (or maybe a subset of new) development to something more your taste instead? (I've heard good things about Flow as well, and maybe it's simpler to "sneak in" to your projects, and offers big enough benefits for you?) In my experience, legacy projects (or projects where there's pressure to cut corners (eg unit tests)) are often the bigger issue than the language. (eg I've been "in pain" working with code in languages I otherwise like that was obviously done in a big hurry, or evolved obviously from clumsy requirements and hence has big inconsistencies. (As an actual example of a reason _that applies to me_, the last Javascript project I worked on ran the integration tests faster than the last compiled statically typed project compiled (and reloaded) - hence I ran the tests in a watching process, and felt more productive and less frustrated. And yeah, I haven't written `this` for a very long time :-p )
- chubot 10y agoI wrote on my blog about some of the annoyances that come with type checking: Type Checking vs. Metaprogramming: http://www.oilshell.org/blog/2016/12/05.html http://www.oilshell.org/blog/2016/12/05.html http://www.oilshell.org/blog/2017/01/21.html http://www.oilshell.org/blog/2017/01/21.html (at the end, pretty printing requires metaprogramming, or escaping into another language) Whenever you have a code generator like an ORM, or protobuf-like schema languages, you can use metaprogramming instead. Generally I think this helps the program so you don't have these impenetrable walls between layers, where one person understands one side and the other person understands the other. I find that a lot of programmers coming from statically typed languages are writing Java in Python, or Java in JavaScript. In Java you don't really think in terms of metaprogramming. If that's the case, then it is going to feel annoying. You're getting all the downsides without any of the upsides. I would look at Go for other examples of the downsides -- namely the lack of generics. Go is attracting a lot of Python and Ruby programmers. In Go, you can't write basic generic functions like max(), map(), filter(), and sort() -- in JavaScript and other dynamic languages this is not something you would think twice about. I guess between metaprogramming and generics, dynamic languages let you write more abstract and concise programs. Programming in statically typed languages feels repetitive to me, and the architecture is quite clunky unless you are doing textual code generation. Steve Yegge also has a bunch of good posts about dynamic languages. Thanks for the honest question. I think it's important to remember that there are tradeoffs. I fully admit that type checking is useful in many circumstances. I would like the best of both worlds. I'm a little disappointed that recent hybrid languages like Dart and to some extent Racket have had problems with optional typing and gradual typing. It is something I'm interested in but it seems like an unsolved problem.
- watson 10y agoYou can't have a language that satisfies both camps. Some like statically typed languages, some don't. Stating that it's an inferior language because it's not statically typed is just plain wrong. I accept that you belong to the statically typed camp, and that's awesome. But don't be fooled into thinking that it's somehow better - it's just a different approach to programming. If you like it, then that's cool.
- erikpukinskis 10y agoI guess I'm a seasoned JS developer. If I needed compile time type checks for a snippet of code, I would use a language with compile time type checking that compiles to JavaScript. If I needed compile time type checks for many snippets of code, I would take a few days off and rethink my architecture. Ask myself why my call sites are so brittle or confusing that I am making frequent type errors.
- graphememes 10y agoWell said, came to say this.
- Illniyar 10y agoWe write tests. Really, I find compile time checks to be moot when you have fast running and good unit tests.
- douche 10y agoYeah, that whole suite of tests that you don't have to write yourself (or, more likely, you were never going to write, if you had to do it yourself...) that runs automatically every time called a compiler.
- Illniyar 10y agoThat's misleading. You don't write tests to check types. You write the same tests you would with a typed language. There is no extra work. A by product of testing your logic is that it will fail if there is a type cast problem.