Hacker Newsnew | past | comments | ask | show | jobs | submit | lpribis's commentslogin

He implied replacing nano was the first step, before using it for more complex (software development) tasks. First use it just for quick one-off edits of /etc/blah.conf then graduate to using it for longer editing sessions.


Rather than being about fast/simple/cheap, I think using SSN as a key was more about the fact that SSN is the only common identifier that almost all US citizens have.


I think you're using the word "key" differently than OP. You're talking about identifiers, and they're talking about security.

SSNs were a good potential identifier, until the people that needed security cheaped out and started using SSNs as a bad implementation of security. Now they're bad at both purposes!


Yes, designing and implementing a new common identifier almost all US citizens have would have been less cheap and fast.


Sure, but splitting "atomic" operations across a reboot is an interesting design choice. Surely upon reboot you would re-try the first `mv a b` before doing other things.


This is local to the device though. Nothing to do with the WAN. Would still work even on the "serverless" ipv6 network.


The Z80 instruction set lives on via the eZ80, Z180 and others which are binary compatible with the original Z80 instruction set. Unfortunately Zilog stopped making the 40 pin DIP package a couple years ago so yeah this specific board will be hard to source. You can still find them on gray market, mostly ones that have been desoldered from existing boards.

Even if you made a version of this board with the footprint changed to the QFP eZ80, it probably wouldn't work because the eZ80 has different memory mapping and clocking differences.


The Z180 has however had its PLCC packages discontinued. Personally, I find SMD CPUs to not be appealing for these sorts of projects, even if the Z180 is a great chip.


Really, the best we can do with the NPU is a less battery intensive blurred background? R&D money well spent I guess...


They can't realistically do this in Germany because the tracks are so much more busy than the US. There would more than likely be a train coming the other direction within the next few minutes, and they cannot guarantee all the people have time to vacate the track area.


Right, but Germany has stations every few miles. Here in America the next station might be hours and hundreds of miles away. Better to stop ¼ mile away instead; people will hardly know the difference. The point is that if for any reason they cannot reach the station then they’ll always stop at the nearest safe place instead. The crew always have an alternate stop.

For really long construction work they’ll actually build an entirely separate train station, like they did in Denver Colorado a few years back. They knew that the construction of the new station downtown would take a few years, so they built a really cheap platform a few miles away on a siding and moved all the arrivals and departures there for the duration.


TCO is not just for parse trees or AST, but in imperative languages without TCO this is the only place you are "forced" to use recursion. You can transform any loop in you program to recursion if you prefer, which is what the author does.


Don't forget about UIOP (Utilities for Implementation and OS Portability) which is part of the ASDF project. Also very easy to type!


Sample of 1, but the hidden gem near me I would actually consider a "hidden gem" that only people from the area know about, and it's a very good family run business.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: