Offler

That's basically every major framework apart from React and it includes some major React libraries.

They weren't used in virtually every single frontend framework though while Signals are

Nah I use Legend-State with Context to provide component stores and it's much nicer than the foot gun riddled useEffect standard React. Fine grained reactivity is fantastic.

Offler

2년 전discuss

React isn't in the list because the creator had a bad experience with backbone.js in 2013 and dislikes Signals. The team have kept true to his preferences without considering modern Signal approaches, concepts like components, dependency injection and TypeScript, npm packages which provide better encapsulation, discoverability and modularity than the state of the art in 2013.

Offler

2년 전discuss

I work on FX trading applications with hundreds of thousands of lines of code. Full fat desktop application replacements. Good luck not using a framework. 20-30 developers with multiple clients with their own devs.

Offler

2년 전discuss

Look at legend-state, it's most definitely not Redux (in a good way IMO).

Offler

2년 전discuss

Signals are used in every framework except React. Observables weren't. That's a huge difference.

Offler

2년 전discuss

Indeed at a certain scale the "easy" approach ends up becoming a mess. A simple counter isn't complex enough but this is a great idea and would be a positive for the language.

Offler

2년 전discuss

Every framework is moving to signals, apart from React and I'd say if this became a standard even they will. This is like Promise. It's a sensible shared concept.

Offler

2년 전discuss

I much prefer the explicit get/set methods. MobX I think used the magic approach as did svelte and I believe svelte have realized it's a mistake. It makes it harder to reason about the code, better to be explicit.

Offler

2년 전discuss

Signals are fine grained reactivity. React is coarse grained reactivity. Legend-state adds signals to React and I'd recommend it over Redux/zustand which we used to use.

Offler

3년 전discuss

I'd rather have the Irish electoral system then the American one any day.

Offler

3년 전discuss

Another vote for LazyVim, it's been great.

Offler

3년 전discuss

Linux is great on such hardware. I've a 10 year old XPS 13 running Pop_OS and it's perfectly usable.

Offler

3년 전discuss

A React project wouldn't have the same issues.

Offler

10년 전discuss

There are many countries in the world who would love to have an economy as strong/modern and prosperous as Japan.

Offler

11년 전discuss

Angular 2 also requires that level of tooling (both allow you to use ES5 and don't require tooling but most devs won't use them like that).

Offler

11년 전discuss

It sounds like the sort of mistake newbie React developers make, you quickly learn to decompose your render into smaller components.

Offler

11년 전discuss

It sounds to me like you are doing React development incorrectly. You should aim to break down your mockups into small components, preferably stateless components (introduced in React 0.14) and only have the higher level components act as wrappers that pass down data into the small stateless component leafs (which should be the majority of your UI).

Offler

11년 전discuss

Mithril appears harder to read than equivalent JSX.

const links = ctrl.pages().map(page => <a href={page.url}>{page.title}</a>);

return <div> {links} <button Rotate Links </button> </div>;

Compared to

		m("div", [
			ctrl.pages().map(function(page) {
				return m("a", {href: page.url}, page.title);
			}),
			m("button", {onclick: ctrl.rotate}, "Rotate links")
		]);

I can see what the UI will be with JSX at a glance with Mithril I have to parse the code.

edit: Mind you both look awful due to HNs poor formatting ability. Honestly how did this website become so popular with tech people?

Submissions

Thoughts on RxJS

Flux without the singletons

Callback hell is a design choice.

comments