https://www.news1.kr/articles/?5291730

Libraries We Use

The following sets forth attribution notices for third party software that may be contained in portions of the Unicorn product. We thank the open source community for all of their contributions.

AFNetworking

                
The following software may be included in this product: AFNetworking. This software contains the following license and notice below:

Copyright (c) 2011-2016 Alamofire Software Foundation (http://alamofire.org/)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
                
            

UICKeyChainStore

                
The following software may be included in this product: UICKeyChainStore. This software contains the following license and notice below:

The MIT License

Copyright (c) 2011 kishikawa katsumi

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
                
            

Toast

                
The following software may be included in this product: Toast. This software contains the following license and notice below:

Copyright (c) 2011-2017 Charles Scalesse.

Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
                
            

Reachability

                
The following software may be included in this product: Reachability. This software contains the following license and notice below:

Copyright (c) 2011-2013, Tony Million.
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
                
            

GetRated

                
The following software may be included in this product: GetRated. This software contains the following license and notice below:

Copyright © 2017 Neil Morton. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.


Copyright © for portions of GetRated are held by Charcoal Design, 2011
as part of iRate.

This software is provided 'as-is', without any express or implied
warranty.  In no event will the authors be held liable for any damages
arising from the use of this software.

Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software
in a product, an acknowledgment in the product documentation would be
appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.
                
            

MMPulseView

                
The following software may be included in this product: MMPulseView. This software contains the following license and notice below:

The MIT License (MIT)

Copyright (c) 2015 ralph li

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
                
            

firebase-ios-sdk

                
The following software may be included in this product: firebase-ios-sdk. This software contains the following license and notice below:


Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.

You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!)  The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
                
            

#import <UIKit/UIKit.h>

#import "AppDelegate.h"

int main(int argc, char *argv[])

{

    @autoreleasepool {

         return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));

    }

}

import UIKit

autoreleasepool {

    UIApplicationMain(Process.argc, Process.unsafeArgv, nil, NSStringFromClass(AppDelegate.self))

}

UIApplicationMain(CommandLine.argc,

    UnsafeMutableRawPointer(CommandLine.unsafeArgv).bindMemory(to: UnsafeMutablePointer<Int8>.self, capacity: Int(CommandLine.argc)), nil, NSStringFromClass(AppDelegate.self))

MAKING bridging header file

#import "AppDelegate.h"

//:configuration = Debug
SWIFT_OBJC_BRIDGING_HEADER = migrating/-Bridging-Header.h

//:configuration = Distribution
SWIFT_OBJC_BRIDGING_HEADER = migrating/-Bridging-Header.h

//:configuration = Release
SWIFT_OBJC_BRIDGING_HEADER = migrating/-Bridging-Header.h

//:completeSettings = some
SWIFT_OBJC_BRIDGING_HEADER

error: using bridging headers with module interfaces is unsupported

//:configuration = Debug
BUILD_LIBRARY_FOR_DISTRIBUTION = NO

//:configuration = Distribution
BUILD_LIBRARY_FOR_DISTRIBUTION = NO

//:configuration = Release
BUILD_LIBRARY_FOR_DISTRIBUTION = NO

//:completeSettings = some
BUILD_LIBRARY_FOR_DISTRIBUTION

https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html

A file system handles the persistent storage of data files, apps, and the files associated with the operating system itself. Therefore, the file system is one of the fundamental resources used by all processes.

APFS is the default file system in macOS, iOS, watchOS, and tvOS. APFS replaces HFS+ as the default file system for iOS 10.3 and later, and macOS High Sierra and later. macOS additionally supports a variety of other formats, as described in Supported File Systems.

Regardless of the underlying format, all of the disks attached to the device—whether they are physically plugged in or are connected indirectly through the network—contribute space to create a single collection of files. Because the number of files can easily be many millions, the file system uses directories to create a hierarchical organization. Although the basic directory structures are similar for iOS and macOS, there are differences in the way each system organizes apps and user data.

Before you begin writing code that interacts with the file system, you should first understand a little about the organization of file system and the rules that apply to your code. Aside from the basic tenet that you cannot write files to directories for which you do not have appropriate security privileges, apps are also expected to be good citizens and put files in appropriate places. Precisely where you put files depends on the platform, but the overarching goal is to make sure that the user’s files remain easily discoverable and that the files your code uses internally are kept out of the user’s way.

About the iOS File System

The iOS file system is geared toward apps running on their own. To keep the system simple, users of iOS devices do not have direct access to the file system and apps are expected to follow this convention.

iOS Standard Directories: Where Files Reside

For security purposes, an iOS app’s interactions with the file system are limited to the directories inside the app’s sandbox directory. During installation of a new app, the installer creates a number of container directories for the app inside the sandbox directory. Each container directory has a specific role. The bundle container directory holds the app’s bundle, whereas the data container directory holds data for both the app and the user. The data container directory is further divided into a number of subdirectories that the app can use to sort and organize its data. The app may also request access to additional container directories—for example, the iCloud container—at runtime.

These container directories constitute the app’s primary view of the file system. Figure 1-1 shows a representation of the sandbox directory for an app.

Figure 1-1  An iOS app operating within its own sandbox directory

An app is generally prohibited from accessing or creating files outside its container directories. One exception to this rule is when an app uses public system interfaces to access things such as the user’s contacts or music. In those cases, the system frameworks use helper apps to handle any file-related operations needed to read from or modify the appropriate data stores.

Table 1-1 lists some of the more important subdirectories inside the sandbox directory and describes their intended usage. This table also describes any additional access restrictions for each subdirectory and points out whether the directory’s contents are backed up by iTunes and iCloud.

An iOS app may create additional directories in the Documents, Library, and tmp directories. You might do this to better organize the files in those locations.

For information about how to get references to the preceding directories from your iOS app, see Locating Items in the Standard Directories. For tips on where to put files, see Where You Should Put Your App’s Files.

Where You Should Put Your App’s Files

To prevent the syncing and backup processes on iOS devices from taking a long time, be selective about where you place files. Apps that store large files can slow down the process of backing up to iTunes or iCloud. These apps can also consume a large amount of a user's available storage, which may encourage the user to delete the app or disable backup of that app's data to iCloud. With this in mind, you should store app data according to the following guidelines:

• Put user data in Documents/. User data generally includes any files you might want to expose to the user—anything you might want the user to create, import, delete or edit. For a drawing app, user data includes any graphic files the user might create. For a text editor, it includes the text files. Video and audio apps may even include files that the user has downloaded to watch or listen to later.
• Put app-created support files in the Library/Application support/ directory. In general, this directory includes files that the app uses to run but that should remain hidden from the user. This directory can also include data files, configuration files, templates and modified versions of resources loaded from the app bundle.
• Remember that files in Documents/ and Application Support/ are backed up by default. You can exclude files from the backup by calling -[NSURL setResourceValue:forKey:error:] using the NSURLIsExcludedFromBackupKey key. Any file that can be re-created or downloaded must be excluded from the backup. This is particularly important for large media files. If your application downloads video or audio files, make sure they are not included in the backup.
• Put temporary data in the tmp/ directory. Temporary data comprises any data that you do not need to persist for an extended period of time. Remember to delete those files when you are done with them so that they do not continue to consume space on the user’s device. The system will periodically purge these files when your app is not running; therefore, you cannot rely on these files persisting after your app terminates.
• Put data cache files in the Library/Caches/ directory. Cache data can be used for any data that needs to persist longer than temporary data, but not as long as a support file. Generally speaking, the application does not require cache data to operate properly, but it can use cache data to improve performance. Examples of cache data include (but are not limited to) database cache files and transient, downloadable content. Note that the system may delete the Caches/ directory to free up disk space, so your app must be able to re-create or download these files as needed.

About the macOS File System

The macOS file system is designed for Mac computers, where both users and software have access to the file system. Users access the file system directly through the Finder, which presents a user-oriented view of the file system by hiding or renaming some files and directories. Apps access the file system using the system interfaces, which show the complete file system precisely as it appears on disk.

