Live data from Hacker News

My Business Card Runs Linux

thirtythreeforty.net

311–320 of 415 posts

Re: My Business Card Runs Linux

#311

Earlier quoted context omitted.

True. This is what i dislike about the "market". There is no reward for knowledge, hardwork, solving complex problems etc. Just "commoditization" and "supply and demand dynamics".

The five following are the principal circumstances which, so far as I have been able to observe, make up for a small pecuniary gain in some employments, and counterbalance a great one in others: first, the agreeableness or disagreeableness of the employments themselves; secondly, the easiness and cheapness, or the difficulty and expense of learning them; thirdly, the constancy or inconstancy of employment in them; fo…

Nice! However your last two paras are a little too succinct; can you elaborate a little bit more?

Re: My Business Card Runs Linux

#312
post #282

Earlier quoted context omitted.

Hah, you had it great! My first PC was a 286, which IIRC either had no HDD, OR. 20MB HDD (might be mixing it with our next PC, which was a 386). I'm pushing 40, and still shake my head in wonder sometimes about just how much is possible at such small scale and cost. But this is now turning into "when I were a lad..." :)

Oh, you kids! My XT had an 8088 @ ~4mhz in it, and we pushed it uphill to school both ways, in the snow! It was multi-functional though. The power supply was inefficient enough to heat the room, while simultaneously being heavy enough to bludgeon large creatures for sustenance. Something inside me misses the radiant heat, sitting here on a cold day with my chilly metallic laptop.

Start a few Electron apps and it'll warm right up

Re: My Business Card Runs Linux

#313
post #305

Earlier quoted context omitted.

My Heathkit H89 had a Z80, 16K of RAM and a built in cassette interface. And we liked it.

I just flipped a bank of 16 switches by hand with vacuum tube gates and core memory...punch cards are for sissies!

You had a computer? Back then I wrote C programs on paper, then executed them by hand...

Re: My Business Card Runs Linux

#314
post #305

Earlier quoted context omitted.

My Heathkit H89 had a Z80, 16K of RAM and a built in cassette interface. And we liked it.

I just flipped a bank of 16 switches by hand with vacuum tube gates and core memory...punch cards are for sissies!

oh kids! i used to crank the wheel by hand on my analytical engine that my hacker friends and me built after there was a leak of babbage's plans! he never knew!

you kids and you petabytes of ram! back in my day....

/s

(i'm looking forward for these comments to be commented on a certain website i'm not supposed to name)

Re: My Business Card Runs Linux

#315
post #172

Earlier quoted context omitted.

Calling this embedded system feels like insult to the spirit of 'running light without overbyte', because it's so comically capable. My first PC had 66/33 MHz 80486 processor and 8 MB ram, 320 MB HDD. You could run AutoCAD, play Doom, Civilization, have dual boot for Linux, Windows 3.11 etc. It could compile Linux from source.

Oh geez I can't imagine how long it would take to compile Linux on that slow of a processor.

depending on how you configure your kernel and what storage you're using, it might be doable.

Re: My Business Card Runs Linux

#316
post #172

To me it's truly mind-bogging that a tiny $1.42 chip contains almost everything needed to boot Linux: a 500mhz cpu, 32MB SDRAM, 2D GPU, SD/MMC support, and USB controller, all packaged inside a 10mm x 10mm chip? It makes me really want to get into embedded development.

Calling this embedded system feels like insult to the spirit of 'running light without overbyte', because it's so comically capable. My first PC had 66/33 MHz 80486 processor and 8 MB ram, 320 MB HDD. You could run AutoCAD, play Doom, Civilization, have dual boot for Linux, Windows 3.11 etc. It could compile Linux from source.

My first few PCs weren't even PCs, I didn't know what they were until I was a little bit older. Somehow I intuited them naturally though; I liked exploring and being curious about what I was looking at.

First one I remember was a Commodore 64, along with a 600 page book full of BASIC that you could type out and record on cassette to have your own game. The book was total gibberish to anyone else; it was just pure code with no explanation. But that's what the C64 gave you; an interactive environment on boot where you could program a new game and write it to a cassette. By default. If you wanted to play a game you had to type `RUN` or maybe one or two other things to set it up. But you wouldn't know that, because you just had an interpreter on a basic blue and white screen.

Worst bit was the 10 minutes of spasmodic strobe animations that showed you the game was loading. But also each game controlled those loading animations. You had to know what game you wanted to play, and be sure of it, or otherwise you could just flip to the B-side and get a different game.

After that I think we had a BBC Micro at school but I'm not sure. All I remember is an adventure game and one of those classic 5" floppies. I still really love the look and feel of inserting a floppy and manually locking it in. Floppies and cassettes and VHS's minidiscs were truly fantastic for the time. They were still mechanical, unlike CDs.

Then on my dad's side I and my siblings got an Acorn PC and a bunch of random floppies. None of them made any sense but some of them did cool things when you ran them. I remember hiding from my family and putting in the floppies that made flashing colours and watching it until time passed.

Must have been 11 or 12 years old before we first got a PC and by that point I was utterly fascinated. It was some shitty off-the-shelf eMachines thing but it was the best we could get; I managed to retrofit a decent graphics card in it a little bit later.

Re: My Business Card Runs Linux

