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

Show HN: My new JavaScript MVC framework

lhorie.github.io

Post reply on HN
Print view View original

21–30 of 167 posts

Re: Show HN: My new JavaScript MVC framework

#23

Post by dangoor »

Geee wrote: post #13

Quite similar to React? Probably about the same performance?

I was actually wondering why this wouldn't just use React for the view. Then it could leverage all of the work going on with React (server-side rendering, possibly rendering from within a Web Worker, etc.)

Re: Show HN: My new JavaScript MVC framework

#24

Post by bjconlan »

The templating language reminds me a little of what spacebars (htmljs) probably looks like if a nice mustache facade wasn't put in front of it. (which goes back to Gee's comment about react... but I guess anything these days that promotes a 'virtual dom' will probably be tarnished with that brush from first glance)

I love the simplicity and independent direction this micro-framework provides. It's very 'non-magical' which I think makes it far more appealing.

If you end up solving the HATEOAS/ember-data sideloading/'embedded foreign key data loading' problem I think this will be my goto library (though this probably falls out of the microframework requirements also ;)

Re: Show HN: My new JavaScript MVC framework

#25

Post by todd3834 »

tzaman wrote: post #15

I don't mean this in a bad way, but do we really need another Javascript framework? Wouldn't author's energy be more useful when contributing to one of the existing ones?

That really depends on the author's motives. A lot can be learned by creating "yet another X". Not everyone thinks the same way and creating a framework from scratch gives the author an opportunity to get a deeper understanding for similar concepts and possibly a chance to invent a whole new approach. So many great things would not exist if everyone just settled to use or contribute to existing projects with similar goals to their own.

Re: Show HN: My new JavaScript MVC framework

#26

Post by pastjean »

Kiro wrote: post #20
sergiotapia wrote: post #12

Earlier quoted context omitted.

The three rings are in a span. So it's content 'o' in span, the 'o' in :before and 'o' in :after. Then he uses a -webkit-animation to translate the positions of each ring. @keyframes logo { from {opacity:0;transform:scale(2) rotate(359deg);} to {opacity:1;transform:scale(1) rotate(0deg);} } @-webkit-keyframes logo { from {opacity:0;-webkit-transform:scale(2) rotate(359deg);} to {opacity:1;-webkit-transform:scale(1) r…

But does that explain how it's not triggered until you click the tab?

This is browser specific to trigger animations on tab open

Re: Show HN: My new JavaScript MVC framework

#27

Post by swalsh »

This actually fills a good niche, if i'm looking for a monolithic framework that trys to do a bunch of things, angular fits the bill. I like that this does one thing, and seems to do it exceedingly well (fast). I'm not in the market for a new framework right now, but the next time I am... i'd consider it, if it stays small and compact like it is today.

Re: Show HN: My new JavaScript MVC framework

#28

Post by Touche »

tzaman wrote: post #15

I don't mean this in a bad way, but do we really need another Javascript framework? Wouldn't author's energy be more useful when contributing to one of the existing ones?

> I don't mean this in a bad way, but do we really need another Javascript framework?

Obviously the author thinks so.

Re: Show HN: My new JavaScript MVC framework

#29

Post by Touche »

tluyben2 wrote: post #4
stronglikedan wrote: post #3

Earlier quoted context omitted.

Unfortunately, they all start out this way it seems. Hopefully, this one will remain this way.

The way to keep it that way is to never add even 1 new feature and only fix bugs. That's not a bad idea actually; if you don't, it'll end up like every other framework on earth. So it's a good niche to say 'this is it' and keep it exactly like that even though it 'lacks features'.

But this was built to solve problems the author was having at the time he/she created it. In the future, as the web evolves, those problems will change, and you're saying the framework shouldn't adapt to solve new problems?
Post reply on HN