Domains Determine the Placement of Files

In macOS, the file system is divided into multiple domains, which separate files and resources based on their intended usage. This separation provides simplicity for the user, who only needs to worry about a specific subset of files. Arranging files by domain also lets the system apply blanket access privileges to files in that domain, preventing unauthorized users from changing files intentionally or inadvertently.

• The user domain contains resources specific to the users who log in to the system. Although it technically encompasses all users, this domain reflects only the home directory of the current user at runtime. User home directories can reside on the computer’s boot volume (in the /Users directory) or on a network volume. Each user (regardless of privileges) has access to and control over the files in their own home directory.
• The local domain contains resources such as apps that are local to the current computer and shared among all users of that computer. The local domain does not correspond to a single physical directory, but instead consists of several directories on the local boot (and root) volume. This domain is typically managed by the system, but users with administrative privileges may add, remove, or modify items in this domain.
• The network domain contains resources such as apps and documents that are shared among all users of a local area network. Items in this domain are typically located on network file servers and are under the control of a network administrator.
• The system domain contains the system software installed by Apple. The resources in the system domain are required by the system to run. Users cannot add, remove, or alter items in this domain.

Figure 1-2 shows how the local, system, and user domains map to the local file system of a macOS installation. (The network domain is not shown but is similar in many ways to the local domain.) This figure shows the visible directories that the user might see. Depending on the user’s system, other directories may be visible or some of the ones shown here may be hidden.

Figure 1-2  The local macOS file system

For information about the contents of the directories in macOS, see macOS Standard Directories: Where Files Reside. For information about the directories that macOS normally hides from the user (and why), see Hidden Files and Directories: Simplifying the User Experience.

macOS Standard Directories: Where Files Reside

Whether provided by the system or created by your app, every file has its place in macOS. Table 1-2 lists some of the top-level directories in a macOS installation and the types of content that each one contains.

Although the directories in Table 1-2 are the ones seen by macOS users, they are not the only directories present in the file system. macOS hides many directories to prevent users from accessing files that they don’t need to.

Sandboxed macOS App File Containers

macOS apps that are sandboxed have all their Application Support, Cache, temporary directories and other related documents stored within a directory located at a system-defined path that you can obtain by calling the NSHomeDirectory function.

For more information, see App Sandbox Design Guide.

Hidden Files and Directories: Simplifying the User Experience

To simplify the experience for users, the Finder, and some specific user-facing interfaces (such as the Open and Save panels), hide many files and directories that the user should never have to use. Many of the hidden items are system- or app-specific resources that users cannot (or should not) access directly. Among the files and directories that are hidden are the following:

• Dot directories and files. Any file or directory whose name starts with a period (.) character is hidden automatically. This convention is taken from UNIX, which used it to hide system scripts and other special types of files and directories. Two special directories in this category are the . and .. directories, which are references to the current and parent directories respectively.
• UNIX-specific directories. The directories in this category are inherited from traditional UNIX installations. They are an important part of the system’s BSD layer but are more useful to software developers than end users. Some of the more important directories that are hidden include:
  • /bin—Contains essential command-line binaries. Typically, you execute these binaries from command-line scripts.
  • /dev—Contains essential device files, such as mount points for attached hardware.
  • /etc—Contains host-specific configuration files.
  • /sbin—Contains essential system binaries.
  • /tmp—Contains temporary files created by apps and the system.
  • /usr—Contains non-essential command-line binaries, libraries, header files, and other data.
  • /var—Contains log files and other files whose content is variable. (Log files are typically viewed using the Console app.)
• Explicitly hidden files and directories. The Finder may hide specific files or directories that should not be accessed directly by the user. The most notable example of this is the /Volumes directory, which contains a subdirectory for each mounted disk in the local file system from the command line. (The Finder provides a different user interface for accessing local disks.) In macOS 10.7 and later, the Finder also hides the ~/Library directory—that is, the Library directory located in the user’s home directory.
• Packages and bundles. Packages and bundles are directories that the Finder presents to the user as if they were files. Bundles hide the internal workings of executables such as apps and just present a single entity that can be moved around the file system easily. Similarly, packages allow apps to implement complex document formats consisting of multiple individual files while still presenting what appears to be a single document to the user.

Although the Finder and other system interfaces hide files and directories from the user, Cocoa interfaces such as NSFileManager do not filter out files or directories that are normally invisible to users. Thus, code that uses these interfaces theoretically has a complete view of the file system and its contents. (Of course, a process really has access to only those files and directories for which it has appropriate permissions.)

Files and Directories Can Have Alternate Names

In some situations, the Finder presents users with file or directory names that do not match the actual names as they appear in the file system. These names are known as display names and are used only by the Finder and specific system components (such as the Open and Save panels) when presenting file and directory information to the user. Display names improve the user experience by presenting the user with content in a more friendly way. For example, macOS uses display names in the following situations:

• Localized names. The system provides localized names for many system directories, such as Applications, Library, Music, Movies. An app may similarly provide localized names for itself and for any directories it creates.
• Filename extension hiding. The system hides filename extensions for all files by default. The user may change option, but when filename extension hiding is in effect, the characters after the last period in a filename (and the period itself) are not displayed.

Display names do not affect the actual name of the file in the file system. Code that accesses a file or directory programmatically must specify the item’s actual name when opening or manipulating the item using the file system interfaces. The only time your app should ever use display names is when displaying the name of a file or directory to the user. You can get the display name for any file or directory using the displayNameAtPath: method of NSFileManager.

For information on how to localize the directories your app creates, see File System Advanced Programming Topics. For more information about localizing app content, see Internationalization and Localization Guide.

The Library Directory Stores App-Specific Files

The Library directory is where apps and other code modules store their custom data files. Regardless of whether you are writing code for iOS or macOS, understanding the structure of the Library directory is important. You use this directory to store data files, caches, resources, preferences, and even user data in some specific situations.

There are several Library directories throughout the system but only a few that your code should ever need to access:

• Library in the current home directory—This is the version of the directory you use the most because it is the one that contains all user-specific files. In iOS, Library is placed inside the apps data bundle. In macOS, it is the app’s sandbox directory or the current user’s home directory (if the app is not in a sandbox).
• /Library (macOS only)—Apps that share resources between users store those resources in this version of the Library directory. Sandboxed apps are not permitted to use this directory.
• /System/Library (macOS only)—This directory is reserved for use by Apple.

After selecting which version of the Library directory to use, you still need to know where to store your files. The Library directory itself contains several subdirectories that subdivide app-specific content into a few well-known categories. Table 1-3 lists the most common subdirectories that you might use. Although Library directories in macOS contain many more subdirectories than the ones listed, most are used only by the system. If you want a more complete list of subdirectories, though, see macOS Library Directory Details.

The iCloud File Storage Container

iCloud provides a structured system for storing files for apps that make use of iCloud:

• Apps have a primary iCloud container directory for storing their native files.  They can also access secondary iCloud container directories listed in their app entitlements.
• Inside each container directory, files are segregated into "documents" and data.  Every file or file package located in the Documents subdirectory (or one of its subdirectories) is presented to the user (via the iCloud UI in macOS and iOS) as a separate document that can be deleted individually.   Anything not in Documents or one of its subdirectories is treated as data and shown as a single entry in the iCloud UI.

Documents that the user creates and sees in an app's user interface—for example the document browsers in Pages, Numbers, and Keynote should be stored in the Documents directory. Another example of files that might go in the Documents directory are saved games, again because they are something that an app could potentially provide some sort of method for selecting.

Anything that the app does not want the user to see or modify directly should be placed outside of the Documents directory.  Apps can create any subdirectories inside the container directory, so they can arrange private files as desired.

Apps create files and directories in iCloud container directories in exactly the same way as they create local files and directories.  And all the file’s attributes are saved, if they add extended attributes to a file, those attributes are copied to iCloud and to the user's other devices too.

