Would be helpful if you provided at least 1 example
HN user
eviks
Why make yet another tool with yet another set of quirks?
Obviously because not all sets are equal?
If you need to install this enumerator and other deps on the machine, how much harder would it be to install nu and its deps?
I still enjoyed the convenience of opening and editing a single file quickly. However, he was right to question it. I no longer needed Sublime Text and got rid of it.
Where did the convenience of editing a single file go?
Ah, it was the legacy version of KDL, the current one got rid of this quotation noise
But since you don't have an infinite number of clients, just a few, there is no need for infinite storage
What's your best alternative for this use case?
picky about syntax. I.e.: single word string MUST be quoted.
Seems like the opposite:
Example from kdl website without quotes
package { name my-pkg
Example from scfg with quotes
train "Shinkansen" {
And what do you suggest users do if that function isn't in the program and is unlikely to appear there?
Wish there were a more widespread config system where you could use a wider range of languages and not be limited to a single bad ancient one.
Because you are less limited by all the mistakes the designers encoded in the static files
That seems like a huge waste of time for anything slightly complicated to convert code to simple configs and lose a lot of functionality in the process. Do you have an indication of how prevalent the cycle is in reality?
How would that help if the result of the template is the same single config file that doesn't separate concerns?
And then most of us shut up because the real world is messy
That's rather ironic because you both can't do that with a fantasy of a simplistic world of "first line bad = whole book bad"
more or less likely
In the real messy world the correct answer is "you have no clue" neither when it comes to the whole universe of books nor to the specific subset of books that were accepted for the competition.
But I'm aware of the allure of the simple nature of a fantasy world where there is a very simple way to judge the quality of any art work, and where such quality is necessarily uniform, so a tiny sample is fine.
you are judging the whole thing
That's literally the opposite of what happens, you can't judge the whole thing if you've only read 1 paragraph!
If the first part is bad that puts the book behind every other book.
That makes no sense, you don't know the quality of other books to make that determination! What if they have much worse paragraphs in the middle? What's so special about the first one expect being helpful to the lazy judges?
Think about judging a 3 course meal.
Don't, you just add more irrelevance her
Seems to work close to how I think, would be interesting to know what people actually think instead of relying on what the author thinks people think
why on earth would I continue reading in the hopes that somehow this book will become magically brilliant, brilliant enough to make up for that paragraph and be the winner of this major award? I have 100 other books to get to. I am not a fast reader.
Because that's literally your literaly job?
Thanks, that's what I didn't get from the other discussion, so it seems to be a rather trivial fix - just use the existing language functionality
The example doesn't seem worse, but more importantly - are these issues part of the class (and why)?
You don't need to tell me anything, just look around beyond your "I", other "I"s have seen the issues and reported them for you to see
If you're so out of touch with the average consumer experience, read comments to this post (e.g. a charger turned out to be too powerful for the device/cable, wasn't there supposed to be negotiation baked in?) or any other popular post about usb-c
The labeling is already standard, but since it's an awful standard, we aren't golden
But the benefits far outweigh the glitches. Using my USB-C cable tester, I can be sure all the cables I have can deliver the amount of power my devices need.
You can't be saying the first with a straight face if you then type the second about a specialized hardware testing device that no average consumer will ever use
Tailscale SSH now rejects usernames with leading dashes.
Is the proper fix not restricting users not possible in these poorly designed ancient systems?
Similarly re another issue: why not just fix the permission issues instead of restricting users?
Tailscale now disallows the use of UIDs or numeric-only usernames via SSH to avoid this ambiguity
where the line between “addictive feature” and "good UX" is.
At addiction?
Every 3 months, for the last 1.5 years, I try it out for a few days, really trying to make it part of my workflow but eventually I give up and go back to git.1
That's not really trying, let's assume you need 1 week to change ingrained workflows, so you just waste time every 3 months stopping right before the threshold. Better try once every year, but for a few*4 days...
commit messages while writing the code, will reorganize and clean them up later anyway
That's just too primitive of a workflow, so repeating it will not run into the risk. You need to add an actual conflict in some feature branch and get stuck being forced to resolve it to compete the rebase to appreciate the op warning
For example, every entry that I've read that relates to cybersecurity: grep -E "keywords.*have_read|cyber_security" file.bib
What a primitive way of searching: no real-time feedback, no way to easily correct a typo based on such feedback, no way to act on the results, e.g. edit the found reference right there in the list of results without opening a file (and doing the search again to find the spot?)
No, a useful language can be just as understandable in the far away future, but also way more approachable in the now/near future
We have never heard this before. User can provide details for us, but if others aren’t experiencing it, it’s unlikely to be prioritized. Still, useful signal for us.
That's a common mistake. Since the support is of the level you've experienced yourself
I’ve rarely gotten useful answers from support from services I use.
You should realize that many people don't contact support with their issues, so the fact that you haven't heard about it before doesn't mean much
putting too much time into support isn’t a differentiator
It’s unlikely I’m going to implement the request. If I did, by catering more to persnickety power users
Sure, why would a user care about how much time you put into declining to improve the app for them? How is that a differentiator, almost every single app doesn't cater much to power users
Change the keyboards to silent. Allow headphones. Still beats the collective waste of forcing to hand write