[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: web design

From: Kendall Shaw
Subject: Re: web design
Date: Mon, 1 Jan 2018 22:33:35 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

On 01/01/2018 09:05 PM, Emanuel Berg wrote:
Jude DaShiell wrote:

One possible direction gnu tools might take
in the future would be in terms of scripts
first to install when necessary Linux tools
and use those locally then send site files
out for further checking and perhaps
processing and collect those the external
sites processed for the developers.
Multiple subdirectories with names of
internal and external tools on them could
hold the processed content as the content got
processed and returned. It would then be up
to the site developers to review what was
returned in each subdirectory to find if any
of the processing tools made
unacceptable errors.
Indeed, feel free to spend 100+ man hours on
that tool, and when done, you'll be so fluent
with every under-the-hood mechanism, you won't
even need it!

My nephew who could use Windows prefers Linux
for his web development he does for other
companies so if any of this starts happening
I think he'll be very interested and may even
be making some technical contributions sooner
or later.
Everyone prefers Linux to Windows for
everything save for games and Facebook, and
most certainly for everything ending with the
word "development"...

So, if web design means web development, I haven't seen people editing html files very often in a long time. For the progammer part of web development, Ruby on rails was a start to web application generators. Or, I think it was the big game changer long ago.

So, angular for example, has tools to generate parts of a web application that are separated into components. Except for rare static html files, what people edit is a template that is bound to javascript, ultimately. Styles (CSS) are compiled from something like less or sass, Javascript is compiled from something like clojurescript, typescript or newer javascript compiled into compatiable javascript. HTML is compiled from the templates.

That whole scheme fits with emacs and unix-like environments intentionally. Instead of a giant program like there were in the 90s, everything is modular so people can use the tools that they are comfortable with, or are told to use by people that they work with.

Everything, including the javascript and CSS is generated by tools. So, you use tide for example in emacs to edit typescript programs, or ensime to edit scala programs, or cider to edit clojure programs and than use the web frameworks nodejs build system the compile source code into HTML, CSS and Javascript. The GUI part of the development environment is within the web browser, where the web framework interfaces to the debugger within the web browser. Tools in emacs, vim, VSCode etc. interfaces with the underlying framework to edit and debug.

Clojurescript, for example can be edited in emacs at the repl as you watch the result of what you typed appearing in the web browser.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]