6,769 karma · joined February 21, 2011
If you have a sparse matrix of nouns and verbs where cells show whether a given verb(noun) pairing is valid, indexing by noun is clearly more efficient, because most of the time you know exactly what you're operating on, but not necessarily what the operation you want is named. The variables are likely right there before your eyes, a couple lines above the cursor, but the functions are spread out all over the code base.
It seems wild to me when people basically shoot themselves in the foot by going "tl;dr", but also if you're the author, it's up to you to present your message in a easily comprehensible form - nobody owes you their time and attention, it has to be earned.
(FWIW, this site doesn't allow downvoting direct replies to one's posts, so it wasn't me who downvoted (nor flagged) your sibling comment.)
http://www.espn.com/nba/attendance/_/year/2019/sort/homePct
Edit: I can't find the numbers for courtside attendance, but it's possible that ticket income for the teams at the bottom of that list is either lower or higher than the overall % suggests, depending on how in-demand the highest priced tickets are.
A modern solution for this use case would be a custom website or a mobile app. Now, even if you disregard for a moment the cost of developing/running/maintaining those things, the UX and reliability of paper and pencil for this use case is far superior to mucking around on your phone or PC.
Plain 15 is trickier. GitHub's search is too fuzzy to see a pattern at a quick glance, but again it seems that JavaScript is the culprit with a disproportionately high number of filename:15 results compared to filename:14 or filename:16.
> Unsound, inconsistent, overly complicated, poorly abstracted, improper paradigms
apply to the current stable version of Scala as well. You'd be comparing Typescript as it is in production right now to a best case scenario of where Scala could end up in a couple years.
`Mappable` provides short-term comfort due to familiarity, but to do so it sacrifices precision that is essential in the long term.
1) Are there domains where naming things is easier? Perhaps even trivial? As a layman in both, biology and astronomy come to mind. Where you just find a Latin word vaguely describing what you see, and if nothing comes up you just pick a name of a famous person from your field that doesn't already have something named after them.
2) If non-English languages are also considered, are there any where naming things is easier? Have to keep in mind that a "good" name maintains a balance between descriptiveness and brevity.
3) Can this be considered as an advantage of point-free style?
4) Is naming things in programming hard as in "building a spaceship" or as in "making the NBA"? That is, can you name all the things if you put in enough effort, or are some things simply unnameable?
If not, please update Wikipedia with references to your original source of information.
(Wikipedia doesn't admit original research.)
Success = means * motive * opportunity.
I feel like Randall Munroe is doing well for himself. The math is probably different for smaller players.
As far as Julia criticisms go, the Dan Luu post felt like it focused more on the right things (https://danluu.com/julialang/, circa late 2014). Of the two, that's the one I'd like to see a follow-up for.
Annatar, both the Rust compiler and ripgrep are available as packages in pkgsrc. The number of hoops one needs to jump in order to use this tool on your niche platform is exactly one. And that hoop is not even on fire.
Keep moving those goal posts though. Hopefully you can move them far enough to keep the Venn diagram of your mistruths and people who recognize them completely disjoint.