Ask HN: What is the job market like for niche languages (Nim, Crystal)?

Post by zinodaur » Sat, Jul 23, 2022, 2:57 PM UTC

thr0wawayf00 wrote: post #36

blocked_again wrote: post #15

Best strategy for becoming a high paying/good software engineer would be to think of yourselves as problem solver and language as just one of the tool for problem solving. Thinking of yourselves as someone who is a writer of a certain programming language is self constarining and missing the point.

I used to think this way and wound up completely exhausted in my career. Coming from web dev, I used to volunteer to dive into a Objective C repo to fix some random bug in a mobile app and then a week later my boss would ask me to build a big feature in that app. I'd spend a few weeks getting up to speed on the language and build the feature, and then I would never use what I learned again. My boss would ask me to di…

Post by japhib » Sat, Jul 23, 2022, 2:58 PM UTC

akudha wrote: post #8

enraged_camel wrote: post #6

We write Elixir at my current job.

Could you share some more details? What kind of project is it? Did/do you hire your team who already knew Elixir, or did they learn on the job?

Post by mmartinson » Sat, Jul 23, 2022, 3:02 PM UTC

rco8786 wrote: post #51

thr0wawayf00 wrote: post #36

Earlier quoted context omitted.

I used to think this way and wound up completely exhausted in my career. Coming from web dev, I used to volunteer to dive into a Objective C repo to fix some random bug in a mobile app and then a week later my boss would ask me to build a big feature in that app. I'd spend a few weeks getting up to speed on the language and build the feature, and then I would never use what I learned again. My boss would ask me to di…

> I've wasted so much time digging into tools that I've never used again. Don’t think of it this way. Learning new tools is almost never a waste of time, you just don’t know when you’ll need the lessons learned next. But you will.

Post by fendy3002 » Sat, Jul 23, 2022, 3:05 PM UTC

egberts1 wrote: post #38

joe8756438 wrote: post #10

What is it about js you dont like? is it really about the language? a lot of the complaints i hear about js have more to do with “the community”, “the team”, “the application”. here’s the thing: there is _so much_ built in js. i think theres a better chance you find what you want in a mainstream language (js or otherwise), but you first have to identify what your values are.

The biggest detractor of JavaScript isn't so much about its language’s: - lack of strong typing (unlike Ada), - lack of a standard framework (VueJS, NodeJS, Angular, React, Ember, Mithril, Aurelia, Backbone, Polymer) - lack of consistent control of packaging (embedded or HTTP[S]), - lack of consistent naming convention (wild west of competing function names, unlike libc library to name one language), - lack of unit t…

Post by icedchai » Sat, Jul 23, 2022, 3:07 PM UTC

dom96 wrote: post #20

blocked_again wrote: post #15

Best strategy for becoming a high paying/good software engineer would be to think of yourselves as problem solver and language as just one of the tool for problem solving. Thinking of yourselves as someone who is a writer of a certain programming language is self constarining and missing the point.

Precisely. Any good company won't care what programming language you are specifically proficient in. They care about how proficient you are in learning new things. I have created a lot of Nim projects and implemented much of its stdlib. My full-time job isn't using Nim, but the experience I gained through my work in Nim has helped my career significantly.