HN user

jablan

492 karma
Posts2
Comments223
View on HN

repeatedly exit a low wattage deep idle state to update the UI

There's a considerable difference in doing that once a second and dozens (hundreds? thousands? depending on how it was implemented) times a second, which I would assume what the previous default ("smooth") setting meant.

Frankly, I think far more performance problems nowadays lie in things like insane SVG/CSS animations for every possible loading spinner than in developers not knowing their O notations.

If I go to the store and there is not paper towels there I don't need to know why there are no towels

You don't _need_ to know, but it's human to want to know, and it's also human to want to satisfy other human's curiosity, especially if it doesn't bring any harm to you.

Also, your post is not really answering any of GP's questions. I presume you wanted to say that FB doesn't _owe_ any explanation to us, but the GP asked, as they already provided one, to whom is it addressed.

Twike 5 years ago

With +3100 pre-orders, expected delivery for new pre-orders is 2023.

Hey, thanks for responding! I know it would take me some more weekends than that! :) Have you documented the process somewhere in greater detail perhaps? I'm working on something relatable on my weekends, also involving PCB design and enclosure design/printing (albeit on a more amateurish level of course), so I'm very curious about other people's experiences.

my_method = Kernel.method(:puts)

That's exactly what being first-class is not. You tell Kernel to wrap you a method called puts into an object of class Method, rather than assigning a method to a variable. You don't have to look further than JS for a counterexample.

Sorry, Ruby methods are not objects. They can surely be wrapped in objects of class Method, but this feature is used quite rarely. Whether this is due to the syntax, the confusion regarding the evaluation scope, or something else, I have no idea.

Yeah, and that's not what first-class usually means. I simply can't say "my_method = Kernel.puts" the same way I can say "my_class = Kernel". Ruby authors seemed to want to make parentheses optional by any price, and that killed the opportunity to make methods first class.

it doesn't really matter

This way can be argued for almost every language, as they almost all allow some form of passing a piece of code to a function. The difference is what matters - whether that's elegant enough to be widely used or not. Ruby is, frankly, somewhere in between.

So it's intentionally distorting sound? Even so, it could be measured and compared, with more complex sound patterns (as opposed to sine waves or whatever is normally used for frequency response).