microsite VS marko

Compare microsite vs marko and see what are their differences.

microsite

Do more with less JavaScript. Microsite is a smarter, performance-obsessed static site generator powered by Preact and Snowpack. (by natemoo-re)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
microsite marko
5 40
876 13,090
- 0.6%
0.0 9.5
about 1 year ago about 15 hours ago
TypeScript JavaScript
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

microsite

Posts with mentions or reviews of microsite. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-06-15.
  • Next.js 11
    7 projects | news.ycombinator.com | 15 Jun 2021
  • Is there a React Framework to build Static Non-React website?
    3 projects | /r/webdev | 6 Apr 2021
  • Ask HN: What Are You Working On?
    100 projects | news.ycombinator.com | 14 Jan 2021
    None are ready for the public yet, but all in the hopper or under serious consideration:

    - Personal site/blog with a bunch of algorithmically generated art and other fun stuff, built on Node/Preact but progressively enhanced/almost completely JS-free at runtime. Motivation for the build approach is that I’m on the low/no client JS static site bandwagon but I quite like the DX of JSX components and CSS-in-JS.

    - I’m using a few excellent existing tools[1][2] for said site which unfortunately aren’t designed to work well together, so I have a variety of wrapper tooling that makes them live peacefully together. I’m also developing a bunch of other build-stage tools for my use cases. I plan to open source (or hopefully contribute back) all of that as soon as I’m satisfied with their quality.

    - A set libraries for building declarative, type safe, automatically validated/documented service API boundaries (HTTP/REST to start, but I also plan to support other transport protocols) — think io-ts[3] type interfaces but you get swagger docs for free in a transport-agnostic interface. I’ve built this kind of thing before, it was wildly successful in real world use, but it’s proprietary to a previous employer and I’m starting over with all the stuff I learned in hindsight.

    - A “nag me” app that’s basically “reading list” plus “reminders” with minimal config, eg “nag me soon” or “nag me after a while”. My personal use case is I frequently screenshot/text myself/etc stuff I want to look at later (usually on phone but need a computer to dive in), then it just goes down the memory hole. I’ve tried setting reminders but it’s often too much fuss, and I’m far too ADHD to use a passive list.

    - Exploring building yet another FE build tool/bundler that’s explicitly multi-stage/sequential with static input/output validation, per-step/time travel debugging. Motivation is that existing tools are just a big ball of config magic and totally inscrutable. I’d likely wrap existing build tools because their set of responsibilities isn’t my motivation and I don’t want to introduce that much more new API surface area to weary FE devs.

    [1]: https://github.com/natemoo-re/microsite

  • Repos interesantes de la semana #1
    5 projects | dev.to | 12 Jan 2021
    Microsite es un generador de sitios estáticos (SSG) construido sobre Snowpack y que utiliza Preact como framework.

marko

