#Preact and React

[orangemantrausa]

Can't decide between Preact and React? Our in-depth comparison helps you choose the best framework for your angularJs Development company project.

[transienturl]

dreamed that redpop was rewritten in htm/preact, breaking the majority of xkit (cool dev tool though), and also that april went on hiatus pending the reintroduction of some kind of hook into what used to be the react props, and then also the site update got pushed to prod with like 2/3 of the site missing or nonfunctional, and then also one of the dependencies of the site was a composite polymer material filled with micro machinery that did security stuff (you know, kind of like a usb security key) and the way you interacted with tumblr's desktop site was now not using a computer but rather by squeezing a small tube of goo into an empty white plastic bag of the sort used to sell soil or concrete mixes at the garden center or hardware store (that this somehow resulted in you being able to peruse media was entirely unexplained)

"was this what sreegs was talking about with that vaguepost," I thought; "I try to give the company the benefit of the doubt but I really think this cost cutting measure may have been too aggressive"

[redneckdysguys]

100daysofcode #day001

The npm advantage

As a developer you need all the api's that are available so that you don't have to reinvent the wheel. There is no point in that, npm allows you to reuse code that someone has made into a lib-utility. I call it a lib utility because it's normally a full set of programming api that enables you to achieve a purpose by making you harness the source code that actually makes your life easy. Infact under the hood react itself is a lib-utility but it's seen as a framework altogether. Most JavaScript frameworks leverage the npm system or reusing code. Frameworks like react, svelte, angular, vue.js, solidJS and quik.

Building cross-platform Apps with Electron and React

Above are most frameworks that are mainstream, I did not include nextjs, nuxtjs and preact because are a subset of mainstream frameworks. React was made as a single page application to solve a problem of server roundtrips which had performance issues. In the same way Electron was developed so that web developers that sometimes get a one of desktop application project don't have to go learn another programming language.

Npm package managers

There used to be a package manager called npm which was the native package manager and its very good. Since everyone is on the mission to solve problem, there has been an introduction of yarn and pnpm which is the latest. Pnpm came out in 2022 and its awesome, I will not go into the improvements made in yarn and pnpm but I will say node package manager(npm) is the tooling you need to use to install all you npm into your projects. After you install NodeJS, the base tool you need to develop JavaScript, It has prebuilt api's that allows you to access the filesystem, scientific and arithmetic base and console tools. These modules will be added by default in any node project along with the ones you would like to use.

[aitoolswhitehattoolbox]

Node + Angular

Lead exp + .Net core + .net framework + OOPS + ASP.NET MVC + ASP.NET Web API or Owin + Entity Framework + CICD + Git or github + Basics of Angular JS or Angular or React / Preact / Typescript with Vite Apply Now

[kapiljetawat]

Top JavaScript Frameworks in 2025

In 2025, the JavaScript ecosystem continues to evolve, with several frameworks standing out for their powerful features and robust community support.

React- React remains one of the most popular JavaScript frameworks, known for its efficiency, component-based architecture, and vast ecosystem. Its flexibility and strong community support make it ideal for building dynamic, large-scale applications.

Angular- Angular is a full-fledged framework maintained by Google, offering a complete solution for building scalable web applications. With features like two-way data binding, dependency injection, and robust tooling, Angular is ideal for enterprise-level applications.

Vue.js- Vue.js is gaining traction due to its simplicity, flexibility, and gentle learning curve. It allows developers to integrate with existing projects easily while offering powerful features like reactive data binding and a virtual DOM for high performance.

Ember.js- Ember.js is known for its convention-over-configuration approach, making it highly productive. It provides a strong set of tools, including a built-in router and state management, making it a strong choice for ambitious web applications.

Preact- Preact is a lightweight alternative to React, offering similar functionality but with a smaller footprint. It��s particularly useful for performance-sensitive applications and projects where size is a priority.

For More Follow This Blog: JavaScript Frameworks

[pritivora26]

If you’re searching for the right frontend framework, you’ll know the options are extensive and sometimes confusing. This concise guide brings you the top 8 frameworks, dissecting the key features and ideal project fits.From the robust capabilities of React and Vue.js, to emerging lightweight alternatives like Svelte and Preact, developers have an impressive array of tools. Each framework has unique strengths, catering to different project requirements and developer preferences, whether for large-scale applications or smaller, more focused endeavors. Read more.

[cssscriptcom]

Advanced Date & Time Input JavaScript Library - Timescape

Timescape is an accessible, headless, touch-enable, user-friendly date & time selector component designed specifically to enhance and replace the native date and time inputs in your applications.  Compatible with popular frameworks like React, Vue, Solid, Preact, and Svelte. With its flexible API, you can use hooks to get seamless component integration. Plus, you have the freedom to render inputs…

