Ferk

And please, get all countries to actually start properly accepting ISO 8601 format for dates as a mandatory universal standard…

Obligatory reference: https://xkcd.com/1179/

It’s also not that uncommon of an acronym in web tech, all the first results when searching “PWA” are consistent and it’s a very common way to refer to that technology. The term PWA has made the news in tech channels a few times before (like when Firefox discontinued support for PWA on desktop).

Even if they said “Progressive Web Apps” it would not have been immediatelly clear what that means for anyone who is not familiar with what PWA is. It’s also not the only acronym they use in the article without explaining it (eg. “API”, or “iOS” which is also an acronym on itself), it just so happens that it’s likely not a well known one in this particular lemmy community where the article was posted. The author advertises himself as a writer dedicated to web technologies (PWA and Web Component in particular), so it would be silly if he has to explain what those are on every of his posts.

But C syntax clearly hints to int *p being the expected format.

Otherwise you would only need to do int* p, q to declare two pointers… however doing that only declares p as pointer. You are actually required to type * in front of each variable name intended to hold a pointer in the declaration: int *p, *q;

I feel it’s a balance. Each operation has a purpose.

Rebasing makes sense when you are working in a feature branch together with other people so you rebase your own commits to keep the feature branch lean before you finally merge it into the main branch, instead of polluting the history with a hard to follow mess of sub branches for each person. Or when you yourself ended up needing to rewrite (or squash) some commits to clean up / reorganize related changes for the same feature. Or when you already committed something locally without realizing you were not on sync with the latest version of a remote branch you are working on and you don’t wanna have it as a 1-single-commit branch that has to be merged.

Squashing with git merge --squash is also very situational… ideally you wouldn’t need it if your commits are not messy/tiny/redundant enough that combining them together makes it better.

Same effort as getting &* and () on a US layout (so, modifier key + 7 8 9 0, respectively), the difference is you press AltGr instead of Shift as the modifier. And i’d argue its actually easier to press AltGr with the thumb than shift with the pinky.

I use EURkey, which is basically a superset of the US layout extended to support symbols from several European languages.

it’s even ISO standardized

Not only are there other ones that are also ISO standards when it comes to software layouts, but funny enough, when it comes to physical layouts, US keyboards normally follow an ANSI standard (not an ISO one), whereas many non-US keyboards typically follow a physical key layout known as “ISO Keyboard”, so one could argue those are more of an “ISO” standard.

https://upload.wikimedia.org/wikipedia/commons/b/b2/Physical_keyboard_layouts_comparison_ANSI_ISO_KS_ABNT_JIS.png

right ctrl + left shift + 9 will do?

No keyboard layout uses ctrl like that… in fact, I don’t think you ever really need to press more than one modifier in any standard non-US keyboard. Unless you have a very advanced custom layout with fancy extra glyphs… but definitelly not for the typical programming symbols.

ISO keyboards actually have one more key and one more modifier (“AltGr”, which is different from “Alt”) than the ANSI keyboards.

In fact, depending on the symbol it might be easier in some cases. No need to press “shift” or anything for a # or a + in a German QWERTZ keyboard, unlike in the US one. Though of course for some other ones (like = or \) you might need to press 1 modifier… but never more than 1, so it isn’t any harder than doing a ) or a _ in the US layout.

Yes… how is “reducing exclamation marks” a good thing when you do it by adding a ' (not to be confused with , ´,‘or’` …which are all different characters).

Does this rely on the assumption that everyone uses a US QWERTY keyboard where ! happens to be slightly more inconvenient than typing '?

Then check-out their due date, specially if they have been left out in a stack for too long, before you pop one out.

Many hosts allow you to set rules to protect branches from getting their commits removed in the remote (in fact, I think that’s the default for gitlab main branches) or to prevent people from pushing their commits to them directly.
I expect even “the main branch has to stay more or less in sync with origin/main” can be automated… though it might not be what you always want, depending how you work.

