Also, Safari on Windows had low usage, and was probably a pain to maintain. Swift cross platform is more about abstracting out Apple specific things (like the standard library and UI toolkit). Apple has already been investing multi-year efforts into Swift on the server for longer than Safari on Windows existed. The last couple versions of Swift (~3-4years of development) have been almost entirely focused on safe concurrency, which is intended for server-side development.
Actually, this isn’t true. Apple has a vested interest in cross platform Swift. They’ve been pushing hard for Swift on Linux because they want Swift to run on servers, and they’re right to. Look at how hard JavaScript dominates on the server-side because of one language everywhere.
I’ve worked with Swift a bunch for Apple platforms, am mildly familiar with how it works on other platforms. It should be able to compile on a wide host of platforms with minimal/no issues. The runtime dependencies are localized to Apple platforms, and I think the dominant UI toolkit on other platforms is a Swift port of qt. So it should be just fine?
What’s wrong with Business Insider? Genuine question
You declare it in the package.json as a category when publishing. It’s completely self-selected with no oversight, review, or enforced permissions.
I believe they’re referring to lower down in the article, where the researchers analyzed existing extensions on the marketplace:
After the successful experiment, the researchers decided to dive into the threat landscape of the VSCode Marketplace, using a custom tool they developed named ‘ExtensionTotal’ to find high-risk extensions, unpack them, and scrutinize suspicious code snippets.
Through this process, they have found the following:
- 1,283 with known malicious code (229 million installs).
- 8,161 communicating with hardcoded IP addresses.
- 1,452 running unknown executables.
- 2,304 that are using another publisher’s Github repo, indicating they are a copycat.
The WinAmp maybe sorta open-sourcing is interesting. I’ve never used it (aside from downloading it to get MilkDrop working in Foobar2000).
That’s how I feel about RuneScape! I don’t find it a particularly fun game, but the music is so great and iconic and fits the game so well, I hear it and want to play.
I didn’t even know this happened lol
I’ve never played any others but SR4 is great, super ridiculous
These names are really fun! Good ones to add to my list…
I believe publishers are responsible for sales, including what countries it’s for sale in. It’s not really up to the devs. Not in the games industry though, so could be wrong.
But a unique identifier in game doesn’t actually enforce bans, because what’s stopping someone from creating a new one? VS if you create a PSN account, you need some sort of verification (e.g. email address).
They could’ve done something similar with a non PSN login, though people would’ve probably still complained. And for them, it’s not 3rd party because it’s published by Sony IIRC, so it’s actually an in house system.
I also don’t own the game, but I just wanted to point out the reason in their argument isn’t entirely invalid.
What’s stopping you from deleting the game, redownloading it, and setting a new account name? Etc
I assume they’re talking about player names, not usernames - steam usernames are unique, but steam player names can be whatever you want and are often duplicates.
Cool to see the Immich team going full time. I don’t use it personally but I hear great things
You mean like git sparse-checkout
? Admittedly experimental but useful
Do you mean admonitions? E.g. info, warning, etc? There’s precedent for that in commonly-used open source implementations, e.g. obsidian.md (which uses the same syntax, and started before). What semantics does it break? It’s designed to read well in plaintext and render nicely even if used in a renderer that doesn’t support admonitions, e.g.
[!NOTE] Information the user should notice even if skimming.
As opposed to other common markdownish implementations that use nonsensical plaintext which renders poorly in alternative renderers. Here’s a discussion on the topic in the CommonMark forums.
My “scrum leader” (who we handled agile just fine without before) is constantly complaining about points or priorities shifting, to the point that he’ll tell us to not put what we’re actually working on on the board because it’ll mess up the burndown chart.
One of the 4 values of agile is “responding to change over following a plan”. He’s parroted this to us before, and yet still doesn’t seem to see the irony.
Rust is a lot more niche and intimidating of a language compared to Swift. Swift is familiar to C++ devs, while modernizing the language and toolchain, and providing safety guarantees.