Why does Ruby make Asciidoctor horrible to work with?
HN user
arunix
And at the end of that Bob says:
For my part I'll just say that I have given due consideration to the points you've made, and while I disagree with your conclusions above, I have integrated several of your better ideas, as well as this entire document, into the second edition of Clean Code.
I agree that the prime list example is really a constructive proof. But what about the sqrt(2) and log(2) examples?
Can you say more about those bugs?
Right at the end of the article:
Why not release the belugas into the ocean?
It's geopolitically difficult to return many belugas to their native waters, because many come from Russia, Lott said.
Sending the Marineland belugas into the wild would have been "inhumane," Trites said. At least half of the animals were born into captivity, so they don't know how to hunt and wouldn't be accepted by the local beluga population.
"The animals are so social that they can't survive on their own," he said.
Which VPS?
Are there any books you'd recommend that get it right?
Is the lack of cons cells a significant limitation?
Altair looks closer than Alpha-Centauri on this map, although it's actually 4 times as far (probably Z axis squashing).
Cantor is mentioned, but I'd also mention the idea that some infinities are equivalent (e.g. Integers and Rationals), but others are not (Rationals and Real numbers).
Does StorX have any special handling of concurrent writes, or would the user need to take care of that?
Thanks. Can you say more about why TypeScript with Deno is your scripting language of choice?
TNG introduced various civilisations that drive much of the plot in DS9.
Season 1: Ferengi
Season 4: Trill, Cardassians
Season 5: Bajorans
Also, Chief O'Brien and his wife Keiko who were recurring minor characters in TNG have more important roles in DS9.
I remember in a previous job having to enable git rerere, otherwise it wouldn't remember previously resolved conflicts.
Do you remember which video that was?
Do you mean local variables per se, or mutable local variables? Clojure, like most Lisps has let.
Recently, I wondered what would happen if two of these systems were set up doing mutual pair programming ...
What does "slow to iterate on" mean?
Is there something about .NET that makes this easier?
Can you say more about how it's better than both?
What are the IntelliJ alternatives you prefer?
Also, the Query Object style, e.g. JOOQ and SQLAlchemy Core
How much do you pay for Gemini 2.5 Pro?
I didn't understand the vampire thing. That seemed like the least realistic part of the story.
Could you add a diagram showing how castling works in this?
What's the difference between Japan and developed?
That syntax suggests the first pair will be flipped, and the rest will just be as they were, i.e. more like flip_first
Consider
% perl -v | head -2
This is perl 5, version 40, subversion 0 (v5.40.0) built for x86_64-linux
%
% perl -E 'use feature "switch"; my ($x, $y); given ($x) { $y = 1 when /^abc/ }'
given is deprecated at -e line 1.
when is deprecated at -e line 1.
This is also mentioned in the docs: Smartmatch is now seen as a failed experiment and was marked as deprecated in Perl 5.37.10.
This includes the when and given keywords, as well as the smartmatch operator ~~.
The feature will be removed entirely in the Perl 5.42.0 production release.
https://perldoc.perl.org/perldeprecation#Smartmatch> In python you can't tell whats a variable and whats a list, and whats a dictionary by looking.
In Perl, sigils are used to distinguish between scalars/lists/hashes. Sigils and references are not the same thing.
The key idea in CLOS is multi method dispatch, which Moose does not provide.
Moose out of the box has its own set of problems, leading to other workarounds, e.g.
Moo (a similar but much less bloated solution)
MooseX::Extended - Moose with more sensible/correct defaults
https://metacpan.org/dist/MooseX-Extended/view/lib/MooseX/Ex...
OO in Perl is lower level compared to Java or C++, so e.g. instead of having a class construct, you have to simulate a class - typically by binding (blessing) a data structure to a namespace. Then any functions in the namespace become methods that can be called via the data structure (object).
In practice, this has turned out to be a mixed blessing because of how tedious it is to do this repeatedly. So over the years there have been many libraries created to make this easier, each with different features.
There's currently work underway to modernise Perl's built in OO to address these problems.
On the other hand, this makes some things easier, e.g. Design by Contract can be added to Perl just by writing a library.
Another example, adding traits to PHP required updating PHP itself, whereas in Perl there are libraries to do that.