153 karma · joined January 29, 2017
Here's another: https://remarkjs.com/
There are even commercial apps, such as Deckset (macOS).
# title
- item1
- item2
some paragraph with an *italic* word
-> <html>
<body>
<h1>title</h1>
<ul>
<li>item1</li>
<li>item2</li>
</ul>
<p>some paragraph with an <i>italic</i> word</p>
</body>
</html>In its original form it was simply an aid to get static html from human readable text (<- that there is the basis for md).
For better or worse, it's been forked a few times, adding new abilities or even in efforts to make it stricter. The main idea of readability still applies. I could hand over a markdown formatted txt file to someone and they'd probably read it just fine, whether they could code or not. Html in plain-text form, though? Not sure that would work.
It has quirks, but the whole I really like it. I've used it for writing guides, taking notes... Maybe even for web content at some point.
Don't worry about references. This is more than enough to get me re-started, dig through my old books/articles and find new ones.
> Further, even under this alternative explanation, I would still not call wa a topic marker.
-> "subject marker"? ;-)
Enjoy your vacation (and maybe pursue a phd)!
Also, see user gizmo686's excellent explanation for one approach below.
Well, I realise the topic + contrast bit but is it really treated as a null anaphora, rather than acting as both topic and subject marker in my example...? My examples referred to information structure more than anything.
Yes, I realise you can have sentences like "Ashita wa Tanaka ga..."/"Sou wa hana ga nagai." - I've even seen a discussion on double topics (some old, theoretical text by Yasuo Kitahara IIRC, probably more known for 'Mondai-na Nihongo'). I also realise that in some contexts where it seems to denote a subject its noun is only a topic ("watashi wa unagi desu").
Logically, it would indeed be quite difficult for a subordinate clause to contain the/a topic.
Anyway, I'm curious if you happen to have further explanations (or articles)!
(Unrelated note: why is it that Japanese of all things make us crawl out from under our rocks...? :-))
Forgive me for saying this, since you seem to be a native speaker, but don't you mean that they both introduce the subject, not topic (using 'topic' as a linguistic term)?
"Wa" would be the topicalising subject marker, denoting known information:
Tanaka wa nihon ni itta.
Tanaka went to Japan. -> As for Tanaka, he went to Japan. Tanaka = known information (i.e. Tanaka is familiar to the listener)
"Ga", while also a subject marker could denote/introduce new information:
Tanaka ga nihon ni itta.
Tanaka went to Japan. -> e.g. It was Tanaka who went to Japan.
Tanaka = new information (e.g. the listener is did not not Tanaka was the one going to Japan.)
(Note: I realise there are other constructions for my interpretation of the ga-sentence)
It was quite different when I grew up. [Home] Internet was not a thing that existed and most data was analogue. When home computers became common I had to learn a bit about the system if I wanted to get some use out of it. I'm not saying user friendliness is somehow bad, it's what we should always aim for! We've come a long way and I like it here. I'm not that old, it's just that I had a childhood before home computers and internet were a thing.
The school system back when did in fact teach me a bit about computers. In my case, in [the equivalent to] high-school when home internet started to take off, our curriculum came to include (very) basic computer science, (very) basic coding in ... prolog? (prolog might be incorrect) We created home pages in class from scratch in html. Not by choice, as most of this concerned every student at my school. Maybe I was lucky?
In my nephews case, they were handed a computer, then absolutely nothing. And I mean nothing. They are still forced to bring the computer to every class but report hardly ever touching it at school. Maybe their bad experience is an exception. I hope so. Back then my teachers definitely weren't the best - or even good - at computer science but they were prepared to try and to learn together with the students.
They could have received iPads, Windows or linux setups... Wouldn't have mattered since there was no plan in place.
I'm at a point where I strongly believe schools should just hand out Raspberry Pis to students to tinker with instead. Add a proper curriculum and let the students fail, mess up their RPIs to get to know the system. Let them write simple scripts. Anything. RPIs are easy to restore.
Maybe other schools are doing better over here, but when my nephew (growing up with minecraft/pokemon go on mobile only) didn't dare to touch most of the stuff on his school laptop due to being afraid of messing up I tried very hard not to scream.
Though, I'm curious what comes of this.
Currently the "official" install/build method via make fails on my mac (sierra - could be some other issue) and on top of that 'opam init' (?) completely broke the fish path evaluation (not Patoline's fault, I guess). Manual fish fix: https://github.com/ocaml/opam/issues/2255.
(Normally not a Windows user so I have no idea why this is the case or if by design.)
I'm just not that surprised to hear that the brain is constantly trying to interpret the inputs it gets, what else is there? Is it then that some simply have a lower threshold as to what their brains determine to be signal?
(I really don't know these things, I'm just curious)