Dawn dweud: A study of colloquial and idiomatic welsh Ceri M. P. Jones

Compared with simple clients, modern clients are generally much easier to use and more Ruby-like

t is in Tyndale’s Bible that we first find the name “Passover” for the holiday Jews call Pesach; it was he who coined the word “scapegoat”; and many biblical verses that are now idiomatic in English are his own translation – notably, “my brother’s keeper,” “the powers that be,” “the salt of the earth,” among many others.

Well-thought-out, idiomatic APIs

You just blew my mind Marc-André. My code just went from idiotic to idiomatic.

Chapter 13 investigates two- and four-bar idiomatic jazz progressions. It also focuses onaural identification and keyboard realization of non-modulatory and modulatoryprogressions with various ii7–V7 or ii≤57–V7 interpolations, as well as miscellaneous four-bar phrases

The French also have the expression la bouche en cul de poule, which literally means “to have a chicken’s ass for a mouth,” but idiomatically indicates that someone has put on a honeyed or fawning look, puckering his lips or not, in the hopes of getting what he wants.

For example, whereas C programmers have argued for years about where to put their brackets, and whether code should be indented with tabs or spaces, both Rust and Go eliminate such issues completely by using a standard formatting tool (gofmt for Go, rustfmt for Rust) which rewrites your code automatically using the canonical style. It’s not that this particular style is so wonderful in itself: it’s the standardisation which Rust and Go programmers appreciate.

Emit clean, idiomatic, recognizable JavaScript code.

But what's the matter with "raw" instance variables? They are internal to your instance; the only code that will call them by name is code inside pancake.rb which is all yours. The fact that they start with @, which I assume made you say "blech", is what makes them private. Think of @ as shorthand for private if you like.

Setting an instance variable by going through a setter is good practice, and using two access modifiers is the way to accomplish that for a read-only instance variable

I don't think it is too clever. I think it solves the problem idiomatically. I.e., it uses reduce, which is exactly correct. Programmers should be encouraged to understand what is correct, why it is correct, and then propagate. For a trivial operation like average, true, one doesn't need to be "clever". But by understanding what "reduce" is for a trivial case, one can then start applying it to much more complex problems. upvote.

Thanks, this was just what I was looking for! This is a perfect appropriate use of instance_eval. I do not understand the nay-sayers. If you already have your array in a variable, then sure, a.reduce(:+) / a.size.to_f is pretty reasonable. But if you want to "in line" find the mean of an array literal or an array that is returned from a function/expression — without duplicating the entire expression ([0,4,8].reduce(:+) / [0,4,8].length.to_f, for example, is abhorrent) or being required to assign to a local, then instance_eval option is a beautiful, elegant, idiomatic solution!!

Popper for Svelte with actions, no wrapper components or component bindings required! Other Popper libraries for Svelte (including the official @popperjs/svelte library) use a wrapper component that takes the required DOM elements as props. Not only does this require multiple bind:this, you also have to pollute your script tag with multiple DOM references. We can do better with Svelte actions!

The problem is that not all tooling supports adding new dependencies from a transform. The first step is figuring out how this can be done idiomatically in the current ecosystem.

it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.

Our custom useEffect is not idiomatic Svelte.

We want to improve this while keeping both the API and the semantics and behavior as Reactish as possible.

this is a common Svelte idiom for manually invalidating something that might have been mutated without there being a visible = sign somewhere

I don't understand why it just launches the mutation once and then it throws the error Function called outside component initialization, the only way to make it work is to do something like $: result = mutation(...) but it doesn't make sense, I don't want to run the mutation after each keystroke.

We’re still working on idiomatic Svelte APIs so this one’s also on our list to figure out what the best way forward is

“I came to Rust from Haskell, and I feel that Haskell is a very elegant and safe language. The biggest differentiator for me is that there is a greater difference between high-performance code and idiomatic ‘clean’ code in Haskell than in Rust. Most Rust code looks like most other Rust code, even when it performs well. Haskell can become unfamiliar real quick if someone is operating under different libraries and goals from what you are typically doing. Small differences in syntax can result in huge differences in behavior, and Rust has more uniformity on that axis.”

whenever there's a lot going on, computers (but mostly humans) will get stuff wrong. In the 6 lines of our component, rendering 2 node types, we change syntaxes from JS to JSX, and back, 8 times! Count them - it's like JS(JSX(JS(JSX(JS))))! This is not the simplest code we can write.