What's the motivation for making it another language as opposed to a framework / library?
Web Origami, for making websites where you can understand how they’re made
31–40 of 77 posts
Re: Web Origami, for making websites where you can understand how they’re made
#32Earlier quoted context omitted.
The best analogy for the feeling I got when reading this is visiting someone at his house and the first thing he says is „BTW, don’t take any of my stuff, that’s stealing!“. Sure, but can I take of my shoes first? If it’s in a CodeOfConduct.md I get it but having it be more than half of the readme feels a bit weird.
Which is it? So problematic that you wouldn't use it even if it were exactly the tool you needed, or "a bit weird". I agree, it's a bit weird. So is putting a lot of effort into a project that nobody is asking for and you'll give it away for free. There are many people in my life that are neurodivergent and some situations cost more than they are worth. I have had several projects I thought were good candidates for o…
> Which is it? So problematic that you wouldn't use it even if it were exactly the tool you needed, or "a bit weird".
Well, it’s weird enough that I wouldn’t use the project unless it’s the only thing available (but there are other SSGs) or if an employer paid me for it (I don’t really care then if the project is stable, that’s my employers problem).
> If reading those rules and abiding by them is too much for you, then just turn around and walk away. That's the intention and goal. They're doing you a favor, letting you know that your brand of weird is not compatible with their brand of weird. They don't have to make space for everyone in their little project, and there might not be space for you there, and that's OK.
I don’t have a problem with the rules themselves, to be clear. My problem is the presentation. It’s also not a big problem to me, I’ll just use something else and move on. That’s fine.
Re: Web Origami, for making websites where you can understand how they’re made
#33And still supporting HTTP. I don't know about this, anyone can suggest a reason to use HTTP nowadays?
Sure: your web server doesn't need to care about the "S" part in the slightest in order for the web site to work over HTTPS.
Reverse proxies have existed for a very, very long time, you simply run a local HTTP server and you let the reverse proxy take care of https-to-and-from-the-WAN-side part. Even in dev context, that takes at most a few minutes to set up these days thanks to letsencrypt's certbot.
Re: Web Origami, for making websites where you can understand how they’re made
#34YAML? C'mon, guys
Re: Web Origami, for making websites where you can understand how they’re made
#35So... it's a static site generator? I've looked through the site, but I'm having trouble putting it in context. Sounds like it takes data and turns it into a static website. Is that right?
That's how I read it too? And while the documentation has lots of examples, I get a bit lost in that you start with some form of JSON file, which consumes either YAML or HTML files, who in turn can consume Markdown files. It doesn't seem (from my reading!) to have the level of abstraction I would expect from a SSG.
Re: Web Origami, for making websites where you can understand how they’re made
#36My interest in this is piqued. I’m really happy to see people doing things to simplify personal standalone website authorship making it expressive and flexible without a bulky content management system or jumping through hoops for some front-end toolchain. I know when I’m developing things I’m often as or more concerned with satisfying multiple use cases or functionality extensibility, but having a nice focused tool…
Whats wrong with just using HTML, Js and CSS for personal projects?
Re: Web Origami, for making websites where you can understand how they’re made
#37This site would benefit from a comparison with other static site generators.
I dare say it's not that difficult for a programmer to roll their own SSG with whatever is at hand.
Does it have any clever properties that naive solution wouldn't?
* Like reproducible builds or incremental/cacheable builds?
* Does it require the entire site fits in memory at build time, or can it generate terabyte-sized sites without breaking a sweat?
Re: Web Origami, for making websites where you can understand how they’re made
#38Don't hate it but it feels like the Origami language should just be a typescript library. I'm not a fan of DSLs in general though.
Yeah, I don't see how using a DSL helps get any closer to "understanding how the website is made" especially once you look at its templating system.
I think a better description of the project is that it's built around its async-tree abstraction: https://weborigami.org/pattern/
Re: Web Origami, for making websites where you can understand how they’re made
#39So... it's a static site generator? I've looked through the site, but I'm having trouble putting it in context. Sounds like it takes data and turns it into a static website. Is that right?
so, you're saying the claim of making websites where you can understand how they're made doesn't seem to hold up?
Re: Web Origami, for making websites where you can understand how they’re made
#40My interest in this is piqued. I’m really happy to see people doing things to simplify personal standalone website authorship making it expressive and flexible without a bulky content management system or jumping through hoops for some front-end toolchain. I know when I’m developing things I’m often as or more concerned with satisfying multiple use cases or functionality extensibility, but having a nice focused tool…
Whats wrong with just using HTML, Js and CSS for personal projects?
I do that. Duplicating the header, menu, and footer manually on every page is a pain in the ass. Not to mention the lack of minification.