Gallery: Gallery1与Gallery2 的比较:修订间差异

来自站长百科
跳转至: 导航、​ 搜索
→‎结论
第138行: 第138行:


==结论==
==结论==
:As you read this article, you might have noticed a bias toward G2 over G1.  I can’t deny it either, because after switching to G2 myself I am a convert.  If this article helped you decide, I am glad no matter what.  If you read the whole thing and still haven’t decided, I would strongly suggest G2.  It has more active developers and really is situated to take over the world, resistance is futile.  My name is Locutus and we are the Borg, prepare for assimilation.
:正如你所读到的,此文似乎偏袒G2一些。但就我个人经历而言,在转用G2之后还是觉得G2比较好。如果此文能帮助你作出选择的话我会十分开心。如果你读完全篇内容后还无法做出决定的话,我会强烈建议你使用G2。G2有更多积极的开发者并且具有无可辩驳的世界影响力,换句话说你无法抗拒它。我是Locutus,我们来自伯格星,准备好被我们同化吧!(入乡随俗吧……)


=特点表单=
=特点表单=

2008年9月24日 (三) 17:25的版本

死斗擂台赛:Gallery1对阵Gallery2

介绍

此文目前应即将发布的G2.2做了适当的调整。在此文早些时候的编辑中包含有G2.1中添加的特点,当然还包括原始的G2.0版本。G2.2添加了一些简洁的特点,其中我认为最棒的是"可下载插件(downloadable plugins)"特点。它允许你直接由G2内部进行*新*插件的下载,而无需使用FTP瞎捣鼓了。
由于Gallery1和Gallery2的并存,你可能就要发问了。该文比较了两者,将二者的不同之处,相似之处,优点及弊端都揭示给读者。这将帮助你选择最适合的一款,同时也给出了建议,并确保你在决定之前,能够获取尽可能多的信息。最好的出发点就是简要地介绍两个产品,这样你就能先对二者做个基本的了解了。
Gallery1和2均为基于web的相片相册软件,由PHP编成。这意味着二者都应依托web服务器,一般是在托管的环境下。它们使用的接口为完全基于web的,这样一来上传,维护和显示图片都更为简单。它们皆使用特定的外部程序进行缩略图和自定尺寸图片的创建,而且它们是在分层文件夹中进行组织的,点击图片的缩略图之后就会转到对应的较大尺寸的图片。主要特点中的一部分为:多用户的,基于web的,高度自动化,灵活多变并且面向用户。

安装

G1和G2的初始安装步骤都很相似。你需要从gallery站点获取 “代码”,进行解压,上传到你的站点并运行安装向导。你可能需要安装某些图片操作二进制,但很可能你的托管服务提供商已经为你准备好了,这能节省不少时间。随着安装的深入,步骤也越发不同了,G1的安装非常复杂并且牵涉到很多选项。 G2的安装则简化了不少,配置选项尽可能地被压缩到最小的数目,但你得提供一些数据库信息,G1则没有对此做要求。
G2.1版本在已有的安装程序中做了改良。这些改良主要是可视化及可用性方面的修改,这些改良是在OpenUsability的调查研究之后作出的。
如果你有自己的服务器,且只安装了最基本的东西(Apache,PHP,MySQL)的话,事情就有点难办了。大部分的服务器distribution使得这些应用程序的安装极快,然而有些瑕疵能够修复却很难弄明白。对于初学者而言,MySQL足以让他们想破脑瓜了。
该选择哪一个呢? 因为G2具有更简单且更直观的安装程序,因此我觉得它是首选。但是如果你更像自己制定更多的变量的话,G1可能会更合你的口味。如果你只是略通皮毛的话,G1不对MySQL做要求的优势就体现出来了,因为MySQL对于初学者而言就是恶梦。

数据库对文件元数据存储

