News for hackers. Stuff that matters.
Re:Polymath: A Markup Language for Everything by alok-g on Sunday February 09, 2020 @03:20PM (#22284081)
I have a basic question partly related to the project. When a markup can be compiled so fast, what's the fundamental reason we don't have WSYIWYG software that saves in the markup format as the norm.
Re:Polymath: A Markup Language for Everything by johnmorrison on Sunday February 09, 2020 @03:29PM (#22284118)
I'm sure that could be done but I'm not sure if it's the right thing to do. I think it's important for people to understand the syntax and what they're using.

I think it'd be cool to do a side-by-side web app where you can type your Polymath code and see the resulting page at the same time.

Re:Polymath: A Markup Language for Everything by alok-g on Monday February 10, 2020 @03:03PM (#22292668)
Think about how many people in the world are missing on the benefits of such markup languages because they aren't interested in non-WYSIWYG/M. The market potential could be much higher if syntax learning can be avoided.
Re:Polymath: A Markup Language for Everything by johnmorrison on Tuesday February 11, 2020 @09:55PM (#22305310)
It really depends on the specific user and why they need the language.

Ultimately, Polymath is meant to provide a file format that will work for the long term, so I don't think users should be always getting an abstraction of the language through WYSIWYG, because then they don't understand the files they are preserving.

If you only care about having a nice blog, then sure, WYSIWYG might be convenient, but the whole reason for using Polymath instead of pure HTML/CSS + JS libraries is because it gives you the same/similar level of convenience as a WYSIWYG editor without losing exactness and understanding.

Re:Polymath: A Markup Language for Everything by alok-g on Wednesday February 12, 2020 @01:46AM (#22306483)
I follow that viewpoint and am OK with the direction being taken.

On the other hand, even after asking many, I have never received a good answer to why the exactness and understanding cannot be obtained with a WSYIWYG/M markup editor.

Re:Polymath: A Markup Language for Everything by johnmorrison on Wednesday February 12, 2020 @05:11PM (#22313370)
They abstract away from the underlying code.

You wouldn't be able to tell the difference between

  {b Bolded} {b text}
and

  b Bolded text
this becomes especially concerning with TeX, custom styling, etc
Re:Polymath: A Markup Language for Everything by alok-g on Thursday February 13, 2020 @07:50PM (#22322934)
That makes sense, and I can imagine that.

However, should it not be possible for the software to find a minimal cover for the formatting that would produce the same visual output, thereby practically recovering what hard-crafted markup would have been?

Thanks.

Re:Polymath: A Markup Language for Everything by johnmorrison on Thursday February 13, 2020 @08:54PM (#22323323)
Yeah, if I'm interpreting your words correctly, this would be like turning

  p {b This} {b text is} {b bolded} this isn't
into

  p {b This text is bolded} this isn't
But then the issue is as follows:

In Polymath, I'm planning on allowing basically arbitrary CSS styling by parent, id, class, etc. So if the user later wants to do something like put a rounded box around each span of bolded text, those two, while initially looking identical in WYSIWYG, end up completely different.

Re:Polymath: A Markup Language for Everything by alok-g on Friday February 14, 2020 @08:28AM (#22326290)
I can take that. Thanks.