[ericvanderburg]

React Developers Love Preact, Here's Why

http://dlvr.it/SrTWFz

[mehbark]

Freshter Logs

after many (mostly happy) hours of blood, sweat, and tears, i made a thing that lets you create append-only pesterlogs:

i made this with https://deno.com/runtime and https://fresh.deno.dev btw, i think i love deno and fresh? but they're both a touch immature. typing could also be better but it always can (gee thanks, haskell (and even haskell's type system is pretty inexpressive when it comes to dependent types (it doesn't really have them ig but yeah this is so far from relevant

[jmarwilhelm]

We are working this week out of our office in Barcelona and want to bring our front end activities ro the next level. #angular #vue #apollo #graphql #react #preact #svelte #frontastic #jquery #javascript #css #html5 #ember #nodejs #backbone #semanticui #cx #machalliance (at Barcelona, Spain) https://www.instagram.com/p/CfdoNEsq3xf/?igshid=NGJjMDIxMWI=

[fancyhints1]

Why I still use jQuery in 2021

I use jQuery in specific use cases. One of those use cases is landing pages.

When running advertisements on social media, native platforms etc. it’s paramount that the core behavior of the page works in every browser. We do get traffic from users using ancient browsers (IE 9 etc). Not only that but

I use all the modern jazz such as babel and esbuild, but jQuery has never failed me for this use case. I’ve recently started using it on some of my smaller sites. If the move seems backwards it’s because I’m getting older and my time is important.

I love jQuery — I usually continue to use it for small features on existing sites. I personally think you’d love something like React for jQuery landing pages. Trust me, it can drastically speed up your workflow, and with the build system you already have (Babel, etc.) it should work in al the same browsers

React is great. Used it many times. And Preact. Gatsby is great too for static site generators (although I still prefer Hugo, which I use to create the HTML for the landing pages because SEO is important too sometimes). I’ve been around the block a lot.

Also, jQuery makes possible the use of a lot of amazing JS plugins… With incredible coverage on older browsers.

Read More — https://fancyhints.com/

[iamdeveloper]

9 Preact Libraries and Tools You Should Know in 2020 ☞ https://morioh.com/p/cc0e4a5d78d9 #Preact #JavaScript #React

[javascriptnews4u]

9 Preact Libraries and Tools You Should Know in 2020 ☞ https://morioh.com/p/cc0e4a5d78d9 #Preact #JavaScript #React

[npmjs]

JavaScript Usage by Industry

We’re continuing our analysis of the results of last winter’s JavaScript Ecosystem Survey, a survey of over 16,000 developers conducted by npm in collaboration with the Node.JS Foundation and the JS Foundation. Our second topic is How JavaScript is used across industries — and, more specifically, how different industries use certain JavaScript tools, frameworks, and practices. To read more about the methodology behind this survey, click here.

We asked about what industry our respondents worked in. 45% of users answered “tech”, revealing an underlying ambiguity in our question. For instance, if you work at Google, do you work at a tech company or an advertising company? What about at Microsoft, which many consider a tech company, but also has advertising and even hardware manufacturing arms? Next time, we’ll ask for more detailed information about industry concentrations.

“We asked about what industry our respondents worked in. The most common answer was “tech” at 45%”

Despite this, we still gathered some good data about how use of JavaScript varies by industry. The top industries were:

finance: 7%

advertising and marketing: 5%

education: 5%

entertainment: 5%

business support and logistics: 4%

healthcare: 4%

retail: 3%

government: 2%

manufacturing: 2%

There were meaningful differences across industries in how and why people use JavaScript. There were also some clear commonalities, not all of which we’re going to mention. But from a statistician’s point of view, the questions where all the industries answered very similarly are useful because it indicates the differences in other questions are “real” and not just random variation.

With 16,000 responses, even the single-digit groups per industry constituted enough data to make meaningful conclusions. We discarded answers from industries with less than 2% responses (i.e. less than 300 individual responses).

JavaScript tools

First, we asked about common tools: bundlers, linters, testing frameworks, transpilers, CSS preprocessors, and more.

Manufacturing across the board uses less of everything — only 51% of manufacturing respondents say they use a testing framework, compared to 75% in finance.

The explanation for this may lie in the answer to another question; “Where does the JavaScript you write run?” 15% of manufacturing developers say their code runs on embedded devices which is twice as much as any other industry. Embedded platforms often have intrinsic transpilers for JS, so you do not need to use your own and have no need for browser-specific optimizations that most of these tools provide.

