Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JavaScript frameworks and topics to learn in 2017

medium.com

Post reply on HN
Print view View original

111–120 of 121 posts

Re: JavaScript frameworks and topics to learn in 2017

#111

Post by ericelliott »

ClayFerguson wrote: post #96

TypeScript is definitely by far the most important thing mentioned in the article. And no I didn't even read the article. I just searched it for the word TypeScript to see what it said. However, the author apparently is pretty clueless because he implied TypeScript has something to do with Angular. It doesn't. TypeScript is needed ANY time the runtime is JavaScript. Namely, in the browser. The only other technology T…

If you click through the links and actually read the content, I have plenty more to say about TypeScript, and why I consider it optional learning for JS developers.

Re: JavaScript frameworks and topics to learn in 2017

#112

Post by ericelliott »

jim_d wrote: post #100

I'm curious what people think about type checkers in JS. I've been doing full stack development for the last few years and BE development before that. Type safety has always been worth it to me, we adopted Flow and haven't looked back, although some FE developers aren't big fans of it.

See "You Might Not Need TypeScript (or Static Types)" https://medium.com/javascript-scene/you-might-not-need-types...

Re: JavaScript frameworks and topics to learn in 2017

#113

Post by jessaustin »

jdd wrote: post #105
jessaustin wrote: post #103

Earlier quoted context omitted.

That's great, but it ain't there yet. [0] Incidentally, releasing a version 2 without deprecating version 1 seems a bit of a project smell... It might be the right thing to do in a particular situation, but what happened on the project that led to that situation? [0] Tree shaking completely broken? #2867 https://github.com/webpack/webpack/issues/2867

Not smell just semver – http://semver.org/

To my mind, the "semver way" would be to make tree-shaking an option on a new minor version. After some number of releases, it might become a default on a new major version, if the maintainers so chose. Splitting the project into multiple codebases is not required by semver.

Re: JavaScript frameworks and topics to learn in 2017

#114

Post by prodigal_erik »

jessaustin wrote: post #103
Kiro wrote: post #102

Earlier quoted context omitted.

Webpack 2 is where it's at. Tree-shaking was Rollup's big feature and Webpack 2 has it.

That's great, but it ain't there yet. [0] Incidentally, releasing a version 2 without deprecating version 1 seems a bit of a project smell... It might be the right thing to do in a particular situation, but what happened on the project that led to that situation? [0] Tree shaking completely broken? #2867 https://github.com/webpack/webpack/issues/2867

Whole versions don't get deprecated. Visible features get deprecated when they are still present in the latest version but will be missing or incompatible in the next major version.

Re: JavaScript frameworks and topics to learn in 2017

#115

Post by ClayFerguson »

ericelliott wrote: post #111
ClayFerguson wrote: post #96

TypeScript is definitely by far the most important thing mentioned in the article. And no I didn't even read the article. I just searched it for the word TypeScript to see what it said. However, the author apparently is pretty clueless because he implied TypeScript has something to do with Angular. It doesn't. TypeScript is needed ANY time the runtime is JavaScript. Namely, in the browser. The only other technology T…

If you click through the links and actually read the content, I have plenty more to say about TypeScript, and why I consider it optional learning for JS developers.

Well you've definitely misguided everyone by suggesting TypeScript is in any way related to Angular. There is absolutely no relation. You should fix that.

Re: JavaScript frameworks and topics to learn in 2017

#116

Post by Can_Not »

heavenlyhash wrote: post #27

I want a javascript framework that allows me to update a page incrementally, but also always works correctly and contains full content from the first server-side page load. Are there any options for this? Are there even keywords I can search for that discuss this? Sure, this files under "anything is possible", but honestly, I'd like a javascript framework that doesn't actively fight me also having static content. Any…

I've been trying to find a solution for this problem. Basically, most of these suggestions here are "rewrite everything in NodeJS" (ignoring the requirement not to) or don't actually come close to meeting your requirements. Great news, I probably won't do better, but I'll post some things I haven't seen yet:

- Ruby - Pakyow framework - I think it uses ring.js and/or vDOM

- Elixir - Texas - might be an experiment, not sure

- Scala - lyft framework

- NodeJS - anything

- anything else - You can use react/vuejs+nodejs as a "templates proxy" and defer your real backend to your language of choice. You get the full whatever of nodejs, plus you can simplify your back-end by only using JSON.

Re: JavaScript frameworks and topics to learn in 2017

#117

Post by Can_Not »

ericelliott wrote: post #106
doomtop wrote: post #78

