6,026 karma · joined October 27, 2019
And there are plenty of other differences besides "who", for example, "how".
That's never the case for any consumer app, the potential for improvement in UI is practically infinite. But also, just use the old version if it's finished, you don't need to upgrade?
(this app has plenty of bugs / missing issues just like everything else, for example, blurry text on some platforms)
> Having multiple names for the same or very similar colors is no problem.
Only if you dismiss clarity as a value "there is no requirement for pinpoint accuracy". At which point, though, what purpose does this database serve??? And again, this db is deduplicated, so it doesn't share your argument, hence it's legit highlighting where it falls short on deduplication.
> low quality "Silent Breeze"
that's a different fail, though not much different from other low quality real colors like Turquoise that did catch on
which a plaint text editor is decidedly not since it fails at the most basic editing tasks - search and search&replace. That is the joy killer. Thus the tool described in the blog is closer to the right one for this task
> When creating new color names, it's essential to understand which areas of a color space are crowded and where new names can be added
Indeed it is. It's also essential to not add names in those uber-crowded areas
> A lot of that is covered by
Almost none of this is, hence the examples.
> markdown without any syntax highlighting
The opposite, syntax highlighting is the only saving grace.
> it should be obvious as soon as you type it due to changed highlighting
Do you know that people copy and paste sometimes? Your "obvious" becomes a needle search operation to find which symbol broke it. Or it may be hidden in the middle of a page.
> Regex handles that pretty trivially
How? Write your trivial regex to exclude arbitrary html markup between words. Start with a simple example of a bold word with multiple maker types, extend into adding color and maybe a tag? Then estimate how many 0.0x% of users in the bright future of universal md support would know what regex is.
> I’ve also never run into the need to replace a phrase that is sometimes partially marked up — seems niche?
That's unfortunately a common issue - people with very primitive document editing experiences where broken search is a non issue suggesting their workflows for the masses
So the top still doesn't understand (it's not diligent), wouldn't you expect the other 99% of the business to be managed just as "diligently"
Except it doesn't because it isn't, the challenges above are from editing raw. There is no joy in reading/editing anything non-primitive in MD
It's the opposite, you remove the major challenge in modification- change one char and break your whole table. It type an extra backtick and now paragraphs of text are misformatted. Add/remove a column? Ha-ha, where did you get so much time to waste? Join two cells? Oh, that's too complicated
Search and replacea phrase? Impossible to find, there are formatting markers between words.
Yet as you note later there is no such thing as a singular markdown. So why would time do magic here? There is nothing remarkable about bad underspecified system suffering from incompatible variety for decades, computers are littered with examples of those
> One of the original ideas behind Markdown was that a document should remain readable even before a computer interprets its formatting
Which was never true since it includes HTML which you criticize in the very next sentence
> We have spent decades dealing with document formats that behave differently depending on which application created them, which version of the software is installed and which operating system is trying to open them. Markdown should be an opportunity to move in the opposite direction.
Weird, MD has all the same issues, why would it present any opportunities?
Not really, you've just gone from one empty argument to another.
> Choosing not to do something you’ve done is experience.
They already had the experience because they used icons before. They had experience adding icons and not adding them to a bunch of menus.
The way out is to use substantive arguments that don't depend on the shaky grounds of someone's authority
> Manual alignment
Guess, another decade before Rust robots can do columns?
> PHP security team, operating on consensus, struggled to choose
What an unfortunate waste of a security audit. (and consensus is an obvious flaw in decision making)
> PHP runs a large share of the web... Yet security work on PHP itself still depends on a small group ...
Another unfortunate big structural issue that's unlikely to change.
Are there structurally much safer ecosystems out there?
Why wasn't this second spend by the parties accepting those certificates as valid before they were accepted?