iCloud containers also allow the storage of key-value pairs that can be easily accessed without having to create a document format.

How the System Identifies the Type of Content in a File

There are two primary techniques for identifying the type of content in a file:

• Uniform Type Identifiers (UTIs)
• Filename extensions

A uniform type identifier is a string that uniquely identifies a class of entities considered to have a “type.” UTIs provide consistent identifiers for data that all apps and services can recognize and rely upon. They are also more flexible than most other techniques because you can use them to represent any type of data, not just files and directories. Examples of UTIs include:

• public.text—A public type that identifies text data.
• public.jpeg—A public type that identifies JPEG image data.
• com.apple.bundle—An Apple type that identifies a bundle directory.
• com.apple.application-bundle—An Apple type that identifies a bundled app.

Whenever a UTI-based interface is available for specifying file types, you should prefer that interface over any others. Many macOS interfaces allow you to specify UTIs corresponding to the files or directories you want to work with. For example, in the Open panel, you can use UTIs as file filters and limit the types of files the user selects to ones your app can handle. Several AppKit classes, including NSDocument, NSPasteboard, and NSImage, support UTIs. In iOS, UTIs are used to specify pasteboard types only.

One way the system determines the UTI for a given file is by looking at its filename extension. A filename extension is a string of characters appended to the end of a file and separated from the main filename with a period. Each unique string of characters identifies a file of a specific type. For example, the .strings extension identifies a resource file with localizable string data while the .png extension identifies a file with image data in the portable network graphics format.

If your app defines custom file formats, you should register those formats and any associated filename extensions in your app’s Info.plist file. The CFBundleDocumentTypes key specifies the file formats that your app recognizes and is able to open. Entries for any custom file formats should include both a filename extension and UTI corresponding to the file contents. The system uses that information to direct files with the appropriate type to your app.

For more information about UTIs and how you use them, see Uniform Type Identifiers Overview. For more information about the CFBundleDocumentTypes key, see Information Property List Key Reference.

Security: Protect the Files You Create

Because all user data and system code are stored on disk somewhere, protecting the integrity of files and the file system is an important job. For that reason, there are several ways to secure content and prevent it from being stolen or damaged by other processes.

For general information about secure coding practices when working with files, see Secure Coding Guide.

Sandboxes Limit the Spread of Damage

In iOS and in macOS 10.7 and later, sandboxes prevent apps from writing to parts of the file system that they should not write to. Each sandboxed app receives one or more containers that it can write into. An app cannot write to other apps’ containers or to most directories outside of the sandbox. These restrictions limit the potential damage that can be done in the event that an app’s security is breached.

Developers writing apps for macOS 10.7 and later are encouraged to put their apps in sandboxes to enhance security. Developers of iOS apps do not have to explicitly put their app in a sandbox because the system does it for them automatically at install time.

For more information about sandboxes and the types of restrictions they impose on file system access, see Mac App Programming Guide and App Sandbox Design Guide.

Permissions and Access Control Lists Govern All Access to Files

Access to files and directories is governed by a mixture of access control lists (ACLs) and BSD permissions. Access control lists are a set of fine-grained controls that define exactly what can and cannot be done to a file or directory and by whom. With access control lists, you can grant individual users different levels of access to a given file or directory. By contrast, BSD permissions only allow you to give access to three classes of users: the file’s owner, a single group of users that you specify, and all users. See Security Overview for more information.

Because iOS apps always run in a sandbox, the system assigns specific ACLs and permissions to files created by each app. However, macOS apps can use Identity Services to manage access control lists for files to which they have access. For information about how to use Identity Services (and the Collaboration framework), see Identity Services Programming Guide.

Files Can Be Encrypted On Disk

Both macOS and iOS provide support for encrypting files on disk:

• iOS. An iOS app can designate files that it wants to be encrypted on disk. When the user unlocks a device containing encrypted files, the system creates a decryption key that allows the app to access its encrypted files. When the user locks the device, though, the decryption key is destroyed to prevent unauthorized access to the files.
• macOS. Users can encrypt the contents of a volume using the Disk Utility app. (They can also encrypt just the boot volume from the Security & Privacy system preference.) The contents of an encrypted disk are available to apps only while the computer is running. When the user puts the computer to sleep or shuts it down, the decryption keys are destroyed to prevent unauthorized access to the disk’s contents.

In iOS, apps that take advantage of disk-based encryption need to be discontinue the use of encrypted files when the user locks the device. Because locking the device destroys the decryption keys, access to encrypted files is limited to when the device is unlocked. If your iOS app can run in the background while the device is locked, it must do so without access to any of its encrypted files. Because encrypted disks in macOS are always accessible while the computer is running, macOS apps do not need to do anything special to handle disk-level encryption.

For more information about working with encrypted files in iOS, see App Programming Guide for iOS.

Synchronization Ensures Robustness in Your File-Related Code

The file system is a resource shared by third-party apps and system apps. Because multiple apps are able to access files and directories at the same time, the potential arises for one app to make changes that render a second app’s view of the file system obsolete. If the second app is not prepared to handle such changes, it could enter an unknown state or even crash. In cases where your app relies on the presence of specific files, you can use synchronization interfaces to be notified of changes to those files.

File system synchronization is primarily an issue in macOS, where the user can manipulate files directly with the Finder or with any number of other apps at the same time. Fortunately, macOS provides the following interfaces to help with synchronization issues:

• File coordinators. In macOS 10.7 and later, file coordinators are a way to incorporate fine-grained synchronization support directly into the objects of your app; see The Role of File Coordinators and Presenters.
• FSEvents. In macOS 10.5 and later, file system events allow you to monitor changes to a directory or its contents; see File System Events Programming Guide.

Files, Concurrency, and Thread Safety

Because file-related operations involve interacting with the hard disk and are therefore slow compared to most other operations, most of the file-related interfaces in iOS and macOS are designed with concurrency in mind. Several technologies incorporate asynchronous operation into their design and most others can execute safely from a dispatch queue or secondary thread. Table 1-4 lists some of the key technologies discussed in this document and whether they are safe to use from specific threads or any thread. For specific information about the capabilities of any interface, see the reference documentation for that interface.

Even if you use an thread-safe interface for manipulating a file, problems can still arise when multiple threads or multiple processes attempt to act on the same file. Although there are safeguards to prevent multiple clients from modifying a file at the same time, those safeguards do not always guarantee exclusive access to the file at all times. (Nor should you attempt to prevent other processes from accessing shared files.) To make sure your code knows about changes made to shared files, use file coordinators to manage access to those files. For more information about file coordinators, see The Role of File Coordinators and Presenters

BigInt 5.3.0

CareKit 2.0.2

DateHelper 4.5.3

Kingfisher 7.2.1

PromiseKit 7.0.0-rc1

Realm 10.8.1

RealmDatabase 11.0.3

Signals 6.1.0

SSToastMessage 1.0.0

SwiftGif 5.4.0

File - Package - Reset ...Cache 안되어서 Package Manager 신뢰도 하락. 모두 따로 관리하기로 함.

DEVICE SECURITY COMPROMISED

CheckDeviceCoordinator

    private func checkDevice() {

        let deviceChecker = CheckDeviceCoordinator(

                navigationController: navigationController,

                jailbreakChecker: DeviceChecker()

        )

        deviceChecker.start()

        addCoordinator(deviceChecker)

    }

class DeviceChecker: JailbreakChecker {

    var isJailbroken: Bool {

        if TARGET_IPHONE_SIMULATOR == 1 {

            return false

        }

        let list: [String] = [

            "/Applications/Cydia.app",

            "/Library/MobileSubstrate/MobileSubstrate.dylib",

            "/bin/bash",

            "/usr/sbin/sshd",

            "/etc/apt",

            "/private/var/lib/apt/",

        ]

        return !list.filter { FileManager.default.fileExists(atPath: $0) }.isEmpty

    }

}

emailListPromptMessage

receiveEmailSelected

