[-] Olissipo@programming.dev 6 points 1 month ago* (last edited 1 month ago)

This one in South Korea is pretty recent (October 2022).

A special police team conducted an investigation of the disaster within a few days of it occurring, and concluded on 13 January 2023 that the police and governments' failure to adequately prepare for the crowds, despite a number of ignored warnings, was the cause of the incident.

[-] Olissipo@programming.dev 5 points 4 months ago* (last edited 4 months ago)

New to Linux: in which case would you stick with an "old-old-stable" release?

Software incompatibility?

54
submitted 4 months ago* (last edited 4 months ago) by Olissipo@programming.dev to c/linux@programming.dev

The Debian Long Term Support (LTS) Team hereby announces that Debian 10 "buster" support will reach its end-of-life on June 30, 2024, nearly five years after its initial release on July 6th, 2019.

Starting in July, Debian will not provide further security updates for Debian 10. A subset of "buster" packages will be supported by external parties. Detailed information can be found at Extended LTS.

The Debian LTS Team will prepare afterwards the transition to Debian 11 "bullseye", the current oldstable release. Thanks to the combined effort of different teams including the Security Team, the Release Team, and the LTS Team, the Debian 11 life cycle will also encompass five years. To make the life cycle of Debian releases easier to follow, the related Debian teams have agreed on the following schedule: three years of regular support plus two years of Long Term Support. The LTS Team will take over support from the Security and the Release Teams on August 14, 2024, three years after the initial release on August 14, 2021. The final point update release for "bullseye" will be published soon after the final Debian 11 Security Advisory (DSA) will be issued.

Debian 11 will receive Long Term Support until August 31, 2026. The supported architectures remain amd64, i386, arm64 and armhf.

[-] Olissipo@programming.dev 15 points 5 months ago* (last edited 5 months ago)

At first glance the difference in width comes from the front wings, which protruded beyond the wheels in the '22 cars.

So hopefully the wings last longer in wheel to wheel action.

[-] Olissipo@programming.dev 4 points 5 months ago* (last edited 5 months ago)

restricting the total amount used and basically anything else makes more sense

Oh you meant eliminate the flow limit, I thought you meant eliminate the fuel itself. And I agree (with the caveat you said, also limiting the total amount).

[-] Olissipo@programming.dev 7 points 5 months ago* (last edited 5 months ago)

That won't happen for 15 years at least, only Formula E can be fully electric.

With an FIA exclusivity deal through 2039 to be the sole EV single-seat series on the FIA menu, Formula E has plenty of time to grow.

https://www.autoweek.com/racing/more-racing/a44319865/formula-e-ceo-jeff-dodds-sees-sustainable-future-for-electric-racing-series/

[-] Olissipo@programming.dev 57 points 6 months ago* (last edited 6 months ago)

Funny story. 50 years ago, to this very day, a revolution occurred in which Portugal took down its dictatorship.

The following day some public administrator/manager sent a letter complaining about people missing work!

Translation after the letter

Your Excellency Director General

I inform Your Excellency that yesterday, April 25, 1974, several employees were absent from work, claiming that a revolution had occurred in the country.

I clarify that this revolution was not authorized by superiors, and no justification was seen for the absences, especially as the service was considerably delayed.

As the current legislation does not provide for absences due to the occurrence of revolutions, I submit the matter to your high discretion, in the certainty that it will deserve due attention.

1
submitted 6 months ago* (last edited 6 months ago) by Olissipo@programming.dev to c/wordpress@lemmy.world

This might not be new, I hadn't dealt with WordPress/WooCommerce in a while.

Currently (v8.8.2) in a new WooCommerce installation the "Checkout" page is created using blocks, like so:

<!-- wp:woocommerce/checkout-payment-block -->
<div class="wp-block-woocommerce-checkout-payment-block"></div>
<!-- /wp:woocommerce/checkout-payment-block -->

(...)

The problem

This might introduce breaking changes to the plugins and themes you normally use. For example, I couldn't add a new field - programatically or using a plugin.

The fix

Remove the blocks and revert to using the shortcode:

[woocommerce_checkout]

[-] Olissipo@programming.dev 3 points 6 months ago

The band played 2 early albums + their latest one in sequence. Listening to whole albums in one go was great for many reasons.

[-] Olissipo@programming.dev 7 points 11 months ago

Not a fan of datalist:

  • Barely works in Firefox (need to click again after initial focus);
  • Doesn't work at all in Firefox mobile (if there is some magic to show the options, I don't know what is);
  • In Chromium and Safari mobile (tested through appetize.io), I don't like how similar it is to a select:

Somewhat liked Chrome's implementation in Android:

[-] Olissipo@programming.dev 11 points 1 year ago

I don't agree with the problem they aim to solve with those goals.

But today it takes several years of mastering tools and frameworks to get to that stage. HTML First principles should allow people to unlock that feeling, and level of mastery, much earlier on in their coding journey.

The onboarding process can be made easier for devs new to the project (junior or senior) with decent documentation. Just enough install/build the project in their local machine and understand the gist of the technologies.

[-] Olissipo@programming.dev 4 points 1 year ago

I'm running a 6700XT and weirdly enough it pre-compiled in Linux but not in Windows.

It's really stuttery for a while in Windows, with low GPU usage and erratic frequency, until it normalizes.

I'm getting none of that in Linux, smooth from the start in-game. Only getting some weird fps fluctuation in the start menu.

17
[-] Olissipo@programming.dev 3 points 1 year ago* (last edited 1 year ago)
[-] Olissipo@programming.dev 5 points 1 year ago

Apparently there's a bug in an AMD's driver. It was supposed to assign processes based on each core's self reported performance, but because of the bug it was random.

This "self reported performance" is based on evaluation done to the cores in the fab process, by AMD. Meaning, due to imperfections some cores are a bit better than others.

view more: next ›

Olissipo

joined 1 year ago