is Apple File System going to become the best file system?

File: 1478674324867.png (595KB, 960x640px) Image search: [Google]

595KB, 960x640px

>>58580416
is APFS gonna make file systems great again?

>>58580416
If it's FOSS, I'm all for it. Especially the encryption part. If apple can mainstream encryption, other tech companies will follow.

Just checked out their features page. This is actually quite interesting.

: >https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/Features/Features.html

>Clones

>A clone is a nearly instantaneous copy of a file >or directory that occupies no additional space >for file data. Clones allow the operating system >to make fast, power-efficient file copies on the >same volume without occupying additional >storage space.

Also supports snapshots.

>>58580552
Looking into it, its actually just a link to the original file. Thats something every os has hd for a while.

>>58580552
cloning in action: https://www.youtube.com/watch?v=90Ml2jGUyG8

though I believe some other file systems have this already, not sure

Wow, revolutionary.
This isn't BTRFS at all.

>>58580743
Well it wouldn't be if it worked.

>>58580743
More like some spawn of F2FS and btrfs.

>>58580756
Works for facebook but doesn't work for you?
I've been using it with SuSE since Leap and had no problems.

>>58580781
Uh no, I don't have billions to spend to get something that's suppose to be reliable to be reliable. I'm glad to see that it might reach past that very long instability phase.

File: 1484580660439.gif (811KB, 200x177px) Image search: [Google]

811KB, 200x177px

>>58580416
ZFS.
Done.

OS X is a test bed for Apple.

This isn't as stable as BTRFS and anyone who thinks it is is a moron.

>>58580912
OS X no longer exists.

>>58580912
If it's just btrfs with Apple branding and features removed then it should be pretty stable assuming the port isn't a complete fuckup

File: chrome_2017-01-19_19-18-04.png (107KB, 614x798px) Image search: [Google]

107KB, 614x798px

>>58580912
>This isn't as stable as BTRFS
>BTRFS
>Stability
Granted, no one with any sense should be using anything other than mirroring but stuff like this hanging out for so long doesn't bode well.

File: ▄█▀ █▬█ █ █ █ █ █ █ ▀█▀.jpg (38KB, 450x495px) Image search: [Google]

38KB, 450x495px

>>58580416
>>58580552
can't wait to see it niggered up like HFS/HFS+ so I can see shitload of people crying over corrupted data they cloned

File: IMG_0516.jpg (26KB, 480x270px) Image search: [Google]

26KB, 480x270px

>>58580416

>>58580968
Shoulod be fine with mdadm, that's been the de-facto Linux RAID tool for a while and it works fine with btrfs.

>>58580912
It's actually taken from iOS. They don't give a shit about OSX or desktop computers anymore. Remember LZFSE, the Apple file compression which was supposed to be good? It's meant for ARM machines so they can do lempel ziv compression without shitting the floor. In reality, it's worse than 7zip, and in many cases, Gzip. They might as well put iOS on their last desktop computers before they kill off the Macintosh.

Why would you use anything other than EXT4, XFS, or ZFS?

I read that as Noob Shill

File: 0d248fc2e6d6b4f3a001baebb1986b3d0242e8edbdfa76c94dab486617055b47.jpg (46KB, 821x459px) Image search: [Google]

46KB, 821x459px

>>58580976
>User keeps backup copy of file in case something goes wrong
>No redundancy on soldered SSD hits a bit flip and all "copies" of file are destroyed
I see no way this can go wrong.

>>58581118
In what machine is the SSD soldiered?

>>58581182
In just about every ultrabook on the planet baring some very rare exceptions.

God, I hate ultrabooks, what's the fucking difference with netbooks from half a decade ago?

>Knob Hill

>>58581210
reduce battery size and remove ports because "muh thin" but also add a shit tier processor so the user doesn't notice the gimped battery size.

>>58581182
on the newest macbook

File: 1483366270781.jpg (34KB, 552x800px) Image search: [Google]

34KB, 552x800px

>>58580416
>is a filesystem made by the most incompetent street shitters that made the worst file system in the history of computing going to become the best filesystem?

>>58580552
clones (aka copy-on-write snapshots) aren't new. btrfs and zfs have had them for ages

>>58581303
Yeah but they aren't as good as Apple Clones.

>2017
>still not ready for boot disc

DROPED!