G1和G2之间主要区别是“元数据”(评论,标题,描述以及关键词等)是如何保留及维护的。Gallery1使用的是基于文件的方法而G2使用数据库的方法。这可能不明显,但它们都具有各自的优势和缺陷,所以在你作出选择之前要好好考量一下。首先,如果你的托管服务提供商无法提供数据库选项(如MySQL)的话,那你只有两条路可选了:使用Gallery1或换个host。
将元数据存储在某个文件中更简单,且对较小的gallery来说更快速。它对资源的要求也更低,因此相对地在低端或较旧的服务器上也能更好地运行。当然它也有缺点。随着G1容量的增多,它会用掉更多的内存(RAM)以完成某些操作。平均下来,G1的5000张图片就该封顶了。当然也有站点能够轻松地托管多余该数字的图片,但寿命大大降低了。
将元数据保留在数据库中利弊皆有。最大的优势就是可扩展性;G2应当能够无区别地保留5张,10张,100张或100万张的相片,而性能方面并不会因照片数量受太大影响。当然其他方面制约着相片数量的上限,但理论上来说,这个上限不小,或者说很大。为了证明这一点,care2 connect站点是基于较早期Gallery的alpha版本上的,并且保留有超过90万张图片(而且可能有超过5000名用户)。数据库驱动的确有劣势,如果要以指定好长度的时间来载入“framework”以处理数据库的话,那么较小的gallery可能无法看到优势所在,甚至会花费更多的时间。一个基于文件的系统打开10张相片的相册可能花费0.1秒,但数据库系统指定的读取时间是0.5秒,那么打开10张相片相册的速度显然大于0.1秒,也就是多花了时间。当然,该基于文件的系统可能需要10秒来打开含有1000张图片的相册,当读取1万张图片的相册时就会崩溃。
选择哪个? 如果你的Gallery内容很多的话,必然要选择G2了。如果你的gallery内容很少(并一直保持很少),并且依托较低端的硬件的话,那么选择起来就比较困难了。G1可能会比较管用,但跟G2的灵活性和强大的功能比起来就相形见绌了。在这种情况下,我会建议对二者都做个尝试,然后再选取你最中意的来使用。


缩略图,重设尺寸图片及全尺寸图片

G1和G2都支持玩家定义缩略图,重设尺寸图片及全尺寸图片。G2允许定义多个重设尺寸图片,某种意义上来说很有用。G1和G2都允许你指定图片的某个部分用于缩略图,该可定制性也十分诱人。G2更进一步地允许你上传自定义的图片,并将其用于特定项目的缩略图。G2还具有的矩(方)形缩略图模块会自动制作矩(方)形缩略图(建材为方形宽高比或按比例填充到方形区域中)。crop-to-square的特点也可通过修改成为G1的特点,但不是独一无二的了。G1和G2都允许用户选择某最大的文件尺寸或规格尺寸,这能有效地对图片占用空间进行限制。G1和G2(自G2.2版本)都支持自动旋转(auto-rotation)。如果你的相机具有方向感应器或旋转按钮的话,那么G1和G2都会自动正确地调整相片的方向。
G1和G2的图片格式支持范围都很大,但G2在这方面更胜一筹,它还支持PSD,PDF和TIFF一类的格式。G2还能更轻松地处理非图片/电影文件类型,允许为不同文件类型自定义缩略图并且允许进行上传。
选择哪个? 因为较之G1,G2支持更多的图片格式而且G2.2以后的版本还支持自动旋转,所以G2不失为一个好的选择。G1只是略逊一筹罢了。

图片工具包

Gallery1和Gallery2在这个方面相当相似,因此只进行简略叙述。它们都支持NetPBMImageMagick—二者都是很流行的开源图片处理工具,用于创建缩略图和定义尺寸的图片。G1也可经修改以支持ffmpeg。而Gallery2则更先进一点,同时支持GD,dcraw和ffmpeg。GD是一个图片处理程序,常以PHP构建;dcraw能够转换来自诸多数码相机份的RAW格式图片;而最令人激赏的则是ffmpeg了,它允许创建各种视频格式的缩略图。对,你可以上传一个视频并可将其中任意一帧画面作为缩略图。Gallery2通过自身的模块系统能够更轻松地支持不同的工具,这就使得将来的扩充更为简便。另一G2所带来的优势就是所有图片工具包可同时处于活动状态。这就意味着按照某种次序,GD,IM和NetPBM可以同时使用。在大多数情况下,这将提供图片格式更广的支持范围。
G1和G2都支持EXIF数据,这对大多数相机用户来说至关重要,因为它会存储有关设定,日期及图片其他方面的细节信息。G2更进一步地支持IPTC,这是另一用于图片内嵌信息的系统。
’’选择哪个?’’ 在这方面,G1可以说甘拜下风了。G2无需执行二进制就可以达成这些目的,GD的选用,IPTC数据的使用,简便的视频缩略图以及RAW格式图片的处理都无疑印证了这一点。

权限系统

