Just to clarify, I google a lot while coding, but one thing I learnt from my engineering degree is that is there is no ‘best’ solution.
Just to clarify, I google a lot while coding, but one thing I learnt from my engineering degree is that is there is no ‘best’ solution.
Writing html is absolute programming in 99% of the cases. You program the structure of a web page, even more so if you use templating or integrate structure with js functionality.
In a loose sense, yes.
But then someone could also say that when making LATEX templates is programming the structure of the documents.
I prefer calling it markup, because, even though people might prefer calling it ‘programming’, due to people’s high esteem perception of the word, if you look at it from a neutral standpoint, markup is a word that represents the actual work, much more closely.
e.g. I use Qt Designer[1] to create UI stuff, and in some cases QML[2] and if I were to only be defining placements, shapes, sizes and colours of elements, I would like to call that part as marking-up the UI [3], while the part where I define functions, timers and connections would be the programming part.
which is a UI to create UI stuff, which creates an XML definition of the final UI to be generated ↩︎
which is based on JS ↩︎
of course I don’t because nobody would understand, but if people did care about the word (and I kinda like the word), it would be more accurate ↩︎
tbh I see a philosophical problem of separating markup from programming. Creating object structures be it in Latex or html is essentially the same thing as creating code objects. Most high level programming is more about structures and “placing things around” than people like to admit and that’s 90% of all programming today.
Although I’d like to say, “it’s not”, that definitely is what takes up most of my time, even though it ends up being lesser part of the code (thankfully). But a lot of that is UI designing and deciding what might give a better UX, rather than programming.
Of course, if I were not using a framework, which does all the painting for me, I would always be programming the UI and that would be 90% of my code and 99% of my coding time.
Also, I would probably take a year to complete a weekly project.
In my dictionary, programming for the UI elements has been done by those, that created the library that parses the markup language and does the paint events. They also have to manage number of separate draw calls and other GPU efficiency stuff, making it easy to just define most of he placements using markup.