I’d actually argue Python stops people learning how to solve problems.

I love teaching juniors and have done so for 10 years but I’ve noticed in the last 4-5 years since Python became the popular choice at universities Graduates aren’t learning anything about Static Types, Memory Management, Object Oriented Programming, Data Encapsulation, Composition, Service Oriented Architecture, etc…

I used to expect most graduates to have a mixed grounding in those concepts and would find excuses for them to work on a small UI projects. I would do this as it gets them used to solving a small problem and UI’s give instant feedback. As Python became dominate university teaching language the graduates aren’t spending their time learning Typescript, Angular, HTML, etc… but instead getting overwhelmed by the concept of types.

Those concepts I want them to learn were created to help make solving problems easier and each has their strengths and weaknesses but most graduates are coming through only knowing how to lay out a small amount of procedural logic using Python and really struggling to move beyond that.

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 shall have a think where it makes sense to create one. Lits were created a while back and seem to have been purged

Short Message Format = Tweet Thread = post

KBin calls a community a “magazine” and Magazine mods can associate hashtags with the Magazine.

The idea is from your instance you can look at the thread view or microblog (tweet) view.

KBin was started by a person called Ernest, he doesn’t seem particularly great at accepting outside help. A number of people who wanted to contribute but found their work stuck for review for months forked KBin and called it MBin.

Have you considered migrating to a magazine on Kbin/MBin?

The daily updates are quite useful but currently my means of finding them is via your posts in Reddit. The post views in Lemmy discourage you to go into spaces and I don’t think thread pinning translates accross instances.

KBin/Mbin support the short message format in Activity Pub so creating a thread on that platform should reflect into Mastodon and Mastodon comments will come through into the post. If you add a couple of hashtags it would also help discoverability.

Your posts are the most useful ones for daily summaries and probably the most useful contribution to the reddit starship dev thread.

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

Uhh how?

The rate of new features/changes is far higher, uptime went through a bumpy transition but is back to normal. From an engineering perspective it supports my point.

Twitters issues are Elon scaring away advertisers/annoying governments/content creators through his hard line on free speech allowing an explosion in hate speech.

MBin is a fork by a group who tried to push into KBin but couldn’t. There seems to be at least 4 active committers and stuff gets merged.

You will see a number of the KBin instances moved over https://fedidb.org/software/mbin

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

deleted by creator

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

The team/organisations knowledge is a huge factor but its easy to fall into a trap where no matter what the problem is the solution is X language.

If I have an organisation that knows C# and we need to build a Web Application. I would suggest we need to learn Node.js and Typescript and not invest in a solution that turns C# into web pages.

Technical Leads are not rational beings and lots of software is developed from an emotional stand point.

Engineering is trade offs, every technical decision you make has a pro/con.

What you should do is write out the core requirements/constraints.Then you weigh the choices to select the option that best meets it.

What actually happens is someone really likes X framework, Y programming language or Z methodology and so decides the solution and then looks for reasons to justify it.

Currently the obvious tell is if they pitch Rust. I am not saying Rust is bad, but you’ll notice they will extoll the memory safety or performance and forget about the actual requirements of the project.

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.

So I know thats a joke but…

With Java 11’s inclusion of ‘var’ I have successfully copied JavaScript code into Java without needing to change anything.

I judge the direction Java is going in

Society is complex, visting a country is different from living there an extended period of time and even then even small geographical distances can result in huge changes in culture.

For example if you started in London and travelled the M4 to Bristol and carried on through Newport and then Cardiff. You would find dramatic differences in housing costs, religiousness, sports played (e.g. football to rugby), views on public transport, job market, jobs people work, education level, favourite drinks, marriage, etc…

You could spend 3 months basing yourself in any one of those locations and derive completely different views on what is wrong with the UK.

Which is why the OP brushed this off as nonsense. It also isn’t uncommon for Americans to go somewhere and suggest it would be miles better if it was exactly like the USA, which is why you get the ad hominem.

It would be like a British Tourist suggesting they don’t drink enough larger or accusing themof being savages for putting salt in tea

The splash screen (boot screen instead of text)used to get me. It provided by an application called ‘Plymouth’.

You used to need to install it and configure grub, however I think if you go into ‘System Settings’ and type ‘Splash’ KDE has an option to install and choose the screen

I thought server side anti cheat was the most effective. Since it can’t be modified by clients and tracks clients for impossible behaviour.