- Oct 2022
-
store.steampowered.com store.steampowered.com
-
a little flaw (Google translation can not find the translation of the word "瑕疵", so can only use the word "flaw" instead)
annotation meta: may need new tag: no exact translation in other language
-
-
raku.org raku.org
-
Definable grammars for pattern matching and generalized string processing
annotation meta: may need new tag: "definable __"?
-
-
openvalidation.io openvalidation.io
-
Machines understand languages, that are formal and rigid, with unique and unambiguous instructions that are interpreted in precisely one way. Those formal, abstract languages, and programming languages in general, are hard to understand for humans like ourselves. Primarily, they are tailored towards the requirements of the machine. The user is therefore forced to adapt to the complexity of the formal language.
.
-
- May 2022
-
Local file Local file
-
To manage this new capacity, we switched from ad-hoc project lengths to repeating cycles. (It took some experimentation to find the right cycle length: six weeks. More on that later.)
We formalized our pitching and betting processes.
My role shifted again, from design and product management to product strategy.
I needed new language, like the word "shaping", to describe the up-front design work we did to set boudaries and reduce risks on projects before we committed them to teams.
-
- Jan 2022
-
thejollyteapot.com thejollyteapot.com
-
- Jun 2021
-
stackoverflow.com stackoverflow.com
-
Programmers should be encouraged to understand what is correct, why it is correct, and then propagate.
new tag?:
- understand why it is correct
Tags
- programming: understand the language, don't fear it
- good advice
- annotation meta: may need new tag
- quotable
- programming languages: learning/understanding the subtleties
- having a deep understanding of something
- spreading/propagating good ideas
- combating widespread incorrectness/misconception by consistently doing it correctly
Annotators
URL
-
- Oct 2020
-
facebook.github.io facebook.github.io
-
Why not just use that instead of inventing a syntax that's not part of ECMAScript?
-
- Sep 2020
-
github.com github.com
-
One of the arguments that's frequently deployed in favour of JSX-based frameworks over template-based ones is that JSX allows you to use existing language constructs:
-
-
github.com github.com
-
Proposes a syntax similar to JSX.
My question would instead be, why not just use JSX for Svelte templates?
-
- Jun 2020
-
stackoverflow.com stackoverflow.com
-
What would be nice is if JavaScript had a built-in way to do what I can do in Ruby with:
> I18n.interpolate('Hi, %{name}', name: 'Fred') => "Hi, Fred"But to be fair, I18n comes from i18n library, so JS could just as easily (and I'm sure does) have a library that does the same thing.
Update: Actually, you can do this in plain Ruby (so why do we even need
I18n.interpolate?):main > "Hi, %{name}" % {name: 'Fred'} => "Hi, Fred"main > ? String#% From: string.c (C Method): Owner: String Visibility: public Signature: %(arg1) Number of lines: 9 Format---Uses str as a format specification, and returns the result of applying it to arg. If the format specification contains more than one substitution, then arg must be an Array or Hash containing the values to be substituted. See Kernel::sprintf for details of the format string. "%05d" % 123 #=> "00123" "%-5s: %016x" % [ "ID", self.object_id ] #=> "ID : 00002b054ec93168" "foo = %{foo}" % { :foo => 'bar' } #=> "foo = bar"I guess that built-in version is fine for simple cases. You only need to use
I18n.translateif you need its more advanced features likeI18n.config.missing_interpolation_argument_handler.
-
-
-
clean and understandable markup template without the help of 3rd party
-
-
medium.com medium.com
-
I really do not like writing templates in a file, such as #each , #if. I do not like to prefer using new approaches for which i can do it with purely in JavaScript.
-