@objc private func

    func didFinish(in viewController: CollectUsersEmailViewController, email: String) {

        if email.isEmpty {

            logEmailNewsletterSubscription(isSubscribed: false)

        } else {

            EmailList(listSpecificKey: Constants.Credentials.mailChimpListSpecificKey).subscribe(email: email)

            logEmailNewsletterSubscription(isSubscribed: true)

        }

    }

class EmailList {

    private let listSpecificKey: String

    init(listSpecificKey: String) {

        self.listSpecificKey = listSpecificKey

    }

    ///We skip email validation since MailChimp does it, and this is low volume

    func subscribe(email: String) {

        guard Features.isPromptForEmailListSubscriptionEnabled else { return }

        do {

            try Mailchimp.initialize(token: listSpecificKey, autoTagContacts: true, debugMode: false)

            var contact: Contact = Contact(emailAddress: email)

            contact.status = .subscribed

            Mailchimp.createOrUpdate(contact: contact)

        } catch {

            //TODO log to remote server

            //no-op

        }

    }

}

Command line invocation:

    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild GCC_PRECOMPILE_PREFIX_HEADER=NO RUN_CLANG_STATIC_ANALYZER=NO SWIFT_COMPILATION_MODE=incremental

User defaults from command line:

    IDEPackageSupportUseBuiltinSCM = YES

Build settings from command line:

    GCC_PRECOMPILE_PREFIX_HEADER = NO

    RUN_CLANG_STATIC_ANALYZER = NO

    SWIFT_COMPILATION_MODE = in

• sourceanalyzer -b dmfh01t_test_delete xcodebuild

 sourceanalyzer -scan -f a.fpr -b dmfh01t_test_delete xcodebuild                 

[error]: When running a scan, you cannot specify both a build session and source files as command-line arguments.

┌─(~/Downloads/DLenc_Hybrid)──────(junhoha@

sourceanalyzer -b dmfh01t_test_delete -verbose -debug -logfile build.log xcodebuild -project DLenc.xcodeproj 

sourceanalyzer -b dmfh01t_test_delete -verbose -debug -logfile build.log xcodebuild -project DLenc.xcodeproj -configuration debug 

sourceanalyzer -b dmfh01t_test_delete -verbose -debug -logfile build.log xcodebuild -project DLenc.xcodeproj -configuration debug clean

• sourceanalyzer -b dmfh01t_test_delete -verbose -debug -logfile build.log xcodebuild -project DLenc.xcodeproj -configuration "debug" CODE_SIGNIDENTITY="" CODE_SIGNING_ALLOW=No CODE_SIGNING_REQUIRED=No

xcodebuild -showsdks

sourceanalyzer -b dmfh01t_test_delete -verbose -debug -logfile build.log xcodebuild -project DLenc.xcodeproj -scheme dmfh01_dev -configuration "debug" -sdk iphoneos15.2

sourceanalyzer -b dmfh01_dev -export-buildsession a.mbs

• sourceanalyzer -b dmfh01_dev -verbose -debug -logfile build.log xcodebuild -project DLenc.xcodeproj -configuration "debug" CODE_SIGNIDENTITY="" CODE_SIGNING_ALLOW=No CODE_SIGNING_REQUIRED=No

kr.co.dlenc.dmfh01d

• sourceanalyzer -b dmfh01_dev -verbose -debug -logfile build.log xcodebuild -project DLenc.xcodeproj -scheme dmfh01_dev -configuration "debug" -sdk iphoneos15.2

sourceanalyzer -b dmfh01_dev -verbose -debug -logfile build.log xcodebuild -project DLenc.xcodeproj -scheme dmfh01_dev -configuration "debug" -sdk iphoneos15.2

┌─(~/Downloads/DLenc_android_20220304)──────(junhoha@Junhos-MacBook-Pro:s001)─┐

└─(17:07:39)──> find ./ -type f -iname "*.java" > list.txt      ──(Fri,Mar04)─┘

┌─(~/Downloads/DLenc_android_20220304)──────(junhoha@Junhos-MacBook-Pro:s001)─┐

└─(17:07:48)──> cat list.txt | xargs sourceanalyzer -scan -f android_20200304.fpr

망고보드

미리캠퍼스

remove BG

회담 중에도 공격은 멈추지 않는 사이코 킬러 푸틴. 러시아군은 수류탄을 들고 우크라이나인은 휴대폰 카메라를 들고 있다.  푸틴 개객기 이런 발전된 시대에 능력 없는 지도자가 있으니 웃기지만, 온갖 만행이 제대로 공개 되는 점은 좋다. 퇴군 하는 척 하다가 공격한 푸틴도 스스로 부끄러운 것을 알 것이다. 공격 원자력 발전소나 일반 시민들을 일부러 공격하는 러시아 군인도 스스로 부끄럽다는 것은 잘 알 것이다. 푸틴 호로객기가 자꾸 등 떠밀어서 어쩔 수 없다고 하는 놈들도 많겠지. 푸틴은 인간 쓰레기로 역사에 기록 될 것은 생각하니 다행이다. 역사를 잘 기록하고 역사를 잊지 말아야 겠다.

TrueDepth API
The Service also makes use of automatically collected information using the device camera and the TrueDepth API provided by Apple. The only use of this information is to track the user’s head and face so that the user can control the Service by moving their head. None of the information collected by the TrueDepth API ever leaves the user's device nor is it persistently stored on the device.

We found a great game titled "hextris" for kids to play. But it is GPL3 protected. Therefore, rather than hiding it in the corner, we put the GPL3 in a prominent place and specify the related licenses. A link to be published when it is revised is also attached. We want many kids to play the game, but we want to remove the link to the game when it becomes a claim to complete source openness. All editorial sources for this game will be disclosed by Github link. In the future, we promise to pay a fair amount agreed upon at the point of revenue generation as FSF donations.


https://www.gnu.org/licenses/
https://github.com/Hextris/hextris/blob/gh-pages/LICENSE.md 
forked to https://github.com/hajunho/hextris/blob/gh-pages/LICENSE.md

GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007

Copyright © 2007 Free Software Foundation, Inc. <http://fsf.org/>

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble
The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.

For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.

Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS
0. Definitions.
“This License” refers to version 3 of the GNU General Public License.

“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.

“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.

To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.

A “covered work” means either the unmodified Program or a work based on the Program.

To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.

To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.

1. Source Code.
The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.

A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.

The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.

The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work.

2. Basic Permissions.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.

Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.

3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.

When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.

4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.

5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.

A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.

“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.

Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.

7. Additional Terms.
“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.

8. Termination.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).

However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.

9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.

10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.

An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

11. Patents.
A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's “contributor version”.

A contributor's “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.

In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.

If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.

A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.

12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.

13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.

If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.

Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.

15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year>  <name of author>

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:

<program>  Copyright (C) <year>  <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type 'show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type 'show c' for details.
The hypothetical commands 'show w' and 'show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.

You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>.

The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.

Bringing People into AR
https://developer.apple.com/videos/play/wwdc2019/607
Copyright © 2022 Apple Inc. All rights reserved.

Parental Gate
https://github.com/henrytkirk/HTKUltimateParentalGate
Apache License 2.0

Apple Visualizing Faces
https://developer.apple.com/documentation/arkit/content_anchors/tracking_and_visualizing_faces
Copyright © 2021 Apple Inc. All rights reserved.

Raywenderlich.com Xcode Test Plans for iOS by Irina Galata
https://www.raywenderlich.com/u/galata

Crashlytics for iOS
https://fabric.io/kits/ios/crashlytics
Copyright 2016 Twitter Inc.

Kingfisher
https://github.com/onevcat/Kingfisher.git
The MIT License (MIT)
Copyright (c) 2019 Wei Wang

EFCountingLabel
https://github.com/EFPrefix/EFCountingLabel
Copyright (c) 2016 eyrefree <eyrefree@eyrefree.org>
MIT License

