Also, typst is just really good.
Though I ended being a graphic designer so LaTeX felt rather limiting very quickly, but fortunately found ConTeXt.
Hoped Typst was going to be great for my use case but alas it's got the same "problem" as LaTeX - modularity. Still it seems to be a great alternative for people doing standard documents.
I'm sure you remember that quite clearly.
Yeah - typst has a bunch of features that I really want for blog posts and rich documentation, where markdown isn't a powerful enough tool. For example:
- Boxes & named figures
- Footnotes
- Variables, functions (incl populated from nearby files)
- Comments
- Chapter / Section headings (& auto generated table of contents)
- Custom formatting rules (For example, typst lets you define your own "warning box". Stuff like that.)
I don't know of a better tool to write my blog posts today. Markdown doesn't have enough features. And I'm obviously not writing blog posts in latex or a rich text editor. I could use actual javascript / JSX or something - but those tools aren't designed well for long form text content. (I don't want to manually add <p> tags around my paragraphs like a savage.)
Pity the html output is still a work in progress. I'm eagerly awaiting it being ready for use!
I filed a bug (this was a few years ago) and I was told commonmark compatibility was an explicit non goal for the project. Meh.
[^0]: it doesn't matter where this is placed, just that this one has a colon.
The table of contents thing is annoying but it's not hard to write a little bash script. Sed and regex are all you need.
> Markdown doesn't have enough features
Markdown has too many featuresThe issue is you're using the wrong tool. Markdown is not intended for making fancy documents or blogs, it's meant to be a deadass simple format that can be read in anything. Hell, its goal is to be readable in a text editor so its more about styling. If you really want to use it and have occasional fanciness, you can use html.
But don't turn a tool that is explicitly meant to be simple into something complicated just because it doesn't have enough features. The lack of features is the point.
When you are losing your semester's 25-page seminal work an hour before deadline because Word had that weird little bug about long documents and random CJK characters (and whether or not the moon was currently in the House of Aquarius supposedly), you develop a ... healthy dislike for it.
LaTeX back in the day didn't need zealots - Word did all the heavy lifting in demolishing itself for anything more involved than 'Secretary writes a letter', 'grandma Jones writes down her secret butterball recipe' or 'suits need a text, and only text, on paper, quickly".
(Yes, that was snarky. I am still bitter about that document being eaten.)
Ah yes, this definitely is the “Modern” approach.
There does seem to be an open source, non-SAAS part, but information about it looks pretty deliberately buried.
They developed the main face of the product first - the online webapp which has live collaboration - which sounds like a sane choice for a new company.
These days I usually default to pandoc's markdown, mostly because the raw text is very readable.
Most students, and many researchers use Overleaf nowadays, though.
Usage level is not correlated to "rate". Sometimes people use stuff because they have to, not only because they like it. See the Microsoft Word case.
I'd agree that LaTeX has fell a bit in popularity this days against Typst - but not much in its usage. It is still the de facto standard of scientific and technical document typesetting.
Perhaps it's a programmer thing.
Don't you need to insert tons of `frame` environments to get anything worth looking at?
I don't know, if your slides are just a few keywords in a few bullet points and the occasional picture / diagram, WYSIWYM is great.
I agree that you shouldn't turn an actual article into a presentation though.
Have you considered writing pandoc-style Markdown that's converted to TeX for typesetting? If not, have a peek at my text editor:
* https://keenwrite.com/screenshots.html
* https://www.youtube.com/playlist?list=PLB-WIt1cZYLm1MMx2FBG9... (see tutorials 4 and 9)
KeenWrite basically transforms Markdown -> X(HT)ML -> TeX -> PDF, although it uses ConTeXt instead of LaTeX for typesetting because ConTeXt makes separating content from presentation a lot easier.
The problems are quite similar, "How do I center a div?" vs "How do I keep this float on this page?" Has latex really modernized? I don't hear a lot about new layouts or style mechanisms.
Most people are probably reading articles online these days, although there is a lot to be said about printing an article to read. It seems to me that adding responsiveness to journal articles instead of using a fixed paper layout regardless of media might be a good improvement for many readers in many situations.
With a fixed medium in mind, you can be extremely particular on where on this canvas you want a piece of text/graphic or whatever.
Without a fixed medium, you have to have logic to address the different mediums and compromises have to be made.
I don't want to manually type (or read past) HTML tags littered around the place. I don't want to manually put <p> tags on my text, or worry about how indentation will affect my rendered output. (For example, <p>foo</p> and <p> foo </p> render differently).
If I'm writing a blog post, I also don't want my post's text to get mixed up with site specific stuff, like meta tags and layout elements.
Are there any good "literate HTML" type tools which first and foremost let me type text, but still let me break into HTML? That I could get behind.
It's partly because I love the simplicity/power of Org and I do all my writing in it nowadays, the other part is to separate the content from the presentation so I can have the content in two different languages but still end up with the same formatted document for both.
Anyone have experience with this or have favorite LaTeX templates for CVs?
I'm currently experimenting with this:
I never got into emacs. Is Org worth it?
My cv is an adaptation of one of the templates there: https://drive.google.com/file/d/1woxVNcJ4AmT7dD2WEnYr9BHEEY7...
EDIT: ahahahahaha I just came across this cv: https://www.overleaf.com/latex/templates/resume-slash-cv-tem...
It's published under GPL so relatively protected from corporate nuisances. Takes five minutes to teach someone how to mark headlines, add content listing and change document type, then a little more to teach how to add tables and images.
cadamsdotcom•2h ago
Knuth & friends were on a roll naming things - the 80s must've been quite a time.
As always wiki knows all: https://en.wikipedia.org/wiki/LaTeX
seanhunter•2h ago
The "La" in latex is Leslie Lamport. https://lamport.azurewebsites.net/
TheAceOfHearts•2h ago
The great thing about language is that you can just change things if enough people play along. Call it gif or jif, arxiv or archive, latex or laytek.
josephg•1h ago
mariusor•1h ago
kashunstva•2h ago
Or “lah-tek”, the Wikipedia article doesn’t seem to address which, if either is preferred. And I think Leslie Lamport said that he didn’t want to impose any particular pronunciation.
mcv•1h ago
mturmon•1h ago
mturmon•1h ago
Knuth, on the other hand, has a whole rationale on why it’s pronounced “tech”. (“Your keyboard should become slightly moist”, iirc).