git switch

Oh wow, I didn’t know about this one. I guess it’s relatively new?

Is it just a convenience command to try and be more specific (less multi purpose) than git checkout for switching branches or does it bring any extra benefit? …I’m already quite used to my git co alias, to the point that it’s almost hardwired to my fingers by now :P

coders revealed to 404 Media that “some of Kirsina’s Instagram posts are word-for-word copies of Sizovs’ LinkedIn posts, sometimes published more than a year later.” In addition, “some of the images [Kirsina] posted on Instagram show computer monitors with code that show her logged in under Sizovs’ name.” But perhaps most striking is the fact that an administrator told 404 Media that both Sizovs’ and Kirsina’s accounts were banned “multiple times” by the Lobste.rs coding forum for “sockpuppeting”—using a false identity to deceive others—in 2019 and 2020.

Lol… for reference, this is the twitter account: https://nitter.net/UnicornCoding

It’s full of advertisements about the DevTernity conference… as does the instagram, which has so many professional-looking photos that feel like she was an actual model, always with different backgrounds. Is the laptop wirelessly streaming to the ultrawide screen in her Twitter profile picture? because I see no cables, she’s not even connected to a charger, how long of a coding session can you have like that?

I agree with the sentiment. But I didn’t want to be too critical about it, because like you said, it’s their project and they don’t have to give particularly strong reasons for what they choose to spend their time on.

And after all, this approach is probably fitting for a non-POSIX compliant shell like fish. I expect that those who would rather break compatibility in exchange for a “look & feel” that appears more “modern” are likely to also prefer breaking support for some old but stable tooling by switching to a more “modern” language ecosystem, even if doesn’t have the battle-tested history and wide compatibility of more traditional languages. Those who care about that kind of stability might be better off using more traditional shells anyway. So maybe doing this would actually make working on fish more attractive for the kind of devs who would be more likely to contribute. We’ll see.

Just wondering: why was the rewrite necessary?

It doesn’t look like they did it for performance, since they claim the code might actually be slower, at least for now.
Was there a particular reason that made Rust give a gain significant enough to deserve a full rewrite or was it just because the maintainers wanted to restructure things anyway and particularly liked Rust?

EDIT: Ok, found their reasoning after some digging.
It seems to be a combination of both things. They believe that switching will attract contributors and make it more modern… but also they seem to have had some trouble with thread safety in C++ that would have required them to do some restructuring anyway.

It’s also kinda annoying to have a history full of “merge” commits polluting the commit messages and an entwined mix of parallel branches crossing each other at every merge all over the timeline. Rebasing makes things so much cleaner, keeping the branches separate until a proper merge is needed once the branch is ready.

be nice

What niceness level exactly?
The most nice I can be in my system is -20… but being too nice to one process leaves others with less time and resources in their life.

Me neither? That’s why I was hoping they might have added some markdown extension.

I have done it in the past with mardown-it-wikilinks npm package, for example.

Also, I’d argue the wikilinks (internal links) using [[any term here]] from Wikipedia, that optionally allow automatically inferring the link, is much more comfortable (and less error-prone) for the usecase of a wiki system, than the [text required](/link_here_also_required_even_when_redundant) from markdown.

I was hoping they might have added some markdown extension to do something similar, but it seems not.

Free version is excluded. No charging tiny side projects, or students or something, it only affects already paying customers.

Wasn’t the free version already excluded from the changes before?

What they have done for the Free version is set the limit to 200k (it was 100k before) and they’ll no longer be requiring the Unity logo to be shown, even on the free version.

Yes, the way his hand is positioned, it would not have worked if they had wanted to make it hold the wooden stick. They’d have needed to edit the hand too much and it would have likely been noticeable / even weirder.

Probably they decided: f*ck it, let them grab it however they want. Maybe it’ll even become a thing.

And it looks like it worked, since we are talking about it and spreading the ad. Smart advertising, imho.