Hacker News Reader

Comment by tipiirai | Hacker News Reader

Vue is indeed similar, but Hyper is more minimal with fewer special characters and syntax patterns. The key difference is that Hyper strictly separates styling: no CSS-in-JS or class manipulation is allowed. This makes components truly reusable across different projects and environments.

View on HN

Well,

I'm waiting for more real world production examples and not just the todo-list hello world.

I like the simpler/cleaner approach of Nue. Now one of the big difference will be the component and theming provided.

I'm a long term vue/vuetify user and i can build powerful and sexy web app in a small amount of time and effort.

I will definetely compare this point.

That's said, you've done an incredible work with your Nue project. i keep a eye on it.

Sounds like no class manipulation will also make it impossible to do... front-end work?

Yes. If you are a keen Tailwind user and think "class names is the reason CSS doesn't scale" (as they say)

You can't say you don't "allow CSS-in-JS" and then not allow class manipulation. These two are quite literally the only ways you can dynamically style DOM elements.

@isqueiros I certainly can. Tailwind evangelist like you should look closer to web standards. Especially CSS. The points you make are simply absurd: feels like you have only worked with React and never understood the DOM. Time to learn!

I don't think you get what I mean, and frankly your tone is quite disappointing. I haven't seen you properly engage with criticism once and all your responses are combative and petty. I'm not gonna grace you with a response.

I have to agree. Instead of trying to explain it immediately turned into trash talk. So wierd.

Sounds more like you have some deeper hate towards tailwind. I am no tailwind fanboy. I write direct no framework css all the time and have been doing frontend for more than a dacade.

What i mean is that classes are used to save interactive state and if you have some component like dropdown or hamburger menu then adding class "open" is very common solution and for certain transitions you need multiple classes because of in-out durations. So what you do? Use custom attributes? Sure but then thats just semantic difference to using a class attribute.

Looking at docs of your project you are doing both

  posts.forEach(post => post.classList.add('fade-in'))
  AND
  main.style.display = 'block'

So whats with those claims?!

Reply on news.ycombinator.com