Gallery1和2都具有庞大的权限系统。它们允许你指定相册拥有者(赋予他们所有控制权),拥有者可以查看图片,上传图片,发表评论等等。用户组也是G2的一大特色了,它使得大量用户的管理变得更加简单。遗憾的是,G2权限的用户界面不是很直观,尽管它比G1要更强大并且提供更好的支持,但唯独这一点让人觉得遗憾。不过这个问题已经放到了已知问题处理日程中了,将来肯定会得到解决。G1和G2都支持"隐藏的"项目,这指的是图片或相册仅当用户访问URL目录或具有足够查看权限时才表现为可见。G2还有受密码保护的相册,这样对图片访问权的限制就更加简单了,而且相对来说共享起来也不是问题。
有关权限,G1和G2之间有一个很大的区别。要让G1运作,你的图片目录必须为公共网络可访的。这意味着所有人都可以直接查看图片,只要能猜中你的图片文件名或目录名称就可以直接查看了。这可以通过某些手段加以限制,但并非总是可行的。
在G2中,图片目录(应当)被存储于web根目录之外。这意味着如果你的站点位于目录/domain.com/htdocs/中的话,你就可以将G2图片存储在/domain.com/g2data/中,这里是无法通过网络进行访问的。所有图片都可直接通过G2框架进行访问,这就使得非网络可访的图片目录无法通过绕行进行访问了。
’’选择哪个?’’ 如果你觉得G2的权限UI较为复杂的话,可以使用G1。但如果你希望图片能够完全通过你所设定的权限得到足够保护,或者你需要管理大批用户的话,G2无疑是你的选择。如果你不介意G2可能迟来的较好的权限UI的话,就选择G2吧。

外观主题

G1和G2都提供外观主题系统,这将允许用户自定义gallery的外观效果。在G1中,这仅限于颜色的自定义以及相当受限的外观种类。大部分的G1外观主题看起来大同小异,主要区别只是颜色,字体和修饰,而总体布局基本相同。G2则成为了鲜明的对比,可谓层出不穷的外观主题集合体。G2所带有的大量外观主题都各不相同,而其中蕴含的变数是无穷尽的。如果有时间,有技术并且有点胆识的话,你完全可以将G2模仿成任何你见过的相片相册系统。你甚至可以打造自己独一无二从未见过的G2相片相册系统。这都要归功于G2极为灵活的外观主题系统。其中有不少外观主题都被开发为Google Summer of Code的一部分,并且某个外观主题竞赛也在筹划之中。某种意义上说,G2的外观主题世界可谓各种爆料之所在。
外观主题及其设定最大的问题已在G2.1版本中解决。现在所有的外观主题都可以被沿用,这样对外观主题所作的更改就能简单地应用到相关联的相册了。G2.2支持递归式的水印效果添加,这无疑是如虎添翼。
’’选择哪个?’’ 这里只有一种选择,毫无疑问的一种选择:G2的外观主题更加吸引人也更加灵活,因此想选G1还真得有点勇气。

整合

G1和G2都支持与相当数量基于web的软件某种程度上的整合--从简单的图片链接到用户共享以及难辨的布局。由于牵涉到的内容太多,因此要花费很多时间进行细节上的讨论。如果你要在G1和G2中进行选择的话,最好看看自己比较偏好哪种整合并看看支持得如何。某些提供G1或G2的整合包有WordPress,phpBB2,Mambo (Joomla),PHPNuke,Invision Board,Drupal,PostNuke以及vBulletin。 可用G2整合列表
另一对熟练开发者的显示问题就是,G2编写时是将整合这一块作为考量范围的。如果你需要从头开始的话,G2包含有的API允许进行用户同步等等的项目。G2理论上可以满足你所有的需求,而不仅仅是纸上谈兵的比划比划而已。
’’选择哪个?’’ 在这种情况下,我会首先检查G1和G2整合的状况,而如果这是你作出决定的条件的话,请选择具有更高级整合的那一个吧。还有,G2整合会更好地与其他飞速发展中的程序兼容。如果你是一位开发者,而且需要从皮毛开始学习编写自己的整合的话,G2会是一条不错的途径。

上传