“Manufacturing across the board uses less of everything — only 51% of manufacturing respondents say they use a testing framework, compared to 75% in finance.”

Put another way: hardware isn’t a browser. This view of manufacturing respondents is backed up by another question, in which 31% of manufacturing respondents say their code is put to use in IoT (Internet of Things). No other industry gets above double digits for that answer. This makes manufacturing an interesting set of answers across the board, as we’ll see.

Finance, on the other hand, uses everything the most. They are the most likely to use a bundler, second-most likely to use a linter (after healthcare), most likely to test, second-most likely to use a web framework (after retail), most likely to use a transpiler, and second-most likely to use a CSS preprocessor (after advertising). Finance just does all the things.

JavaScript frameworks

We’ve examined the popularity of JavaScript frameworks in the past. Our survey data provides another view into these preferences, and the results are enlightening.

Angular was a fairly popular choice across all industries, but strongest in finance. Developers in entertainment were the least likely to use Angular, their strongest preference being for React (65%).

React was the most popular framework in the survey overall, though with strong variations by industry. As mentioned, 65% of developers in entertainment chose it, but that fell to 46% in government and 38% in manufacturing. Manufacturing’s strongest choice for a framework was jQuery (52%), suggesting the industry is a late adopter. Government also had jQuery as its top pick at 52%.

Around 20% of developers in most industries reported using Vue, though it was notably more popular in advertising, with 34% of developers reporting it there.

“We also asked developers how they made decisions about choosing frameworks. Big majorities (60-90%) in every industry reported things like support, features, and stability being important, with little variation.”

Ember did not get a lot of mention from our respondents, with an average of 4% of developers reporting that they used it. Also in this range were Preact (5%), Hapi (5%), Next.js (5%), and Meteor (5%).

A surprisingly popular choice was Electron, which is obviously not a web framework at all but we included in our options. More than 20% of developers in every industry reported using Electron for some projects.

We also asked developers how they made decisions about choosing frameworks. Big majorities (60-90%) in every industry reported things like support, features, and stability being important, with little variation. Security was the lowest ranked concern for frameworks, averaging only 25%, though finance was most concerned at 30%. We’ll go more into attitudes to security later in this post.

Language choices

Obviously everybody in the survey uses JavaScript, but lots of respondents use another primary language as their back-end choice and there were noticeable variations by category.

Python was the choice of the unemployed. This sounds unflattering, but thanks to a poorly-phrased question on our part, the “unemployed” category includes people in full time education. Their questions (such as what level of schooling the respondent had completed) lend weight to the idea that the unemployed category was full of people who are still in school, so we believe Python is popular in education.

Java was the choice of the finance industry by quite a margin—41% versus 27% for the second most popular language in finance, .NET.

PHP was the choice of the advertising industry, again by a huge margin — 49% to 26% for Python, the second most popular. Why advertising companies choose PHP is unclear to us, but PHP is popular with advertising agencies putting together micro-sites. Furthermore, a question about company size showed that over 50% of advertising respondents worked at small companies (less than 50 people), so this category is probably dominated by small shops putting together these sorts of sites.

Our poorly-chosen “.NET” category (not really a language) was no industry’s first choice. Its strongest showing was in the manufacturing category at 33%, a very close second to Python at 34%. However, because we didn’t pick out C# and F# separately, it’s possible these results are skewed by people who use those languages, but don’t use .NET.

Ruby is a relatively unpopular option across all our respondents, chosen by less than 13% in all cases. Its weakest showing was in manufacturing, where only 3% chose it, and its strongest in education, where 13% did.

C and C++ were unsurprisingly most popular in the hardware-dominated manufacturing industry, at 9% and 18% of respondents respectively. C++ was more popular than C across the board. The retail industry is the least fond of C++, with only 4% of respondents reporting using it.

We also polled on Go, Swift, and Rust. Go was about 10% usage across the board, Swift was 3-5%, and Rust about 3% except in manufacturing, where it hit 7%.

Why do you choose JavaScript?

In general, people are pretty clear why they choose JavaScript: the huge ecosystem of libraries. An academic study of the same topic in 2013, An Empirical Analysis of Programming Language Choices (Meyerovich and Rabkin, 2013) exhaustively researched what makes developers choose programming languages and it reached the same conclusion. It’s not controversial to conclude that the modules in the npm registry are a major reason people choose JavaScript. However, people cited a number of other reasons and there were notable variations by industry.

Respondents who say they work in government were the least likely to report that they chose JavaScript for productivity gains, with only 51% saying so versus 60% in the finance industry, where this belief is strongest. Instead, government was most likely to believe that using JavaScript gave them performance gains: 31% of government respondents cite this, while in most other industries only 20-21% said this.

