EDIT: devRant April Fools joke (2017)
-------------------------
@trogus and I have had an absolute blast working on devRant over the last year. However, we're strong believers in only working on a project if you're passionate about it, and over the last few months, we've sadly lost some of that passion so we've to announce, with heavy hearts, that we will both be moving on. We've decided to focus 100% of our energies on our next product, one which we are confident has billion dollar potential: Semicolon JS (http://semicolonjs.com).

We identified this sizable market opportunity as we were building out the new devRant website. Every JavaScript framework we tried left us wanting more. More efficiency. More elegance. More extensibility. That's what Semicolon JS is: more. More than a framework, it's a guiding philosophy. We believe that Semicolon JS will do for front end development what Material Design has done for user interface design. We're calling it Semicolon JS because even though you can still develop JavaScript without it, like a semicolon, we think it will soon become a standard and synonymous with quality JS development.

So comes the obvious question. What will happen to devRant? We wanted to make the announcement today because we will be officially shutting down the product in 30 days. So that gives everyone a full month to take in the last memories, look at those rants they really loved, and hopefully take some time to chat with @trogus and I about Semicolon JS and what we have planned.

With so many thanks and looking towards the future,
- @dfox and @trogus

Haven't seen a JS framework in a while? Well say no more, I just created a framework to make sure the flow is ongoing:
https://github.com/tahnik/...

Enjoy!

So I was asking what are the most hilarious JS framework names can we find, and this is what I get from npm 😂😂😂

- bitchify (https://github.com/Schascha/...)

- fuck-shit-up (https://npmjs.com/package/...)

- css-what? (https://npmjs.com/package/css-what/)

- hooker (https://npmjs.com/package/hooker/)
there are many actually

- thanos-glove (https://npmjs.com/package/...)

And many more, what's yours?

Can someone recommend me some good js readings ( algorithms / pure js / no framework related ) ? I just discovered this website: http://www.thatjsdude.com/ and I want more ...

!rant
Here's a peek at the current state of the service that I'm developing as a side project(plenty of time meanwhile searching for job).

It's a renting service, more automated and with more(and better, imo) search criterias. By automated I mean that I don't have to scroll through search results half backed with poor filters. You create a search, the search will iterate as soon as there is process power in the queue of the searches, and when it's done it will notify you(in different ways(communication channels) and different times, all setup by the user)

.NET Core 2 is the reference framework for the backend; HTML5,Razor, SCSS,JS for front-end.

What do you think about?
(https://thepra.github.io/previewRen... for more pictures)

There has been a post today about the existence of too many js frameworks. Which reminds me of this awesome post https://hackernoon.com/how-it-feels...

At first I thought someone was corpseposting, as it is my understanding that the js ecosystem is calming down a bit. But then I noticed that post got almost 20 upvotes. So here's my thoughts:

(I'm not sure what I'm ranting about here, as it feels kinda broad after writing it. I think it's kinda valid anyhow.)

I'm ok with someone expressing frustration with js. But complaining about progress is definitely off to me.

How is too many frameworks a bad thing?

How does the variety and creation of more modern frameworks affect negatively developers?

Does it make it hard to understand each of these new frameworks?
Well, there's no need to. Just because it has a logo and some nice badges and says it will make you happy doesn't mean you should use it.
You just stick to the big boys in the ecosystem and you'll be fine for a while.

Does it make you feel compelled to migrate the stack of every project you did?

Well, don't. If you don't like being on the bleeding edge of js, then just stick to whatever you're using, as long as it's good code.

But if a lot of companies decided to migrate to react (among others frameworks), it's because they like the upsides: the code is faster to write, easier to test and more performant.

In general, I'm more understanding/empathic with beginner js programmers.

But I have for real heard experienced devs in real life complain about having to learn new frameworks, like they hate it.
"I just want to learn a single framework and just master it throughout my life" and I think they're lowering the bar.

There's people that for real expect occupying positions for life, make money, but never learn a new framework.

We hold other practitioners to high standards (like pilots or doctors), but for some reason, some programmers feel like they're ok with what they know for life.

As if they couldn't translate all they learned with one framework to another.

Meanwhile our lives are becoming more and more intertwined with technology and demand some pretty high standards. Standards that historically have not been met, according to thousands of people screaming to their devices screens.

Even though I think the "js can be frustrating" sentiment is valid, the statement 'too many js frameworks is bad' is not.

I think a statement like 'js frameworks can go obsolete very quickly' is more appropriate.

By saying too many js frameworks is a bad thing you're
1) Making a conspiracy theory as if js devs were working in tandem to make the ecosystem hard,

But people do whatever they want. Some create packages, others star/clone/use them.

2) Making a taboo out of a normal itch, creating.
"hey you're a libdev? just stop, ok? stop"
"Are you a creative person? Do you know a way to solve a problem in an easier way than some famous package? it doesn't matter, don't you dare creating a new package."

I'm not gonna say the js world is perfect. The js world is frantic, savage, evolves aggressively.
You could say that it (accidentally) gives the middle finger to end users, but you could also say that it just sets the bar higher.

I liked writing jquery code in the past, but at the same time I didn't like adding features/fixing bugs on it. It was painful.

So I'm fine with a better framework coming along after a few years and stealing their userbase, as it happens almost universally in the programming world, the difference with js is that the cycle is faster.

Even jquery's creator embraced React.

This post explains also
https://medium.com/@chrisdaviesgeek...

Today I've confirmed that there actually are real developers that aren't monkeys in my company and team.

Me: {discussing how to fix something, he said we will use some new tech} ... So how do you up with all this latest tech?
Him: https://www.thoughtworks.com/radar
Me; Thanks! I was thinking it was just a web dev skill :) I mean looking at it package.json, I always think how can someone pick all these modules for a single app... And there's always a new JS framework.
Him: You goto sleep knowing be day will bring new frameworks to keep up on :D

So yea there are actually people here that actually know what they're doing...

A new JavaScript framework you're saying?

I was working on a dashboard website, and when I was deciding what to use (plain JS, Angular...) I've decided to make my own, lightweight routing framework.

It's on GitHub (https://github.com/Kamebase/Kame)
What do you think about it?