Search Hacker News by keywords, user, score, etc.
Subscribe to new search results by RSS or JSON

I always thought Angular 1.x was _fine_, so long as you had incredible discipline in your team and stuck to predefined patterns.

React’s main benefit wasn’t technical, it was organisational. It’s so opinionated that it’s difficult for an incompetent developer to introduce very low quality code into the project. Meanwhile in AngularJS, a developer with a clever implementation idea was a terrifying prospect for future productivity.

Well, if you want a more lightweight alternative, that is actually more powerful, spend an hour with this:

https://github.com/Qbix/Q.js

I will release a playground soon on qbix.org so you can try it out. You can use it alongside React and Angular

For sure it isn't the perfect solution for everything, and I say that as someone who spends most of their time in either React or Angular now. For application-like development or just sites with tons of interaction it's become as standard as reaching for Spring or PSQL though.

I can't speak to the complexity you've encountered, but for me it's pretty much zero. A button component is just a function. React-Router is good enough and code splitting is pretty much just changing how to import something. Component state is dead-easy to write by just adding a useState hook. Bundlers pretty much handle everything these days so not to much concern about size.

Your view on front-end developers having been mediocre in the past isn't far off though, at least in my experience. I noticed a big difference between the people who wanted to build nice looking pages and the ones that wanted to build applications myself. Even today it amazes me how many people have never unit tested their code, have no idea about layering an application and have poor JS/TS fundamentals. It's gotten a lot better though.

Ultimately it isn't perfect for everything, but for a lot of people it's an easy choice. And for me personally, the tons of other JS frameworks do very little in that area that I'd pick them. I'd rather spend my time working on the product. Lol, maybe its just the default because its the default at this point.

React was actually pretty simple in the early days. It's gotten significantly more complex because of hooks, suspense, SSR, and other features they've introduced more recently. But I would still take modern React over AngularJS 1 and I think it's far more explicit.

Yes, but when React launched, 1.x was its main competition. We started to incorporate React into parts of our app that needed better performance, and found ourselves using it for essentially all our new projects. It was quick to pick up, made apps easier to reason about, and had much more performant DOM updates.

That was in 2013. Angular 2 came out in 2016, and by that point React had won. Have had to dabble in other frameworks since then, and none of them seem to do anything significantly better than React. I spent my early career learning a new FE framework every year, at this point I'm happy to have something boring that does what I need and has a great ecosystem around it.

Actually, React's problem is that it's the inverse of how HTML and JavaScript works in terms of how to handle callbacks. Of the major UI frameworks, it is the only one with this quality (Vue, Svelte, Angular, Solid, etc. use signals).

This inverted behavior is the cause of most of the pain and footguns in React and React Hooks because the way state behaves in a React component is not the way state behaves in any other front-end JS one would normally write.

That's why I think for some folks who started with HTML + vanilla JS, React Hooks just feels wrong. It points the reactive callback to the component function whereas every other framework/library uses some sort of signal to point the reactive callback to a handler. Because React points the callback to the component function, then you have to be really cautious about where you put state inside of a component[0][1][2]

Even You wrote this about React's design choice which I think sums it up best:

    > The pain and suffer[ing] of hooks all roots from the mismatch between a dogmatic belief in the superiority of immutability and the harsh reality of the host language that is JavaScript 

- Vanilla: https://jsfiddle.net/qtmkbdo2/8/

- Vue: https://jsfiddle.net/vys2rmup

- React: https://jsfiddle.net/0gjckrae/1/

It should be obvious that Vanilla and Vue behave like how one would expect callbacks to work. React, because it points the callback to the component function, then requires that you be cognizant of state inside of the component function (placement, memoization, immutability, etc.). All of the pain of React is self-imposed from this design decision.

You can read more about it here: https://chrlschn.dev/blog/2025/01/the-inverted-reactivity-mo...

--

[0] https://adevnadia.medium.com/i-tried-react-compiler-today-an...

[1] https://tkdodo.eu/blog/the-useless-use-callback

[2] https://adevnadia.medium.com/react-re-renders-guide-why-reac...

I remember the space being backbone (+ marionette!), and angular 1. webpack was a cool new confusing thing. enter react (with the mysterious redux). Purists said one should only use redux state and never local component state or context. Don't use refs! Don't you try to touch the dom! also jquery. my beautiful jquery. betrayed by the community, and cast out.

Well, that's just argument against angular 1.x

