I would like to see TS as the first class citizen however, with JS being deprecated essentially.
What do you mean by that.
From what I read, Deno does primarily use and target TS. They label all that JS stuff as backwards-compatibility and ability for a migration path.
I strongly and broadly disagree, both with the premise and the argumentation they do.
But first off, and because it's significant to the argumentation; Why is their entire argumentation in line-based diffs, but when I go to their homepage I see screenshots of inline diffs?
Inline-marking of differences are incredibly powerful. Programming language aware diffing should make use of understanding to support the highlighting, with the option to ignore different levels of irrelevance at the users choice.
I don't want anything hidden. I want to default to every difference shown, but put side by side as much as possible, with different levels of highlighting of the differences according to their relevance and significance.
I want to default to every difference shown, but have alternative options to ignore things. I want to have the option to ignore whitespace changes, and potentially additional options to ignore more (this is the opportunity semantic understanding could bring, in addition to the line and change matching).
TortoiseGitMerge allows me to choose between
I default to the first, but regularly switch to the second and third, when indents change. They are irrelevant when assessing the logical changes. But whitespace is still significant in laying out code. It's both significant, but for different reasons, and as different layers and layers of assessment.
All that being said, we don't use an enforced automatic formatter.
But also, we use whitespace, line breaks, and other syntax consciously. Readability takes precedence over consistency. I hate hard character limits on lines. Sometimes the vertical structure is much more significant to readability than an arbitrary (and often narrow) line character limit.
One example:
Do you write
if (error != null) return error;
or do you write
if (error != null)
return error;
or do you write
if (error != null)
{
return error;
}
I dislike the second because its semantic structure not very obvious and somewhat error prone. For simple early returns like this, I prefer the first. But in cases where it's not a simple and short return, the third can be preferable despite being only one statement.
Automated formatters often can't do one or the other alternatively, and sometimes don't allow ignoring one rule.
I host/manage it in my workplace. Only for groups, repositories, and merge requests with reviews. It's super bloated for such a [simple] use case. Every time I upgrade I especially see how loaded it is.
Their promotion is targeting a full-featureset devops and delivery pipeline with stats tracking and managed target environment.
Back then it was the better alternative to Phabricator, which we used before. We (I) may have chosen something different today.
He's gonna live a long life. Until we know pi.
Nested CSS obscures complexity
An interesting point. Something I will take with me for observation and consideration.
Maybe sometimes it's worth despite it and other times not.
Ubuntu LTS.
It has the option for PPAs when the distro doesn't offer packages or recent package updates but the upstream project does.
It's a well-established and stable distro.
Why would it have to be a fork? Firefox violates none of the points you listed.
Depends on the implementation. OP talked about potential of a CDN serving the shared resources. The instance servers wouldn't have to proxy the content. Which would allow caching and not duplicating content and transmission through multiple endpoints.
Yeah, I guess it's linear rather than exponential in growth. From an instance hoster point of view, it just never ends though, and not very predictable.
PDF magic… It has grainy text. But the selectable text and displayed text have a 1-character offset.
I assume they display the original scan so it definitely does not contain errors, while still providing the image-parsed text for searchability, indexability, and select-+copyability?
Unfortunately, the grainy text is hard[er] to read.
I had no idea experts exchange existed before stack overflow.
For me, it started showing up in web search results years after stack overflow became popular. And I was confused and annoyed why a copycat with pay walled features (even the answers IIRC) was given priority by search engines.
tl;dr: They merged the code of an unmaintained dependency into their project.
I don't think I can take anything else away from it.
eeew (/s)
I have a dislike for both of them. Well, for JavaScript mainly the server-side part. I'm fine with it on web scripting, where it's the only native one.