Great list! But I was perplexed by the text editors mentioned. Author claims to be looking at trend data, but seems to have a bias against Subljme Text editor. I don't know if there is some connection to Atom or VSCode, but it seems easily verifiable that Sublime and vim are vastly more popular than other editors mentioned, yet Sublime is inexplicably absent and vim is mentioned last and sort of offhand as more of ju…

Sublime is absent because a lot of previous sublime users are now Atom users, and it is now the more popular editor by a large margin. Those comfortable with Sublime will find Atom very inviting.

Except when you need to open a file more than 100 lines, atom is nicer.

Re: JavaScript frameworks and topics to learn in 2017

#118

Post by heavenlyhash »

bigmanwalter wrote: post #66
heavenlyhash wrote: post #27

I want a javascript framework that allows me to update a page incrementally, but also always works correctly and contains full content from the first server-side page load. Are there any options for this? Are there even keywords I can search for that discuss this? Sure, this files under "anything is possible", but honestly, I'd like a javascript framework that doesn't actively fight me also having static content. Any…

It's no longer cool on HN to use it, but jQuery-Pjax ( https://github.com/defunkt/jquery-pjax ) solved this problem years ago in a minimally intrusive way. I build all my projects with it. It's the only SPA framework that allows for full server side rendering after minimal configuration. It also manages to do this without introducing needless abstractions into your code. Even more magical: it works with any server si…

This looks really cool! And simple. I am looking at it closely.

I'm wondering if it can also support merging elements into an existing document:

for example, I have a table of elements, and suppose that I have an 'id' attribute for each row which correctly identifies which elements I would like to replace when new content is fetched. If some elements are replaced, of course I must replace them; but if neighboring rows are unaffected, if the users has a selection in them, their cursor should not move. So, replacing the entire content div is not ideal: the user's cursor will be discarded if it's anywhere in the replaced area.

This seems like something that almost a for-loop around this jquery-pjax stuff would handle, but of course if someone else has written it already, I want to join their project rather than reinvent it!

Re: JavaScript frameworks and topics to learn in 2017

#119

Post by Can_Not »

bkovacev wrote: post #89
_uhtu wrote: post #86

Earlier quoted context omitted.

That's simply not true. I'm kind of tired of hearing about this kind of stuff said about JS. This comment adds absolutely nothing to the discussion about this article. Did you even read the article before making this comment? It would appear you didn't since this is just a classic, low effort javascript bashing comment that mentions no evidence from the article. Every single thing he marks as important to learn is ei…

From my personal experience what the parent comment stated is actually very true. As someone who is actively trying to get into the JS world coming from the back-end side it is extremely hard to find best practices that do not change every other week. In the beginning of the year, tutorials were made with grunt, yarn, yeoman and the likes, then they were written to use gulp, bower and now it's webpack and what not. I…

I followed a gulp tutorial, continued using it. When webpack came out, the gulp community seemed like it's was just as alive as before. When webpack came out I didn't rewrite all my gulp code to webpack. I'm not sure how you got different results.

Re: JavaScript frameworks and topics to learn in 2017

#120

Post by bigmanwalter »

heavenlyhash wrote: post #118
bigmanwalter wrote: post #66

Earlier quoted context omitted.

It's no longer cool on HN to use it, but jQuery-Pjax ( https://github.com/defunkt/jquery-pjax ) solved this problem years ago in a minimally intrusive way. I build all my projects with it. It's the only SPA framework that allows for full server side rendering after minimal configuration. It also manages to do this without introducing needless abstractions into your code. Even more magical: it works with any server si…

This looks really cool! And simple. I am looking at it closely. I'm wondering if it can also support merging elements into an existing document: for example, I have a table of elements, and suppose that I have an 'id' attribute for each row which correctly identifies which elements I would like to replace when new content is fetched. If some elements are replaced, of course I must replace them; but if neighboring row…

https://github.com/MoOx/pjax is a version that might work.

It's a reimplementation of the library without jquery and with a few extra features.

Instead of working on a single container where all the ajaxing happens, you provide it a list of IDs, and then it extracts the nodes with those IDs from the response and replaces them throughout the document. If I understood you, that's the behaviour you're looking for. It also has a few extra hooks for animating content in and out.

It's not as widely used as the defunkt version though, and I remember needing to stop using it because of a bug where it wasn't scrolling to in-page anchors properly. But hopefully it would work for you.

Personally, I might just use the defunkt version and write a before and after hook to refocus the appropriate input. When it comes to reimplementing browser features in JavaScript, there are lots of edge cases so it's nice to use widely adopted libraries.

jQuery-Pjax is used by GitHub so you know it's well tested :)

Post reply on HN