Olissipo

Fellow PT-PT ISO user here. And although I use PT-PT in the OS, both my mechanical keyboards' physical layout is DE ISO, which has most special symbols in the same place. (finding DE keyboards is easier)

I've considered switching to UK ISO before. Typing brackets "[] {}" and a semicolon ";" is harder in PT-PT. Especially the curly brackets {}, which are really awkward to type with my small hands.

One that is written in C and also has a Python module: https://aubio.org/

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:

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.

May be a coincidence, but it stopped launching for me too. Worked Monday and Tuesday, yesterday I didn't try to play, today it didn't work.

Tried:

• running "verify integrity of game files"
• forcing Proton,
• clearing shader cache
• attempted various launch options, like vulkan, fullscreen, and windowed
• update all flatpaks (since I installed steam through flatpak)
• reboot

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.

you can easily forget to catch it and handle it properly

Even if I coded the form by hand and that happened, it's on me, not on the programming language.

But I don't, I use a framework which handles all that boilerplate validation for me.

When you say user, you mean a user of a function? In that case PHP would throw a TypeError, and presumably only happens when developing/testing.

If you mean in production, like when submitting a form, an Exception may be thrown. In which case you catch it and return some error message to the user saying the date string is invalid.

My point is, you won't ever try. You'd only use "weak" variables inside the function you're working on.

It's explicit when you absolutely need it to be, when the function is being called and you need to know what arguments to pass and what it'll return

I like it in modern PHP, it's balanced. As strict or as loose as you need in each context.

Typed function parameters, function returns and object properties.

But otherwise I can make a DateTime object become a string and vice-versa, for example.

From the F1 channel, here it is in action (shakedown test).

I don't know if we're discussing semantics. A performance score is attributed, and before the fix their scores were all 166. It doesn't work, as you said. So the consequence is the preferred core being "random", isn't it?