I'm working with a large Angular app, and my dev experience has been abysmal. TS language server running out of memory, Angular language server frequently crashes or freezes leaving weird half line diagnostics in its wake. Go to definitions are so slow in the proje too.

I've worked on 2x, if not 3x larger React codebase without these issues. I can't tell a single instance where language tooling was failing me so severely that I've contemplated turning it off because it's creating more uncertainty than its helping.

I'm relatively new to Angular 20 itself—only used Angular 1, and also migrated that project to React. So I'm not yet qualified to make big statements about it (but a preliminary gut feeling is that it often feels complex in the wrong places). C'est la vie though

Good. Innovation isn't the latest framework that barely improves the model and as much as front-end developers like to nit about bundle size, 100kb here and there isn't going to matter for most markets.

Honestly between React, Angular and Vue, there's enough jobs if you do want to specialise, but the mental model between the three isn't that different that a good engineer wouldn't be able to adapt.

React is boring old tech to me at this point and I'm happy with that. Like choosing Java, C# or Python for the back-end. I'd rather focus on innovating my clients products until something earth shattering comes along.

Yes, this is probably the wrongest statement in a post full of wrong statements. When React was launched, it was one in a pool of thousands of web frameworks -- some of which were being pushed hard by companies with even more resources (Angular), some of which had already "won" (jQuery, Backbone), some of which were even more hyped than React (remember Meteor?).

React didn't win by default, it won because developers tried it and found it was betetr. It absolutely won on technical merit.

There's a bit of a question of whether React would still win on technical merit versus all the upstarts. I personally think it is still better than Svelte, Vue, etc, but I'm a bit of a React apologist.

here here, being involved with porting a huge angular 1 project to the first angular2 RCs (golden dev choice) was the worst frontend project i ever witnessed in my not short career :-)

The premise is bullshit... there were LOTS of competing options when React first came out... it wasn't really until Redux hit that a lot of people started seriously using it. A lot of the flux implementations were painful, configuring Webpack was a pain, etc, etc.

It may be the default today, but it largely earned that position by being one of the better options out there. Today there's alternatives and even Angular still has a decent following, not that I'll touch it if I can avoid it.

> React didn’t win purely on technical merit

A sentence written by someone who clearly hasn't worked on a large Angular 1.x project.

Three reasons spring to mind:

1- the DOM APIs are very verbose, excepting perhaps replacing chunks by setting innerHTML, but

2- manual DOM manipulations aren't composable without also using web components

3- naive manual DOM manipulation can potentially be slow by way of triggering needless layouts/repaints or inefficient use of the APIs

Web components didn't exist when the major frameworks came about, and the ones before them handled composition rather poorly if at all (such as backbone). Angular, ember, react and company all sought to provide a cohesive story for code reuse and composition. Many had their own performance stories, though it was always a secondary concern to everything else.

I've done a bit of everything, including pure vanilla JS, just jQuery, vanilla + web components, all the way up to next, ember, angularjs and angular, and more. If you're building a web site, vanilla JS is fine. If you're building a web "app", you'll pretty quickly appreciate what a framework can bring to the table. If you don't, you'll also quickly find yourself building your own mini framework and runtime to manage things.

Very much agree.

It was a few years ago, and very AngularJS focused, but I posted something along these lines: https://charemza.name/blog/posts/angularjs/e2e/consider-not-...

In summary: having thing look cleaner at a glance is not helping if you’re (almost) always going to need to do more than glancing

It's effectively impossible to have no angular momentum with these processes.

There are a bazillion ways to rotate but only one way to not rotate. I'd say that the probability of a gas cloud without angular momentum is as low as to be indistinguishable from zero.

> The scientists found that bright material — likely hot gas — swirled around in a furious vortex, one that backed up Furtak’s preliminary findings.

Which is probably science-journalist for "has an accretion disk". That enough angular momentum for you?

I didn't see any mention of angular momentum. If a gas cloud has essentially no angular momentum relative to its center of mass, it will collapse directly into a BH, no?

If angular momentum exists, you get a galaxy.

SEEKING WORK

Location: Curitiba, Brazil

Remote: yes

Willing to relocate: no

Technologies: TypeScript, JavaScript, Python, Redis, MongoDB, PostgreSQL, MariaDB, Angular, ExpressJS, AWS, Rust, Axum, HTMX and TailwindCSS.

Résumé/CV: https://www.linkedin.com/in/adelmo-junior-2a576b156/ | PDF on request

Email: development@silvajunior.dev

I'm a software engineer working to help people build products and deliver value to their customers.

