Builder is extremely useful to pair with a parser, e.g. SAX. The parser parses the input, and the builder then decides what to do with it.
9,295 karma · joined August 21, 2009
Builder is extremely useful to pair with a parser, e.g. SAX. The parser parses the input, and the builder then decides what to do with it.
Yes, but what about factory factories? https://factoryfactoryfactory.net
And if you ever find yourself actually doing command line parsing, use getopt(). It handles all the corner cases reliably, and consistent with other tools.
The initial edition was published in 1976, in German, but the latest version is available online:
https://people.inf.ethz.ch/wirth/CompilerConstruction/Compil...
There are also parser generators like ANTLR (https://en.wikipedia.org/wiki/ANTLR) which take an input not unlike yacc, but generate a LL parser using explicit code, rather than the table driven LALR parsing of yacc.
And those are really the core use cases for AirPods, HomePods, and CarPlay, the contexts where a hands-free eyes-free interface is most useful.
It sort of makes sense that villains would employ villanelles.
But I don't think it's implemented widely, if anywhere.
I assume GP's point was that assembly language literacy was a pointless skill nowadays. I found it quite useful, precisely because it's no longer an ubiquitous skill, so you can shine with your expertise in some situations.
The worst earthquake that was induced that way was 3.5, but given that one of the quakes happened in an area that had a catastrophic earthquake in the Middle Ages, some caution might be warranted: https://en.wikipedia.org/wiki/1356_Basel_earthquake
Anthropologically, I've heard that cultural acceptance of staring at people is inversely correlated with amount of clothing worn, i.e. in cultures where people habitually live unclothed, it's considered rude to look at others' bodies.
Of course, I'm old and fat, so I have good reasons for not fearing people being sexually attracted to me…
But "The customer experience was all-important" is a bit reductionist. The hockey puck mouse stuck around for years after it became clear it was a poor customer experience. And I have cursed desktop Macs countless times for having all their ports in the back, because Jobs disliked seeing them, customer experience be damned.
But my primary takeaway was that this is hard & dirty work, and there are numerous ways in which you can make mistakes that ruin the car and/or endanger your safety, so generally paying a professional to do it is a more sensible way.
Of course, if you enjoy doing this, or have a very old car, or more time than money, the trade-offs are different.
And systemd already follows Microsoft best practices, such as "Fire and Motion" https://www.joelonsoftware.com/2002/01/06/fire-and-motion/
I'm pretty sure factory work was a step upward for these families.
Apple definitely had programs to pay all or part of relevant educational programs, and they sometimes paid for people to attend conferences. I'm sure it was much more restrictive than the HP policy you're describing here, but it was definitely more than nothing.
What really set apart the Apple II from many of its peers is that it came preassembled, in a neatly designed case (though the Commodore PET and TRS-80 were pretty much released at the same time), and those esthetics were due more to Jobs than Wozniak.
Jobs did not write product code, or design boards, but he had a constant presence in the design of Apple's products and many (though by no means all) of his inputs changed the products for the better.