Is that true? In communities or tribes of antiquity I assume there was some trading fruits of different labours before coinage. Still an 'invention' beyond baser individual survivalism.
Templated though, not manually writing it out for every blog post say. I think GP means it just has more friction as a writing format than markdown for example.
No, literally manually typing out HTML tags and everything. Many of us did it so much things like Emmet (https://emmet.io/) were invented and used so we could hammer out full HTML documents even faster.
Even after React became popular, people are still manually typing out HTML elements, although they call it "JSX" instead, but in reality it's just HTML.
My first blog on the internet literally was a bunch of .html files, where my post "template" was the first post copy-pasted when you wanted to make a new post. Changing the design involved changing the same thing across all files.
> PS: Really cool static site generators that shoot for simplicity don't require you to create extra template files written in a new, made-up template language. When you want to create a new post, you give it (a) the static files from your existing site and (b) the markdown for your new post. The "templating" engine inspects your existing posts (incl. e.g. class attributes) and then copies the same document structure into a new file, except with the right stuff (timestamp, title and heading, post content...) substituted in to the places where it's supposed to go.
Basic HTML really isn’t a big step up from Markdown though, and no one was complaining about that. In some instances it’s simpler even. I often forget the exact syntax for a table in Markdown, by comparison <table>, <tr> and <td> are easy to remember. All of the major parts of Markdown are pretty easy, <h1>, <strong>, etc etc. It was written with human authorship in mind.
Typing out <p> for every paragraph is annoying, for sure. But a converter that switches out \r\n\r\n for a new paragraph would be a reasonable middle ground IMO.
When using AI, I often find myself preferring either plain text (no markup whatsoever; just manual / text editor formatting of text blocks) or simple html to markdown, depending on the situation. To the point that I rarely see any point in using markdown for anything. If it is meant for to be a simple text mainly for human consumption, the markups often don't add much clarity (and often bring in an amateurish look, as if the author didn't know how to emphasize using English constructs), in which case plain text feels more pprofessional. If it is meant to be [lightly] processed before being presented to a human, or if it is meant to be processed by a tool / bot / LLM, then HTML is infinitely more straightforward.
Also I often call out my colleagues if they try to put a table in markdown. Markdown is not built for tabular data in most professional settings (i.e., one or two table cell could easily take a whole line of markdown to express). A basic <table><tr><td style="background: red">some number</td></tr></table> goes a long way.
A lot of editors will auto add the ending tag, and auto-update the ending tag if you rewrite the start tag. I think it's gotten pretty darn easy to use HTML er I mean XML ;)
Well if you're going to be like that you may as well say something about assembly, butterflies, and what the hell's a web log anyway, spiders and beavers have nothing to do with one another.
'we have been authoring' is present perfect continuous. Going forwards, and for at least the last two 'decades', HTML blog posts can use CMSs.
I don't know which version you read of course, but worth noting they've been increasingly diluted over the years, in much the same way as OP says Disney did to Pinocchio.
Not meaningfully, but sometimes 6mo-1y as part of an undergraduate programme to gain industry experience. E.g. I had 6mo in my third year (not at Cloudflare).
> How is the company morale at github? I imagine it to be really very depressing
Since we're guessing I could also imagine the opposite: stressful sure and heaps of work, but numbers absolutely through the roof, and lots of opportunities, bonus/promo-boosting wins, etc.
That's standard for HN and explicit in the guidelines linked in the footer. No need to include the company/domain in the title, and it should match that on the submitted page. Which is 'Incident with Actions' as it reads here (now) too.
You don't see these edits happening as regularly with other submissions, though.
It's not like OP is running out of space in the HN title, either. How is "Incident with Actions" more user-friendly than including "GitHub outage" in the headline?
Furthermore, the subtitle of the OP is "Incident Report for GitHub," so why not just include this if we need to follow the rule so carefully?
Well, I don't know what it looks like in Apple Wallet, because I use Google Wallet, but for the same reason I'm struggling to imagine the problem because there the cards are pretty large – maybe ⅔ real card size on my Pixel 10 – and in a carousel at the top. So you can see clearly which one the active one is, and just swipe between them if it's not the one you want.
Easier than my physical wallet tbh, where they're behind each other, which I say begrudgingly because I've long held out, only starting to use the app a couple of weeks ago.
> That means the AI was performing more like a clinician producing a second opinion based on paperwork.
That actually seems like a good application – automatically get a quick AI second opinion for everything; if it's dissenting the first/human medic can re-review, or comment why it's slop, or get a third/second-human opinion.
(I'm assuming most cases would be You're absolutely right, that's an astute diagnosis.)
reply