But 3D printers are more useful for making enclosures to said circuit boards, not for fabbing them.
Made brackets for the power-supply to my CNC mill so that it conveniently hangs off the side of the workbench but can be quickly removed for transport.
In same workshop, a cheap 8-port switch I bought for it turned out to not have wall-mount keystone holes. So made some clips which screw into the side of the bench and hook into the vent slots of the switch to brace it.
The most useful things for it tend to be the most pedestrian. Though my other use is for enclosures for custom electronics projects, which is also extremely useful.
I'm 'guilty' of leaving the kids (9 and 11) to read in the car if I know I'll only be in a store for less than ten minutes. But even lately I've limited that to things like a quick pop-in at the drug store, since it seem more likely people would overreact to seeing a child in a car at the grocery store, where the average time the child would be left along is much higher. That I even have to worry about that is just crazy.
The problem with bring authorities into a situation is that they are a very blunt instrument. They are not going to care that I actually am being mindful about evaluating (the usually miniscule to begin with) risks involved. For example:
- If it's too hot, they stay with me.
- If I think there's a chance I might get hung up past 5-10 minutes, they stay with me
- If it's both of them, I'll often apply stricter standards, since the biggest risk is them getting into fight. And the biggest risk with a fight is them causing undue attention to the fact that there are alone in the car.
Ironically, this sort of unnecessary heightened vigilance leads parents to make potentially riskier decisions, if that decision is less likely to come under public scrutiny. For example, if I'm the only parent covering after school, sometimes one or the other has to be picked up, or I have to run out for some other reason. If it's less than 30 minutes, and the child's time would be better spent finishing homework than being stuck in the car, then I'll consider leaving them home. Fortunately they have good judgement, as the hazards in the home far outweigh that of being in a car.
And even then, I'll almost never do that if it means leaving them both alone, as the sibling rivalry factor raises the other risks by several orders of magnitude.
So some stranger's knee-jerk reaction to something that has actually had some thought applied to it poses a greater risk to the welfare of the child than whatever it is they think they are saving them from.
Short of the too-small screen, it performs admirably. And the size/weight/battery-life has a lot going for it. I recently was spending day-long sessions on a deployment site upgrading firmware to over a hundred embedded devices. The two other guys had Dells, which crapped out by lunch (why they didn't bring a spare battery is beyond me, but whatever), whereas my Air cooked along all day. And was way less fatiguing to carry around from station to station.
So these aren't necessarily status symbols for light workloads. They are capable of real work.
It is a valid catalogue entry, the comments are hilarious tho.
Dammit! I can only imagine what my "Recommended for you" list is going to look like for the next month...
I went to college on the east coast and spent plenty of time in NYC and the folks from NYC were among the most parochial people I've ever met.
Yeah, no kidding. Unexpectedly spent three years there and was amazed at the juxtaposition of metropolitan and provincial. Our next stop (RI) outdid NYC in terms of provincial, just without being as metropolitan.
You woke up and discovered you had installed Windows 2000?
Scary what one can accomplish while on Ambien and not remember a thing the next morning.
> You mean.... gasp!
In terms of the larger systems that it is integrated with, that is EXACTLY what it is. It is a highly specialized application that does one thing well and leaves the scope creep for other programs that consume it's services.
It may even be broken down into a lot of highly specialized background processes like Oracle.
Well, ok, a database server isn't a great example. Because a database server is essentially an API exposed for the purpose of being consumed by other applications. This is nothing specific to Unix, since database servers work more or less the same way on other OS's.
But my point was that often-touted killer design feature of Unix (take a bunch of little specialized programs, add pipes, mix well, and bake in a 350F oven) isn't really how complex programs are designed. On that point Torvalds is spot-on.
There's still value in understanding the traditional UNIX "do one thing and do it well" model where many workflows can be done as a pipeline of simple tools each adding their own value, but let's face it, it's not how complex systems really work, and it's not how major applications have been working or been designed for a long time. It's a useful simplification, and it's still true at some level, but I think it's also clear that it doesn't really describe most of reality.
You mean.... gasp!
Seriously though, and without belittling the value of the bunch 'o pipelined commands (especially for sysadmins), it's nice to hear someone clearly and concisely articulate this rather obvious reality.
Hey, just because you don't know the language doesn't mean it's necessarily wrong.
And just because you do know the language doesn't mean it's necessarily right!