When I searched for text "github" I did not find anything. But searching in the inspector to cover urls:
Firefox and related code is stored in our git repository.
Which makes it all the more confusing. Stored there, but patches only elsewhere?
Really, for a "moved their sources" claim I'd prefer some form of announcement or docs that describe this.
While the 2nd approach is not wrong, the first method is considered more Pythonic. Many people don’t agree, but I’ve already put forward my points in a previous article on that debate.
Does Pythonic mean best practice in the python community or "good python"?
If "many people don't agree", how can they claim it to be "pythonic"? Isn't that contradictory?
What makes you think only GitHub is celebrating?
without downloading them (client side)
if they're client side they must be downloaded
The EU passed laws that require companies (under conditions) to ensure base requirements in their supply chain.
I think a digital equivalent could be possible and similar. Requiring reasonable security and sustainability assessment.
It's not very obvious or simple to enforce, but would set requirements, and open up opportunities for fines and prosecution.
First half is a general introduction, second half is an introduction to their product Digma, which is limited to Java and IntelliJ.
Currently, Digma fully supports Java and IntelliJ, along with related frameworks such as Spring, Spring Boot, Dropwizard, and Micronaut. If you’re interested in other languages, you can find more information here.
Overall it feels shallow to me.
From what I see they didn't even support the claims they set out to present. They show a few screens of their tool, but never how that would "avoid breaking changes". The conclusion is incredibly generic. Feels like publicity/promotion and keywords content was the goal rather than actually sharing information. OP only posting their Digma content fits the impression of PR too.
How do you self-review while writing? What do you mean by that?
I see it as different phases of development, mindset, and focus. You inherently can't be in multiple at the same time.
It makes no sense to be thorough during experimental and iterative exploration. That'd be wasted effort.
After finding a solution, and writing it out, a self-review will make you take a systematic, verifying review mindset.
Mastodon is a Fediverse platform. Lemmy is too. Anyone can host their own Mastodon and Lemmy instances.
When a user uploads an image or video on Mastodon instance 1, and a user of Mastodon instance 2 is following them, that image or video is copied over to Mastodon instance 2 - because that's where that user resides.
This means content gets replicated and duplicated across every shared-network instance. Resulting in resilience, but also ~~exponential~~, excessive storage needs.
OP is suggesting that media files should be shared across platform instances so that they don't get duplicated many times. This would significantly reduce storage and bandwidth needs and use for the platform instances themselves, offloading and centralizing media file concerns.
Go has goto too. They surely did not "mindlessly copy" it.
The standard library makes use of it. So they most definitely see a warranted use-case for it.
OP argument against using it in high level languages may still hold though. Go may have introduced it as a systems language which allows control over alternative implementations.
Static typically refers to static pages. Which can have dynamic elements, but no backend.
IE: you can’t have a contact form without paying a 3rd party.
Unless you open an email client or other url to forward the contracting I don't consider that (purely) static anymore.
Given that, I'm not sure what you even want "static gen" for? You may be looking for the wrong thing.
Looks like they weren't able to borrow a 'was' for the sentence.