• 3 Posts
  • 35 Comments
Joined 6 months ago
cake
Cake day: January 3rd, 2024

help-circle
  • QT is a cross platform UI development framework, its goal is to look native to the platform it operates on. This video by a linux maintainer from 2014 explains its benefits over GTK, its a fun video and I don’t think the issues have really changed.

    Most GTK advocates will argue QT is developed by Trolltech and isn’t GPL licensed so could go closed source! This argument seems to ignore open source projects use the Open Source releases of QT and if Trolltech did close source then the last open source would be maintained (much like GTK).

    Personally I would avoid Flutter on the grounds its a Google owned library and Google have the attention span of a toddler.

    Not helping that assessment is Google let go of the Fuschia team (which Flutter was being developed for) and seems to have let go a lot of Flutter developers.

    Personally I hate web frontends as local applications. They integrate poorly on the desktop and often the JS engine has weird memory leaks




  • I agree Grian shenanigans are fantastic.

    I am currently working my way through Mumbo’s S6 and the best episodes so far have Iskall and Grian in them.

    The thing I have noticed it Mumbo isn’t really pressuring himself on a build. He has just kept focus on the storage system because he is finding it fun.

    I thought Grian was at his best with the barge, his episodes had a flow where he would resource, stock the bardge, do a “small” build/project and then shenanigans.

    I am not sure that flow is sustainable but he was clearly having fun.

    At the moment it just seems he is increasingly beating himself up on being a builder and needing to build the most epic base ever.


  • I have listened and as the seasons go on I get increasingly worried about him. He is increasingly showing signs of burn out so clearly his flow isn’t working for him.

    Listen to season 7 as he talks about the back of the mansion. He is feeling self pressure to complete the back and he is getting fustrated at himself.

    Its the same with the Ally, you can hear how excited he is at the start and as the season progresses anything to do with the ally he talks about like an unpleasant chore.

    With the stones other hermits try to intervene to help him, his reaction there really doesn’t seem a bit. It sounded a lot like the panic caused by burn out.

    He clearly loves being on the SMP and his shenanigans and ideas are fantastic and clearly a lot of fun for him. I want him to stick around and think unless he learns how to break up work so he can find joy in all his builds he will loose that joy




  • When AMD launched Ryzen they deliberately offered way more I/O bandwidth than Intel.

    The first generation Ryzen CPU’s used RAM frequency that could cause performance issues if you used low frequency RAM. That got fixed in the 3000 series.

    There are a small number of Ryzen CPU’s which end with “3D,” it means they had 3D Cache memory and its supposed to add rediculous performance in certain situations. Phoronix runs tons of benchmarks on CPU and GPU.

    The only Intel instructions AMD haven’t implemented is AVX-512 and AVX-10. No one uses AVX-512 as Intel CPU’s get so hot they performance throttle so much its faster to not use the extension. AVX-10 is something new Intel released this year to get around that.

    AMD does support AVX2 which a lot of Audio/Video products do use.


  • See its the opposite in Linux land.

    AMD open sourced their drivers so everything just works, while Nvidia drivers have to be built against your system and Nvidia refused to supply proper desktop drivers for years (EGLStreams vs GBM).

    The downside of AMD’s approach is it has to trickle down which depending on what distribution you use can take weeks to a year and it normally takes a couple iterations to get everything working nicely. Which basically expect the 6800 XT to work brilliantly but the 7300 to be flakey for a bit.

    My favourite bit is I owned a few Athlon 5300 APU and 5 years after they were released AMD were still adding performance improvements to them.


  • Immutable distributions won’t solve the problem.

    You have 3 types of testing unit (descrete part of code), integration (how a software piece works with others) and system testing (e.g. the software running in its environment). Modern software development has build chains to simplify testing all 3 levels.

    Debian’s change freeze effectively puts a known state of software through system testing. The downside its effecitvely ‘free play’ testing of the software so it requires a big pool of users and a lot of time to be effective. This means software in debian can use releases up to 3 years old.

    Something like Fedora relies on the test packs built into the open source software, the issue here is testing in open source world is really variable in quality. So somethinng like Fedora can pull down broken code that passes its tests and compiles.

    The immutable concept is about testing a core set of utilities so you can run the containers of software on top. You haven’t stopped the code in the containers being released with bugs or breaking changes you’ve just given yourself a means to back out of it. It’s a band aid to the actual problem.

    The solution is to look at core parts of the software stack and look to improve the test infrastructure, phoronix manages to run the latest Kernel’s on various types of hardware for benchmarking, why hasn’t the Linux foundation set up a computing hall to compile and run system level testing for staged changes?

    Similarly website’s are largely developed with all 3 levels of testing, using things like Jest/Mocha/etc… for Unit/Integration testing and Robots/Cypress/Selenium/Storybook/etc… for system testing. While GTK and KDE apps all have unit/integration tests where are the system level test frameworks?

    All this is kinda boring while ‘containers!’ is exciting new technology


  • You seem to be intentionally missing the point, but to reiterate…

    You shower before entering a pool to wash the dirt from your body off (your cleaning yourself).

    The more of your body covered the less effective that shower is.

    Ideally everyone would be naked in the shower, but there are probably outfits which increasingly render the shower less and less effective (e.g. speedos are better than shorts, etc .).

    It would not surprise me if a Burkina covered so much that the cleaning shower is rendered pointless


  • The shower before a pool is to ensure people aren’t entering the pool coated in dirt (e.g. sweat, hair, dead skin, etc…).

    The chemicals in a pool are designed to bind to that dirt and kill any bacteria introduced.

    There is a limit to the chemicals you can add to a pool (before it hurts humans) and once the amount has activated you need to drain the pool and refill it.

    Swimming pools hold crazy amounts of water which is also really expensive to heat up, so pools want to do that as little as possible.

    Clothing interfers with cleaning your body, so people entering near fully clothed (e.g. like a Burkina) will likely introduce more dirt into the pool.

    That translates into increased costs for swimming pools or pools which maintain the old schedule and just operate unsafely.

    This is all based on owning a hot tub and learning how to maintain it.

    Hopefully this also explains why it doesn’t matter people enter the sea fully clothed




  • stevecrox@kbin.runtoFediverse@lemmy.worldWhat's going on with kbin.social?
    link
    fedilink
    arrow-up
    62
    arrow-down
    1
    ·
    edit-2
    5 months ago

    The developer behind KBin seems to have issues delegating/accepting contributors.

    If you look at the pull requests, most have been unreviewed for months and he tends to regularly push his branches once complete and just merge them in.

    That behaviour drove the MBin fork, where 4-5 people were really keen to contribute but were frustrated.

    To some extent that would be ok, its his project and if he doesn’t want to encourage contributions that is his decision but…

    KBin.social has gotten to the size where it really should have multiple admins (or a paid full time person). Which it doesn’t have.

    The developer has also told us he has gone through a divorce, moved into his own place, gotten a full time job and now had surgery.

    Thats a lot for any normal person and he is going through that while trying to wear 2 hats (dev & ops) each of which would consume most of your free time.

    Personally I moved to kbin.run which is run by one of the MBin devs



  • Firstly it was just a bit of fun but from memory…

    Twitter was listed as having 2 data centers and a couple dozen satellite offices.

    I forgot the data center estimate, but most of those satelites were tiny. Google gave me the floor area for a couple and they were for 20-60 people (assuming a desk consumes 6m2 and dividing the office area by that).

    Assuming an IT department of 20 for such an office is rediculous but I was trying to overestimate.


  • The Silicon Valley companies massively over hired.

    Using twitter as an example, they used to publicly disclose every site and their entire tech stack.

    I have to write proposals and estimates and when Elon decided to axe half the company of 8000 I was curious…

    I assigned the biggest functional team I could (e.g. just create units of 10 and plan for 2 teams to compete on everything). I assumed a full 20 person IT department at every site, etc… Then I added 20% to my total and then 20% again for management.

    I came up with an organisation of ~1200, Twitter was at 8000.

    I had excluded content moderators and ad sellers because I had no experience in estimating that but it gives a idea of the problem.

    I think the idea was to deny competition people but in reality that kind of staff bloat will hurt the big companies


  • It does but for the 90’s/00’s a computer typically meant Windows.

    The ops staff would all be ‘Microsoft Certified Engineers’, the project managers had heard of Microsoft FuD about open source and every graduate would have been taught programming via Visual Studio.

    Then you have regulatory hurdles, for example in 2010 I was working on an ‘embedded’ platform on a first generation Intel Atom platform. Due to power constraints I suggested we use Linux. It worked brilliantly.

    Government regulations required anti virus from an approved list and an OS that had been accredited by a specific body.

    The only accredited OS’s were Windows and the approved Anti Viruses only supported Windows. Which is how I got to spend 3 months learning how to cut XP embedded down to nothing.



  • Docker swarm was an idea worse than kubernetes, that came out after kubernetes, that isn’t really supported by anyone.

    Kubernetes has the concept of a storage layer, you create a volume and can then mount the volume into the docker image. The volume is then accessible to the docker image regardless of where it is running.

    There is also a difference between a volume for a deployment and a statefulset, since one is supposed to hold the application state and one is supposed to be transient.


  • There will always be someone who is beating you in a metric (buying houses, having kids, promotions, pay, relationships, etc…) fixating on it will drive you mad.

    Instead you should compare your current status against where you were and appreciate how you are moving forward

    As for age

    During university my best mate was 27 who dropped out of his final year, grabbed a random job, then went to college to get a BTEC so they could start the degree.

    It was similar in my graduate intake, we had a 26 year old who had been a brickie for 5 years before getting a comp sci degree.

    The first person I line managed was a junior 15 years older than me, who had a completely different career stream. They had the house, kids, had managed big teams, etc… honestly I learnt tons from them.