What are the newest popular ideas and/or projects? What's trending up and what's trending down?
For further actions, you may consider blocking this person and/or reporting abuse
What are the newest popular ideas and/or projects? What's trending up and what's trending down?
For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (49)
That's a good question, Ben! I'm exactly in the middle of my next JS digest to put all the cool repos I've recently found. There I already see some interesting frontend trends to follow. Hope, I'll manage to finish it this week!
I'm back again. One trending project I forgot to mention is Flutter.
Yes! Flutter.
You welcome!
ps: Currently taking the Flutter course on Udacity
Haven't seen a mention of webVR (which google is pushing heavily) and more specifically a-frame by Mozilla which makes threeJS far more palatable to newbies, novices and apprentices.
VR and AR are huge growth-points in the world of tech, and - as the google speakers in the webVR link above demonstrate - the Web is a major part of the strategy of major VR players like Google.
It represents a whole new direction for the web with lots of space for innovation. Eg What's the best way for a user to be able to navigate in 3D space? etc.
The trend might be early, but it's definitely UP :]
Here would be things I would list specific to front-end. Obviously these are just my opinion
Trending up:
Plateau (not fading but not maybe peaked):
Trending down:
I know some will take issue with my trending down on Angular. I don't think it is going away by any means - lots of large enterprises especially rely on it - and it remains a huge community. But I do think we people are being drawn away by frameworks like Vue, that brought along an audience that wasn't comfortable with the idea of switching to React.
Things are getting commodotized all the way. Moving thingsfrom front-end devs to designers and from back-end devs to front-end devs, because they are just easier to handle now.
Stuff like Pagedraw could accelerate the UI development (which is the slowest part I think) and also moving it from developers to designers.
Glueing together the back-end with the UI is still a major pain-point that needs to be handled by a dev.
On the other hand, serverless makes back-end development much simpler and allows front-end devs to get into it easier.
This gives back-end devs more time to consider tech that was too hard or time-consuming to learn years ago, like machine learning etc.
on the top of my head the following:
YES! +1
Up:
Down:
PWA's
Online IDE's like stackblitz
Libraries like React after its newer release 16.3 , VueJS
React Ecosystem in total
Serverless Hosting for PWA's and Mobile Apps(AWS AppSync , AWS Lambda and Firebase).
Code Formating (parceljs, prettier etc..)
Thats all I know. Anything Else i missed?
Just GraphQL and Headless Chrome. There is a project called Puppeteer that makes it easier to work with headless Chrome.
It's not entirely Front End but definitely it is a thing.
The pipeline operator is becoming a thing (hopefully sooner rather than later).
for await will be nice as well.
Pipeline operator will be sweet. I really like to use the Lodash/fp
composefuntion, but I would be nice if they integrated it in the language.I think the camp is divided on this still, but regardless, the adoption of static typing in JavaScript is increasing.
My experience has been with TypeScript, so in this space there are several large projects in OSS land that have been or started using TypeScript. The thread in this tweet names some big ones.
On the Flow side, I have less knowledge of projects using it as I don't really work in that space, but I'm aware that FireFox DevTools and spectrum have embraced types with Flow. If you know of other large OSS projects using Flow, please comment.
Also related...
Do you use Static Typing in JavaScript?
ℕ𝕚𝕔𝕜 𝕋𝕒𝕪𝕝𝕠𝕣
Coming from a Java/C background in university this really really intrigues me. It was one of my big hangups context switching, learning web while studying Java. I am interested to see where this goes. There was an article I read by Eric Elliott called The Shocking Secret About Static Types where he basically says that static typing in JavaScript is not necessary and doesn't necessarily reduce bugs.
It is an interesting, albeit controversial, take.
It's definitely not necessary as many have built large scale applications in Javascript before Flow and TypeScript, but in my experience, if you want to scale your team quickly on a project, avoid silly mistakes like typos and be able to refactor quicker, you need something like TypeScript. Couple that with editors that have plugins or native support for TypeScript, and you all of a sudden have a way better developer experience.
I agree partially with him about it not preventing bugs. TypeScript eliminates certain kinds of bugs: runtime errors due to typos, potentially issues related to type coercion and stuff like assigning a completely different type to a variable because these are caught at transpilation (compile) time. Basically a lot of the same issues that would fail at compile time in strongly type languages like C# or Java.