Podcast (mp3): Play in new window | Download | Embed
Subscribe: Google Podcasts | Spotify | Stitcher | Email | TuneIn | RSS
Sponsored by: do.co/dl
Hosts of Destination Linux:
Ryan, aka DasGeek = https://dasgeekcommunity.com
Michael of TuxDigital = https://tuxdigital.com
Zeb, aka Zebedeeboss = https://youtube.com/zebedeeboss
Noah of Ask Noah Show = http://asknoahshow.com
Matt aka Dark1LTG = https://twitter.com/dark1ltg
Want to Support the Show?
Support on Patreon or on Sponsus
Destination Linux Store destinationlinux.network/store
Want to follow the show and hosts on social media?
You can find all of our social accounts at destinationlinux.org/contact
Topics covered in this episode:
Mozilla, Intel, fastly, and Red Hat Form the Bytecode Alliance
Kdenlive 19.08.3 Released
Volla Phone Kickstarter
Google Project Nightingale
If Linux Feels Slower, That’s Because It Is
Shovel Knight: King of Cards and Shovel Knight Showdown
Helvetii Coming To Linux
Drill – very fast file search utility
Tips & Tricks:
– Trick to navigate through Telegram is Ctrl + 0 to jump to saved messages
– Ctrl + 1-5 jumps to pinned chats that you have in whatever order you put them in.
– Press and hold the Send button on Mobile to Schedule a message or Send without activating a notification sound
@Ulfnic - thanks for providing the link - I’m a couple of episodes behind so link on here allows me to comment straight after watching
Thanks everyone for another enjoyable and informative episode. On the speed of the kernel and whether or not AMD CPUs also get a hit even though their hardware has fewer vulnerabilities; I would have thought that perhaps setting appropriate flags when compiling the kernel would be one way around this; not sure exactly how different distros do their builds, though if I were running gentoo I’d certainly be tempted to compile some software with processor specific flags.
Google and medical health… sickening really, pardon the pun
My feelings are mixed regarding bytecode, partly due to the security side of things, but definitely a technology with potential, so let’s see what happens.
@Ulfnic thanks for posting this
AMD doesn’t get hit as hard because they addressed many of these things in the hardware many years ago. The mitigations aren’t necessary on their hardware so by not applying them it means they do not lose any speed as the hardware itself has addressed many of the issues. AMD is already a faster processor these days than Intel and so Intel having to add mitigations on top of that makes the difference drastic.
I agree and I think puns aren’t used enough . . . I’ll need to break out my cringe syringe.
This is effectively my same feelings on this topic.
Continue the discussion at discourse.destinationlinux.network