The method for uploading images to G1 and G2 is almost certainly going to be the most important aspect for your gallery’s users. If it is hard to use, ugly, or awkward, people will complain and your family might decide bodily harm is deserved. Luckily, the Wife Acceptance Factor (WAF) is fairly high due to the number of options available for upload.
G1和G2都 support an HTML form for uploading where users simply click a browse button, find the file they wish to upload, select it (and up to 10 more) and go. For a few images this is pretty easy, but for more than about 5 it gets tedious. That is why they also offer a Java mini-applet that loads right in the upload page. Uploading is as simple as dragging the images from a file explorer shell to the Java applet and clicking upload. There is also an “Add Pictures” button which will popup the familiar file selection box, but instead of only allowing a single selection it allows multiple. The final upload method with a high WAF is the built in Windows XP upload. On the computer you intend to use, simply download and install the registry file that is offered in your gallery. Now you will have a context based sidebar in XP that will allow you to upload any number of images, right from the shell.
Moving on to the more geek related upload methods, there's a full blown Java-based Gallery Remote (similar to the Java mini applet, but of course much bigger), uploading from a local server and uploading from a URL. The full Java applet Gallery Remote is a standalone application run on a client computer that allows you to interact with your gallery in many ways, including photo upload. Gallery Remote offers drag-and-drop file upload when used with KDE, offering a very attractive option for Linux and *BSD users. Uploading from local server allows you to provide a path on the file system where files will be found, perhaps uploaded with FTP by you earlier. The upload from web page is a very interesting upload method which most people overlook. If you give it the path of an image file, it will download it and add it to your album, but if you give it the path to an html file (or directory), it will parse the html and find all references to images and give you a list to pick and choose from. Very useful! G2's local file upload goes beyond what G1 offers in that you can select a directory for upload, and the entire directory tree will be recreated as an album structure, with all of the files in the directory added, mirroring the structure on disk.
G2 adds one more method that might not be fully considered an upload method, but must be mentioned here for completeness. That is its webcam feature, which allows you to input a URL which will be refreshed at the interval you specify. So if you point it at a webcam, it will download it when ever it should instead of just once. Interesting, but not the full blown webcam system many might hope for.
G2 also adds the ability to upload images directly from certain Nokia camera phones. Of note are also a few modules and tools, such as a Picasa importer and a plug-in for iPhoto (these two are not yet bundled with G2) and the scripts galleryadd.pl and g2add.pl (nearly the same script, but the former is for G1 and the latter for G2) which can be used locally or remotely.
’’选择哪个?’’ In this case, since G1 and G2 share a base feature set with G2 bringing a few more extras in, I believe the choice is G2. That said, they are both fairly well off and similar, so picking G1 wouldn’t be a mistake either.

水印

对于很多人来说,线上的相片展示离不开这一块儿。因为很难保证某张相片不会被别人“剽窃”,因为这是真格的开放式的展示;因此最好的保护手段就是给图片添加水印效果。G1和G2都支持水印效果,它们都能够应用户的需要可选地为缩略图,设定尺寸的图片以及全尺寸图片添加水印效果。G2在这方面也略胜一筹。使用G1,如果你为全尺寸图片添加了水印,那么该效果就会直接应用于全尺寸图片而且是永久性的。而在G2中,水印效果是被应用于图片拷贝的,这样就可以关闭水印效果,使得将来修改水印效果并用于其他项目成为可能。这里指的其他项目中包括仅为hotlinked(热链的)图片添加水印效果。这意味着,如果某人访问了你的网站,所有的图片都不会带有水印效果或仅你选择的图片带有水印效果(可能是某某某版权所有一类的字样)。稍后,如果该访问者选择了你的图片链接并将其放在自己的网站中时,水印效果就体现出来了,可以是“该图片来自domain.com。”。这也是hot linking比较不错且有意思的解决办法了!
G1和G2都支持上传时的水印添加,但仅通过HTML的形式。如果你使用的是基于java的小程序,那么水印效果就不会被应用。只要将图片所在的整个相册都打上水印效果就能解决此问题了(自G2的2.2版本开始及G1)。
’’选择哪个?’’ 在这种情况下,G2会比较好(自G2.2以来的版本;之前的G2版本不支持递归式的水印添加)。G2支持如此有趣的水印特色,但使用起来却很难。G1的水印特色使用起来很简单,但它们仅限于原始图片而这种局限性对原始图片来说是毁灭性的(无法恢复或取消)。如果使用G1的话,请不要为全尺寸图片添加水印效果,这样当你进行迁移的时候,G2就能够拷贝出一套干净不带水印效果的图片了。

投票/推选/评分