I can help build: - web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX); - services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069); - serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda); - microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus); - data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom); - small CLI apps to help automate common tasks (Rust); - integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests; - proper documentation for common services using OpenAPI specification and/or frameworks such as Diátaxis (Swagger)

Location: Curitiba, Brazil

Remote: yes (preferably part-time, but I can do full-time as well)

Willing to relocate: yes

Technologies: TypeScript, JavaScript, Pytho, Redis, MongoDB, PostgreSQL, MariaDB, Angular, ExpressJS, AWS, Rust, Axum, HTMX and TailwindCSS.

Résumé/CV: https://www.linkedin.com/in/adelmo-junior-2a576b156/ | PDF on request

Email: development@silvajunior.dev

I'm a software engineer working to help people build products and deliver value to their customers.

I can help build:

- web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX)

- services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069)

- serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda)

- microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus)

- data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom)

- small CLI apps to help automate common tasks (Rust)

- integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests

- proper documentation for common services using OpenAPI specification (Swagger)

Location: Cape Coast, Ghana (UTC+0)

Remote: Yes | hybrid | onsite

Willing to relocate: Yes, Europe

Technologies: Typescript, Python, PostgreSQL, SQL; Crystal, Elixir, Java, Kotlin, Ruby, C/C++, Go, Angular, Vue, Android, Flutter, Linux, Docker, Terraform, Kubernetes, GCP, AWS, Shell, NestJS ...and open to learn new technologies.

CV: https://drive.google.com/file/d/1M-tUwpkBlnZYPDQcwCeezzFXHa3...

Email: ephrimlawrence11@gmail.com

Hi, I’m Lawrence, and I'm passionate about building impactful products. I am a full-stack engineer with over five years of experience. I am proficient in TypeScript, Python, and Java, and I have experience with frameworks such as NestJS, Laravel, and Flutter. Additionally, I have experience in DevOps with GCP and AWS, as well as system administration. I learn quickly, enjoy new challenges, and thrive in team environments.

I am flexible with remote, hybrid, or onsite work and open to relocation. I am also looking for remote opportunities anywhere.

> I can’t get a good intuition about how tidal forces explain (1) Earth’s moon causing ocean bulges on both sides of Earth

Try to imagine that all the Earth is liquid, so no landmass that resist deformation. And now ask yourself a question: which form this Earth should take in presence of Moon? You see the reason for a bulge facing the Moon, but what kind of shape should be the other side? Anti-bulge, depression? Or maybe an approximate spherical surface? Or another bulge facing from the Moon?

> tidal friction making Earth’s moon stop spinning and move further away.

Deformed Earth is rotating and the bulge under the Moon tends to move faster than Moon (in terms of angular velocity). So the bulge is sort of "in front" of the Moon and it pulls it forward speeding it up. The other bulge works in opposite direction, but it is more distant so the force is lower.

Why -ng ? I thought it had something to do with angular.

Created this PWA App Store for Android. Based on F-Droid database. Written in TypeScript using Angular. Also created an assistant android app that, when paired with PWA, allows apps to be installed directly to your phones. Doesn’t require accounts, uses random sha256 hashes as a pairing code (still working this out properly).

Any TypeScript capable devs looking to help out feel free. Code is a mess.

That's pretty awesome. I'd love to see the Lockheed F-117 Nighthawk get the same treatment. Seems like its angular design would lend itself well towards an origami version.

For the most part, cars are being designed to meet the required safety regulations in a way that constrains what they are able to build. Gone are more angular designs because sharp angles are all points which people get caught/trapped by - definitely no flip up headlights either for the same reason. Larger A pillar supports to provide roll over protection and door frame rigidity. Larger fronts to provide better small overlap collision deference.

All together it results in all cars kind of looking the same. Shame in a way because my favourite looking car of all time is the Golf Mk2, very angular and boxy but it wouldn't have been made now.

Remote: Yes

Willing to relocate: Yes

Technologies: Flutter, Java, Kotlin, Swift, Objective-C, React Native

Web Technologies: React.js, TypeScript, JavaScript, Node.js, Angular, Grails, Express.js

Backend, Tools & Other: REST APIs, GraphQL, Docker, Fastlane, Shorebird, PostgreSQL, MongoDB, MySQL, GIS, Firebase, Sentry, Kochava, Amplitude, Meta SDK

Résumé/CV: https://pitskhela.github.io/

Email: mailto:pitskhelauri.elene@gmail.com