>>58580416
>designed to scale from an apple watch to a mac pro
that's not very scalable

>>58580552
that description is exactly what reflinks are in linux

>>58581005
>using software raid
>portability
Nah nigga, get a raid card.

>>58581480
>hardware RAID
>2017

Hahaha no

>>58581480
wat, your post makes no sense

>using software raid
>portability

here you suggest software raid isn't portable, how are they not? they're entirely hardware independent

>Nah nigga, get a raid card.
"mah nigga" is a term of agreement, then you say "get a raid card", disagreeing with his use of software raid

are you new to 4chan or what?

it will but the pedos and pajeets on /g/ will never appreciate it and stick to C and whatever the hell they know

>>58581296
/thread

File: 47e653b16fc321d7c3b5dd93bb0fe51039870e3f6ca4921e670b8e2c830983a2.jpg (32KB, 600x450px) Image search: [Google]

32KB, 600x450px

>>58581480
The only RAID card necessary for would be a QAT offload card for my software RAID's native compression.

>>58580644
you're thinking of sym/hardlinks, to explain them;
hardlink: two or more "files" that link to the same data, they are separated by metadata only, editing the data of one edits them all
symlink: similar to above, but works more like a "shortcut", the symlink is a special type of file which references another file by path, it can be placed on another filesystem, unlike a hardlink, but it becomes invalid when the original file is deleted/unavailable
reflink: like a hardlink, but acts like separate files when modified, effectively a (deduplicated) real copy

>>58580552
>sparse files
hold up, HFS+ didn't support sparse files? really?

>>58581441
Yeah but this will be at FS level. OS X had symlinks for ages as well.

>>58580925
OS X is everything before 10.12

>>58582013
>this will be at FS level.
as opposed to?

>OS X had symlinks for ages as well.
not sure how this is relevant

File: 1436519677048.jpg (33KB, 361x500px) Image search: [Google]

33KB, 361x500px

>>58580416
Can't wait my mane
>Space Sharing allows multiple file systems to share the same underlying free space on a physical volume. Unlike rigid partitioning schemes that pre-allocate a fixed amount of space for each file system, APFS-formatted volumes can grow and shrink without volume repartitioning.
>Each volume in an APFS container reports the same available disk space, which is equal to the total available disk space of the container. For example, for an APFS container with a capacity of 100GB that contains volume A (which uses 10GB) and volume B (which uses 20GB), the free space reported for both volumes A and B is 70GB (100GB - 10GB - 20GB).

>>58582231
aka subvolumes, which btrfs and a couple other filesystems also already support

>>58581296
HFS+ is considered bad in many ways mostly because it hasn't had a redesign since its initial release in 1998 and was only extended with modern features

>>58581319
What?

>>58581296
This.

>>58580898
>ZFS
proprietary garbage.

File: 1446453098814.gif (180KB, 404x416px) Image search: [Google]

180KB, 404x416px

all these butt hurt BTRFS defenders

File: 1464338965453.webm (891KB, 912x656px) Image search: [Google]

891KB, 912x656px

>>58582326
>t. HFS using mactoddler

https://www.youtube.com/watch?v=79fvDDPaIoY&t=18m28s

>>58580416
>is Apple File System going to become the best file system?
>homOS X now at 5% market share
lolno

>>58582425
>firmware issues
It's amazing how software has to take account for fucking HARDWARE ISSUES
And worse yet how companies have to tolerate this.

It's like writing some c++ performance module but the CPU you're targeting has bonkers cache that only works during 30 seconds of its internal clock and you're supposed to write around that.

Fuck these niggers

File: 1483950203215.gif (468KB, 500x282px) Image search: [Google]

468KB, 500x282px

>>58582436
>implying that most popular == best

File: 1459741724128.jpg (8KB, 250x165px) Image search: [Google]

8KB, 250x165px

>>58581480
>>58581480
>>58581502

>raid
>2017

>>58582318
Get with the times, gramps, we have ZoL now.

>tfw still on ext4

>>58581296
>the most incompetent street shitters

were not talking about MS

>coming soon to a macshit near you
>drm baked into file system
>drm baked into lightening connectors

>>58580512
>apple can mainstream encryption

>doesn't even know the struggle that was fought for consumer encryption

typical macfag. apple invents another thing. you better be 20 yrs old or in a coma in the 90s