#317

Earlier quoted context omitted.

The five following are the principal circumstances which, so far as I have been able to observe, make up for a small pecuniary gain in some employments, and counterbalance a great one in others: first, the agreeableness or disagreeableness of the employments themselves; secondly, the easiness and cheapness, or the difficulty and expense of learning them; thirdly, the constancy or inconstancy of employment in them; fo…

Nice! However your last two paras are a little too succinct; can you elaborate a little bit more?

There's almost certainly a book or two in there, to do it justice.

Tackling the latter: I recall listening to a BBC interview of a banker, probably in the wake of the 2007-8 global financial crisis, though the example's really an evergreen. The presenter asked how the executive justified his (it was a he) income. He responded based on value creation. Oddly, that's not a basis for compensation in a competitive market -- price should be set equal to marginal cost. Of course, if bank-executive services are a form of rent, he might be correct, but that's an interesting argument on its own.

It was a few years later when I finally got to actually reading Smith that I came across his "five following" discussion. Which a true market-capitalist banker really ought to have fully internalised. It made the interview response all the more curious.

I've also kept this in mind as other discussions of wages (particuarly concerning the tech world, but also other worker classifications) come up.

On the "information wants to be free" comment: skill itself is (in parts) an informational good, though one that lacks inforation's fundamental fungibility (we can transfer information from storage device to storage device across channels and networks, less so skills).

But like information, skill is difficult to both assert and assess. Beyond zero marginal costs, a chief reason information markets behave so poorly is that it's hard to assert high-quality information, and expensive to assess it. If you're reading a book, or article, or ... lengthy and/or cryptic HN comment ... somewhere in your head is the question "is this even worth my time?"

This is what makes tech recruiting, from both sides of the table, such a PITA. The front-line people writing ads and screening calls ... have all but no capability to assess skills. Responses are all over the map, from the absolutely unqualified to domain specialists and experts. "Expertise" itself is almost certainly a misnomer as so much information has so short a half-life -- it's generalised problem-solving and learning which are most required. And the tasks and projects to which talent is applied can itself be called into question. Take the 737 MAX development -- Boeing almost certainly would have been better for not trying to drag out the lifespan of that airframe, a decision which likely should have been made in the mid-1990s. Full costs (or benefits) of decisions cannot be known when they're made, and only manifest over years, decades, or even centuries (fossil fuel use).

Some coverage of that here: https://news.ycombinator.com/item?id=21864949

https://news.ycombinator.com/item?id=21864646

The notion of "manifest vs. latent" properties or consequences is one I've been looking at. Some earlier work by Robert K. Merton and others.

"The market" rewards short-term, highly-apparent, risk-externalising, liquidity-generating behaviours. There are inherent distortions to all of this. Skills and competence (as well as skills development, mentoring, training, preservation, etc.) are poorly served.

There's also some interesting discussion relating to this in Alvin Toffler's Future Shock, from 1970, which I'm reading for the first time. Bits drag, but there is much that's prescient.

Re: My Business Card Runs Linux

#319

Earlier quoted context omitted.

I am sorry, you are very wrong. A complete "Embedded System" (HW+SW) is orders of magnitude more complex than "Web Client Design and Implementation" (unless you approach Google/Facebook scale). The malleability of SW means you can quickly try out various techniques without too much "learning overhead". With all the existing Frameworks/Libraries/etc it becomes more of a "plug & play" proposition. Not so with Embedded…

Be careful with that statement. An "embedded system" can be as simple as "when this button is pressed for 3-5 seconds, turn on this light for 30 seconds." That hardly requires much of a skillset. And as far as having all the things you mention in "one head," every member of my team can handle that easily and we're not particularly noteworthy!

I think in a sense you are proving my point. Real knowledgeable people have done the hard work to simplify much of technology so that it is easy to get started on. But the moment you are past the "commoditized" part, the "learning ramp" for an embedded system becomes exponential. Not so with pure higher-layer Software Apps. There is also the fact that an "embedded system" spans a very broad domain and hence requires a broad spectrum of knowledge and skills eg. developing a Network Appliance vs. Bread toaster.

In my own experience moving from pure applications software development (though not a web developer) to network appliances to lower-level embedded development i have been amazed at all the "hidden complexity" which you suddenly become exposed to. And this is just the software part. If you get into the hardware part you have a whole another world of knowledge to learn. Merely doing something without understanding is the difference between a "Technician" vs "Engineer/Scientist".

Re: My Business Card Runs Linux

#320

Earlier quoted context omitted.

I highly recommend the ESP8266 and ESP32 once you're a little more familiar with the arduinos. They have Wifi, and the ESP32 is actually very powerful and has two cores. They make for great DIY home automation/IOT devices and are pretty easy to work with.

> ESP8266 Second this. The ESP8266 (a nodeMCU) is about as powerful as an Arduino Uno, is about half the size of a credit card, is very thin and costs around $3. The wifi part is the biggest advantage. You can send sensor data directly to your server via simple http requests.

Esp8266 is way more powerful than an arduino Uno. It's got a 32bit 96MHz proc with 96k of ram and Wifi, often coupled with 4MB flash. Uno has 32k of flash 2k ram and (from memory) 20MHz 8bit cpu.
Post reply on HN