Moya
https://github.com/Moya/Moya
Copyright 2014-present Artsy, Ash Furrow
MIT License

RxSwift
https://github.com/ReactiveX/RxSwift
Copyright 2015 Krunoslav Zaher All rights reserved.
MIT License

LocoKit
https://github.com/sobri909/LocoKit
Copyright (C) 2007 Free Software Foundation
LPGL License

SnapKit
https://github.com/SnapKit/SnapKit
Copyright 2011-Present SnapKit Team - https://github.com/SnapKit
MIT License

SwiftySound
https://github.com/adamcichy/SwiftySound
Copyright 2017 Adam Cichy
MIT License

SwiftyUserDefaults
https://github.com/sunshinejr/SwiftyUserDefaults
Copyright 2015-present Radosław Pietruszewski, Łukasz Mróz
MIT License

Swinject
https://github.com/Swinject/Swinject
Copyright 2015 Swinject Contributors
MIT License

SwiftSVG
https://github.com/mchoe/SwiftSVG
Copyright 2015 Michael Choe, Strauss LLC
MIT License

Toast-Swift
https://github.com/scalessec/Toast-Swift
Copyright 2015-2017 Charles Scalesse.
MIT License 

Google ML-Kit for iOS
https://github.com/googlecodelabs/mlkit-ios/blob/master/LICENSE
Apache License 2.0

2048
https://github.com/gabrielecirulli/2048
MIT License

Hextris
https://github.com/Hextris/hextris
Copyright (C) 2018 Logan Engstrom
GPL 3.0
Modified Source Code Link
https://github.com/hajunho/hextris

Marbles
https://github.com/neizod/marbles
MIT License

Buscayasminas
https://github.com/jalbam/buscayasminas
One's License below
This project can be used, reproduced, distributed and modified freely for any non-commercial purposes but always keeping the author's name and copyright clauses.
Other than that, just use this project as you wish but never sell it!

이오스 단톡방 주소 오픈쳇 링크 http://kakao.bullish.love/

이오스 사용자 모임

이오스 단톡방 주소 오픈쳇 링크 http://kakao.bullish.love/

이오스 카톡방

이오스 텔레그램 은 아님. 단톡방임.

A novel method for the 3 dimensional simulation of orthognathic surgery by using a multimodal image fusion technique

Orthognathics Three-Dimensional Imaging for Virtual Assessment and Treatment Simulation in Orthognathic Surgery

256

https://medium.com/thundercore

   Everybody has a dream of traveling to the perfect world to find their friends. Each 3D model will help your life later on.

https://www.cgtrader.com/free-3d-models/character/fantasy/a2-cihibi-nierautomata

개발자는 디자이너가 없어서 디자인을 배우고... 디자이너는 개발자가 없어서 개발을 배우는 것 같다.

https://www.youtube.com/watch?v=OCUHYvnGPKY&ab_channel=%EA%B9%8C%EB%A7%9D%EA%B3%A0%EB%8B%88%EA%B9%8C%EB%A7%9D%EA%B3%A0%EB%8B%88

내 경우는 아는 3D 디자이너들이 다들 바빠서... ㅠㅠ

2021-05-23 19:00:15.547127+0900 Touch[44871:4072399] [Session] ARSession <0x123d5d970>: did fail with error: Error Domain=com.apple.arkit.error Code=102 "Required sensor failed." UserInfo={NSLocalizedFailureReason=A sensor failed to deliver the required input., NSUnderlyingError=0x280670780 {Error Domain=AVFoundationErrorDomain Code=-11800 "The operation could not be completed" UserInfo={NSLocalizedFailureReason=An unknown error occurred (-12785), NSLocalizedDescription=The operation could not be completed, NSUnderlyingError=0x28180d290 {Error Domain=NSOSStatusErrorDomain Code=-12785 "(null)"}}}, NSLocalizedRecoverySuggestion=Make sure that the application has the required privacy settings., NSLocalizedDescription=Required sensor failed.}

"applicationDidEnterBackground"

unknown error 로그는 항상 소중함.

로그 나오는게 어디야 ㅋㅋㅋ

다 조금씩은 알고강의도 하고,

제품도 만들었다.

기술로서 어느 것 하나를 포기하라고 하면 못하겠다. 3D는 국내 최고 기술을 가져서 글로벌에도 상대할 수 있는 회사에 3년을 다녔다. 그 회사의 엔진은 자체 기술로 만드는데 원 기술은 FX엔진의 라이센스를 3년간 사와서 자체 기술로 만들었다. 3D 엔진 자체를 만들 수 있는 기술력이 있는 회사는 사실, 네이버나 카카오도 없다. 그래서 XR은 못 버린다. 친구도 3D 디자인을 하니까.

AI는 대세라 ... 어쩔 수 없이 꾸역꾸역... 학교로 넘어가야 할 학문의 경계로는 넘어가지 않고, 제품을 만드는 쪽에서만 열심히 하고 있었는데. 요즘엔 AI 워크 플로우를 만드는 회사가 워낙 많고. 대부분 그 정도 돈을 쓸 수 있는 능력의 기업은 해당 솔루션을 사서 그것만 만들고 끝이다. 확장성을 고려하지 않은 부분에 대해서는 어차피 책임도 없고 원하지도 않는데. 올 해 안 짤리거나, 계약 연장만 되면 되기 때문이다. 확장성까지 고려하려면 드는 AI 개발 인건비가 사람을 대체한 효율성이나 비용에 메리트가 없기 때문이기도 하다. 그래서 AI는 계속 국가 돈을 필요로 한다. 그렇게 나라 전체가 망해간다. 게임 산업처럼 수 많은 폐인을 양성하는 엔터테인 사업으로 특화시키는 쪽으로 가지 않을까 생각한다.

IoT는 본래 하던거니 당장은 못 버리고 또 제대로 된 커리큘럼이나 워라벨만 외치는 엔지니어들 때문에 꾸준한 것 같다.

블록체인은... 흠... 그 이용 결과물이 대부분 투기라고 해도 사람의 마음을 움직일 만한 수학적, 그리고 기술적 메리트는 확실히 있다. 그리고 사람들이 온갖 구라는 쳐 가며 지켜내는 본인들의 돈 때문에 현실 세계의 인플레이션이 똑같이 반영된다. 신기하게도 다이라는 코인은 부동산, 달러를 따라가게 만들었다고 한데... 내가 초창기부터 이 동네에 참여하고 지켜본 바로는... 오히려 그런거면 망할거라고 생각한다. 왜냐면 사람의 욕망이 반영되지 않았기 때문이다. 내가 보는 시각으로 돈을 번 주변 사람들이 너무 많다. 물론, 너무 앞서간 미래를 공유를 안했는데 그래서 오히려 빨리 나갔던 내가 도박판에서는 진 것이다. 수익이 나도 푼돈. 인생이 바뀔 만큼의 수많은 기회를 차버린 것이다. 아니나 다를까 지금 상황에서 보면 다이는 거래량이 확 줄었다. 코인은 거래량이 줄면 망한다. 중앙화가 아니기 때문에 누군가는 계속 채굴을 하면서 시스템을 유지해줘야 하고, 누군가는 계속 거래를 하면서 해당 코인의 미래를 밝혀줘야 하기 때문이다.

기술이던 미래를 보는 식견이던. 내 주변에 정말 내가 말한 방법으로 20~30억 번 사람들은 많은 것 같다. 그러나 난 처음부터 최소 수백억을 꿈꿨고, 지금은 그 길을 나아가려고 한다. 시에서 물래방아까지 만들어 주던 지역 유지인 삼촌께서 말씀하신 것이 있다. 돈 벌 방법이 확실하면 절대 말하지 말고 니가 그것을 해야 한다고.

내 주변에서 300억씩 벌어 보라는 사람이 생기고 계속 그 말을 들으니 가진 것을 모아 인생의 마지막 도전을 해 봐야 겠다는 생각이 든다.

