When you're writing a release, or about some detail of your project, you need to directly give new readers background, or at least provide some navigation to something else that provides background.
A lot of tech and tech-adjacent writing is like that these days. Our cool project X now does Y! With no introduction about what X is, or even a link to something that describes it. So most readers are left to wonder about why should care. At times, I've even tracked down X's github repo only to find that their README has the same problem.
It's an easy trap to fall in when you write. It's easy to feel like you're over-explaining things. You, the author, know what it is, and likely many of the people who follow X know too. The problem comes when some curious person outside of the Xosphere takes a look. Chances are good you'll lose most, if not all, of them.
If you want people to be interested in your X, then make sure they have a way of learning about your X when you introduce improvement Y.
A simple font selector would be nice. I have some seriously impaired vision w/o correction and monospaced fonts really help when I have to look at a screen that way.
That and ability to zoom in/out or increase/decrease font size.
Note that Bike does support changing font size already.
I'm getting a lot of request for also adding changing the underlying font. Will likely add that sooner then later now since lots of people seem to need.
Thanks. (In case people wander by later, this was tweeted half an hour after my post above, and the OP has made it clear in a parallel subthread that they were referring to something that was later admitted to be a hoax by the perpetrator.)
The same user later tweeted: "to the people getting mad at me for this, it's ya' own fault for believing a single tweet from an unverified source instead of looking at the official twitter pages. i'm just havin' fun." https://twitter.com/SPLLTHEMANSNAME/status/13711921957772328...
So yes, unsurprisingly, something that "apparently" happened but wasn't sourced didn't actually happen.
Is this a regional thing? I haven't ever perceived it that way over the internet or here in Europe, but I've seen several comments who agree with you on HN.
I'm in NA and also don't understand why coder is negative. I remember it was very common in the old demoscene days. I've never even seen someone non-technical use the term. Usually non-technical people use programmer.
The one that irks me is engineer. I've met very few developers who have the sort of professionalism that the term engineer requires. Most developers are more like cowboys whose primary goals are making other developers and themselves happy. An engineer needs to instead feel responsible for serving the users of the application, which includes maintenance by others as a subgoal. No doubt my definition of engineering is not popular here.
I haven't seen it as a pejorative either, yet I would not refer to myself as a coder.
A good software engineer/developer has more than just code on their mind when getting something done. In fact, code is ideally the last thing you get around to.
Related: I can tell you that the publishing industry is very active on Twitter. Search for the usual hashtags and you'll find editors who may be able to help field questions!
A lot of tech and tech-adjacent writing is like that these days. Our cool project X now does Y! With no introduction about what X is, or even a link to something that describes it. So most readers are left to wonder about why should care. At times, I've even tracked down X's github repo only to find that their README has the same problem.
It's an easy trap to fall in when you write. It's easy to feel like you're over-explaining things. You, the author, know what it is, and likely many of the people who follow X know too. The problem comes when some curious person outside of the Xosphere takes a look. Chances are good you'll lose most, if not all, of them.
If you want people to be interested in your X, then make sure they have a way of learning about your X when you introduce improvement Y.