HN user

rjmorris

89 karma
Posts0
Comments47
View on HN
No posts found.

Can you elaborate on how the two titles mean something different? To my reading, "Here's how they ..." and "How they ..." mean the same thing. "Here's" is unnecessary. (Not saying I agree with HN removing it automatically, just that in this case I don't think it changes the meaning.)

This is specifically not selectlist. "Previously, the Chrome team was working on the idea of a selectlist element. What's described in this post is that feature redesigned to reuse the existing select element instead."

I can say from experience that it doesn't.

No, I don't think you can say that. If you're getting daily notifications about being out of date, then you clearly haven't gotten the update yet. There are two possibilities: (1) You have rebooted. In this case, the dev option must have worked, because you rebooted and didn't get the update, exactly what the dev option promised. (2) You haven't rebooted. In this case, the dev option doesn't apply, because it specifically refers to what happens after you reboot.

Maybe I misunderstood you, but Anduril doesn't include strobe modes on the main cycle, and it lets you configure how many brightness steps you want (or hold for continuous ramping). So it sounds to me like you should want people to check out Anduril, since it addresses the two issues you mentioned with your old flashlights.

The underscore is to avoid conflicts with your own attributes named make, asdict, etc. So you could do:

  MyClass = namedtuple("MyClass", ["make", "asdict", "fields"])
  x = MyClass(make=10, asdict=11, fields=12)
  print(x.asdict)
The "underscore-to-avoid-naming-conflicts" approach is used elsewhere in the Python standard library, too, although another example isn't coming to me at the moment.

Not wild at all if those extra features get in the way and make it harder to do the subset of things you want to do. Those extra features also occupy the developers' attention, leaving less time for them to focus on the things you care about.

Thanks for this great explanation! These do sound like useful reasons for daemon mode. My workflow is pretty different, so some of these wouldn't apply to me, but it does give me a lot to think about plus some potential workflow tweaks.

The multiple daemon approach is intriguing. I don't think I've run across anyone discussing that before, although a quick search turns up a few posts/threads that I've missed.

Thanks for this, I found a few things to investigate adding to my own config.

I have a question about the server/client mode:

Experienced Emacs users run a single instance of Emacs and do all their editing activities via this single instance.

What's the motivation for running it this way? I think the repo should explain why, especially since it's targeted at newbies. Also because it looks like a lot of effort was put into explaining how and discussing the em script that makes it more convenient.

For what it's worth, I'm an experienced Emacs user, and I don't run a single instance. Instead, I start lots of new instances. As best I can tell, the motivating factor for a single instance is startup speed. However, I'm satisfied with my startup speed and haven't felt the need to improve it with server/client mode.

Bouba/Kiki Effect 5 years ago

I'm guessing because you misunderstood the question. The question in the research was something like, "Which one of these shapes is called 'bouba' and which is called 'kiki'?" There was no option to invent your own word.

My concern with this approach is that it gives the impression that you can use all the same switches that are available to the real shell commands, which isn't the case. For example, taking the first command documented on the README, cat, shelljs supports the -n switch only, but `man cat` shows about 10 switches for me. So although I agree that the learning curve is lower to get started, you do have to remember that the switches are limited and be sure to check the docs to see which of your shell command switches are supported.

I'm pretty sure sh just runs the commands in a subprocess using the shell, so it isn't like shelljs at all. From the linked page:

"Note that these aren’t Python functions, these are running the binary commands on your system by dynamically resolving your $PATH, much like Bash does, and then wrapping the binary in a function. In this way, all the programs on your system are easily available to you from within Python."