뭘로 풀 건지도 비밀로 해야 겠다. 다만, 내 주변에 코인 투자 하는 사람이 많이 생겼는데 왜 그것은 안 될 것 같은지에 대해서는 공유를 하는 것이 좋겠다. 내 생각이 틀렸을지는 모르겠지만. 난 아니라고 생각하고. 사실 그 결과는 내가 거의 50이 다 되었을 때 가진 자산으로 증명될 것 같다. 돈에만 매여 살 필요는 없다. 이미 기술적 성과는 거의 이룬 것 같고. 그 성과로 지금 기술 관련 제품의 상황을 정확히 판단할 능력이 생겼다. 또 미래를 위해 단순 텍스트로, 영어로 , 누가 정리해 주지 않아도 알아서 헤쳐나갈 수 있는 기술을 가졌다.

물론, 사업으로 풀 생각은 아니다. 사업은 기술로 하는게 아니라는 생각이 들었기 때문이다. 기술로 사업이 따라오게. 또 돈이 따라오게 할 생각이다. 역시 과학/기술이 최고다.

디자인은 잘 모르지만 디자이너에 따라 "결"은 확실한 것 같다. 그래서 회사가 어떤 디자인으로 갈지 정하는 것이 중요하고 거기에 맞는 디자이너를 데려오는 것은 더 중요하다는 것을 알게 되었다. 제너썬아이브가 애플을 만든 택이니 이 부분은 논란의 여지는 없는 것 같다.

AI 엔지니어의 경우 모델은 스스로 결과 시연 가능한 평가 방법을 정하고 기준에 맞는 퍼포먼스를 보여줄 수 있는 사람으로 해야 겠다.

디자이너랑 개발자도

카테고리가 많네.

나도 좀 더 구체적으로 정해야 겠네..

사실, 쿠팡의 미래는

https://brunch.co.kr/@jyzz21/15

쿠팡의 미래

아마존의 재무제표 분석을 통해 쿠팡의 미래를 예상합니다. | 쿠팡의 현재와 미래를 걱정하는 분들이 참 많습니다. 쿠팡과 관련하여 워낙 많은 글과 기사들이 넘쳐나므로 쿠팡에 대한 이야기는

brunch.co.kr/@jyzz21/15

이런 시각으로 보는 것이 맞겠다.

내가 매거진을 만든 이유는 내 시각을 이야기하고 나와 비슷한 곳에서 현상을 바라보는 분이 있다는 것에 감사하기 위해서이다.

내가 보는 시각은 이렇다.

http://www.saramin.co.kr/zf_user/company-info/view/csn/8158101244/company_nm/%EC%8B%AD%EC%9D%BC%EB%B2%88%EA%B0%80(%EC%A3%BC)

십일번가(주)기업정보 - 사람인

십일번가(주)기업정보 및 연봉정보, 취업자료, 진행중 채용정보 제공

www.saramin.co.kr

 SK의 11번가는 대한민국 기업이다.

SK는 대한민국 사람을 팬다. 그 현상이 이상해서 뉴스 기사도 나고, 베테랑이라는 영화도 나왔다.

https://news.kbs.co.kr/news/view.do?ncd=3643310

[취재후] “한 대에 100만원”…‘맷값폭행’ 피해자, 8년 지나도 고통은 진행형

"매 한 대에 100만 원이니까 스무 대만 맞아라" 2015년 개봉한 류승완 감독의 영화 <베테랑>은 안하무인 재벌 2세 조태오(유아인)의 '망나니' 연기로 흥행 돌풍을 불러일으켰습니다. 하지만 <베테랑>

news.kbs.co.kr

쿠팡은 일본 기업이라고 한다. 또, 아니라고도 한다.

https://www.logibridge.kr/product/thedepths17

온라인쇼핑 최저가 시대의 종말…쿠팡VS롯데VS신세계 '누가 살아 남을까?'

<1부에 이어서><1부 듣기 클릭> ◇남 : 지금 온라인 시장은 엄청나게 소비자 편익 ...

www.logibridge.kr

난 손정희는 한국 사람이라고 생각한다. 만약 아니라면, 미국 사람+ 일본 사람+한국 사람일 것이다. 그런데 이런 논란은 중요치 않다.

https://www.ajunews.com/view/20200727181821438

여직원 늘어난 쿠팡맨, 1만명 돌파…'쿠팡친구'로 개명

[사진=쿠팡 제공]쿠팡이 ‘쿠팡맨’의 명칭을 ‘쿠팡친구’로 변경했다. 27일 쿠팡은 지난 22일 1만번째 배송직원을 채용하면서 ...

www.ajunews.com

임직원 1000명과 0 하나 더 붙은 10000명은 차원이 다른 차이이다. 근무 환경, 근속 년수, 복지, 정직원 개념? 그리 중요치 않은 것 같다. 내가 삼성전자 정직원 7년 동안 단, 한 번도 정직원이라고 생각해 본 적 없는 것 같이 말이다. 잘하면 남는 거고 못하면 나가는 거고, 시대의 흐름과 맞으면 같이 가는 거고 같이 가지 말자면 가지 않는 것이 기업의 속성이고 실력이 있다면 이직이 자유로운 IT 개발자 세계의 특징이기 때문이다.

공개적으로 발간하지 못한 내 책에 가장 중요한 개념은 "시간"이라고 말했었다. 딱 지금의 스냅샷만 찍어서, 딱 그 순간의 시간만 따서 말하는 것이 틀렸다고 생각할 수 있다. 그러기에는 너무 큰 사건이고, 어려운 시기에 너무도 많은 같은 밥 먹는 식구이다.

어려운 시기에 한국 사람을 더 뽑을 수 있다는 것.

영화 "원라인"에서 이를 가리켜

사이즈가 다르네

라고 한다. 이를 따라한 기사도 있다.

https://www.wikitree.co.kr/articles/503324

“사이즈가 다르네...” 우한 병원에 '112억 원' 기부한 연예인

치료법 찾는 실험실에 기부한 것으로 전해진 가수

www.wikitree.co.kr

쿠팡은 사이즈가 다르다. 검색은 구글이라고 하지만 상품 검색은 쿠팡으로 한다. 내 생각을 말할 뿐, 내가 쿠팡을 도와주려고 글을 쓰는 것은 아니라 잠깐 다른 이야기를 하면 사실, 검색은 좀 다른 의미로 새로운 기술 도입이 필요해 보인다. 필터를 먹일 때마다 원하는 상품이 사라진다. 그리고 오픈 마켓 이후에는 검색 유이나 검색 조건에 따라서 가격도 달라진다. RTX2080 그래픽 카드를 샀는데 지금 보니 14만 원 다운되어서 하나 더 살까 고민하다가... 반품하려고 반품 버튼 눌렀는데 1달 지났다는 팝업 창 뜬 이후로 다시 가격이 복구되었다.

손정희가 주춤할 때 쿠팡 같은 회사는 산업은행에서 2~3조 꽂아주면 좋겠다. 그리고 쿠팡에 중고 물품을 사고팔 수 있는 시스템을 도입하고 중고 판매자에게 수수료를 떼는 방식으로 수익의 다각화를 하면 좋겠다.

이 모든 생각은 단지, 쿠팡 배송은 확실히 다른 곳과 차별점이 있기 때문이다. 나 개인적으로 한 명의 쿠팡 맨 때문에 쿠팡 배송에 대해서 무지하게 좋지 않고 오랜 기억(유리는 깨지고 캔 음료는 다 터지고 전자제품은 망가지는 등... 강력한 컴플레인 전, 몇 달간)이 있으나 쿠팡 배송은 다른 곳과는 확실히 다르다고 할 수 있겠다. 

이런 생각을 할 수도 있다. 다른 물류 업체도 중요하니, 11번가나 G마켓과 연계된 다른 배송업체의 서비스를 쿠팡 수준으로 올리도록 도우면 안 될까? 응,... 안된다.

