[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: vue.png (4 KB, 400x400)
4 KB
4 KB PNG
why do chinks shill this broken garbage so much
>>
>Angular :|
>Angular, China :OOO
>>
chinksects have an autistic tendency to force everything "made in china"
>openresty
chink nginx. worse than nginx and only used by chinks
>vue
chink react. worse than react and only used by chinks
>Milan Public License
chink Apache License, only used by chinks
>>
>>101562277
what's broken ?
>>
>>101562640
I'm pretty experienced in Vue.
There are a few bad design decisions there.
The worst is automatic unwrapping. They tried to remove the .value for convenience.
But imagine you have a class like so
class SomeThing {
public someValue = ref<string>('someString');
}

Now go initialize that class in a template like so:
const state = reactive<{
someThing: SomeThing;
}>({
someThing: new SomeThing,
})

The "reactive" unwraps" someValue so that it is accessed as just "someThing.someValue" instead of "someThing.someValue.value". This breaks consistency (and typing). At larger scale, it makes things very unpredictable to work with.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.