hhas01

48 ms·

331.
by hhas01 7y ago
It’s a broad church, long as they know to how to add dollar bills to the right palms.
332.
by hhas01 7y ago
You mean students making religious statements like “2π = 6”? Yeah that’s definitely not right, the correct solution of course being “Burn the mathematician^W witch!”
333.
by hhas01 7y ago
Disappointing, but unsurprising. See also: Greenspun’s Tenth Rule, “Yo Dawg…”.
334.
by hhas01 7y ago
Skimming the WDL “Quick Start Guide” ( https://software.broadinstitute.org/wdl/documentation/quicks... ) to get an overview, it’s like watching a snake eat its tail. You’d think a narrative in this problem space wou
335.
by hhas01 7y ago
“we seem to be talking about "Scientific Computing Workflow" or some sort of data pipeline” So, more along the lines of https://en.wikipedia.org/wiki/Dataflow_programming . A good problem space to bring declar
336.
by hhas01 7y ago
Those who can, implement solutions. Those who can’t, implement Standards.
337.
by hhas01 7y ago
Perhaps a wiser phrasing would be “a language’s interface should be simple enough that the programmer should be able to know everything about it”. (Counterpoint: C++ syntax and semantics.) The internal implementation can (and usually will
338.
by hhas01 7y ago
The article’s title is itself nonsense: the `imperative <> declarative` disjoint alone means it’s logically impossible for a single language ever to satisfy all programming needs; and that’s even before you start decomposing them into
339.
by hhas01 7y ago
The article’s title says “ perfect programming language”. “Impure” means the language design is by definition compromised. The moment you allow imperative behaviors to leak into a declarative system it loses its ability to reason reliably
340.
by hhas01 7y ago
“You get to set mWordClockTime as part of the init” While I’ve never had the pleasure of dealing with Core Audio, I’m getting the strongest impression that our problem is not that its API documentation is inadequate, but that its API was de
341.
by hhas01 7y ago
Aye, I’m well aware what can go wrong when an integer overflow occurs. My point was the way Apple presumably[1] uses this particular Uint64 precludes such an event ever occurring within macOS’s lifetime, therefore there’s no need to explain
342.
by hhas01 7y ago
Even if it counts in picoseconds it’ll take several centuries to roll-over, so these probably aren’t questions you ever need to ask. Though that’s kind of the point: the API and its documentation should highlight the stuff you need to worry
343.
by hhas01 7y ago
Link to article on a GDPR-compliant site: https://baltimore.cbslocal.com/2019/11/08/maryland-medical-c...
344.
by hhas01 7y ago
The true beauty of Logo comes in the realization that you can add your own words to it, and that all these specialist words you devise are themselves first-class citizens of the language, of syntax and status equal to its generic builtins.
345.
by hhas01 7y ago
Businesses gonna business. Can’t really blame them for exploiting the artificial bottlenecks created by the lazy thoughtless corner-cutting geeks who (ostensibly) designed the thing. To copy-paste myself ( https://news.ycombinator
346.
by hhas01 7y ago
#ISWYDT
347.
by hhas01 7y ago
My software shits itself all the time. What matters is that it does so safely . And when it doesn’t, I can tell you why, because I know what corners have been cut and why, and I’m not afraid to accept and acknowledge my responsibilities in
348.
by hhas01 7y ago
“We occasionally roll out bad software.” Honestly, as a profession we very rarely roll out anything else. It’s one of the reasons we should be designing systems and procedures that are fault-tolerant from the very start. In this particular
349.
by hhas01 7y ago
Except client A never crashed when receiving data from server A. You can rightly argue that client A was irresponsible in not protecting itself more intelligently against invalid or unexpected inputs (dumping core is the crudest, bluntest p
350.
by hhas01 7y ago
“roll back first, ask questions later” Better yet: build code and processes appropriate for long-lived massively distributed systems that will be incrementally upgraded over time. If the system is architected right, it will never get into a
351.
by hhas01 7y ago
“But math is also very difficult to understand.” Sure it is, if you’re not a professional mathematician. For those who are , it is a fabulously precise concise system of communication. The same can be said for “legalese”, “medicalese”, o
352.
by hhas01 7y ago
Presented without further comment: https://image.slidesharecdn.com/tceacsimperative-15072621371...
353.
by hhas01 7y ago
Not for those who professionally speak Mathematics; which is the audience APL was made to serve, after all. Amusing so many programmers will complain how they feel horribly excluded by APL, but see no issue with every other programming lang
354.
by hhas01 7y ago
HTTP hyperlinks FTF. Vannevar Bush hypothesized much a higher-level “mesh of associative trails”, with relationships formed directly and largely automatically. The closest today’s WWW has gotten to this is search engines, but again these ar
355.
by hhas01 7y ago
So what you’re proposing is to increase the period in which unprotected infants may be exposed to dangerous diseases, just to pander to a bunch of noisy know-nothing narcissists? The CDC et al already tried placating those malevolent turds
356.
by hhas01 7y ago
Well isn’t that fortunate, seeing as aluminium is only the third most common element in the Earth’s crust and so everywhere you go you’re already exposed to it every day of your life; in the food you eat, in the dust you breathe, in the cut
357.
by hhas01 7y ago
Except that antivaxxers proselytize , vastyly increasing the likelihood of crippling or killing their own unvaccinated crotch-spawn far beyond the ~one-in-a-million risk of injury inherent in vaccination. Sorry, but anti-vax is not an exer
358.
by hhas01 7y ago
Aluminium is a “heavy metal”? Delete your account, you scientific illiterate.
359.
by hhas01 7y ago
Query builders != ORMs. A query builder carefully preserves the underlying relational and RPC semantics and exposes all of that to the user in an easier-to-use form. That’s just good cautious modest abstraction. An ORM believes it knows w
360.
by hhas01 7y ago
JXA, like Scripting Bridge before it, was shipped crippled and buggy and abandoned once it was out the door. Apple finally disbanded the Mac Automation team and fired the PM responsible a couple years ago. In fact, there are several product

More ›