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

Too Many Tools and Frameworks (2015)

mrmrs.io

Post reply on HN
Print view View original

31–40 of 125 posts

Re: Too Many Tools and Frameworks (2015)

#31

Post by asimuvPR »

douche wrote: post #22
asimuvPR wrote: post #18

The only way we are going to build better tools is to keep building them. Complaining about the sort of cambrian explosion going on right now on web development is short sighted. Ideas need to be discovered, explored and improved. Everything needs to be challenged. This is unknown territory in many ways. It does get a little hectic and tiring at times but that's the price we pay.

The tools need to be better than what came before, rather than just different . So far I've dealt with grunt, then gulp, then webpack. None of these are appreciably better than make, they are just different and newer...

They should definitely try to do things differently. Even when the end result is the same. The reason is simple: it provides an alternate point of view of the problem. Some issues only appear when we try to do things differently. Those issues might exist in the more common approach and be completely unknown.

Re: Too Many Tools and Frameworks (2015)

#32

Post by KerryJones »

This is simply the Pareto principle (80/20) rule, and it's true of most things.

This is also true of Startups -- most of them die, but that doesn't mean they didn't add value in validated learning (positively or negatively).

Elon Musk has often stated that he thought Space X had very little odds of success, but he continued because he believed he could create value that someone else could build on.

Re: Too Many Tools and Frameworks (2015)

#33

Post by usgroup »

AdrianB1 wrote: post #30

Looking at the long term life of an application, the abundance and volatility of the tools and frameworks is a nightmare. Who will find developers for ZZZZ framework in 3 years from now? Also the fragmentation of efforts to improve the tools is a waste of resources. Instead of choosing a few directions and delivering, everyone knows better and it's doing his own version of different, but usually not better, tool. Tha…

Yes then at some point we all end up using ML, Lisp or C, and then it all starts again :)

Re: Too Many Tools and Frameworks (2015)

#34

Post by enraged_camel »

DSteinmann wrote: post #25
niftylettuce wrote: post #20

I'm building a better JS framework https://github.com/crocodilejs/crocodile-node-mvc-framework - release v1.0.0 comes out soon, join in Slack at http://slack.crocodilejs.com/

> CrocodileJS is a Node MVC framework that lets you chew apart JavaScript Four words in and CrocodileJS is already lumped onto the 4/5ths heap of unusable frameworks (Node is an immediate non-starter in the same vein as MongoDB). Just to give you some perspective and perhaps help you see the irony.

Node is an application runtime environment, not a framework. There are frameworks written on top of Node, such as ExpressJS.

http://www.javaworld.com/article/2079190/scripting-jvm-langu...

Re: Too Many Tools and Frameworks (2015)

#35

Post by KerryJones »

mgalka wrote: post #3

> "Using the same standards that categorize 90% of science fiction as trash, crud, or crap, it can be argued that 90% of film, literature, consumer goods, etc. is crap." 90% is also roughly the failure rate of startups. Pareto principle?

Yep, you just very concisely explained a comment I just wrote (I didn't see this one).

Re: Too Many Tools and Frameworks (2015)

#36

Post by austinpray »

douche wrote: post #22
asimuvPR wrote: post #18

The only way we are going to build better tools is to keep building them. Complaining about the sort of cambrian explosion going on right now on web development is short sighted. Ideas need to be discovered, explored and improved. Everything needs to be challenged. This is unknown territory in many ways. It does get a little hectic and tiring at times but that's the price we pay.

The tools need to be better than what came before, rather than just different . So far I've dealt with grunt, then gulp, then webpack. None of these are appreciably better than make, they are just different and newer...

You don't understand what webpack is. It's a module bundler. You use webpack in conjunction with make, grunt, gulp, or any other task runner or build system.

Re: Too Many Tools and Frameworks (2015)

#37

Post by KerryJones »

bungle wrote: post #7

Light bulbs have not improved, they have become worse, and are designed to fail.

How so? Energy consumption is far less, the raw price is much cheaper, varieties of brightnesses and Kelvin, different quality of lights, different designs for the aesthetic look.

We even have smart light bulbs -- my door light turns itself on and off at dusk and dawn.

Re: Too Many Tools and Frameworks (2015)

#38

Post by rurounijones »

niftylettuce wrote: post #20

I'm building a better JS framework https://github.com/crocodilejs/crocodile-node-mvc-framework - release v1.0.0 comes out soon, join in Slack at http://slack.crocodilejs.com/

I am honestly not sure if this is some satirical masterpiece or not.

The README says yes but the amount of work that has gone in to it...

Re: Too Many Tools and Frameworks (2015)

#39

Post by ffggvv »

electic wrote: post #27
dperfect wrote: post #13

The problem really isn't a function of the number of tools and frameworks in existence, but rather in the distribution of popularity among them. Each ecosystem around a set of technologies essentially has its own "Herfindahl index"[1] of sorts. For example, the Ruby ecosystem's index might be fairly high, simply because Rails is so dominant (to the point where Ruby and Rails are often conflated by outsiders). On the…

You can spin it this way if you like. However, a big part of this framework and Tool epidemic is ego. The trick is to take a dominant framework or tool, find a deficiency, and then rewrite it again with that deficiency fixed. Why? Because if it takes off, your career takes of. What developers should really do is contribute and make the existing projects better. Everyone will thank you for it.

Nope they won't, because then your are just another contributor.

There are thousand working on linux (the kernel). How many of them do you know?

Post reply on HN