There has been plenty of talk and speculation for years about what a Grand Theft Auto 6 game could look like, what world it would be set in and how it might work. It’s not an industry secret that GTA V is a money-making machine, still making a tidy profit in the seven years it has been out.
Microsoft Flight Simulator 2020 was recently released and it is a next-gen marvel. The game uses a combination of real-life data (Bing Maps run through a 3D algorithm) combined with real weather and air traffic, you’re flying in a realistic living world.
I do a bit of live streaming over on Twitch (give me a follow if you’re interested in coding and this post helped you) and while I primarily use my desktop PC, I was travelling recently and wanted to use my gaming laptop to do a little code streaming (scroll down to the “fix” section if you’re in a hurry).
Like many, I use Streamlabs OBS for my streaming needs. While I attempted to enable display capture for my live scene, my webcam was working fine, but none of my laptop display was being captured. All I got was this black screen and no explanation.
Depending on who you speak to, WebAssembly will kill Javascript, WebAssembly will enhance Javascript, and WebAssembly will merely appeal to a small subset of die-hard developers working on problems that require lower-level bare metal solutions written in a compiled language.
A lot of work has gone into reducing the performance issues that have plagued WebAssembly regarding making JS calls (especially when working with the DOM). Efforts seem to be focused on making WebAssembly more than a memory-siloed thing, but rather a viable alternative for anyone wanting to work mainly within the confines of WebAssembly.
You’ll notice from time-to-time that Node.js will release a new minor version and sometimes a major version. If you’re working with TypeScript, you’ll want to install the @types/node typings into your project.
If you’re running Node.js version 12.14.1 confusion might set in because there is no matching version for the Node types package.
Node is known to introduce new features into minor releases, so ensuring that your typings are up-to-date within the latest major release band will ensure that your typings are not too old or too far forward (LTS vs current release).
You fork a repository on somewhere like GitHub or GitLab and you make some changes. Maybe you want to contribute to an open-source repository. You work on your fork, but in the interim, the repository you forked has had a new release and quite a few new commits.
How do you get those commits from the repository you forked and merge them into your fork? This is where setting an upstream from the forked repository comes in handy.
If you’re a developer, chances are you have a penchant for dark mode. Staring at a screen all day and possibly part of the night, dark mode is easier on the eyes and it just looks awesome.
It might surprise some of you to know that CSS has native support for dark mode and styling specifics using a property called prefers-color-scheme.
@media (prefers-color-scheme: dark) { /\* paint it black \*/ } The best thing about prefers-color-scheme is that it is well-supported. If you do not have to support Internet Explorer, then you can use it and not have to worry about any polyfills or Javascript fallbacks.
I have had my current Core i5 6600k PC for a few years now and it has served me well and if I wasn’t upgrading, would continue for years to come. However, now I am working from home more and find myself branching out into streaming, video editing and trying to play Microsoft Flight Simulator, I needed something stronger and more future proof.
Five years for a PC is an incredible run. I never turn my PC off, not to mention, I overclocked it and it never skipped a beat or reduced its lifespan. I have always been Team Blue (Intel), but the price and compelling benchmarks of the Amd Ryzen chips had me intrigued.
I’ve had this thought one and off over the last few years since I started using TypeScript back in 2015 actually. What if Web browsers natively supported TypeScript?
If Web browsers could natively support TypeScript without needing a build step first, would it be possible and secondly, would it be performant? As in, you just build your site and instead of .js files you reference .ts files.
It turns out, someone else had the same idea back in 2016 when they created an issue on the Chakra GitHub repository requesting native TypeScript support. The team had discussed the possibility but they were against it because TypeScript isn’t a web standard and they believe WebAssembly is a better option.
When I last tried Yarn v2, it was a nightmare. Besides the fact it was a completely new major version that fundamentally changed how Yarn worked (from its architecture to how dependencies were handled).
After seeing news about the latest release for Yarn v2, I got to thinking and the idea I would migrate one of my Aurelia 2 Projects from Yarn v1 go Yarn v2 was born.
This isn’t going to be a tutorial or how-to for upgrading. I didn’t actually encounter any issues upgrading to v2. In fact, this is quite a non-eventful post.
Nvidia unexpectedly dropped three new graphics cards in its recent announcement. The 3070, 3080 and 3090 at price points which are just as impressive as the cards themselves.
The 30 series Ampere cards are a new generational leap for graphics cards which have a lot of people excited. Noticeably quiet, but imminently expected to launch its Big Navi architecture cards is AMD.
And it seems AMD is getting ready, given they’re doing publicity stunts in Fortnite and seemingly, staging them as well.