Posts with mentions or reviews of marko. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-04.
  • The Best UI Libraries for Cross-Platform Apps with Tauri
    10 projects | dev.to | 4 Aug 2023
    SolidJS and Tauri form another potent combination for creating performant, lightweight, and secure experiences. SolidJS is a reactive UI library that is similar to Svelte in the way it compiles away reactivity and updates the DOM directly, but it also incorporates a fine-grained reactivity system reminiscent of libraries like Marko, Knockout, and MobX.
  • Mudanças na DevPT
    2 projects | /r/devpt | 29 Jun 2023
  • FLiP Stack Weekly for 06 February 2023
    22 projects | dev.to | 6 Feb 2023
  • Marko: An HTML-Based Language
    5 projects | news.ycombinator.com | 30 Jan 2023
  • The Qase for Qwik: Love At First TTI
    7 projects | dev.to | 21 Dec 2022
    Marko is a huge leap in the right direction. It has streaming, partial hydration, a compiler that optimizes your output, and a small runtime. I’ve also heard through the grapevine that Marko V6 also adds resumability to the framework as well.
  • Movies app in 7 frameworks - which is fastest and why?
    4 projects | dev.to | 21 Nov 2022
    Nevertheless, the future of JS frameworks is exciting. As we’ve seen from the data, Astro is doing some things right alongside Qwik. However, more noteworthy frameworks such as Marko and Solid are also paving the path forward with some similar traits and better performance benchmarks. We’ve come back full circle in web development - from PHP/Rails to SPAs and now back to SSR. Maybe we just need to break the cycle.
  • Repeating Navigation, Header, and Footer in CSS and HTML?
    7 projects | /r/Frontend | 21 Nov 2022
    If you want more, take a look on Marko, fresh, qwik or pug. Dind't tested yet but they look like same as Nunjucks.
  • Client-side Routing without the JavaScript
    3 projects | dev.to | 7 Nov 2022
    And that is a similar feeling to the exploration we've been doing recently. Inspired equal parts from React Server Components and Island solutions like Marko and Astro, Solid has made it's first steps into Partial Hydration.
  • Astro 1.0
    15 projects | news.ycombinator.com | 9 Aug 2022
    I haven’t done any serious work with either, but I’ve been following both closely (and have contributed a bit to Astro early on). So this isn’t the hands-on response you specifically asked for, and may not contain new information to you. I’m posting anyway in case it adds context for others.

    Qwik City[1] is probably more directly analogous to Astro, Qwik being more analogous to Astro’s integrated renderers. But that highlights one of the key differences.

    Astro’s compiler mostly focuses on server rendering of static content (.astro templates, MDX) and bundling client resources along with the logic necessary to hydrate islands. Astro defers to those renderers (and in some cases their own compilers) for any further optimization of the client bundle.

    Qwik’s compiler optimizes the component code directly, serializing state into the HTML it renders server-side, for the client bundle to resume from that state. Its output is conceptually similar to Phoenix LiveView (which was mentioned in another sub-thread).

    Both are compelling approaches. I think Qwik’s will probably (eventually) have an optimization advantage because that’s a core focus of the client library. Astro will likely have an adoption advantage because it’s client-library-agnostic.

    Another framework in the space often gets passed over: Marko[2], which has been doing partial hydration for years at eBay. Marko is probably more similar in approach to Qwik (and as I understand it, getting more similar as they’re going resumable too), but like Astro has its own templating language which enables its compiler optimizations.

    Also worth watching SolidJS[3] (whose creator has also worked on Marko), which is tracking partial hydration/resumability on its roadmap. I’m not sure what their approach will look like but there’s quite a lot of insight both in the issue and the creator’s tweets/replies on the topic.

    Personally I think there’s a gap between all of these approaches which could leverage type-level analysis to go much further. But that isn’t really feasible when types being available or accurate isn’t a safe assumption.

    1: https://qwik.builder.io/qwikcity/overview

    2: https://markojs.com/

    3: https://www.solidjs.com/

  • Syntax highlighting library support for modern frontend frameworks
    2 projects | dev.to | 22 Jun 2022
    There is no support for newer frameworks like Marko, which have their own file extension (format).

What are some alternatives?

When comparing microsite and marko you can also consider the following projects:

astro - The web framework for content-driven websites. ⭐️ Star to support our work!

Jade - Pug – robust, elegant, feature rich template engine for Node.js

EJS - Embedded JavaScript templates -- http://ejs.co

handlebars.js - Minimal templating on steroids.

solid - A declarative, efficient, and flexible JavaScript library for building user interfaces. [Moved to: https://github.com/solidui/solid]

nunjucks - A powerful templating engine with inheritance, asynchronous control, and more (jinja2 inspired)

qwik - Instant-loading web apps, without effort

doT - The fastest + concise javascript template engine for nodejs and browsers. Partials, custom delimiters and more.

dustjs - Asynchronous Javascript templating for the browser and server

hogan.js - A compiler for the Mustache templating language

JavaScript-Templates - 1KB lightweight, fast & powerful JavaScript templating engine with zero dependencies. Compatible with server-side environments like node.js, module loaders like RequireJS and all web browsers.

eta (η) - Embedded JS template engine for Node, Deno, and the browser. Lighweight, fast, and pluggable. Written in TypeScript