그것은 SK에서 전화 거는 사람들은 전부 위촉직이라는 이름의 알바로 쓰는 것만 봐도 자회사의 사원으로 쓸 의지가 있는 회사와 상황에 따라 꼬리 자르기를 할 회사와의 큰 차이이다.

손정희의 업을 이룬다는 것은

아마도 완전히 다른 형태의 승부로 보인다.

untact 시대 대한민국에서 그 날, 혹은 다음 날 중고거래 보다 더 믿음직하고 안전하게 물건을 배송해 주며 한국 사람들을 최대한 많이 뽑고 정직원의 희망을 줄 수 있는 회사는 수익 구조와 관계없이 몇 조 넣어줘도 괜찮은 사이즈다. 나 역시 월급쟁이지만 그런 사이즈의 회사에 2~3조는 일 년 치 연봉 정도로 보인다.

사이즈가 다른 쿠팡은 대한민국의 대표 기업이다.

삼성전자까지도 다녀봤지만 삼성전자에 있었던 슈퍼 컴퓨터 that is available when you raise proposalthat is available when you raise a proposal 를 제외하고 정말 나에게 지급된 컴퓨터 중에 집에 있는 컴퓨터 보다 성능이 좋은 적은 단 한 번도 없었다.

그러나 software 2.0 시대가 오고 나서 컴퓨터 비용이 많이 비싸졌다.

이에 상응하는 컴퓨터 마련을 위해 개인 컴퓨터들을 구입하는데 3000만원 가량이 들었다. 덕분에 신용 대출도 하게 되고.

쩝... 국가 과제의 필요성을 절실히 느끼는 요즘이다.

CTO로 있는 법인이 2개 인데, 지분이 그리 높지는 않다. 대표자나 생사고락을 할께 할 동료들에게 연대 보증이 없어진 것은 참 좋지만 지금 상황은 사실 연대 보증 있을 때랑 별 구분이 없기 때문이다. 개발도 중요하지만 특히나 서류를 작성하는 것이 얼마나 중요한지 깨닫는 요즘이다.

무조건 좋은 컴퓨터를 살 필요는 없지만... 컴퓨터만 있으면 창업이 가능한 시대에서 바뀐 것은 없으나 그 비용이 상당히 커졌다. 클라우드도 막상 써보면 비싸긴 마찬가지 ㅡㅡ; 매출 0원으로 상장하려면 독보적 기술력을 가지던지, 그에 맞는 BM을 가지던지 해야 할 것 같다.

"구라"가 제목에 들어 간 이유는 빌드 타임에 맞게 끔 회사에 컴퓨터 사양을 요구하는데 들어주지 않기 때문이다. 거의 다 그렇다. 뭐, 그렇다가 내가 불만 가지고 꿍 하고 있을 사람도 아니도 다양한 방법으로 해결 했었다. 그런데 지금은 내 컴퓨터를 회사로 들고 와서 써야 하는 상황이 왔다. 그래서 써 둔다. 회사도 개발자 능력을 정확히 평가하고 거대한 오픈 소스를 빌드 한다고 하면 컴퓨터 사양을 정할 창구를 좀 만들라고 하고 싶다.

1. iPhone and iPad Apps on Mac. All newly created and existing compatible iPhone and iPad apps will be made available on Mac. Your compatible apps will be published on the Mac App Store on Apple Silicon Macs unless you edit their availability. Manage Availability

애플 개발자 사이트에 접속했다.  이 문구를 보고 타고 들어가, 아이폰 앱스토어에 올려져 있던 앱 중 맥에서도 사용할 수 있게 하려면 체크박스 체크하고 확인 버튼 누르면 끝.

ARM MAC이라 가능한 이야기.

구글은 안드로이드 모바일은 시장을 먹었지만 데스크톱을 먹지 못했고,

마이크로 소프트는 데탑(랩탑) 마켓 셰어를 가져갔지만 모바일은 못했는데,

그 틈을 파고들어 결정타를 날렸다.

2. VMware가 열심히 마소랑 구글을 돕겠지만... 가상 환경과 퍼포먼스 차이가 클 것이라 예상된다.

변수는 언리얼 엔진과 텐서 플로우. ARM에 최적화된 3D 엔진 개발자, AI 논문 구현 개발자 몸 값은 하늘을 찌를 것 같지만 애플에 입사한다는 가정이라고 생각하고 일반 직장인이라고 생각해 보면 딱히 그렇지만은 않은 것 같다. 그 외 사람들은 여전히 3D, AI 엔진을 사용할 테니 기여 방법이라면 ARM용 unreal engine, ARM용 tensor flow가 되겠다. ARM에 기여하면 구글도 덕을 보니... 텐서가 비공개가 될 일은 없어 보인다. 이미 공개했는데 다시 비공개로 가는 것도 불가능한 이야기. 비공개로 가는 순간 이미 공개된 것으로 사업화를 하는 기업들에게 이름을 빼앗겨 버릴 테니 말이다. 공개된 Eclipse 보다 래셔널 제품이나 인텔리 J가 더 좋았던 것처럼.

ARM으로 CPU를 만들면 시장을 평정할 거라 생각한지는 오래다. ARM Firmware 강사 한지도 4년이 넘었는데 공식이고 비 공식으로는 오드 로이드를 처음 봤을 때였다. 어차피 휴대폰도 하나의 컴퓨터라고 생각해보면 오드 로이드 같은 임베디드 제품이 나오는 것은 당연한 일일 것이다. 그리고 임베디드를 겨냥해서 치열하게 설계를 고민하고 거기서 쌓아 올린 CPU는 또 얼마나 뛰어날까 생각도 해 보았었다.

3. 물론, 리사수가 나타나기 전까지는 말이다.

https://www.youtube.com/watch?v=QZU8H4d8KmA

IT계에서 그녀는 이렇게 불립니다.

빛 사수

이민자, 황인, 여성이라는 유리천장을 박살 낸 그녀. MIT학석박에 IBM에 근무했고 인텔이나 엔비디아 자유롭게 선택할 수 있었음에도 

그런 회사는 ‘쉬운 선택지’이긴 하지만 매력이 없다.

며 망해가는 AMD로 가서 본인 연구를 칩에 적용하여 INTEL을 이겨버립니다.

https://youtu.be/X-byHrNIxAQ? t=1227

성능을 더 뛰어나게 만들고, 값은 반토막 내어버리는... 개발 단계에서는 가능하지만 상용 제품 양산에 이것이 가능하다는 것은 정말 대단합니다. 개발된 제품도 양산시에는 거대한 생산기술 프로세스가 들어가기 때문입니다. 손으로 두들겨 만드는 것과 양산을 위해 자동화한다는 것에는 많은 차이가 있습니다. 스웨터를 손으로 만드는 것은 힘들긴 하지만 스웨터를 만들어 본 사람이라면 어느 정도 그림이 그려지나, 그 스웨터를 여러 개 뜨기 위해 스웨터를 만드는 기계를 만들어야 하는 것은 또 다른 큰 작업이라는 뜻입니다.

4. 애플이 과거 자사 CPU로 power PC를 만들다 INTEL로 넘어갔다. 잡스는 더 좋은 게 있으면 유저를 위해 그냥 그것을 쓰라는 철학이 있었다. 그래서 인텔로 갈아탔고, 거대한 회사인 adobe의 플래시를 구리다며 빼 버렸다. 그 때문에 올해 말 플래시는 완전히 끝난다.

https://www.youtube.com/watch?v=Ga_7u8IU49E

