{"id":3038,"date":"2020-04-24T08:53:35","date_gmt":"2020-04-24T08:53:35","guid":{"rendered":"http:\/\/the-codest.localhost\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/"},"modified":"2026-04-24T11:29:19","modified_gmt":"2026-04-24T11:29:19","slug":"objektivs-skats-uz-biblioteku-kara-react-vs-vue","status":"publish","type":"post","link":"https:\/\/thecodest.co\/lv\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/","title":{"rendered":"Objekt\u012bvs skat\u012bjums uz bibliot\u0113ku karu: React pret Vue"},"content":{"rendered":"

No kurienes m\u0113s n\u0101kam? Kas m\u0113s esam? Kur m\u0113s ejam?<\/h2><\/p>\n

Apst\u0101simies uz br\u012bdi un apdom\u0101sim, kur m\u0113s atrodamies. K\u0101 piln\u012bgs bumbieris es patiesi \u0161aubos, vai pirms aptuveni 10 gadiem k\u0101ds b\u016btu var\u0113jis paredz\u0113t, ka... t\u012bmek\u013ca izstr\u0101de<\/a> var\u0113tu iet tik t\u0101lu.<\/p>\n

Lietder\u012bg\u0101s darbvirsmas lietojumprogrammas ir pag\u0101tne, jo visu var izdar\u012bt p\u0101rl\u016bkprogramm\u0101. Paties\u012bb\u0101 ar\u012b lietojumprogrammas, kur\u0101m j\u0101izmanto zem\u0101ka l\u012bme\u0146a API, kas nav pieejami p\u0101rl\u016bkprogramm\u0101, tiek rakst\u012btas, izmantojot p\u0101rl\u016bkprogrammu dzin\u0113jus un valodas, jo tas atvieglo to uztur\u0113\u0161anu.<\/p>\n

Mobil\u0101s lietojumprogrammas var viegli aizst\u0101t ar r\u012bkiem, ko izmanto, lai t\u012bmek\u013ca vietne<\/a> att\u012bst\u012bbu - sk. React<\/a> Viet\u0113jais<\/strong>, NativeScript. Turkl\u0101t mums ir PWA, kas viegli \u201cimit\u0113\u201d mobilo lietojumprogrammu darb\u012bbu. Turkl\u0101t komponenti, kas darbina lietojumprogrammu, kas uzrakst\u012bta valod\u0101 Vue<\/a><\/strong> vai React<\/strong> var viegli kop\u012bgot da\u017e\u0101dus kods<\/a> elementus starp platform\u0101m. <\/p>\n

Mums j\u0101atz\u012bst viena lieta - t\u012bmek\u013ca lietojumprogrammas pa\u0161laik ir sp\u0113c\u012bgs sp\u0113ks, kuru b\u016bs gr\u016bti nolaist uz zemes. K\u0101 lietot\u0101js es redzu, ka izmantoju t\u0101s praktiski visur: sazinoties, izmantojot Slack, lietojot koda redaktoru, veidojot prezent\u0101cijas vai pat rakstot bloga rakstu.<\/p>\n

Ir gr\u016bti paredz\u0113t, kas notiks p\u0113c da\u017eiem gadiem. WebAssembly k\u013c\u016bst aktu\u0101ls, un tas \u013caus mums<\/a> p\u0101rvietot p\u0101rl\u016bkprogrammas, kur\u0101s nepiecie\u0161ami sare\u017e\u0123\u012bt\u0101ki apr\u0113\u0137ini, uz p\u0101rl\u016bkprogrammu pasauli. Tom\u0113r viens fakts paliek nemain\u012bgs - ir patie\u0161\u0101m gr\u016bti atrast \u0161\u0137\u0113rsli, lai, izmantojot t\u012bmek\u013ca tehnolo\u0123ijas, izveidotu t\u0101du lietojumprogrammu, par k\u0101du m\u0113s varam tikai sap\u0146ot. <\/p>\n

Lielais spr\u0101dziens interneta realit\u0101t\u0113 <\/h2><\/p>\n

Pie lietas b\u016bt\u012bbas - atgriez\u012bsimies uz br\u012bdi pag\u0101tn\u0113, pirms par\u0101d\u012bj\u0101s pirmie noz\u012bm\u012bg\u0101kie t\u012bmek\u013ca ietvari un lietojumprogrammas tika izstr\u0101d\u0101tas imperat\u012bv\u0101 veid\u0101. Katra interakt\u012bv\u0101 meh\u0101nika lap\u0101 tika apstr\u0101d\u0101ta manu\u0101li, un t\u0101 bija atbild\u012bga par konkr\u0113tu darb\u012bbu.<\/p>\n

Lab\u0101kais piem\u0113rs, ko var min\u0113t, ir jQuery bibliot\u0113ka - savulaik viens no popul\u0101r\u0101kajiem vienk\u0101r\u0161u notikumu apstr\u0101des risin\u0101jumiem. Ar t\u0101s pal\u012bdz\u012bbu tika ieviestas da\u017e\u0101das nolai\u017eam\u0101s izv\u0113lnes, p\u0101rejas, anim\u0101cijas, kalkulatori un l\u012bdz\u012bga meh\u0101nika.<\/p>\n

Ir v\u0113rts piemin\u0113t, ka probl\u0113mas sare\u017e\u0123\u012bt\u0101k\u0101s lietojumprogramm\u0101s tika paman\u012btas jau tad - viet\u0101s, kur da\u017e\u0101d\u0101m, neatkar\u012bg\u0101m da\u013c\u0101m bija, piem\u0113ram, react l\u012bdz pareizam klik\u0161\u0137im vai kaut k\u0101 rakst\u012b\u0161anai. Liel\u0101kaj\u0101 da\u013c\u0101 lietojumprogrammu nebija skaidra st\u0101vok\u013ca, t\u0101 viet\u0101 gl\u0101ba, piem\u0113ram, elementu atrib\u016bti vai to klases.<\/p>\n

Tolaik bija skaidrs, ka pa\u0161reiz\u0113jai pieejai tr\u016bka reactivity - struktur\u0113ta veida, k\u0101 komponent\u0113m savstarp\u0113ji sazin\u0101ties un kop\u012bgot, piem\u0113ram, savu st\u0101vokli vai da\u017e\u0101dus notikumus, kas atvieglotu lietojumprogrammu uztur\u0113\u0161anu un \u013cautu t\u0101m nodro\u0161in\u0101t labu lieto\u0161anas pieredzi par zem\u0101m izmaks\u0101m.<\/p>\n

<\/article-digital-product-development><\/p>\n

Pirmie so\u013ci ce\u013c\u0101 uz labi zin\u0101m\u0101m sist\u0113m\u0101m<\/h2><\/p>\n

Laika gait\u0101 s\u0101ka par\u0101d\u012bties pirmie front-end ietvari, kuru m\u0113r\u0137is bija struktur\u0113t arhitekt\u016bru sare\u017e\u0123\u012bt\u0101k\u0101m lietojumprogramm\u0101m.<\/p>\n

\u0160ie karkasi galvenok\u0101rt balst\u012bj\u0101s uz MVC modeli - da\u017ei no tiem, piem\u0113ram, Backbone.js, pied\u0101v\u0101ja vair\u0101k manu\u0101lu pieeju, bet citi, piem\u0113ram, Knockout.js, izmantoja divvirzienu pieeju. dati<\/a> saisto\u0161s.<\/p>\n

Tom\u0113r var\u0113ja just, ka lietojumprogrammas rakst\u012b\u0161ana bija sare\u017e\u0123\u012bt\u0101ka, pras\u012bja daudz vair\u0101k kod\u0113\u0161anas un ne vienm\u0113r deva iecer\u0113tos rezult\u0101tus vai kompens\u0113ja lietojumprogrammas izstr\u0101d\u0113 zaud\u0113to laiku.<\/p>\n

Galvenais iemesls, k\u0101p\u0113c zelta vidusm\u0113ra atra\u0161ana JS<\/a> Ekosist\u0113ma bija gr\u016bti bija tas, ka tas bija mazliet d\u012bvain\u012bba starp labi paz\u012bstamu programm\u0113\u0161anas valodas<\/a> kas jau sen ir bru\u0123\u0113ju\u0161i savu ce\u013cu.<\/p>\n

Un es nev\u0113los \u0161eit kav\u0113ties pie t\u0101, k\u0101di tie\u0161i ce\u013ci pavad\u012bja da\u017e\u0101du ietvaru att\u012bst\u012bbu v\u0113stures gait\u0101. Tom\u0113r ir svar\u012bgi atz\u012bm\u0113t vienu lietu - JS ekosist\u0113mas brieduma laiks p\u0101rl\u016bkprogramm\u0101s nebija viegls un sask\u0101r\u0101s ar daudziem p\u0101rbaud\u012bjumiem.<\/p>\n

Tas ir vien\u012bgais iemesls, k\u0101p\u0113c \u0161odien m\u0113s varam veidot t\u012bmek\u013ca lietojumprogrammas un izstr\u0101d\u0101t t\u0101s \u013coti vienk\u0101r\u0161\u0101 un nes\u0101p\u012bg\u0101 veid\u0101.<\/p>\n

Pamatinform\u0101cija un neliels sal\u012bdzin\u0101jums<\/h2><\/p>\n

T\u0101 viet\u0101, lai m\u0113t\u0101tos ga\u013cu, k\u0101 tas ir ierasts internet\u0101, apskat\u012bsim abas bibliot\u0113kas, apkoposim par t\u0101m inform\u0101ciju un sal\u012bdzin\u0101sim t\u0101s - gan teor\u0113tiski, gan praktiski.<\/p>\n

PIEZ\u012aME: meh\u0101nismu, kas darbojas Vue <\/strong>attiecas tie\u0161i uz 2. versiju. 3. versij\u0101 ir ieviestas daudzas b\u016btiskas izmai\u0146as, ta\u010du t\u0101 nav re\u0101ls konkurents 3. versijai. React<\/strong> \u0161obr\u012bd, ja tikai t\u0101 brieduma d\u0113\u013c - Vue 3 izlai\u0161anas datums: 2020. gada 18. septembris.<\/p>\n

\"React<\/p>\n

Izskaidrosim vienu lietu - iedzi\u013cinoties ab\u0101s bibliot\u0113k\u0101s, var redz\u0113t, ka paties\u012bb\u0101 ir vair\u0101k l\u012bdz\u012bbu nek\u0101 at\u0161\u0137ir\u012bbu. Ne\u0146emot v\u0113r\u0101 bibliot\u0113ku lieto\u0161anas veidu k\u0101 t\u0101du - ab\u0101m bibliot\u0113k\u0101m ir \u013coti l\u012bdz\u012bgas koncepcijas par to, k\u0101 t\u0101s darbojas. Abas nodro\u0161ina l\u012bdz\u012bga ekosist\u0113ma, un to izmanto\u0161ana nav diametr\u0101li at\u0161\u0137ir\u012bga.<\/p>\n

\u25cf Velns sl\u0113pjas deta\u013c\u0101s - jo bie\u017e\u0101k m\u0113s izmantojam k\u0101du r\u012bku, jo liel\u0101kus tr\u016bkumus m\u0113s paman\u0101m t\u0101 da\u017e\u0101do risin\u0101jumu d\u0113\u013c. Labs piem\u0113rs \u0161eit var b\u016bt divvirzienu datu sasaiste, ko visbie\u017e\u0101k izmanto Vue<\/strong> k\u0101 v-mode\u013ca \u012bpa\u0161\u012bbu: tas bie\u017ei vien atvieglo darbu, par daudz\u0101m liet\u0101m r\u016bp\u0113jas autom\u0101tiski un neprasa kod\u0113t papildu atbalstu v\u0113rt\u012bbu mai\u0146ai.<\/p>\n

Tom\u0113r ir gad\u012bjumi, kad mums ir \u012bpa\u0161i j\u0101seko l\u012bdzi izmai\u0146u m\u0113\u0123in\u0101jumam un attiec\u012bgi react, un t\u0101d\u0101 gad\u012bjum\u0101 uz v-modeli balst\u012btie komponenti bie\u017ei vien liek mums \u0137erties pie citiem. Vue<\/strong> meh\u0101nika, piem\u0113ram, apr\u0113\u0137in\u0101t\u0101 \u012bpa\u0161\u012bba, t\u0101p\u0113c sasniegtais efekts bie\u017ei vien izskat\u0101s daudz slikt\u0101ks nek\u0101 ar manu\u0101lu pieeju;<\/p>\n

\u25cf V\u0113l viens interesants aspekts ir JSX, kas ir \u0161\u0101ds \u201cvagrant\u201d veids, k\u0101 atveidot saturu, izmantojot React<\/strong>. Izstr\u0101d\u0101t\u0101ju kopien\u0101 par to ir da\u017e\u0101di viedok\u013ci.<\/p>\n

P\u0113c maniem nov\u0113rojumiem \u0161\u0137iet, ka izstr\u0101d\u0101t\u0101ji, kas izmanto citu vidi, nevis JS, piem. PHP<\/a> vai C#, ir vair\u0101k tend\u0113tas uz \u0161abloniem, kas Vue<\/strong> dara.<\/p>\n

Apkopojot - veidnes, kas zin\u0101mas no Vue<\/strong> \u013cauj \u013coti skaidri un eleganti defin\u0113t skatus, savuk\u0101rt React JSX \u013cauj tos veidot daudzos gad\u012bjumos \u0101tr\u0101k, piel\u0101got konkr\u0113t\u0101m vajadz\u012bb\u0101m un bie\u017ei vien prasa maz\u0101k koda, lai izveidotu da\u017e\u0101das strukt\u016bras;<\/p>\n

\u25cf Apskat\u012bsim ar\u012b \u0161o divu r\u012bku ekosist\u0113mas. Princip\u0101 varam teikt, ka t\u0101s ne ar ko neat\u0161\u0137iras. Abus tos ne velti sauc par bibliot\u0113k\u0101m - tie nodro\u0161ina minimumu react\u012bvs t\u012bmek\u013ca lietojumprogrammu atbalsts.<\/p>\n

Savuk\u0101rt p\u0101r\u0113jie, kas saist\u012bti ar sazi\u0146u ar API<\/a>, datu pl\u016bsma, UI komponenti, kas tiek izmantoti ap da\u017e\u0101d\u0101m apak\u0161lap\u0101m, ir t\u0101 sauktie p\u0101rdev\u0113ji - bibliot\u0113kas, kas \u0146emtas no \u0101rpuses un kas ir pareizi j\u0101pievieno. projekts<\/a>. Tas ir l\u012bdz\u012bgi k\u0101 Lego pasaul\u0113: ja v\u0113laties uzb\u016bv\u0113t vienotu veselumu, jums tas ir j\u0101saliek kop\u0101 no atsevi\u0161\u0137iem, maziem kluc\u012b\u0161iem.<\/p>\n

\u0160\u012b alegorija attiecas uz prec\u012bzi pievienot\u0101m sast\u0101vda\u013c\u0101m, kas ir lietojumprogrammu, kuras izveidotas ar React<\/strong> vai Vue<\/strong>;<\/p>\n

\u25cf Svar\u012bgs aspekts, \u012bpa\u0161i cilv\u0113kiem, kuriem nav lielas pieredzes JS vid\u0113, ir piek\u013cuves l\u012bmenis konkr\u0113tai bibliot\u0113kai. Citiem v\u0101rdiem sakot - r\u012bka sare\u017e\u0123\u012bt\u012bba, ko veido tie\u0161ais laiks, kas j\u0101pat\u0113r\u0113, lai izprastu t\u0101 meh\u0101niku.<\/p>\n

Es dom\u0101ju, ka \u0161eit ir nep\u0101rprotami j\u0101nor\u0101da viena lieta - attiec\u012bb\u0101 uz Vue<\/strong>, tas ir daudz vienk\u0101r\u0161\u0101k. Mums ir divvirzienu datu sasaiste, mums ir eleganti noteikts \u0161ablons, kas ir maldino\u0161i l\u012bdz\u012bgs citu valodu, piem\u0113ram, twig, risin\u0101jumiem, un visbeidzot - mums nav galvass\u0101pju, ko rada teorijas apguve par atsevi\u0161\u0137u \u0101\u0137u darb\u012bbu un gad\u012bjumiem, kad j\u0101izmanto konkr\u0113ta meh\u0101nika.<\/p>\n

Ko liecina statistika?<\/h2><\/p>\n

Tie\u0161a seko\u0161ana p\u016b\u013ca balsij nav \u012bsti laba izv\u0113le. Tom\u0113r labs solis, lai pie\u0146emtu labu l\u0113mumu, ir izanaliz\u0113t, ko saka cilv\u0113ki, kuri ir sadarboju\u0161ies ar \u0161\u012bm bibliot\u0113k\u0101m.<\/p>\n

\"vue<\/p>\n

Un j\u0101 - zvaigznes par github <\/a> var b\u016bt r\u0101d\u012bt\u0101js tam, cik liel\u0101 m\u0113r\u0101 konkr\u0113t\u0101s bibliot\u0113kas kopiena ir iesaist\u012bta t\u0101s att\u012bst\u012bb\u0101, k\u0101 to uztver izstr\u0101d\u0101t\u0101ji un vai vi\u0146i ir ieinteres\u0113ti, kurp t\u0101 virz\u0101s. In\u017eenieri<\/a> kuri izmanto konkr\u0113tu repozitoriju, bie\u017ei sa\u0146em pazi\u0146ojumus par jaun\u0101m versij\u0101m vai izmai\u0146\u0101m kod\u0101, t\u0101d\u0113j\u0101di tie\u0161\u0101 veid\u0101 ieg\u016bstot zin\u0101\u0161anas par bibliot\u0113ku.<\/p>\n

Tom\u0113r zvaigzn\u012b\u0161u skaitu github vietn\u0113 nevajadz\u0113tu uzskat\u012bt par z\u012bmi - ne katrs izstr\u0101d\u0101t\u0101js, kuram pat\u012bk k\u0101ds r\u012bks, atst\u0101s z\u012bmi - t\u0101 viet\u0101 es to uzskat\u012btu par t\u012bras aizrau\u0161an\u0101s paz\u012bmi, ko izstr\u0101d\u0101t\u0101ji izr\u0101da attiec\u012bb\u0101 uz konkr\u0113tu atv\u0113rt\u0101 koda projektu.<\/p>\n

\"react<\/p>\n

Google Trends <\/a> ir labi zin\u0101ms pakalpojums, kas \u013cauj p\u0113t\u012bt interesi par konkr\u0113t\u0101m t\u0113m\u0101m laika gait\u0101. Lai gan tas nav racion\u0101ls kvalit\u0101tes vai izmanto\u0161anas r\u0101d\u012bt\u0101js, tas var sniegt da\u017e\u0101da veida anal\u012bzi.<\/p>\n

Sal\u012bdzinot abus \u0161odienas raksta varo\u0146us, ir viegli paman\u012bt, ka p\u0113d\u0113jo piecu gadu gaita ir iez\u012bm\u0113jusies diezgan l\u012bdz\u012bgi. No diagrammas var secin\u0101t, ka galvenie secin\u0101jumi ir \u0161\u0101di. React<\/strong> mekl\u0113\u0161anas popularit\u0101te ir augst\u0101ka sal\u012bdzin\u0101jum\u0101 ar pretinieku.<\/p>\n

Lai b\u016btu skaidrs - atra\u0161an\u0101s Google tenden\u010du top\u0101 nenoz\u012bm\u0113, ka bibliot\u0113ka ir lab\u0101ka. Tas ir saist\u012bts ar p\u016b\u013ca popularit\u0101ti, k\u0101 jau min\u0113ju iepriek\u0161 - iesp\u0113jams, par \u0161o r\u012bku ir dzird\u0113ju\u0161i vair\u0101k cilv\u0113ku, tas ir izrais\u012bjis liel\u0101ku interesi starp CTOs<\/a>, programmat\u016bras izstr\u0101d\u0101t\u0101ji<\/a> <\/strong>vai cilv\u0113kiem, kuri vienk\u0101r\u0161i v\u0113las apg\u016bt k\u0101du konkr\u0113tu r\u012bku.<\/p>\n

Vai \u0161is grafiks atspogu\u013cojas realit\u0101t\u0113? Nedaudz, j\u0101. Kopum\u0101 - aptauj\u0101to cilv\u0113ku vid\u016b vair\u0101k ir t\u0101du, kas uzr\u0101da daudzveid\u012bgas un sare\u017e\u0123\u012btas zin\u0101\u0161anas par React<\/strong> nek\u0101 Vue<\/strong>. K\u0101dus viedok\u013cus j\u016bs varat ieg\u016bt, run\u0101jot ar \u0161iem cilv\u0113kiem? Es cent\u012b\u0161os to izkl\u0101st\u012bt n\u0101kamaj\u0101 rindkop\u0101.<\/p>\n

\"R\u0101mju<\/p>\n

\"JS<\/p>\n

\"React<\/p>\n

JS st\u0101voklis\u00a0<\/a> ir vietne, kur\u0101 katru gadu tiek veikta ar JavaScript saist\u012btaj\u0101s tehnolo\u0123ij\u0101s str\u0101d\u0101jo\u0161o aptauja. T\u0101s m\u0113r\u0137is ir apkopot inform\u0101ciju no izstr\u0101d\u0101t\u0101jiem par to, k\u0101 vi\u0146i v\u0113rt\u0113 r\u012bkus, ar kuriem vi\u0146i str\u0101d\u0101 ikdien\u0101.<\/p>\n

Jaut\u0101jumos apl\u016bkoti atsevi\u0161\u0137i r\u012bki da\u017e\u0101diem m\u0113r\u0137iem, piem\u0113ram, r\u012bki, ko izmanto front-end un back-end, k\u0101 ar\u012b r\u012bki test\u0113\u0161anai, lietojumprogrammas st\u0101vok\u013ca p\u0101rvald\u012bbai u. c. Uz katru no \u0161iem jaut\u0101jumiem nav vienk\u0101r\u0161as atbildes \u201cj\u0101\/n\u0113\u201d, vietn\u0113 tiek uzdota virkne jaut\u0101jumu par pa\u0161u r\u012bku, interes\u0113m, pieredzi un visp\u0101r\u0113ju nov\u0113rt\u0113jumu, kas reduc\u0113jas l\u012bdz teikumam \"Vai j\u016bs izmantotu \u0161o r\u012bku turpm\u0101kajos projektos?\".\u201d<\/p>\n

Pati vietne \u013cauj veikt daudz anal\u012b\u017eu, sal\u012bdzin\u0101t attiec\u012bgos r\u012bkus un da\u017ek\u0101rt uzzin\u0101t par maz\u0101k zin\u0101m\u0101m bibliot\u0113k\u0101m, kas JS pasaul\u0113 s\u0101k labi att\u012bst\u012bties, g\u016bstot popularit\u0101ti un vienlaikus baudot augstu \u201clieto\u0161anas prieka\u201d r\u0101d\u012bt\u0101ju. Sirsn\u012bgi iesaku jums p\u0101rl\u016bkot \u0161\u012bs vietnes saturu.<\/p>\n

Apkoposim \u0161o sada\u013cu ar statistikas datiem. Da\u017e\u0101du veidu grafiku anal\u012bze bie\u017ei vien var b\u016bt \u013coti laba iesp\u0113ja, lai sal\u012bdzin\u0101tu da\u017e\u0101dus konkr\u0113tas t\u0113mas aspektus. Tom\u0113r ir svar\u012bgi \u0146emt v\u0113r\u0101, ka sekot p\u016b\u013ca balsij ne vienm\u0113r b\u016bs visgudr\u0101k\u0101 r\u012bc\u012bba. T\u0101 viet\u0101 j\u016bs varat pie\u0146emt pamatotu l\u0113mumu, izmantojot da\u017eas no diagrammu anal\u012bz\u0113 g\u016btaj\u0101m atzi\u0146\u0101m.<\/p>\n

Lab\u0101k\u0101 izv\u0113le izstr\u0101d\u0101t\u0101jam<\/h2><\/p>\n

Iepriek\u0161 es min\u0113ju zem\u0101ko ieejas slieksni uz Vue<\/strong> - Paties\u012bb\u0101 tas \u013cauj jums nedaudz \u0101tr\u0101k piev\u0113rsties faktiskajai lietojumprogrammas izstr\u0101dei, izmantojot r\u012bku un l\u012bdz minimumam samazinot laiku, kas nepiecie\u0161ams, lai iepaz\u012btos ar vidi, meh\u0101niku un da\u017e\u0101diem lieto\u0161anas gad\u012bjumiem.<\/p>\n

Kopum\u0101 mans viedoklis ir, ka Vue<\/strong> ir vair\u0101k piem\u0113rots cilv\u0113kiem, kuri v\u0113l nav str\u0101d\u0101ju\u0161i ar front-end bibliot\u0113k\u0101m. Protams, tas \u013caus jums daudz iedro\u0161ino\u0161\u0101k\u0101 veid\u0101 \u012bs\u0101 laik\u0101 ieg\u016bt apmierino\u0161us rezult\u0101tus.<\/p>\n

Tom\u0113r teiksim ska\u013ci - valodas, kur\u0101 lietojam konkr\u0113tus r\u012bkus, nezin\u0101\u0161ana agri vai v\u0113lu mums kait\u0113s. Vienk\u0101r\u0161\u0101m liet\u0101m tas ir nenoz\u012bm\u012bgs elements, bet, pieaugot rad\u012bto lietojumprogrammu sare\u017e\u0123\u012bt\u012bbai, b\u016bs arvien gr\u016bt\u0101k un gr\u016bt\u0101k izveidot lietojumprogrammas pien\u0101c\u012bg\u0101 veid\u0101 bez lab\u0101m zin\u0101\u0161an\u0101m. JavaScript<\/a>.<\/p>\n

Es \u012bsti nerun\u0101ju par sp\u0113ju rakst\u012bt sare\u017e\u0123\u012btas funkcijas, jo \u0161o da\u013cu liel\u0101 m\u0113r\u0101 var aizst\u0101t, piem\u0113ram, ar p\u0101rdev\u0113jiem. Es run\u0101ju par da\u017e\u0101m bie\u017ei sastopam\u0101m k\u013c\u016bd\u0101m, ko var pie\u013caut valod\u0101, un neapzin\u0101\u0161anos, ka nepareiza uzved\u012bba nav saist\u012bta ar bibliot\u0113kas, bet gan ar valodas lieto\u0161anu. Visbie\u017e\u0101k sastopam\u0101 k\u013c\u016bda, kas \u0161eit izpau\u017eas, ir t\u0101 saukt\u0101 nemain\u012bba - tas ir, zin\u0101\u0161anas par atsauces meh\u0101nismu JavaScript.<\/p>\n

Es nevaru ieteikt, kura bibliot\u0113ka ir lab\u0101ka izstr\u0101d\u0101t\u0101jiem, kas vair\u0101k vai maz\u0101k p\u0101rzina JavaScript. Bet es zinu vienu - ja v\u0113laties g\u016bt re\u0101lu priek\u0161statu par to, k\u0101 izskat\u0101s izstr\u0101de ar abiem r\u012bkiem \u201cno iek\u0161puses\u201d, - pam\u0113\u0123iniet rakst\u012bt lietojumprogrammas katr\u0101 no tiem. Tas sniegs jums priek\u0161statu, \u013caus saprast, kuri meh\u0101nismi j\u016bs uzrun\u0101 vair\u0101k un kas jums ir lab\u0101ka izv\u0113le.<\/p>\n

K\u0101 jau iepriek\u0161 min\u0113ju - abas bibliot\u0113kas darbojas l\u012bdz\u012bg\u0101s ekosist\u0113m\u0101s, un t\u0101m ir l\u012bdz\u012bgi uzskati par lietojumprogrammu veido\u0161anu ar maz\u0101m komponent\u0113m. Ab\u0101m bibliot\u0113k\u0101m kl\u0101jas labi - nekas neliecina, ka k\u0101da no t\u0101m tuv\u0101kaj\u0101 n\u0101kotn\u0113 izzud\u012bs. L\u012bdz ar to darba pied\u0101v\u0101jumi ab\u0101s saglab\u0101sies l\u012bdz\u012bg\u0101 l\u012bmen\u012b.<\/p>\n

Secin\u0101jumi ir vienk\u0101r\u0161i - izmantojiet to, kas jums ir piem\u0113rots, uzkr\u0101jiet pieredzi un izv\u0113rt\u0113jiet. Tas pal\u012bdz\u0113s jums izstr\u0101d\u0101t racion\u0101lu pieeju tam, vai konkr\u0113taj\u0101 projekt\u0101 lab\u0101k izmantot vienu vai otru bibliot\u0113ku; turkl\u0101t m\u0113\u0123iniet eksperiment\u0113t - nekas nem\u0101ca tik dzi\u013ci k\u0101 pag\u0101tn\u0113 pie\u013caut\u0101s k\u013c\u016bdas.<\/p>\n

Lab\u0101kais izv\u0113le CTO<\/a> <\/h2><\/p>\n

Nav nosl\u0113pums, ka nav zelta vidusce\u013ca, kas b\u016btu lab\u0101kais risin\u0101jums konkr\u0113tam projektam. Jo \u012bpa\u0161i front-end lietojumprogrammu izveid\u0113 izmantotie r\u012bki \u0101tri noveco, un bie\u017ei vien ir gr\u016bti orient\u0113ties jaun\u0101kaj\u0101s tendenc\u0113s.<\/p>\n

Tom\u0113r tehnolo\u0123iju izv\u0113le nav vai vismaz nevajadz\u0113tu b\u016bt atkar\u012bga no t\u0101, kas atbilst pa\u0161reiz\u0113j\u0101m tendenc\u0113m. T\u0101 viet\u0101 mums t\u0101 b\u016btu j\u0101virza uz konkr\u0113t\u0101m gaid\u0101m un pie\u0146\u0113mumiem par lietojumprogrammu, ko gatavojamies izveidot. Katrai no sal\u012bdzin\u0101taj\u0101m bibliot\u0113k\u0101m ir savas stipr\u0101s un v\u0101j\u0101s puses, kas, saska\u0146otas ar lieto\u0161anas gad\u012bjumu, \u013caus mums izdar\u012bt vispamatot\u0101ko izv\u0113li.<\/p>\n

Interesants variants var izr\u0101d\u012bties lielo korpor\u0101ciju tehnolo\u0123iju kopsavilkumi, kuros bie\u017ei aprakst\u012bti to lietojuma gad\u012bjumi, k\u0101 norit\u0113ja vai norit milz\u012bgu lietojumprogrammu izstr\u0101de un k\u0101das k\u013c\u016bdas t\u0101s pie\u013c\u0101vu\u0161as pag\u0101tn\u0113. Iesp\u0113jams, starp tiem atrad\u012bsim gad\u012bjumus, kas ir \u012bpa\u0161i interesanti kontekst\u0101 ar bibliot\u0113kas izv\u0113li konkr\u0113tam projektam.<\/p>\n

Iez\u012bmes, kas j\u0101\u0146em v\u0113r\u0101, lai izv\u0113l\u0113tos pareizos r\u012bkus veidojamai lietojumprogrammai, ir \u0161\u0101das: lietojumprogrammas izstr\u0101des laiks, lieto\u0161anas \u0113rtums, lietojumprogrammas izstr\u0101des ilgums, lietojumprogrammas izstr\u0101des vieglums, lietojumprogrammas lietojumprogrammas uztur\u0113\u0161ana<\/a>, lietojumprogrammas sare\u017e\u0123\u012bt\u012bbu un izstr\u0101d\u0101t\u0101ju pieredzi konkr\u0113tu bibliot\u0113ku izmanto\u0161an\u0101.<\/p>\n

Izstr\u0101d\u0101t\u0101ji ir cilv\u0113ki, kuri visvair\u0101k laika pavada ar manis sal\u012bdzin\u0101tajiem r\u012bkiem, un vi\u0146i ir tie, kuri var sniegt lab\u0101kos padomus un pal\u012bdz\u0113t jums izdar\u012bt lab\u0101ko izv\u0113li lielaj\u0101 bibliot\u0113ku sadursm\u0113. Tie\u0161i lietojumprogrammu izstr\u0101des laik\u0101 j\u016bs redzat da\u017e\u0101das probl\u0113mas, kas rodas tie\u0161i no tehnolo\u0123ijas izv\u0113les, un vislab\u0101k redzat, k\u0101das lietas apgr\u016btina konkr\u0113ta r\u012bka izmanto\u0161anu konkr\u0113t\u0101m funkcij\u0101m.<\/p>\n

K\u0101 jau min\u0113ju iepriek\u0161 - abas bibliot\u0113kas, \u0161\u0137iet, nepaz\u016bd no tirgus<\/a>, vismaz ne tuv\u0101kajos gados. T\u0101 viet\u0101, lai pie\u0146emtu l\u0113mumus, pamatojoties uz statistiku un viedok\u013ciem
\nno da\u017e\u0101diem cilv\u0113kiem internet\u0101 - varb\u016bt lab\u0101ks risin\u0101jums ir vienk\u0101r\u0161i aprun\u0101ties ar izstr\u0101d\u0101t\u0101jiem.<\/p>\n

Iepaz\u012bstiniet vi\u0146us ar to, ko sagaid\u0101m no pieteikuma, k\u0101ds laiks ir atv\u0113l\u0113ts t\u0101 iesnieg\u0161anai, un \u013caujiet vi\u0146iem br\u012bvi apmain\u012bties viedok\u013ciem par to, ko vi\u0146i dom\u0101 par abiem risin\u0101jumiem, pirms m\u0113s pie\u0146emam gal\u012bgo l\u0113mumu.<\/p>\n

Secin\u0101jumi<\/h2><\/p>\n

Interneta kari parasti - vai varb\u016bt visos gad\u012bjumos - ir bezj\u0113dz\u012bgi. Vienm\u0113r atrad\u012bsies cilv\u0113ki, kas sp\u012bt\u012bgi apgalvos, ka vi\u0146u izv\u0113le ir lab\u0101ka, nesniedzot nek\u0101dus racion\u0101lus argumentus, kas apstiprin\u0101tu vi\u0146u l\u0113mumu.<\/p>\n

T\u0101 viet\u0101, lai ap\u017eilbin\u0101tu ar konkr\u0113t\u0101m izv\u0113l\u0113m, koncentr\u0113simies uz anal\u012bzi, m\u0113\u0123in\u0101sim izdar\u012bt atbilsto\u0161us secin\u0101jumus un izmantot tos, lai piel\u0101gotu vai noraid\u012btu konkr\u0113tu risin\u0101jumu.<\/p>\n

K\u0101 jau nor\u0101da virsraksts - es negribu vainagot k\u0101du konkr\u0113tu bibliot\u0113ku k\u0101 l\u012bdzekli pret vis\u0101m s\u0101p\u0113m. T\u0101 viet\u0101 tiek izvirz\u012btas da\u017eas hipot\u0113zes un atkl\u0101tas abu bibliot\u0113ku stipr\u0101s un v\u0101j\u0101s puses. Esmu sniedzis da\u017eus padomus par to, kam piev\u0113rst uzman\u012bbu, izv\u0113loties starp t\u0101m, lai pie\u0146emtu gudru l\u0113mumu un nevad\u012btos p\u0113c tendenc\u0113m vai nejau\u0161iem cilv\u0113kiem no interneta.<\/p>\n

Katrs r\u012bks var pietiekami labi atbilst projekta vajadz\u012bb\u0101m. Neviens no tiem tuv\u0101kajos gados \u0101tri nepazud\u012bs no tirgus. Abiem ir sp\u0113c\u012bgas kopienas un diezgan liela brieduma pak\u0101pe, kas liecina, ka \u0161iem diviem r\u012bkiem kl\u0101jas diezgan labi.<\/p>\n

Gal\u012bg\u0101 izv\u0113le ir j\u016bsu rok\u0101s. Tom\u0113r, ja jums ir k\u0101das \u0161aubas vai vienk\u0101r\u0161i v\u0113laties apspriest savu lietu ar The Codest<\/a> - sazinieties ar mums!<\/p>\n

<\/article-product-development-consulting><\/p>\n

Las\u012bt vair\u0101k:<\/b><\/p>\n

K\u0101p\u0113c jums (iesp\u0113jams) vajadz\u0113tu izmantot Typescript<\/a><\/p>\n

K\u0101 nenogalin\u0101t projektu ar sliktu kod\u0113\u0161anas praksi?<\/a><\/p>\n

Datu ieg\u016b\u0161anas strat\u0113\u0123ijas NextJS<\/a><\/p>","protected":false},"excerpt":{"rendered":"

T\u012bkla strauj\u0101 izaugsme, kas s\u0101k\u0101s aptuveni pirms 10 gadiem, ir rad\u012bjusi lielu apjukumu interneta pasaul\u0113. Tas ne tikai \u013c\u0101va p\u0101rl\u016bkprogramm\u0101 veikt vair\u0101k darb\u012bbu, bet ar\u012b main\u012bja visp\u0101r\u0113jo skat\u012bjumu uz lietojumprogrammu izstr\u0101di. Tom\u0113r \u0161\u012b pieeja pras\u012bja da\u017eus uzlabojumus p\u0101rl\u016bkprogrammu lietojumprogrammu koda uztur\u0113\u0161an\u0101. Tas bija laiks, kad tika izstr\u0101d\u0101ti pirmie front-end karkasi. Divus no tiem \u0161odien analiz\u0113\u0161u zem mikroskopa.<\/p>","protected":false},"author":2,"featured_media":3039,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[8],"tags":[],"class_list":["post-3038","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software-development"],"acf":[],"yoast_head":"\nAn objective look at the library war: React vs Vue - The Codest<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/thecodest.co\/lv\/emuars\/objektivs-skats-uz-biblioteku-kara-react-vs-vue\/\" \/>\n<meta property=\"og:locale\" content=\"lv_LV\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"An objective look at the library war: React vs Vue\" \/>\n<meta property=\"og:description\" content=\"The explosive growth of the web that has started about 10 years ago has caused great confusion in the world of the internet. Not only did it make it possible to do more things in the browser, but also changed the general view of application development. However, this approach required some improvements in maintaining the code of browser-based applications. This was the time of development of the first front-end frameworks. I will analyse two of them under the microscope today.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/thecodest.co\/lv\/emuars\/objektivs-skats-uz-biblioteku-kara-react-vs-vue\/\" \/>\n<meta property=\"og:site_name\" content=\"The Codest\" \/>\n<meta property=\"article:published_time\" content=\"2020-04-24T08:53:35+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-24T11:29:19+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/react_vs_vue.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"960\" \/>\n\t<meta property=\"og:image:height\" content=\"540\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"thecodest\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"thecodest\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"14 min\u016b\u0161u\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/\"},\"author\":{\"name\":\"thecodest\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/person\\\/7e3fe41dfa4f4e41a7baad4c6e0d4f76\"},\"headline\":\"An objective look at the library war: React vs Vue\",\"datePublished\":\"2020-04-24T08:53:35+00:00\",\"dateModified\":\"2026-04-24T11:29:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/\"},\"wordCount\":2808,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/05\\\/react_vs_vue.jpg\",\"articleSection\":[\"Software Development\"],\"inLanguage\":\"lv-LV\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/\",\"url\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/\",\"name\":\"An objective look at the library war: React vs Vue - The Codest\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/05\\\/react_vs_vue.jpg\",\"datePublished\":\"2020-04-24T08:53:35+00:00\",\"dateModified\":\"2026-04-24T11:29:19+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/#breadcrumb\"},\"inLanguage\":\"lv-LV\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"lv-LV\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/#primaryimage\",\"url\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/05\\\/react_vs_vue.jpg\",\"contentUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/05\\\/react_vs_vue.jpg\",\"width\":960,\"height\":540},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/an-objective-look-at-the-library-war-react-vs-vue\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/thecodest.co\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"An objective look at the library war: React vs Vue\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#website\",\"url\":\"https:\\\/\\\/thecodest.co\\\/\",\"name\":\"The Codest\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/thecodest.co\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"lv-LV\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#organization\",\"name\":\"The Codest\",\"url\":\"https:\\\/\\\/thecodest.co\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"lv-LV\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/03\\\/thecodest-logo.svg\",\"contentUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/03\\\/thecodest-logo.svg\",\"width\":144,\"height\":36,\"caption\":\"The Codest\"},\"image\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/pl.linkedin.com\\\/company\\\/codest\",\"https:\\\/\\\/clutch.co\\\/profile\\\/codest\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/person\\\/7e3fe41dfa4f4e41a7baad4c6e0d4f76\",\"name\":\"thecodest\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"lv-LV\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g\",\"caption\":\"thecodest\"},\"url\":\"https:\\\/\\\/thecodest.co\\\/lv\\\/author\\\/thecodest\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Objekt\u012bvs skat\u012bjums uz bibliot\u0113ku karu: React pret Vue - The Codest","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/thecodest.co\/lv\/emuars\/objektivs-skats-uz-biblioteku-kara-react-vs-vue\/","og_locale":"lv_LV","og_type":"article","og_title":"An objective look at the library war: React vs Vue","og_description":"The explosive growth of the web that has started about 10 years ago has caused great confusion in the world of the internet. Not only did it make it possible to do more things in the browser, but also changed the general view of application development. However, this approach required some improvements in maintaining the code of browser-based applications. This was the time of development of the first front-end frameworks. I will analyse two of them under the microscope today.","og_url":"https:\/\/thecodest.co\/lv\/emuars\/objektivs-skats-uz-biblioteku-kara-react-vs-vue\/","og_site_name":"The Codest","article_published_time":"2020-04-24T08:53:35+00:00","article_modified_time":"2026-04-24T11:29:19+00:00","og_image":[{"width":960,"height":540,"url":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/react_vs_vue.jpg","type":"image\/jpeg"}],"author":"thecodest","twitter_card":"summary_large_image","twitter_misc":{"Written by":"thecodest","Est. reading time":"14 min\u016b\u0161u"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/#article","isPartOf":{"@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/"},"author":{"name":"thecodest","@id":"https:\/\/thecodest.co\/#\/schema\/person\/7e3fe41dfa4f4e41a7baad4c6e0d4f76"},"headline":"An objective look at the library war: React vs Vue","datePublished":"2020-04-24T08:53:35+00:00","dateModified":"2026-04-24T11:29:19+00:00","mainEntityOfPage":{"@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/"},"wordCount":2808,"commentCount":0,"publisher":{"@id":"https:\/\/thecodest.co\/#organization"},"image":{"@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/#primaryimage"},"thumbnailUrl":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/react_vs_vue.jpg","articleSection":["Software Development"],"inLanguage":"lv-LV","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/","url":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/","name":"Objekt\u012bvs skat\u012bjums uz bibliot\u0113ku karu: React pret Vue - The Codest","isPartOf":{"@id":"https:\/\/thecodest.co\/#website"},"primaryImageOfPage":{"@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/#primaryimage"},"image":{"@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/#primaryimage"},"thumbnailUrl":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/react_vs_vue.jpg","datePublished":"2020-04-24T08:53:35+00:00","dateModified":"2026-04-24T11:29:19+00:00","breadcrumb":{"@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/#breadcrumb"},"inLanguage":"lv-LV","potentialAction":[{"@type":"ReadAction","target":["https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/"]}]},{"@type":"ImageObject","inLanguage":"lv-LV","@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/#primaryimage","url":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/react_vs_vue.jpg","contentUrl":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/react_vs_vue.jpg","width":960,"height":540},{"@type":"BreadcrumbList","@id":"https:\/\/thecodest.co\/blog\/an-objective-look-at-the-library-war-react-vs-vue\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/thecodest.co\/"},{"@type":"ListItem","position":2,"name":"An objective look at the library war: React vs Vue"}]},{"@type":"WebSite","@id":"https:\/\/thecodest.co\/#website","url":"https:\/\/thecodest.co\/","name":"The Codest","description":"","publisher":{"@id":"https:\/\/thecodest.co\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/thecodest.co\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"lv-LV"},{"@type":"Organization","@id":"https:\/\/thecodest.co\/#organization","name":"The Codest","url":"https:\/\/thecodest.co\/","logo":{"@type":"ImageObject","inLanguage":"lv-LV","@id":"https:\/\/thecodest.co\/#\/schema\/logo\/image\/","url":"https:\/\/thecodest.co\/app\/uploads\/2024\/03\/thecodest-logo.svg","contentUrl":"https:\/\/thecodest.co\/app\/uploads\/2024\/03\/thecodest-logo.svg","width":144,"height":36,"caption":"The Codest"},"image":{"@id":"https:\/\/thecodest.co\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/pl.linkedin.com\/company\/codest","https:\/\/clutch.co\/profile\/codest"]},{"@type":"Person","@id":"https:\/\/thecodest.co\/#\/schema\/person\/7e3fe41dfa4f4e41a7baad4c6e0d4f76","name":"thecodest","image":{"@type":"ImageObject","inLanguage":"lv-LV","@id":"https:\/\/secure.gravatar.com\/avatar\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g","caption":"thecodest"},"url":"https:\/\/thecodest.co\/lv\/author\/thecodest\/"}]}},"_links":{"self":[{"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/posts\/3038","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/comments?post=3038"}],"version-history":[{"count":5,"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/posts\/3038\/revisions"}],"predecessor-version":[{"id":7718,"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/posts\/3038\/revisions\/7718"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/media\/3039"}],"wp:attachment":[{"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/media?parent=3038"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/categories?post=3038"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thecodest.co\/lv\/wp-json\/wp\/v2\/tags?post=3038"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}