herio

Tired people are more likely to make mistakes. Less maintained machines are more likely to have issues.

Not saying this is always the case but I've seen this happen in real life. New company takes over, starts skipping maintenance to produce more, machines now start breaking like clockwork. Eventually the machines were so broken they had to be replaced.

https://edpb.europa.eu/sites/edpb/files/files/file1/edpb_gui...

Statement 82 reads:

"The GDPR does not allow controllers to offer pre-ticked boxes or opt-out constructions thatrequire an intervention from the data subject to prevent agreement(for example ‘opt-out boxes’)."

This in my mind pretty much invalidates most of the existing cookie banners out there, not to mention the multi layered messes some sites do (oath comes to mind).

Ultimately I think it's just another leaky abstraction like so many other things we do. Wonderful when it works as intended and less so when it goes wrong.

I also think that the more layers of software and management you add in makes it more complicated to troubleshoot, you simply get a lot more to learn in order to understand things.

One of my life philosophies is "It's always more complicated", meaning when you think you understand something you've barely just started scratching the surface of the complexity of it.

I can understand the pull of the container and lambda style workflows, you gain feature velocity which is ultimately what gains you the business. On the flip side, I also suspect that it builds technical debt faster.

I don't think they sold them to other companies, MOS was at this stage fully part of Commodore. Commodore was really big on vertical integration, they didn't like buying components from other companies if they could help it. They even manufactured a few 74xx logic chips sometimes used in their 8-bit computers.

The other part of reverse engineering something like this is to figure out the other parameters of the chip, e.g. propagation delay, slew rate, output voltage profile etc. etc.

On the C128 it is also involved in the DRAM refresh handling.

The C64 PLA was originally a programmable device, the Signetics 82S100. Later version were MOS/CSG copies of the same device but programmed with changes to the manufacturing masks instead, similar to the difference between an EPROM and a Mask ROM.

For a lot more detail and background, I can recommend reading Thomas Giesels excellent paper on the C64 PLA, found at http://skoe.de/docs/c64-dissected/pla/c64_pla_dissected_a4ds...

Sounds like normal human interaction to me. This is a feature, not a bug as far as I'm concerned.

From my point of view there is a whole spectrum of things in between these two opposites. I see full unfettered capitalism as harmful as I consider full blown communism. They're both totalitarian systems just with different masters and propaganda.

Social democracy as done in much of Europe is in between the two (or at least used to be when I grew up). It tries to respect basic human rights such as housing and health care, while still allowing corporations to do their thing. Controls imposed on corporations tries to ensure that they don't go completely bonkers in search of the almighty profit.

There are some other pretty nice and featured 68k cores that are open source (TG68, WF68K30L etc.) but none that is really close to the features and performance of the Apollo 68080.

While the Amiga was actively worked on nobody really cared about the 8-bit stuff. The Commodore name and trademark was not actually included in the IP package, it went to Tulip Computers in the Netherlands. From there it went on to Yeahronimo ventures and then into C= holdings.

The patents and copyrights were always in the big IP package passed around but since there was no real money in dead 8-bit stuff nobody actively enforced the rights on those ROMs. As such I think it would be hard for anybody today to start trying to enforce the IP rights on the 8-bit ROMs, they are so widely spread, distributed and used.

All the IP rights (except the Commodore name and trademark) is now owned and managed by Cloanto. You can buy legal copies of all the ROMs and software from them, they also seem very amenable to make deals with makers of retro computers etc.

Hasn't really gone anywhere of importance.

I personally think there's been a few factors as to why:

* Distrust of DNSSEC and centralized authority.

* Lagging DNSSEC deployment, not just in DNS but also in clients and applications.

* Needs another DNS lookup on connection to validate certs, adding lag. I think it probably needs stapling support in some form just like cert validity checking.

There's also been follow up RFC detailing it's use for SMTP, SRV records and PGP.

The only reason to read this is if you are interested in technical details of a 35 year old 8-bit computer.

https://www.nextbigfuture.com/2019/11/spacex-starlink-28-mil...

There is an FPGA based version of the SID called (surprise) FGPASID (http://www.fpgasid.de/) which is pretty much indistinguishable from an original SID. The only real downside to it is the cost, it's not a cheap one.

The FPGASID was created by decapping and reverse engineering original SID chips and the result is pretty spectacular.

As long as I have enough to live comfortably, stash some away and not worry I'm good, I don't need more. As such, I don't really get involved in most of the things that this post is about nor do I particularly care to do so either.

Work is what I do in order to sustain myself, it's not my life. The minute I walk out the door at work I've forgotten all about it and never think about it until morning. I realise this is me being pretty lucky but I'd probably even change career completely if I couldn't do this anymore working in tech. I think a lot of people struggle to find that balance, sadly.

As a new programmer, you certainly spend more time thinking about the details and minutae of the code itself.

Changing languages within the same group tends to come pretty easy, a C-like is mostly similar to other C-likes, flipping from python to ruby isn't all the terrible (or vice versa).

Moving between language groups is harder though, still struggling to wrap my head around lisp and haskell for example. Probably due to my skewed upbringing, BASIC to 6502 to 68k to C to python.

Back home in Sweden, records are automatically sealed after two years (if my memory serves me correctly).

PCI is vastly superior to Zorro-3 though, in both features and performance. Z3 never achieved the performance given in the specs and had quite some problems. IIRC Dave Haynie said that he would have used PCI instead of developing Z3 if it had been out at the time.