ARM으로 갈아탄 애플이 성능으로만 승부를 하고 싶다면, 당장 해야 할 일은 ARM 설계자와 리사수를 데려오는 것일 수 있다(Apple + ARM + AMD). 그러나 애플은 워낙 사용자 층이 두꺼워서 알아서 제품을 공급해 주려고 할 것이다. 혹은, ARM용 맥과 X86 기반의 CPU용 데스크톱을 계속 이원화하여 출시할 수도 있겠다. GPU 성능이 점점 중요해지면서 CPU는 일정 수준만 되어도 된다고 생각한다면 승부해 볼만 하겠다. GPU 외 TPU가 AI 분야에서 큰 성능 차이를 보였기 때문에 이제는 뭘 하는지에 따라 맞는 제품을 쓰는 게 맞다고 생각할 수도 있겠다. 초연결 시대에 데탑 성능에 집중하지 말고 그냥 클라우드 접속용으로만 쓰고 화면 공유에만 신경 써도 된다고 생각할 수도 있겠다. 이처럼 다양한 관점이 있다. 이런 관점들을 추려내는 가장 중요한 기준은 "애플은 충성 고객을 다수 보유하고 있다"는 것이다.

5. 애플의 전략을 바라고는 다양한 고려 사항이 있다. 애플을 제외한 시장이라면, 어느 기업이던 시장에서 승리하는 조건은 간단하다. 뛰어난 성능과 저렴한 가격이다. 단, 애플의 경우 지금까지 하드웨어 성능으로 승부하지 않았다. 하드웨어부터 소프트웨어까지 모두 만들 수 있으니 사용성에 집중했다. 사용자가 편리하면 그만이었던 것이다. 블루투스로 연결하던 와이파이로 연결하던 케이블로 연결하던 사용자는 "연결"이라는 것만 신경 쓰면 되었다. 가령 아이폰으로 전화가 왔을 때 맥에서 받을 수 있게 하는 기능. sidecar처럼 아이패드를 연결하면 보조 디스플레이로 쓸 수 있게 하는 것. 아이클라우드, 타임캡슐을 이용해서 자동으로 백업이 되게 하는 기능, 이전 아이폰 옆에 새 아이폰을 두면 내용을 그대로 복사해서 옮겨 주는 기능 등. 애플이라서 생각하고 구현할 수 있는 기능을 많이 보여주었다. 그런 애플이 ARM을 선택한 것은 맥 프로 같이 고성능 데스크톱 군도 만들 수 있으니 굳이 당장 고성능 시장에 집중하지 않아도 된다는 전략이 있을 것이라 생각된다.

6. 독자들 중에도 아마 애플이 WWDC에 관심이 없지만 애플 제품을 쓰고 계신 분들을 많을 거라 생각한다. 애플은 큰 변화가 있어도 기존 사용자들이 거의 느끼지 못한다. 애플 제품 사용자는 새로운 기능을 보고 사용법을 익혀서 사용하는 것이 아니라. 늘 사용하던 기능이 시나브로 더 좋게 되면서 자연스럽게 익혀지게 만든다. 기술보다 사용성에 집중하기 때문이다.

7. 어린아이도 애플 로고를 보고, 어 사과(애플)다.라고 한다. 이미 이미 로고에서 모든 철학이 결정 나 버리는 애플을 이길 만한 것이 딱히 떠오르지 않는다. 세상을 변화시키고 싶은 사람들이 구글이나 마이크로소프트, 페이스 북에 모여 있다고 해도 아마 애플에서 자유로운 능력의 발현을 보장하는 입사 제의가 오면 어느 엔지니어가 그것을 단숨에 뿌리칠 수 있겠는가?

이제 좀 더 진솔한 이야기를 해 보자.

따지고 보면 각자 상황에 맞는 컴퓨터가 따로 있다.

 난 오래도록 리눅스를 했고, 윈도를 했다. 애플에 입문한지는 6년 정도인데 맥북 프로, 에어, 아이패드 프로, 아이패드, 애플 워치, 에어포트 익스트림, 아직 안 팔고 가지고 있는 아이폰 3gs, 6, 7, 8, X, XR, 11 등 애플빠라고 해도 된다. 그중 가장 성능이 뛰어난 맥은 제온 CPU가 장착된 아이맥 프로인데 노트북을 많이 쓰고 들고 다니기 무겁고 색 결정 장애라, 맥 프레도 2개를 샀고, 나중에는 에어도 2개를 샀다. 1개는 최근 전자신문 1면에 나신 모 회사 대표님께 무상으로 드렸다. 아이패드도 6개월~1년간 안 쓰다 보니 아이패드 미니는 동생에게 보냈고 또 하나는 처가로 보냈다. 아이패드 프로도 안 켠 지 오래...

그래서 생각해 본다. 아이맥 프로는 개발할 때 참 좋다. 화면이 넓어서, 휴대용 컴퓨터는 맥북에어로 충분한 것 같다. 내 작업 대부분이 서버와 붙어서 하는 작업이라 윈도 데이터 센터 붙을 때는 mstsc, 우분투 리눅스에는 termius로 충분하다. 그 외는 CUDA  AI 컴퓨터 컨트롤은 team viewer로 컨트롤한다. 맥북 프로는 무겁고, 아이패드로는 컨트롤이 어렵기 때문에 맥북 에어로 충분하다는 것이다. 

그러나 외주 프로젝트할 때는 맥 프레가 필수다.

그리고 내 주 컴퓨터는 사실 맥이 아니다. AMD 기반의 데탑이다. X399, 64GB ram, 스레드 리퍼를 쓴다. 왜냐면 맥에서는 오버워치가 안되기 때문이다. 물론, AI도 AMD데탑에 꽂힌 2080에서 더 공부하기 쉽다. 최근 언리얼에서 무료 게임을 계속 푸는 바람에 하드디스크도 더 늘렸는데 MAC은 자유롭게 하드 디스크를 늘이려면 외장 하드가 최선이다. 맥은 하드웨어 확장이 어렵다. 최근 친구 컴퓨터를 보니,

윈도에 쿼드로 P6000을 2개 달고 쓰더라. 클라우드 쓸 것 아니면, Sli나 CrossFire나 최근 4개보다 2개가 대세인 것 같다.

http://prod.danawa.com/info/?pcode=4728048&keyword=%EC%BF%BC%EB%93%9C%EB%A1%9CP6000&cate=112753

[다나와] NVIDIA 쿼드로 P6000 D5X 24GB ABKO

최저가 7,599,990원

prod.danawa.com

만약, IT를 업으로 하지 않았다면 많은 컴퓨터를 살 일도 접할 일도 적으리라 생각한다. 그래서 일반 사용자 입장인 와이프 입장에서 생각해 본다. 집에 맥이 많지만 쓰지도 않고 프린트한다고 아이맥 프로 쓰는데 힘들어한다. 그래서 대한민국의 일반 사용자 입장에서는 다른 모든 컴퓨터는 필요 없고, 

LG 노트북 gram 이 최고다.

라고 말할 수도 있는 것이다. 참고로 LG 싫어함, 개인적으로 ㅡㅡ; 그래도 LG gram이 좋은 것은 fact니 어쩔 수 없다. 애플 자랑하는 사람에게는 "옵치 돌아가니?"라고 할 수 있고, 애플 제품 없는 사람에게는 "뭔가 다르니 그래도 한 번 써봐"라고 할 수 있겠다. 내 경우엔... 그냥... 다 싫다. 취미가 일이 되는 순간 싫은 것 같다. 한 때 얼리어답터를 좋아했었던 기억에 좋아한다고 스스로 속이고 산다. IT로 먹고사는 내가 가장 좋아하는 것은 종이와 연필이다. 만년필도 좋다.

글은 이렇게 늘 산으로 간다. 대한민국 만세. 애플이 좋긴 해도 되도록이면 국산 제품을 쓰자. 애플을 쓴다면 애플 에코 시스템 기반으로 새로운 가치를 창출하자는 것이 결론이다. 일단, ARM으로 갔으니 난 대 환영이다. 운영체제 지배받지 않는 드라이브 삽입 가능하게 해 주고, Hz 높고 쇼트에 안정적인 GPIO 포트를 직접 뽑아 주면 정말 땡큐 하겠다. 그럼, 오실로스코프도 MAC S/W로 가능할 것 같다. 뭐, 이미 만들었었지만.

혼술.

디자이너는 2D 디자이너 3D 디자이너 둘 다 있어야 겠다.