¿Cuál es la mejor manera de evaluar las herramientas de desarrollo web?

Purpose and scope is truly important and unfortunately very few people/agencies guide people on it. I have came across founders who expect their product to be build in wordpress, and others who would want a simple portfolio or landing page in custom solution. The first one is a bad idea because even if you squeeze your functionality in wordpress, sooner or later you will have to throw away the code and start over wasting all the effort In second case, you are wasting time and resources on a simpler website that can be done in few clicks and design tweak.

In my experience as a developer, some factors matter beyond language or framework. Some important questions that we need to raise are also points such as: - What platform will this run on? Cloud, local server, IOT. - Functionality: for each type of platform where your web code can run, a language can be more optimized than another to perform its function on that platform or for that type of service. Not every language is great for working with managing multiple request queues, or training models with artificial intelligence. - Greater platform support: some IOT platforms may have more support for some languages than others, libraries, community, etc.

💡 Indeed, planning everything from the start is the most important step in web development. 💡 It's all about decisions, and the tools you start with, the features and functionality you plan for of your web application, are the most important ones, before you stat that hard work of coding. 💡 Another important factor to plan for is perfotmance - the volume of data processing, storage needed and the estimated user traffic of site will tell you what choices you have for the machines that will run your application. Performance is always the key and good software, without good hardware is not as good as you might imagine.

I had worked with a few organizations as well as completed a few Freelancing projects, so far what I understood is the ability to convince what exactly the client is looking for. If your client wanted a static web page to showcase their business profile, as a developer, you are gonna ask them about details. Their brand color, font, assets etc. What if the organization doesn't have a proper color or a registered font family? The developer himself gets help from a designer and does a mockup, right? But what if they call/mail you to change what you were working on. The important fact everyone should know is how to communicate or express the requirements in a proper channel.

Web development has grown rapidly in the last one decade, and it's important to choose the right tools before starting the development. Here is what I think before selecting a tool: 1) The popularity of the technology and how big the community is, if it's an open source tool. 2) How easy or difficult it's to find developers. 3) Development ecosystem and interoperability with other technologies.

Performance is really important when you are planning the usage, concurrent usage, size of data etc. Some systems might be data intensive but used by 5 people (scientists for example), others would be something simple like Twitter and be used by millions hence each system needs its respective design and usage based performance selection. What's important to note, is you don't want to build a complex distributed system while developing a simple system until you are actually targeting to reach millions or you might end up spending more on hosting and services than in development that will actually bring customers.

Depending on the scope of the application, thinking about scalability may or may not be an option. Does the language you are building your website support to scale the services you need easily and cheaply?

When assessing web development tools, two critical factors to consider are performance and compatibility. Performance encompasses how well a tool or technology can handle the demands of your project, including speed, responsiveness, and efficiency. Compatibility, on the other hand, focuses on whether the chosen tools align with the various platforms, browsers, and devices your website or application needs to support. To ensure a seamless user experience, prioritize tools that offer optimal performance and compatibility with your project's target environments.

Truly important even after GPT. There will always be unique challenges needing discussions and support of development community. Also the support of any limited used system can disappear in a day so always use publicly used and supported tool & technology unless you can take over and maintain the tool in case the owners decide to abandon it.

Unsupported languages and outdated documentation keep new programmers away from their choice, as no one wants to be without support when they need to implement something different from what is in the manual

I check if the tools has a good community, support and some examples. Also an important thing is if the tool is manteined. You can check this on Github with the released dates and with the medium time of response or closing the issues.

Imho is one of the most important things a good dev community of the tools you a working with. Performance is very important, of course. But if your choosen framework or library is unsupported in 1 or two years you often have to replace that. Especially in the enterprise segment this is critical.

Popularity is definitely important, but it shouldn't be the sole decision make else everything would be built in js these days. Every tools and framework has its pros and cons and need to be analyzed based on lots of factors.

Don't always go with the flow. Think about the problem and consider the best solution for solving it. For instance, if the requirement is to create an SEO-friendly web application using a JavaScript framework or library, you might want to consider using Next.js, as it provides the best solution for SEO. Additionally, it's important to consider whether the framework you intend to use has the potential for a significant market share in terms of job opportunities.

Every day there is a new library or framework around the corner. Especially in frontend development. During my 20 years++ I've seen a lot of them. So coole wisely if you need this or that... or just stay with the tools that work.

A confident IDE could support and so speed up the development. But the IDE must have also a good looking and organization and must be quick to respond.

Functionality: Do they offer the same features or features missing from one tool but present in another? Usability: Are they easy to learn & use documentation & tutorials clear & concise Tools performance scenarios: How well do they handle different types of data & scale to large projects? Development process: Do they make it easier or harder to develop a website? More productive? Output: Easy to maintain? Do they produce high-quality code Web development tools: Code editors: VS Code, Sublime, Atom IDEs: IntelliJ IDEA, Eclipse, NetBeans Frontend frameworks: React, Angular Backend frameworks: Laravel, Django, Spring Boot CMS: WordPress, Drupal, Joomla Version control systems: Git, GitHub, Bitbucket Testing frameworks: PHPUnit, Jasmine, Mocha

Always consult with someone and run your selection with someone, especially someone who is more inclined to a different tech stack or tool and see what they say with an open mind. It could save you huge trouble in the long run.

Tool vendors should offer ways to onboard new users which take into account different learning styles(visual, auditory, interactive, instructor-led, etc), such as slideshows, podcasts, developer playgrounds, checklists, or office hours