The standard VGA resolution fit a full screen in a single 64KB segment nicely, you had many colors but not limitless, so I would argue that this was really the golden era of the demoscene. Partly because almost anyone could do some kind of a short demo that was still enjoyable to watch, and did not require the insane amount of cycle-counting and optimization and planning that the C64 does.

Although you still wouldn't download a CD, simply because... you wouldn't have been able to take it home with you! Hard drives were in many cases smaller than a single CD. Anything more than a few 10s of MBs would have been considered excessive.

He hasn't learned the correct speak yet. He should instead say that he is _very confident_ that they will cure cancer until the end of the year.

Really, guys, learn from Musk, he is the master of promising everything, but not actually committing to anything.

In contrast, Delphi provided you all the UI code by default, so even if you did not write a single line of code, your program ran and displayed a window or dialog with all the UI elements you could interact with. This was a higher level abstraction (one could argue VS did not even have an abstraction - you still had to code your window procedure from scratch. MFC was the first real attempt at simplifying UI code, but you still had to write code...).

But it did not stop here: it was trivially easy to add a database "connection" to your app (IIRC it was represented by a UI element that was not actually displayed), just provide the connection parameters, connect it to a complex UI element like a table, and voila - you had a live database view within 5 minutes.

Don't even mention SVGA, with it's pre-VESA non-standardised chaos, and abysmal high res performance. OK, the 320x200(240)x256 was actually quite usable for games, quick enough to run Doom in 93. But for video editing, there wasn't really anything on the PC that even compared to the Genlock, at least not for that price.

And to top it off, AmigaOS had preemptive multitasking (in 1985!), Windows 95 was the first real OS to do that (not counting OS/2 and NT) with graphics (not counting Linux or any unixes), yay, that's 10 years for you.

In 91 I sold my Commodore 16, and got an XT with Hercules graphics and the built-in PC Speaker. Not even on the same planet as the Amiga.

In 92 or 93 I got my first 386, with VGA but no sound card for a while, though I secretly wanted an Amiga 500 instead, but it wasn't my call. However around 92/93 PC gaming and the demoscene (!) really took off, so I got a soundcard as soon as I could, and life was very swell after that.

No, it actually competes with Excel.

At least in the finance world, there are still a million small processes driven by an Excel spreadsheet put together in an afternoon by an intern 20 years ago. If it is a really business critical process, then the input is usually a csv file, read by an Excel macro.

Because Excel is user friendly, and "is good enough". Mostly...

It's not necessarily about "advantage", especially on longer journeys. What if there is a crash on the Autobahn 1 hour in front of me? Even if I don't reroute, I at least have a choice of planning my toilet and lunch stop _before_ the crash site.

It is also possible to plan a different route if the crash is visible so far ahead. There are usually multiple routes I could take, and I decide based on the traffic and other factors, where I go. It can depend on the time of day, the time of year, etc. Maybe usually I don't take the one which is 100kms longer, but in the case of a crash, or even just heavy traffic it could be quicker still.

So for any non-trivial journey, I always use navigation, even if I could drive to the other place blindly. It's not really about navigation, it is about the current situation on the roads.

Just checked the dashboard, and we seem to have the exact same $200 credit as others, enterprise or not. Token inflation affects us just like everyone else.

It feels a bit like buying the same box of chocolates every day, but the size / weight of the box is shrinking... the price remains unchanged!

I find this kind of behaviour disgusting. Why don't you do a Show HN on your own?

Good news is, Oracle extended extended extended support for Java 8 will not last forever, and eventually - if you work in a regulated industry - the company WILL have to pull the trigger.

On the other hand, "where there is muck, there is brass", so a little bit of legacy can be beneficial for some.

I guess my point is, 4MB was really a lot of memory around 1992, and fitting a windowing environment in 640K was more the norm, and not an especially outstanding feat. Just think about GEOS and how it ran on the C64... or the Amiga (with a preemptive OS running on 256KB), or the Atari ST...

There might be value in your bugfix, but maybe that value is not greater than the cost of reviewing and accepting it.

> Reviewing code fixes is strictly easier than coming up with them yourself.

This is completely false, for any sufficiently complex project. The fix might be a single line change, but the consequences might be far reaching.

> As a user-and-eveloper, why would I sink time into a project with such rules that put a barrier to improving my life with the software?

Please don't! You don't owe the project anything. The other side of that equation is that the project also doesn't owe you anything. As simple as.

Firefox and Chromium are running much larger teams, let alone the Linux kernel, that other people suggested as a model. Maybe they can afford accepting your contributions.

One thing though that I still have nightmares about is Visual SourceSafe, Microsoft's idea of a source control system for small teams. It was not only terrible to use (and slow), but we regularly lost data in it due to concurrency issues.

(A nice thought-experiment is to ask if Quake could have been coded in TP at all - even if memory hadn't been an issue (I think there was no DOS extender for TP, but I could be wrong).)

My interview happened on the phone while I was commuting on a crowded train, and was extremely successful - at the end, we both agreed that we were not looking for each other :)

This was back when leetcode was just coming in full swing (early 2010s), which since then replaced it completely. I think the (startup - coincidence?) company that was trying to hire simply didn't have the money to pay for a leetcode hosting service, a phone call costs nothing after all, only time...