The ‘n’ node manager easily installs latest or stable versions of Node.js. Install with npm:
npm install -g n n stable
Done.
Articles, notes and random thoughts on Software Development and Technology
The ‘n’ node manager easily installs latest or stable versions of Node.js. Install with npm:
npm install -g n n stable
Done.
Before the launch of Microsoft Flight Simulator 2020 last year I took a number of comparison screenshots in FS 2002, 2004, and FSX but I never went back and retook screenshots from FS2020 after the launch. Here’s one example of the level of photographic detail in the scenery compared to Visual Flight’s VFR photographic scenery add-on for FS 2002. It wouldn’t be a good comparison to the base products without a scenery add on since they were only doing scenery autogen and didn’t even have photographic scenery, but here’s a good comparison just how good the FS2020 scenery is (drag the bar to compare):
Since the recent UK scenery update, here’s a comparison in roughly the same area looking along the Southend coast. Unfortunately I didn’t have a screen from before the update showing where the pier should be – originally it was submerged in the imagery, but as you can see from the image on the right above it’s now a very impressively modeled landmark:
Here’s a couple of other screenshots taking a closer look at the scenery along the sea front and the pier:
It’s interesting while the pier got a full custom model, the fun fair areas each side got a couple of buildings but the rides and rollercoaster where just left as flat imagery:
When starting out in software development or even learning a new language as an experienced developer, the most likely cause of most ‘I don’t know why this code isn’t working’ type questions is pretty simple:
What you think your code should be doing is often not what it’s actually doing.
This seems like an obvious observation, but it’s easy for even an experienced developer to get caught up in what they think their code is doing, and they forget to look at what it’s actually doing.
Next question: “ok, so how do I find out what my code is actually doing at runtime?”
Answer: you use a debugger. You step through your code and you compare what you think each line should be doing with what it’s actually doing. At some point you’ll find a line where you assumed the code was doing one thing but it’s actually doing something else. It could be the variable of a value that you were assuming to be a particular value but actually it’s something different and it results in a result that’s different from what you were expecting. It could be a condition you were assuming to be true is actually false. It could be a block you were assuming would always get executed but never is. There’s many reasons.
Learn how to use your debugger:
Knowing how to use a debugger is an incredibly valuable skill. It’s seems a given that as a developer you would learn to use and use a debugger as an integral part of your development, but all too often though when asked ‘why is this code not working’, if you ask ‘have you stepped through in a debugger to see why it’s not working?’ the answer is ‘no’.
Learn to use your debugger!
Sad to read today that the upcoming FPR32 release of TenFourFox, a browser built to run on older PowerPC G4 and G5 Macs, will no longer be developed.
I run TenFourFox on both a Power Mac G4 Quicksilver 2002 and a Power Mac G5, and have enjoyed having this option of a current browser that still runs and is able to access most modern websites on these older machines. Given that TenFourFox is developed and maintained by a single developer for free, it’s really nothing but outstanding that we’ve been able to enjoy having the option of running a modern browser on these aging machines.