• 2 Posts
  • 282 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle


  • Unless you are gunning for a job in infrastructure you don’t need to go into kubernetes or terraform or anything like that,

    Even then knowing when not to use k8s or similar things is often more valuable than having deep knowledge of those - a lot of stuff where I see k8s or similar stuff used doesn’t have the uptime requirements to warrant the complexity. If I have something that just should be up during working hours, and have reliable monitoring plus the ability to re-deploy it via ansible within 10 minutes if it goes poof maybe putting a few additional layers that can blow up in between isn’t the best idea.









  • There is nothing like this availlable currently. Framework probably comes closest, but they only sell in a few countries, and there is lots of stuff to dislike about their solutions - but building your own around a framework board might be feasible.

    I have two mnt reforms - as you said, slow and expensive. They have their use for work prototyping for me, but generally wouldn’t recommend. They also have the worst keyboard I’ve encountered in a notebook in the last decade.





  • aard@kyu.detoTechnology@lemmy.worldThe decline of Intel..
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 month ago

    Not just that - intel did dual core CPUs as a response to AMD doing just that, by gluing two cores together. Which is pretty funny when you look at intels 2017 campaign of discrediting ryzen by calling it a glued together CPU.

    AMDs Opteron was wiping the floor with intel stuff for years - but not every vendor offered systems as they got paid off by intel. I remember helping a friend with building a kernel for one of the first available Opteron setups - that thing was impressive.

    And then there’s the whole 64bit thing which intel eventually had to license from AMD.

    Most of the big CPU innovations (at least in x86 space) of the last decade were by AMD - and the chiplet design of ryzen is just another one.


  • Is it a ‘death by quantity’ thing?

    Pretty much that - those companies rely on open projects to sort it for them, so they’re pretty much scraping open databases, and selling good data they pull from there. That’s why they were complaining about the kernel stuff - the info required was there already, just you needed to put effort in, so they were asking for CVEs. Now they got their CVEs - but to profit from it they’d still need to put the same effort in as they’d had to without CVEs in place.


  • Short version: A bunch of shitty companies have as business model to sell open databases to companies to track security vulnerabilities - at pretty much zero effort to themselves. So they’ve been bugging the kernel folks to start issuing CVEs and do impact analysis so they have more to sell - and the kernel folks just went “it is the kernel, everything is critical”

    tl;dr: this is pretty much an elaborate “go fuck yourself” towards shady ‘security’ companies.


  • One fascinating example is one owner that replaced the DC barrel jack with a USB-C port, so they could utilize USB-PD for external power.

    Oddly enough that’s also an example for bad design in that notebook: The barrel jack is soldered in. With a module that is plugged into the board that’d be significantly easier to replace - and also provide strain relief for power jack abuse. All my old thinkpads were trivial to move to USB-C PD because they use a separate power jack with attached cable.

    The transparent bottom also isn’t very functional - it is pretty annoying to remove and put back, due to the large amount of screws required. For a notebook designed for tinkering I’d have wanted some kind of quick release for that. Also annoying is the lack of USB ports on the board - there’s enough space to integrate a USB hub, but just doing that on the board and providing extra ports would’ve been way more sensible.

    The CPU module also is a bit of a mixed bag - it pretty much is designed for the first module they developed, and later modules don’t have full support for the existing ports. I was expecting that, though - many projects trying to offer that kind of modular upgrade path run into that sooner or later, and for that kind of small project with all its teething problems ‘sooner’ was to be expected. It still is very interesting for some prototyping needs - but that’s mostly companies or very dedicated hackers, not the average linux user.


  • RDS and related protocols like TMC have specifications for both FM and AM transmitters. Those are used to stop playback if an urgent message comes. I’m assuming you have AM stations with such signals in the US (I don’t think we have in the EU) - otherwise the AM radio mandate would indeed be stupid.

    edit: did some digging (it’s been almost 30 years since I cared about that stuff) - seems the US was pretty late to the party for radio data channels, and side channels for AM (which wasn’t of that much interest here due to the FM heavy radio landscape in Europe) only was discussed in the early 90s for the US specific variants. I couldn’t find any details if that actually ever got implemented. Given that most documentation available on that topic is heavily focusing on EU I’d guess it never got that much use in the US.


  • Ability for AM radios to interrupt other playback for announcements has been around at least since the 90s. Back then it was commonly used to pause cassette playback when traffic announcements were made.

    This just requires for the device to monitor radio when on, and to be on - and with how integrated it is in modern days cars functionality I’d say the chance for them to be on is higher than it was in the 90s. So having that functionality is a pretty good way to reach a lot of car drivers.