作死or革命？21:9液晶是否曇花一現(xiàn)(2)
編輯：admin 2014-03-11 09:16:11
瀏覽：838
來源：中關(guān)村在線
第
[1] < color=#ff0000>[2] [3] 頁
第2頁：豐富用戶16:9之外的選擇
豐富用戶16:9之外的選擇
作者有時候在想，21:9顯示器為什么要叫21:9呢，為什么不干脆稱之為7:3或者2.33:1呢？尤其后者更能體現(xiàn)出它跟2.35:1的好萊塢片源的近親關(guān)系不是嗎？后來想了想，顯示器廠商顯然是為了讓它和16:9的顯示器形成正面PK。 
幾種顯示器屏幕規(guī)格對比，21:9看上去更像是為了豐富用戶的選擇
跟很多網(wǎng)友的觀點不同，作者倒認為，廠商推出21:9的產(chǎn)品倒不是為了取代16:9的顯示器，而是為了在目前顯示器行業(yè)死氣沉沉的整體氛圍下為用戶提供更多的選擇，也為自己提供更多的可能。
正如手機行業(yè)所描述的那樣，你可以用iOS系統(tǒng)的手機，也可以買Android系統(tǒng)的手機，還可以選擇Windows Phone、火狐OS、烏班圖等操作系統(tǒng)的手機。顯示器廠商也是懷著這樣的一種心態(tài)，讓用戶根據(jù)自身需求有更多的選項。
21:9顯示器在多任務(wù)處理方面的確有自己的一套 
21:9顯示器在設(shè)計制圖等方面的優(yōu)勢也很明顯，并支持PIP和PBP模式
并且，目前推出的該比例顯示器產(chǎn)品均具備一個殺手級的賣點：多視窗多任務(wù)處理功能。隨著分辨率的提升，以及屏幕的寬度得到了延展，它的屏幕可以被有效利用起來。廠商在推出產(chǎn)品時都會隨機贈送分屏軟件，讓用戶根據(jù)使用環(huán)境和需求進行二屏、三屏、四屏操作，讓用戶在同一屏幕下無需切換就可以同時進行多項任務(wù)處理，從而提高用戶的工作效率。這也點還是備受消費者和網(wǎng)友認可的。
第
[1] < color=#ff0000>[2] [3] 頁
關(guān)注我們
公眾號：china_tp
微信名稱：亞威資訊
顯示行業(yè)頂級新媒體
掃一掃即可關(guān)注我們
基本
文件
流程
錯誤
SQL
調(diào)試
- 請求信息 : 2025-03-13 00:05:05 HTTP/1.1 GET : http://www.badianma.cn/news/13974.html
- 運行時間 : 0.203125s [ 吞吐率：4.92req/s ] 內(nèi)存消耗：4,654.52kb 文件加載：225
- 查詢信息 : 30 queries
- 緩存信息 : 0 reads,1 writes
- 會話信息 : SESSION_ID=8d107f7ba930f1c789884d1eb38e4ce5
- CONNECT:[ UseTime:0.000000s ] mysql:host=127.0.0.1;port=3306;dbname=chinafpdv2;charset=utf8mb4
- SHOW FULL COLUMNS FROM `tp_system` [ RunTime:0.015625s ]
- SELECT * FROM `tp_system` WHERE `id` = 1 LIMIT 1 [ RunTime:0.000000s ]
- SELECT * FROM `tp_system` WHERE `id` = 1 LIMIT 1 [ RunTime:0.000000s ]
- SHOW FULL COLUMNS FROM `tp_link` [ RunTime:0.015625s ]
- SELECT * FROM `tp_link` WHERE `status` = 1 ORDER BY `sort` [ RunTime:0.000000s ]
- SHOW FULL COLUMNS FROM `tp_link_type` [ RunTime:0.015625s ]
- SELECT * FROM `tp_link_type` ORDER BY `sort` [ RunTime:0.000000s ]
- SHOW FULL COLUMNS FROM `tp_article_recom` [ RunTime:0.015625s ]
- SELECT * FROM `tp_article_recom` WHERE `recom_id` = 14 ORDER BY `sort` DESC LIMIT 4 [ RunTime:0.000000s ]
- SHOW FULL COLUMNS FROM `tp_article` [ RunTime:0.015625s ]
- SELECT `id`,`title`,`image`,`summary` FROM `tp_article` WHERE `id` IN (39994,39918,39483,39123) ORDER BY `sort` DESC [ RunTime:0.000000s ]
- SELECT * FROM `tp_article_recom` WHERE `recom_id` = 15 ORDER BY `sort` DESC LIMIT 4 [ RunTime:0.000000s ]
- SELECT `id`,`title`,`image`,`summary` FROM `tp_article` WHERE `id` IN (39129,30890,28183,27543) ORDER BY `sort` DESC [ RunTime:0.000000s ]
- SELECT * FROM `tp_article_recom` WHERE `recom_id` = 16 ORDER BY `sort` DESC LIMIT 4 [ RunTime:0.015625s ]
- SELECT `id`,`title`,`image`,`summary` FROM `tp_article` WHERE `id` IN (39555,39554,39129,38913) ORDER BY `sort` DESC [ RunTime:0.000000s ]
- SELECT * FROM `tp_article_recom` WHERE `recom_id` = 17 ORDER BY `sort` DESC LIMIT 9 [ RunTime:0.000000s ]
- SELECT `id`,`title`,`image`,`summary` FROM `tp_article` WHERE `id` IN (39573,39495,39430,38906,25538,24624,24623,24266,23221) ORDER BY `sort` DESC [ RunTime:0.000000s ]
- SELECT * FROM `tp_article_recom` WHERE `recom_id` = 18 ORDER BY `sort` DESC LIMIT 9 [ RunTime:0.000000s ]
- SELECT `id`,`title`,`image`,`summary` FROM `tp_article` WHERE `id` IN (39555,39430,31948,28652,30,29,28,27,26) ORDER BY `sort` DESC [ RunTime:0.000000s ]
- SELECT `id`,`title` FROM `tp_article` WHERE `status` = 1 ORDER BY `sort` DESC LIMIT 9 [ RunTime:0.000000s ]
- SHOW FULL COLUMNS FROM `tp_ad` [ RunTime:0.015625s ]
- SELECT `id`,`image`,`url`,`sort`,`type_id` FROM `tp_ad` WHERE `type_id` IN (4,5,6,7) AND `status` = 1 ORDER BY `sort` [ RunTime:0.000000s ]
- SELECT * FROM `tp_article` WHERE `status` = 1 AND `id` = 13974 LIMIT 1 [ RunTime:0.000000s ]
- UPDATE `tp_article` SET `hits` = `hits` + 1 WHERE `status` = 1 AND `id` = 13974 [ RunTime:0.000000s ]
- SHOW FULL COLUMNS FROM `tp_hit` [ RunTime:0.015625s ]
- INSERT INTO `tp_hit` SET `article_id` = 13974 , `create_time` = 1741795505 [ RunTime:0.000000s ]
- SELECT * FROM `tp_article` WHERE `status` = 1 AND `cate_id` = 76 ORDER BY `sort` DESC LIMIT 15 [ RunTime:0.000000s ]
- SHOW FULL COLUMNS FROM `tp_cate` [ RunTime:0.031250s ]
- SELECT `id`,`cate_name`,`parent_id` FROM `tp_cate` WHERE `id` = 76 LIMIT 1 [ RunTime:0.000000s ]
- SELECT `id`,`cate_name`,`parent_id` FROM `tp_cate` WHERE `id` = 3 LIMIT 1 [ RunTime:0.000000s ]
0.203125s