G1和G2.1都以某种方式支持评分系统。G1的评分机制更加灵活,并且能够自定名称及推选/投票的类型。G1评分系统的不足之处就是没有G2具有吸引力。G2的评分系统与netflix非常相似,带有5颗星星而星星的颜色则用来显示平均分*及*你打的分数。它还包括投票数量并能*可选地*将平均投票显示为一个小条。因为G2的评分系统使用了图形,因此能更好地融合到你的网站中去。
’’选择哪个?’’ 如果你偏好自定性强且美观的评分系统的话,G2更好些。如果你需要用户可定的评分及推选机制的话,G1能满足你的需求。

菜单语言

G1和G2都 fully support alternate languages in menu and navigation items. G1 has an extensive set of languages available already, fully translated and ready to go. G2 is a little worse off in this regard, with only a few translations fully done, more fairly done and a lot that are mostly not done. There's a complete list of G2 translations. Browse to http://example.com/gallery2/lib/tools/reports/localization.php (available in the devel package of G2) to see the status of the completion of all installed translations. Fortunately, all it takes is someone who speaks both languages and has some time. Maybe you could help?
’’选择哪个?’’ If you absolutely need your gallery in a language that G2 doesn’t have available yet, you have to choose G1. If you are one of the lucky 4 or 5 languages that are 98% done, G2 would probably be the better choice. If you have the time to actually do the translations, pick G2 and submit them back to the project!

多语言相册

One important difference between G1 and G2 is multilingual support in albums. In G1, I have been struggling to balance display aesthetics and the need to let my Chinese audience and English audience both feel comfortable. My solution has been to create really concise titles in both languages and display both on the same page. In G2, you can create a title, a description, and other text info for each language. Users of one language do not see (and be confused by) text info you created for another language.
A subtle difference also leaves a big impact on practicality in multi-lingual support. In G1, default installation includes only English. Each additional language module you add will be shown as an additional option in the language drop box. In G2, default installation includes all available languages (at least for "full installation"), so the drop box is always crowded with more than a dozen choices. There is no obvious method to remove any installed language. So if your gallery is designed to support English and Chinese only, your users will have to scroll really hard to switch to the other supported language - and there is no obvious way for a user to determine which languages do you intend to support.
Assume the gallery's default language is Chinese, a French user will likely select French as the alternate language. Now the user will see that although all menu items becomes French, all titles and descriptions are still in Chinese. If this user also reads English, he or she could have obtained more information by switching to English, but he or she is unlikely to try English under this circumstance. Even worse, this user may have even ventured English (UK) and still find all titles and descriptions in Chinese. He or she would be even more discouraged to try another language so all the information you prepared for English (US) would be wasted.
Another subtle difference affects practicality in multi-lingual support. In G1, one can use an explicit URL to force a language selection. In G2, one cannot. Therefore, in G1, you can announce your gallery or album in different languages with a definitive URL that makes sure the audience sees the URL in the language used in the announcement. You cannot do this in G2.
’’选择哪个?’’ If you want true multi-lingual support, G2 is definitely superior. However, if you only plan to add album information in a few of the many supported languages, your effort could be buried in the crowded languages drop list. You also lose the ability to announce a convenient URL to audiences of different languages.

相片打印服务

G1 and G2 offer the built in ability to send images to an online photo processing facility, but G1 offers more of them. Currently G1 and G2 both offer the services of PhotoAccess, Shutterfly and Fotokasten. Fotokasten offers services in European countries, which could be important for some users. G1 also offers Fotoserve, and adds a service called mPUSH which allows thumbnail images to be sent to cell phones. Fortunately, due to G2’s module system it is much easier to add new services. It is even possible that a service might develop or commission a module for its service to attract new business! Speaking of which, the service "Digibug" developed their own module which is included in G2.2. This is a very interesting module because it *requires* site owners to register with them and allows the site owner to set their own detailed pricing. The latest addition to Gallery 2 printing modules list is SnapGalaxy - they provide local (USA & India) as well as worldwide shipping.
’’选择哪个?’’ From release G2.2 (and probably G2.1), the number of photo printing services in G1 and G2 are virtual identical. If you take into account the Digibug service for G2 which is extremely flexible, the favor definitely falls to G2.

硬件