The advertising industry is the one most likely to say that developer satisfaction is a reason they choose to use JavaScript, with 50% of respondents saying so. This is notable since the advertising industry has a lot of PHP developers, and as we’ll see in a future analysis based on programming language choices, high satisfaction with JavaScript is a characteristic shared by most PHP developers.

“Across every industry, solid majorities (more than 90% in every case) expected to use JavaScript more or about the same amount as they had previously in the next 12 months.”

Cost savings as a reason for choosing JavaScript were most cited by respondents who work in finance (41%). This seems pretty logical, as finance is an industry that presumably can be relied upon to think of the costs of things.

The entertainment industry was the most likely to cite the size of the developer pool (41%) while the retail industry was most likely to say the ease of on-boarding new developers (40%) was their reason for choosing JavaScript. While JavaScript has a big pool of developers and we think on-boarding developers in JavaScript is pretty easy, it’s unclear why these industries in particular would note those advantages.

Finally, some people don’t get to choose what programming language they work in. This number was highest in government, at 21%.

Across every industry, solid majorities (more than 90% in every case) expected to use JavaScript more or about the same amount as they had previously in the next 12 months.

Attitudes to security

npm is making a big push to improve the security of the modules in the registry in 2018, so we asked our users about their attitudes toward security. You can see our previous post for a deeper analysis of attitudes to security, but there are some interesting variations by industry.

Firstly, everyone is concerned about the security of the code they write (87-90%) and of the open source code they use (73-79%). Developers who work in tech were the most likely to be concerned, but there wasn’t a lot of variation.

Majorities in every industry reported that they were dissatisfied with current methods of evaluating the security of code (51-60%). Advertising and entertainment were the most likely to say they were dissatisfied with available methods.

“Firstly, everyone is concerned about the security of the code they write (87-90%) and of the open source code they use (73-79%). Developers who work in tech were the most likely to be concerned, but there wasn’t a lot of variation.”

A whopping 90% of people working in education (non-students) were likely to be concerned about the quality of the code they wrote themselves. This was an interesting result as they were also the industry most likely to say they were doing nothing at all to assess security (33%):

The industry most likely to be actively doing something about security is the finance industry. They were the group most likely to participate in code reviews (81%), most likely to have external audits of their code (30%), and the most likely to be using automated scans of their code (52%). The tech industry was a close second to finance in all of these answers.

Private code

We explored the ways developers use and store private code.

Everybody reports having private code and GitHub is an extremely popular place to store it — 93% of the advertising industry report using it, with most industries in the high 80’s. Manufacturing was an outlier here, with only 75% of developers saying they used GitHub. We thought this was a strange result, but it was consistent; when asked how they discovered packages, developers in manufacturing were also the least likely to report using GitHub (14% versus 20% for other groups).

Developers also store private npm packages. Across all industries, about a third of developers said they had created private npm packages. However, their reasons for doing so varied.

“However, by far the most popular reason for everyone using private packages was the most obvious: the packages contain private IP. Majorities from 65% in education to 91% in manufacturing reported this as a reason for creating private npm packages.”

Developers sometimes use private modules to hold test projects which aren’t ready for release. This practice varies widely across industries, with 23% of developers in education saying they do this but only 8% in retail.

More common was keeping code private for release as open source later. Education was likely to do this, with 27% saying so, and government employees following close behind at 25%. Healthcare developers, who reported less engagement with open source, were the least likely to report this as a reason, at 9%.

A big reason for everyone to keep private packages was re-use by their co-workers — including majorities from 53% in finance and 67% in retail.

However, by far the biggest reason for everyone using private packages was the most obvious: the packages contain private IP. Majorities from 65% in education to 91% in manufacturing reported this as a reason for creating private npm packages.

Testing

Finally, we explored attitudes toward testing across the industries.

In keeping with its answers in every other category, finance was the most likely to report that they use a testing framework (88%). Government and manufacturing developers on the other hand were the least likely to use a testing framework, with only 68% of developers in both industries saying so.

Across every industry, the most popular testing framework choice was Mocha (50%), followed by Jasmine (33%) and Jest (19%). Unlike web framework choices, there was less variation between the popularity of testing frameworks across industries.

Conclusions

There were some fascinating differences across the industries. The advertising and entertainment industries often found themselves paired together in terms of practices. Finance was cautious and security-focused. Government and manufacturing were mostly on the opposite end of that scale, with lower reported use of best practices and modern tooling. Whether you’re in these industries or building products for developers in these industries, we hope these results help you get a better sense of the broader universe of JavaScript developers.

Thanks to everyone who took the survey. We’ll be providing more analysis in the near future, so stay tuned!