File: 1454138280910.jpg (2KB, 138x138px) Image search: [Google]

2KB, 138x138px

>>58581480

Is there any file system which was not branded next-gen?
>optimized
>encryption
Hello, toddler buzzwords!

>>58580644
>its actually just
it isn't, and if you can't tell the difference you should leave /g/ immediately

>volume pooling
>COW

Wow, it's all the features that are 20 year old. I mean, its good that they're adopting them, but this shit is hardly new.

>>58581210
>God, I hate ultrabooks, what's the fucking difference with netbooks from half a decade ago?
Usable screens.
Usable keyboards.
Usable trackpads.
Not gimped on power.
Actually selling.

>>58584392
better late than never, at least it's not HFS+

File: 1297125155451.gif (2MB, 211x173px) Image search: [Google]

2MB, 211x173px

>>58581480
You only have to execute
>mdadm -Asf && vgchange -ay

To mount a foreign array you dumb nigger.

Enjoy getting an array to load after your card kicks the bucket.

>>58582623
In this case yeah, only a non-dogshit file system would be popular.

>>58580416
Only if you camp in front of an APplE store for 3 nights before launch

>>58581441
>that description is exactly what reflinks are in linux
Except that many, many more people will actually use them in the desktops and laptops.

>>58581784
>hold up, HFS+ didn't support sparse files? really?
Since forever. That's what makes Time Machine work.

>>58582255
>which btrfs and a couple other filesystems
But how many mainline OSs support them?

>>58580711
how is this any different to creating a bunch of shortcuts in windows?

if you modify one, does each change, are only the changes recorded (similar to git) or is a new file created for the newly modified version?

>>58580416
It doesn't even have checksums.

It's like a really shitty f2fs.

>>58581009
Maibe they shifting it all into mobile tegnology because people use this more and we are the neanderthal of tegnology, still using laptops and big computers with mechanical keyboards and mouse that has a cable instead of the modern batteries.
That would explain why the new laptops from Apple cost that much and dont bring much performance, they selling les of those devices but what to maintain the same profit so the price goes up and de performance down (with some meme features to trick people)

>>58585857
Chrome OS, Android

>>58585857
Every Unix out there has some form of LVM, either as a separate layer or baked into a filesystem (ZFS, BTRFS, ...).

>>58580552

It isn't interesting. This is just copy-on-write and such filesystems have been around for fucking ever. It's not very new at all.

>>58586600
Maybe, but nobody cared about such filesysterms until Apple made them.

>>58586734
>Maybe, but nobody cared
Maybe in your underage brain, but ZFS is used at Google, Alibaba, Facebook to a degree(rest is btrfs), Oracle, Microsoft, Twitter, pretty much any BSD deployment, etcetc, you get the idea.
It's currently the best storage filesystem on the planet.

>>58586734
>Maybe, but nobody cared about such filesysterms until Apple made them.

Yes they fucking did. People have been choosing FreeBSD on NAS machines for ages now because ZFS is so good. BTRFS has been a rather big deal in Linux circles for a long time. Google uses ZFS, Facebook uses BTRFS etc.

Filesystems aren't usually something consumers care about, but they are a big deal for sysadmins and people setting up stuff like NAS, servers etc. It's just Apple that's hyping a type of filesystem that has been around for over a decade. It's not new, and it's not too interesting, it's just another COW filesystem implementation.

>>58586756
>>58586854
Lel, as if anyone cared about a bunch of companies, they will now be known because of Apple to everyone and you know it.

>>58587629
Lel, as if I or anyone of value here or elsewhere care about a bunch of normalfaggots that need wikipedia to know what NTP and DHCP mean.

>>58586854
To be fair to Apple, you've gotta admit they do a great job of getting complete fucking retards interested in something as inane as file systems.

>>58587629

Sure thing, but people don't actually give a shit about file systems unless they have a particular requirement for a good one (data integrity for example). This is why Apple and Microsoft both got away with HFS+ and NTFS respectively for the past 20 years, despite the fact that they're both shitty file systems by modern standards.

>>58587675

The complete fucking retards won't be interested in it. They'll use it as some selling point when evangelising on the internet and get told by people who actually know what they're talking about.

thoughts on APFS by ZFS user

http://arstechnica.com/apple/2016/06/a-zfs-developers-analysis-of-the-good-and-bad-in-apples-new-apfs-file-system/