In other IDEs this discards tracked changes, untracked files usually stay untouched.
In my opinion, it’s a combination of user error and bad implementation here
In other IDEs this discards tracked changes, untracked files usually stay untouched.
In my opinion, it’s a combination of user error and bad implementation here
I guess not everyone likes his helpers
Also a lot of infrastructure in Africa is being funded in China, their position there is only going to grow stronger.
That’s why it’s called piracy, not theft.
You’re using a purposely convoluted example from the spec. And I think it shows exactly how TOML is better than JSON for creating config files.
The TOML file is a lot easier to scan than the hopelessly messy json file. The mix of indentation and symbols used in JSON really does not do well in bigger configuration files.
Seems to have the same effect to me, very weird.
Normally I tend to skim text pretty quickly, skipping words, but this makes my focus snap back to read every word, very funky feeling.
Kapsalon superiority
You forget 11. Shoot me, Daddy Musk
Haven’t heard that term, it’s usually called “ecoduct” over here.
This post misses the entire point of JSON/TOML/YAML and the big advantage it has over databases: readability.
Using a file based approach sounds horrible. Context gets lost very easily, as I need to browse and match outputs of a ton of files to get the full picture, where the traditional methods allow me to see that nearly instantly.
I also chuckled at the exact, horribly confusing example you give: upd_at. A metadata file for an object that already inherently has that metadata. It’s metadata on top of metadata, which makes it all the more confusing what the actual truth for the object is.
So trying to hack hackthebox is not permitted? Confusion is the name of the game
I use syncthing, which works great unless you need a ton of space.
Bloatware and probably spyware. They’re all out to get your data.
No, you have it the other way around. It means copyright owners can share “corrupted” versions of their works and the AI can still use it. Possible AI leaks won’t return the original work, since it was never used.
Of course I think this is only one aspect of why artists wouldn’t share their works, but it’s not the point the paper is trying to make. They’re just giving an aspect of how it could be useful.
It’s not what the paper is about at all, seems this is just shit journalism again.
All the paper says about copyright is that this method is more secure because AI can sometimes spit out training examples.
The fun thing about web pages is that you can share an url instead of taking a screenshot:
Forks are meaningless.
Unless a team steps up to continue development, the project is as good as dead.
No, this is exported by Greenland.
They’re using only chunks that have already separated, transporting it on outgoing cargo ships that are already empty and it becomes one of the few export products for Greenland.
Weird idea, but there are a few redeeming points if you look at the full story.
Nothing has been said about time travel though
What’s more infuriating is that they immediately gave in and removed it without any discussion