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

It requires a different way of coding: bug-free is a serious target, as far as it can be approached. It is a permanent concern while coding, with a lot of testing, and releases are hard releases, not agile output. No titanic effort there, just being serious and focused with quality.


Well, my 2-cent is that you can laugth of everything but not with everybody... So defying the norms with Easter Eggs sent to the wild can be an issue. You have to know your audience to properly chose your level of impertinence.


I completely agree with the first sentence - however I would argue that normal, level-headed and sane person either laughs or just shrugs and moves on if that particular joke is not to their taste.


I love the story... But don't forget this story is the proper selection of events with textual glue and interpretation to make it feel like a novel.

Some statements belong more to the glue than to History, and they should remind us this is a real-life-based * novel *. I especially noted this one: "nobody at IBM had any real experience with [microcomputers]".

IBM senior management was certainly reluctant, but "nobody"... They even had microcomputer products that hit the market:

- IBM 5100 1975, first IBM personal computer

- IBM 5110 1978, 5100 updated for a larger market target

- IBM System/23, under parallel development with the IBM PC and released 1 month before in July 1981: many of the IBM PC features are shared with or taken from it (8-bit Intel processor family 8080 vs. 8088, very same expansion connector, reuse of the electronic expansion cards such as serial, exact same keyboard - just in a different box and with different function keycaps...)


Small fix: the IBM System/23 Datamaster was based on Intel 8085, an improved version of the 8080 (binary compatible, more features, requiring less electronics around).


If two friends ask you to judge a dispute, and you don't accept... You might loose two friends since both of them think they are right and will not understand you do not support them.


Then they aren't my friends. If a "friendship" is that delicate, I'm better off, without.

I have extremely close friends, with whom I have deep, fundamental, disagreements.

I have absolutely no problem, telling people that they are dreaming, if they think they can extort me into taking their side.

"Support" can mean that I won't participate in destructive behavior. I often can't stop others from doing it, but I can make sure I don't get dragged into the cesspool, and be ready with towels and a power washer, when they get out.


This same exact argument could be applied to the first saying as well.


That is correct. It's just a quote. Real life tends to have more subtlety.


If they are that sensitive, I can also be sensitive and ask them why they've involved me in a conundrum where I stand to gain nothing.


That would be a mildly weird reaction to "I don't want to get involved in your dispute", in _most_ cases. (I think there are edge-cases where not wanting to get involved might in itself be taking a stand, but certainly for everyday disputes most people wouldn't take offence to "I don't want to get involved").


I would trust they would instead be happy to have such a socially intelligent friend once the dust has cooled.


Probably because the so-called "low level" work and skills are underrated:

Have you ever wondered why your modern computer makes you wait for so many things? ... while you or other people were doing so many of the same things like 30 years ago on computers hundreds times slower.

Is it that your computer is getting old? ... No way! Hardware does not slow down when aging: software does. And it does because most developers have no idea of what happens under their feet in lower software and hardware layers - or worse, they just do not care.

I am so sure we would get so much better software if most developers were skilled in so-called "low level" stuff... Because "low level" skills are exactly the opposite: they are high level skills.


A cool DIY computer project could be a free re-creation of computers of the past. I believe it would make sense re-running the path of computer history, but pushing more and more open-source in it. You already can buy a NuXT, based on Sergey Kiselev's work to provide DIY resources to create a PC XT computer (including the BIOS).

I thought someone could enlarge the design to a more modern architecture when I found an old Compaq internal documentation showing the internal design of the first commercially available 80386 computer (Compaq Deskpro 386). I have just posted the reference on HN: https://news.ycombinator.com/item?id=38480275

Such new re-created computers would certainly be interesting to run legacy software, but it would also be very interesting to have modern and light-weigth software like KolibriOS (I know it requires a Pentium or more, but there is certainly little to change to downgrade to 80386).


I found a treasure on eBay this year and I shared it on Archive.org (link above, scroll down below the image) and Minuszerodegrees (Manuals > Third parties > Compaq).

It is a Compaq internal document of 1986, a full technical documentation of the first commercially available 80386 PC.

It is of interest for historical reasons (read abstract on Archive.org) and for people who would like to re-create a free x86-32 hardware respecting the original design... Something like a PC NuXT upgraded to 80386 or better.


"Between them IBM and MS traded performance for forced standardisation"

Maybe I misunderstand, but for me it is a strange statement:

* IBM fought standardization: they initially released a PC compatible with nothing, even in their own product lines, and fought hard against any kind of clones - those that transformed the IBM-PC in a de-facto standard. They even tried with the PS/2 line to break compatibility for all third-party hardware extensions (the MCA bus that could be used only by paying royalties to IBM).

* Microsoft cared neither for performance (obviously) nor for standardization. They just fought to own the market. Their products became de-facto standards because MS worked hard to kill competition and real standards. They even theorized and practiced the "embrace extend extinguish" process to kill competing products by breaking standards.


That logic is like breaking windows to feed the glazier's family... Or puncture tires to feed the garage owner's family.

It does not make any sense: it is fake work while there is so much real work to do.


I understand your feeling: I have a vague uneasy feeling when I see DOSbox or other emulations running. It is a great achievement to allow legacy software to remain alive and executable... But still it seems fake. Nothing to do with the real software running on real antique hardware.


Pretty irrational honestly. The input and output devices make more of a difference than digital software being emulated or not. I'd rather play old arcade games in an emulator connected to a CRT arcade monitor than real arcade PCBs connected to an LCD using some scaler. The former is going to be a more authentic experience.


I think it's related to latency. There is no way to fake low latency and for that you often need the complete chain of hardware.

I'm the opposite to you though, rather have an original C64 on modern capture (low latency GV-USB2) and (S)NES classic controller input.


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

Search: