But why? Why should web pages that don't require javascript require it?
Ferro – Simplifying web development, no more HTML
21–30 of 67 posts
Re: Ferro – Simplifying web development, no more HTML
#22Oh god, why?
Re: Ferro – Simplifying web development, no more HTML
#23It’s great to play around with madcap ideas like this! That’s how we move towards better technology, and that path isn’t always obvious. That said, this is awful. Never, ever, ever override native scroll experience unless you’re building something that isn’t a page - and even then think thrice about it.
> Never, ever, ever override native scroll experience
I don't think it does.
Re: Ferro – Simplifying web development, no more HTML
#24This is more a ruby-to-js compiler than a simplification of web development. You can do the same thing is pure javascript (generate html and css rather than specify it) - which would likely have even less ceremony.
It's not just a ruby to js transpiler. Opal is that.
Re: Ferro – Simplifying web development, no more HTML
#25> no more HTML/JS/CSS But it's there, just an abstraction (or many) away. If you don't get HTML/CSS then no framework will help you that generates it. You can avoid JS, but understanding the DOM and CSS best practices is essential. Once you get it, you don't need libraries like this.
Theoretically you could write WebAssembly code that generates e.g. a bitmap, or an SVG, and have a minimal, unchanging HTML+JS "bootloader" for it. Using browser's caching, you can save bandwidth and keep that WebAssembly code from being re-downloaded. Then you can feed it URLs serving your own content in your own compact, logical and otherwise awesome format, and have it rendered. By that moment you will have reinve…
You've basically just described "The Birth & Death of JavaScript" https://www.destroyallsoftware.com/talks/the-birth-and-death...
Re: Ferro – Simplifying web development, no more HTML
#26It’s great to play around with madcap ideas like this! That’s how we move towards better technology, and that path isn’t always obvious. That said, this is awful. Never, ever, ever override native scroll experience unless you’re building something that isn’t a page - and even then think thrice about it.
> Never, ever, ever override native scroll experience I don't think it does.
Yeah, looks to just be an tag with overflow:auto set
Re: Ferro – Simplifying web development, no more HTML
#27I've never been totally comfortable with CSS, even if it's been all I've used for years. Something about thinking in tables and having to translate.
I've just begun learning CSS Grid and found it a vast improvement. It's so great to not have to translate anymore. The two negatives are no support in IE and it gets complicated once you get beyond simple forms though a fix is promised.
Re: Ferro – Simplifying web development, no more HTML
#28Says the website which has double scroll bars when the viewport is too short vertically? This is definitely under-baked.
Re: Ferro – Simplifying web development, no more HTML
#29Or how to produce a website that no one (or nearly) will be able to maintain :)
Re: Ferro – Simplifying web development, no more HTML
#30It is possible to define an android application without defining a single XML file. There's a reason Android provides XML based definition for layout definition. The alternative is VERY tedious and bloats the code. Which is what this seems to be going towards. This has the added disadvantage of not making it clear in one place what the structure of things is. You have to hold it in your head or on paper what the defi…
Flipping your comment upside down: then we just need a layout design tool on top of Ferro and we'll get a Ruby equivalent to VS or Android Studio for the web.