For many people, this will not be a concern due to the fact that they are in a shared hosting environment where they either don't know what their hardware is or have no choice in how powerful it is. Paid shared hosting environments are likely to have much more powerful servers than an individual would have, but they may also tend to be more loaded due to the sheer number of users involved. This is a hard section to write because it can depend on so many variables, but to sum it up before we start: G1 will be more appropriate for "low end" hardware, but of course both will work better as the system increases in power.
The two main aspects of any system are CPU speed and amount of RAM. Generally, since G1 uses a file-based system for metadata, you will need more and more RAM as your gallery and number of images in an album grows. Things in G1 that will increase the amount of RAM needed are the search, stats and block random features. Moving images and albums can also cause high RAM usage, especially when there are lots of sub-albums. This is because it has to build the sub-album list in memory by parsing lots of data files that have to be stored in memory. The only main point when G1 will use CPU is for resizing and building thumbs, but it's likely that you won't really care about this.
G2 should work better in lower RAM environments because the database backend is doing all the grunt work of presenting statistical data, *and* this is what a database is made to do. G2 will benefit more from CPU speed, mainly because the database and abundance of php code will need it. G2 can also build thumbs/sizes on the fly (as well as at upload), so the *initial* load of an album or resized image can take longer as G2 creates the thumb/resized image, so CPU speed will come into play here.
Let's try and apply some numbers, but keep in mind they will be very general and your specific results could vary widely. I would suggest anything below ~800MHz with ~256Mb RAM as "low end", ~800MHz - ~1.5GHz with 512Mb RAM as "middle" and ~1.5GHz+ with 1Gb+ RAM as "high end". These are just rough guesses. The amount of actual traffic will have a pretty big effect on your requirements as you climb into the big time. G1 and G2 should both run on any of these, but G1 will almost certainly have the edge at the low end. At the middle, it will depend a lot on your specific requirements and at the high end you probably won't notice much of a difference between G1 and G2.
’’选择哪个?’’ If you have a really low end system, you will almost certainly want G1. Installing a php accelerator like eAccelerator can help a lot for any system though. Try both, and if one drastically outperforms the other pick it. Just keep in mind that G2 will scale to a huge number of images and users without requiring much more RAM, but G1 will choke at some point for sure.

杂项

This section contains some items that are hard to categorize or would yield a very small category. It is mostly features that one or the other does not contain at all which might be of interest.
The main features that G1 has that G2 does not that cannot be categorized are email notification of changes and mirroring. On the G2 side, there are quite a few more. Of major note is the module system that makes G2 so flexible. Pretty much any idea can be developed as a module and then used in G2 with no hard work required, simply unzip the module in the modules directory and turn it on via the web interface. G1 also features RSS feed support and this is not included in the current final release of G2, but it was a Google Summer of Code project that went very well and will be available shortly after release (I have it installed now!).
Some of these unique modules include captcha, maps, quotas, user albums, shopping cart, zip download and random highlights.
  • Captcha is the name for a method of using a distorted image of letters to determine if a user is human or a script of some sort. It can be used during registration, when a user attempts to log in with the wrong password too many times, and to prevent anonymous comment spam.
  • The Maps module extracts the GPS coordinates from your images (if your camera supports this) and shows an interactive (Google) map with the positions where the images have been taken.
  • Quotas allow you to limit the amount of space used by a user, assignable on both a per user basis and a per group basis.
  • User albums are the automatic creation of an album for each user in your gallery, useful for easily adding new users to your gallery if you normally give each user their own album.
  • The “shopping cart” (really just “cart”) module allows users to add images to a standard cart. Instead of just being able to buy images though, the cart can be used to allow images to be sent to one of the printing services or even downloaded as a single zip file.
  • Another of the Google Summer of Code projects is a Zen module that uses the gallery cart. Zen is an open source e-commerce application.
’’选择哪个?’’ If you need email notification of changes, G1 is probably the choice for you. If you read the paragraph on G2 features and thought to yourself “Wow, some of these are very interesting and useful!” then G2 should be your choice.

结论

正如你所读到的,此文似乎偏袒G2一些。但就我个人经历而言,在转用G2之后还是觉得G2比较好。如果此文能帮助你作出选择的话我会十分开心。如果你读完全篇内容后还无法做出决定的话,我会强烈建议你使用G2。G2有更多积极的开发者并且具有无可辩驳的世界影响力,换句话说你无法抗拒它。我是Locutus,我们来自伯格星,准备好被我们同化吧!(入乡随俗吧……)

特点表单

与其他程序的比较

G1,G2,CM及其他的比较G2对CM(旧)