eureka
org-mode-site-template
| eureka | org-mode-site-template | |
|---|---|---|
| 11 | 1 | |
| 4 | 0 | |
| - | - | |
| 1.8 | 5.6 | |
| over 3 years ago | 3 months ago | |
| Emacs Lisp | ||
| GNU General Public License v3.0 only | MIT License |
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.
eureka
-
How to build a website without frameworks and tons of libraries
Here's an example of building a well-structured, maintainable web-site using JavaScript, HTML and CSS: https://github.com/wisercoder/eureka/tree/master/webapp/Clie...
It doesn't use React (imagine the horror!), instead it uses two tine 500-line libs.
-
React is 10 years old
> a literal 5-20x productivity boost
Not really. See a better way here: https://github.com/wisercoder/eureka
- Building a Front End Framework; Reactivity, Composability with No Dependencies
-
React is a fractal of bad design
I'm not quite seeing React being used, just JSX though? All the view and state updating is being done manually, but it looks fairly well-organised. There are small optimisations like debouncing onInput with a timeout (avoiding rapid re-rendering for every character typed): https://github.com/wisercoder/eureka/blob/master/webapp/Clie...
- Ask HN: Good resource on writing web app with plain JavaScript/HTML/CSS
- Can We All Just Admit React Hooks Were a Bad Idea?
- Ask HN: What happened to vanilla HTML/CSS/JS development?
-
I don't miss React: a story about using the platform
React works well for simple, non-interactive components. Complex, interactive components are going to have state. Stateful components don't work so well in React. If you want to update props in a stateful component, the recommendation is to replace the component entirely by changing its key. At the point all of the benefits of React (preservation of selection, caret position, scroll position etc.) vanish. You might as well use vanilla js instead of React.
What does using Vanilla JS look like? Here's an example: https://github.com/wisercoder/eureka It uses two tiny 500-line libs. It uses TSX files, just like React. It has components, just like React. It doesn't have incremental screen update, but neither does React, if your components are interactive and stateful.
- A Visual Guide to React Rendering
org-mode-site-template
-
How to build a website without frameworks and tons of libraries
You can create a decente static website with templating, sitemaps, etc. with Emacs' built-in Org Mode. Here's my minimal setup:
https://github.com/hcarvalhoalves/org-mode-site-template
What are some alternatives?
webcomponents - Web Components specifications
lowtechguys
Ink - 🌈 React for interactive command-line apps
aws-gocljs - fullstack web should be easy
el - Minimal JavaScript application framework / WebComponents base class
decap-cms - A Git-based CMS for Static Site Generators
editable-website - A SvelteKit template for building CMS-free editable websites
uhtml - A micro HTML/SVG render
render - render github markdown to html
10kbclub - A curated collection of websites whose home pages do not exceed 10 KB compressed size
Slim - Slim is a template language whose goal is to reduce the syntax to the essential parts without becoming cryptic.