I recently got into TypeScript, if that counts. I'm really enjoying it so far, but I'm running into some annoying things as a beginner: * For many third-party libraries, needing to write `import * as Something from 'some-package'` instead of `import Something from 'some-package`. * Not being able to import non-TypeScript files, further fragmenting my import style by needing to write stuff like `const styles = require…
For packages with default export, you can use synthetic imports options in tsconfig. For non-js imports, you can create global module declarations (like the below snippet): declare module "*.css" { const value: any; export { value }; export default value; } But you will still need to use some bundler tool like webpack. It will just stop TypeScript from complaining. Type definitions are the biggest issue even today, b…
Ask HN: What “new” programming languages will you be using in 2017
71–80 of 85 posts
Re: Ask HN: What “new” programming languages will you be using in 2017
#72My Q1 goal is to build a simple game of Risk using text-based interface, and some AI that plays the other players - all to help my two nephews in Italy learn Python and have fun at the same time.
Not sure how long it will take, or if I'll ever be successful. Any hint (particularly on the text-based interface) would be really appreciated. I am now looking into Curses and Pygame.
Re: Ask HN: What “new” programming languages will you be using in 2017
#73I recently got into TypeScript, if that counts. I'm really enjoying it so far, but I'm running into some annoying things as a beginner: * For many third-party libraries, needing to write `import * as Something from 'some-package'` instead of `import Something from 'some-package`. * Not being able to import non-TypeScript files, further fragmenting my import style by needing to write stuff like `const styles = require…
Next time I'll go with Flow. Generally the only thing I REALLY need to be typed are the domain-specific models, and so I'd rather be as close to idiomatic JS/babel as possible.
Re: Ask HN: What “new” programming languages will you be using in 2017
#74Lovely syntax, great performance, fast compilation times. With templates and macros provides you can build just right amount of magic you need into your programs.
It desperately needs more developers to bring the language 1.0, and I'm hoping things will move faster in 2017.
- Elixir.
For near-real-time, concurrent systems, I'm tired of using the tools I know (python, js), and I'm eager to start using the battle-tested solutions (BEAM).
- C# (maybe?)
I mainly develop line-of-business applications, and python, with it's great ORM, sqlalchemy makes things so much easier. But I want more type safety, and I'm hoping C# and the ecosystem will reach maturity on linux front in 2017, so I can evaluate C# as my main language for line-of-business applications.
Re: Ask HN: What “new” programming languages will you be using in 2017
#75Re: Ask HN: What “new” programming languages will you be using in 2017
#76We are using it to build our newly minted startup, Metriculator - https://www.metriculator.com
This is the first functional language we are using (long time Ruby/Rails devs). We are also using the Phoenix framework.
Reasons why we chose Elixir/Phoenix -
- Immutability of data makes it easier to reason with and figure out exactly what is changed where.
- Lots of asynchronous work involved. Elixir is built for this.
- Real-time data push (Phoenix channels scale well in this respect)
- Syntax, stability and a vibrant, helpful community.
Re: Ask HN: What “new” programming languages will you be using in 2017
#77I recently got into TypeScript, if that counts. I'm really enjoying it so far, but I'm running into some annoying things as a beginner: * For many third-party libraries, needing to write `import * as Something from 'some-package'` instead of `import Something from 'some-package`. * Not being able to import non-TypeScript files, further fragmenting my import style by needing to write stuff like `const styles = require…