I've focused on backend for the last 7 years or so, so I've been kind of out of contact with the frontend world. Recently I started working on a personal project, and I thought it would be a good time to learn some of the modern tools people have been using for frontend dev.<p>I was completely baffled by the myriad of options out there, how complex they look (note I've been working on very high performance, distributed backend applications, so complexity on itself is not an issue), and how it's very unclear when to use any one of them or what each one is good for. I tried Angular and React, and both feel like almost a different language. You have to learn their internals to work effectively with them, and it often looks like they create more complexity then the original complexity they were trying to reduce. I have no problem learning new things, in fact, I love it! It just feels like there are other things to learn that will stick around for longer - JS frameworks/libraries seem to be very hype-driven these days. What are your thoughts on this?
Nowadays I only consider switching front-end frameworks if there is a substantial conceptual improvement. React did this for me due to its uni-directional dataflow and component-based architecture. There is nothing new here conceptually.
I've discovered Marko in one of the various react-alternative topic that emerged yesterday and it looks like something sane, which is rare in the js ecosystem. I'm wondering if anyone on hn used in in a real world project and how it was.
So many new UI frameworks, yet no one really mentioned SmartClient.com (LGPL licensed).<p>I've been using it for almost 10 years and some of the concepts they pioneered have only recently been discovered by the new kids.<p>I still use it, though some of the 'fixes' they had to put in place to support old browsers are often polluting the DOM unnecessarily in modern browsers (this is something I hope they fixed).<p>My favourite aspects of it are that I can declare components declaratively, it has a technique called autoChildren that allows managing a tree of components as a flat set (useful for complex components like tabsets), and the data binding layer. The documentation is top notch (which it needs to be given the depth of stuff in there).<p>Again, all of this was around in 2009 since when I started using it - and not sure how many years before I found it they'd been going.
I just skimmed the page and seen that sort coloured of sine wave... Then read «The above animation is 128 <div> tags. No SVG, no CSS transitions/animations. It's all powered by Marko which does a full re-render every frame.».<p>Well, as soon as my browser renders that thing, the browser process reaches 122% cpu usage (according to htop). And i'm using a 4th gen core i7 processor. I can literally (literally in the literal sense of the word) hear my fan spin up. That <i></i>hurts<i></i> battery so much.
Don’t abuse the term “isomorphics”.
To prove 2 groups are isomorphic mathematically you have to show there exists a product preserving map between the groups.<p>Just kidding.
Quick question, is there anything conceptually interesting about Marko thats different in ideology and structure from Angular and React or Vue?<p>For background to why I'm asking: I'm an IOS mobile dev and was a web dev before and I often use web dev structures and ideas as there is less structure, frameworks (unless you count RxSwift) and general philosophies I find in IOS mobile dev aside from best practices and tips like avoid Massive View controllers, etc.
Ecosystem is so important these days, there might be technical reasons for choosing this but considering the support (knowing stack overflow answers will be available) and pre-existing component ecosystems for Vue & React, I can't see a reason anyone would pick this.
Here's a great introduction to Marko by its main dev:<p><a href="https://www.youtube.com/watch?v=i6eZA8Y_GgA" rel="nofollow">https://www.youtube.com/watch?v=i6eZA8Y_GgA</a>
For those interested in spreading this on PH: <a href="https://www.producthunt.com/posts/marko-js" rel="nofollow">https://www.producthunt.com/posts/marko-js</a>
I don't believe the marketing when it says that working with something is "fun". Working is maybe enjoyable sometimes, but it will stay hard work if you're doing it right.