HN user

casion

1,362 karma
Posts1
Comments332
View on HN

They make sense for sound designers and derivative artists (e.g. sampling, which is a real artform).

Forms of manipulation bring inaudible content into the audible range.

Of course that doesn't mean audiophiles aren't being audiofooled by it, but there is legitimate usage.

You've created problems that don't exist. They're concerns that most people don't have.

You don't know what to say. That's fine.

You might be wasting their time. That's fine.

You might not know how to end the conversation. That's fine.

It's ok to be awkward. It's ok to be honest. It's ok to bother people as long as you take their feedback appropriately. It's ok to walk away without saying anything.

The more often that you talk to people and actively reflect on the REAL outcomes of it, the sooner you'll realize those concerns aren't shared by most other people.

There's more clojure users than ever before and the team is active and afaik larger than ever before.

Things just mature and hype isn't as cool when you heard it 5 years ago.

It's a total nonstarter for me. Bring unsure that I can find a working charging station, and have to go out if my way to take that risk sucks.

I've rented quite a few EVs long term and if you have to travel 200+ mile trips even 5% of the time they incite terrifying range anxiety in some (most) parts of the country (US).

If you are always or very nearly always under 100 miles a day, they're fine. Most _people_ live in that realm, but most _areas_ in the US are full of people who do not.

Yes, and like most language features it's not about the feature, it's about having _that feature_ in a language with other benefits.

Think generics in Go or concurrency (effects) in OCAML or smart pointers in Rust. Not at all unique things, but having them in the language with other benefits is worth some discussion as it may provide extra leverage in context.

To give a shallow overview, transducers allow you to define steps in collection processing _per item_ rather than having collection processing as a series of transformations of collections.

So rather than processing the collection, passing it to the next function that processes the collection, passing it to the next... etc.. consuming all the CPU and memory that involves, you can define steps that are applied for each item in the collection thereby having the iteration through the collection happen once.

These steps (transducers) are also composable and reusable.

I suspect you know this, consider this a basic explanation for other people reading.

Untouchable number 3 years ago

There's only one sum of all the proper divisors for any given integer.

This really seems to assume that uniqueness is an implicit property of each integer of such sums. I don't understand how you would know know that or how to discover that other than "you couldn't get the answers we're showing you unless you assumed that".

Untouchable number 3 years ago

In particular the set does not allow for repetition (you cannot count a proper divisor twice).

How would I know this having read the description/definition?

I checked multiple definitions for proper divisor and untouchable number before I wrote my post and I could not find anything explicit.

Thank you for the explanation btw. Still a bit hung up on how I could have figured that myself given the information presented.

Untouchable number 3 years ago

Could someone explain this better? The definition in the wiki page appears to be leaving out some information that makes it necessary to understand.

Why is 2 + 2 + 1 = 5 not sufficient? It doesn't say unique proper divisors. The definition of proper divisors doesn't seem to explain either.

i.e. why is 10 not an untouchable number but 5 is?

Specifically given the precise definition given, anything should be touchable as 1 is a proper divisor, and you can sum any number of 1s to "touch" a number. Clearly we're missing some implicit restriction.

For some people it is. A tropical storm doesn't even shut down schools here.

Some folks are being ignorant and dismissive with "just", and some are relating their personal experiences.

I have caught myself saying "just 2 inches of rain" since we get that frequently, sometimes in an hour or two. For many people that is a dangerous and life changing amount of rain... and that can be easy to forget if it isn't for you.

tldr; hanlon's razor

This book was written before Clojure was released as 1.0. (1.0 and Programming Clojure were released together!) Stu and Rich worked closely at that point. The process of writing the book and Stu were influential on Clojure.

If you want to make your project more open to contribution

This is a key point, and assuming this in the positive is often a mistake. Not all projects want, or can handle, increased contribution.

No matter your size, all of those things violate safety. It's not always about being attacked, but general welfare being violated.

Datomic is Free 3 years ago

Heavily according to people who work there. They appears to be a conj talk about it today.

Datomic is Free 3 years ago

Maven actually has a tutorial on publishing binaries without source. So I assume it's ok when they tell you how to do it.

Because they are the best quality, in every dimension, and when something is almost purely a hobby then many people are willing to pay a premium for a friction-free experience.

There are other brands that are just fine, but you will occasionally get missing pieces, poor fitment, poor/strange construction etc... With LEGO you'll not get any of those (except the occasional strange construction).

I used to buy ~50/50 LEGO/Clone, and despite improvements in clones, it's 95/5 now. The LEGO experience is simply disproportionately better relative to the cost.

It's simply worth it.

signed, Owner of A LOT of of LEGO kits/bricks _and_ clones.