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

Preact, a fast 3k React alternative

developit.github.io

Post reply on HN
Print view View original

131–140 of 142 posts

Re: Preact, a fast 3k React alternative

#131

Post by esailija »

pacomerh wrote: post #57
terrortrain wrote: post #53

Earlier quoted context omitted.

Nope. People should always create and attempt improve upon whats out there. Don't try to stifle innovation for the sake of making decisions simpler. If you don't want to make decisions, don't use libraries, or use an opinionated framework.

I'm supporting this mentality. You should always be looking for ways to make existing things better. This is exactly how React was born damn it.

I didn't know React was born by taking another library and removing all the polish and most features from it and then publishing it with almost the same name.

Re: Preact, a fast 3k React alternative

#132

Post by mattlutze »

steego wrote: post #62
Cartwright2 wrote: post #56

Earlier quoted context omitted.

> People should always create and attempt improve upon whats out there. Don't try to stifle innovation... I agree completely and my argument is that a lot of the Javascript libraries being pushed around over the past three to four years are neither creative nor improvements over what already exists. React is innovative. Redux is (arguably) innovative. jQuery was innovative. Many other libraries have been innovative.…

> These libraries do nothing but add to decision fatigue. Developers have to make decisions, sure, but we need to have limits too. Nonsense. These "me too" libraries add to the decision fatigue only if you're including them in your list of candidate libraries in the first place. Personally speaking, I won't even consider Preact until one of the following events has occurred: 1: I tell myself I really really need a 3k…

> Nonsense. These "me too" libraries add to the decision fatigue only if you're including them in your list of candidate libraries in the first place.

Unless you're one of the minority of folks who read all the new trends and follow all the new releases, you won't know not to include some or all of the Me Toos in your AOA.

Most anyone who falls into the less-than-expert experience level included, which covers a ton of folks having to waste far too much time evaluating all these different libraries (and sometimes or often making bad choices as a result).

What's the technical debt and wasted time in the industry due to "I've got an idea" library glut? More than a bit, I'd wager.

Re: Preact, a fast 3k React alternative

#134

Post by jbergens »

sotojuan wrote: post #82
cageface wrote: post #45

Earlier quoted context omitted.

I prefer opinionated, integrated frameworks. I can count on the whole stack being well tested and don't have to worry about subtle bugs and versioning issues between components. The JS community has gone way overboard on factoring everything into a dozen little submodules, IMO.

While I feel like I'm close enough to tame the React ecosystem (and like it!), I honestly agree. Personally I do prefer opinionated. Luckily Ember exists in the JS world.

Until they rewrite everything, like angular 1 to angular 2.

Re: Preact, a fast 3k React alternative

#135

Post by jbergens »

nilliams wrote: post #25
jallmann wrote: post #21

Off-topic, but am I the only one who thinks that classes are the most puzzling feature of ES6? How is writing "class Blah extends Component { ... }" any better than "Blah = Preact.createComponent({ ... })", except to save a few keystrokes? ES6 is full of syntactic sugar to improve readability, but classes substantially increase the "surface area" of the language for... what benefit? Static analysis and tooling, maybe…

Well for one 'class Foo extends Bar' will work without any further code to make inheritance work in the way you'd expect, including use of super() etc. Whereas your second example is using non-trivial framework code, that some framework author has to write. See Backbone's extend() for a clear example of what is required [0]. That's work that every framework author is potentially going to implement differently, needle…

But it's sad that not more framework authors tried StampIt or similar instead of reimplementing inheritance (more or less badly)

https://github.com/stampit-org/stampit

Re: Preact, a fast 3k React alternative

#136

Post by developit »

boubiyeah wrote: post #127
zbyte64 wrote: post #103

Earlier quoted context omitted.

Then how would something like react-redux work without context?

It can already work without contexts. You just pass a store instance via props. I don't like contexts either :(

Yup. I've successfully added contexts to Preact, but I still am not 100% sold on the value. Thankfully, simply supporting them doesn't add much bloat.

Re: Preact, a fast 3k React alternative

#137

Post by developit »

gnat wrote: post #40
corywatilo wrote: post #24

Yeah, there's already a company called Preact. =] preact.com

A good one, too. The last startup I worked for was one of their first customers. You fire off events, they machine learn normal behaviour for your customers and feed the intel to your customer success team so you can prevent churn and identify your high-performing customers.

Yeah... causing this confusion is one of my more regrettable mistakes of the year. Honestly if some amazing name came along I would not be entirely opposed to changing it.

Re: Preact, a fast 3k React alternative

#138

Post by developit »

mikemikemike wrote: post #122

less code !== faster code. I wouldn't even try this without seeing some impressive performance benchmarks. Giving up the support of the entire react team and community in exchange for a small framework that may or may not be faster is a huge ask.

https://github.com/developit/preact-perf https://localvoid.github.io/uibench/

In the second benchmark, Preact is only faster in around half of the tests. However, this benchmark only tests complete top-down re-renders and intentionally triggers synchronous rendering in Preact. In a normal app composed of Components, Preact batches state changes which improves performance considerably.

Re: Preact, a fast 3k React alternative

#139

Post by localvoid »

developit wrote: post #138
mikemikemike wrote: post #122

less code !== faster code. I wouldn't even try this without seeing some impressive performance benchmarks. Giving up the support of the entire react team and community in exchange for a small framework that may or may not be faster is a huge ask.

https://github.com/developit/preact-perf https://localvoid.github.io/uibench/ In the second benchmark, Preact is only faster in around half of the tests. However, this benchmark only tests complete top-down re-renders and intentionally triggers synchronous rendering in Preact. In a normal app composed of Components, Preact batches state changes which improves performance considerably.

All libraries in uibench have batching, and batching doesn't improve performance, it just prevents from doing unnecessary work during one frame. It is pointless to test performance of different state changes with enabled batching.

Re: Preact, a fast 3k React alternative

#140

Post by szines »

sotojuan wrote: post #95
orf wrote: post #92

Earlier quoted context omitted.

Ember is awesome, it doesn't seem to get much love on HNews though. Which is a shame because its really really good - I tried react and spent 2 days messing with various starter packs, trying to get webpack configured and not getting anywhere. Ember took me half an hour to get started.

Not just HN. I rarely see it mentioned elsewhere. Even in those "JS fatigue" articles which is funny because Ember is the antidote to that.

Because Ember devs already found the best tool years ago and they are super productive. The community is huge and super active but they definitely totally ignore this "fatigue" bullshit... you know, if you found your love of your life, you don't go any more in the dance club to chase other boys/girls... ;)
Post reply on HN