How many centuries did it take for civil engineering, for example, to become the codified, standardized, and respected calling it is now? While I'm sure "software development" will leapfrog that span of time, but it's only been 75 years since the discipline was invented to begin with (Lovelace's work was more applied math than anything else, but the starting point is arguably between then and, let's say, FORTRAN?).
That is to say, as a programmer, I feel like we're wading in an ocean of unknown size and depth. As we learn, by trial and error, the confines of that space will fuel the standardization and codification of the craft will only increase as a function of time until it isn't craft, but applied science.
I'll be entirely honest here, this kind of game is generally up my alley but I clicked off when I came across the list of available cities to build in being exclusively in the US. Not even a fictional playground for messing around in the engine, just "US primacy or bust", doesn't inspire confidence for a full release down the line. Not that I don't understand why it's like this, pulling the required real-world data is hard enough as it is, but it will limit the market I think.
With 32 GiB of memory it's just too slow. A laptop, to me, is supposed to be a device much like a phone in that I can just flip it open and do what I need to do, suspend is supposed to be that, but if I don't charge my Dell precision every single day it'll just run down to 0 for absolutely no reason.
Sort of, the "zip folder" thing was introduced with the "98 Plus!" pack, but came natively with XP. That said, "natively supported in Windows" is one thing, but the usability was... well, not great. The entire "it's a compressed folder!" analogy seems reasonable, but the implementation wasn't. It ate memory like few other components, crashed often, and because it was treated like a folder only in file explorer the analogy quickly broke down when using a file picker anywhere else. WinZIP and WinRAR were basically requirements if you often worked with zip archives until 7zip came along and did everything just a tad better.
In the multiple inheritance sense, but I wouldn't call it a descendant either. Larry "simply" scrounged around in '87 and looked at everything he could to put into his awk-but-better tool. In his own words C was a big part of that, with BCPL in the back of his mind.
I feel like this idea is another form of, or at least related to, my own habit to process input in two phases, plan and execute. Run the input through a planner component that produces a sequential list of instruction that would 'do' whatever it is we're doing. I've changed this style to permit parallel execution or other more complicated structures than just a flat list, but I often come back to this base plan. Invalid input would be caught during the planning phase, and I need to ensure the planner can't make impossible plans up to an extent. Can't say I've avoided every type of problem or bug this way, but it sure as hell gives me a good base to work with.
I'd like to fat comma shame you for this, but I've done the same on occasion, so meh. The thing that irks me about it is that it appears as if the function takes a hash on first read, and I'll happily cargo cult the call style until I finally read the docs for capture, in this case. I don't know, would you put this in prod for other devs to maintain?
> All of this meant that the Voodoo Rush was dead on arrival.
Interesting this should be my first video card that I bought myself. I do remember there being issues using specific renderer libraries, swapping out glide dll's and that sort of stuff to make certain games work. For a DOA card I sure was happy with it!
In jest I'll also assume the author could write a similar article lamenting what storage tech could have been, but instead everyone with data that mattered took the maintenance hit with RAID and called it a day.
Commoditization is, to me, just a natural effect of product development in a free market, capitalist(-ish) society. It feels to me that as long as much of the population is chasing financially optimal outcomes this will continue to happen, and that may be okay.
Publisher is financially incentivized to kill the servers, maintenance, and bugfix time for this title since single purchase licenses and long term online infrastructure requirements are financially incompatible.
If nothing else it's respect for the science communicator side of Sagan, who 'obviously' would get increasing praise with the STEM-advocates over the past decades.
That aside, wanting your name struck from a project, internal or not, is reasonable if someone has something against the business practices of a company. That's about the only, to me, valid reason for requesting the cessation. Doubling down with butt-head astronomer instead is pretty dickish, though.
From the documentation:
* However, only about 78 significant digits are stored at any point.
* SpeedCrunch stores integers with a precision of up to 256 bits.
If you mean bc as the 'calculator that comes with linux', thats somewhat to be expected. Speedcrunch deals with a maximum integer size of 256 bits (~1.15e77), while bc is an arbitrary precision calculator.