Why is Frontend Such a nightmare? I don't think i can even call this coding. 90%

Why is Frontend Such a nightmare? I don't think i can even call this coding. 90% of it, is switching between files and DOM manipulation. Also why are there so many frameworks for everything.

为什么前端是一场噩梦？我不认为我什至可以调用这个编码。其中 90% 是在文件和 DOM 操作之间切换。另外为什么有这么多框架可以解决所有问题。

图片: https://i.4cdn.org/g/1787166797571733.jpg

>>109598273

Millennials created this stuff and coding skipped millennials.

千禧一代创造了这些东西，而编码则跳过了千禧一代。

How old is JSON now?

JSON 现在多大了？

>still no universally supported comment syntax

>仍然没有普遍支持的注释语法

>still no equivalent to XSD

> 仍然没有相当于 XSD

>>109598273

>90% of it, is switching between files

>90% 是在文件之间切换

skill issue. your setup should make navigating between files virtually frictionless.

技能问题。您的设置应该使文件之间的导航几乎毫无摩擦。

>why are there so many frameworks for everything

>为什么所有的事情都有这么多框架

so you don't have to do

所以你不必做

>DOM manipulation

>DOM操作

frontend is pisseasy nowadays.

现在的前端很糟糕。

you can go plain html and css with a nice css framework like Bulma.

你可以使用像 Bulma 这样的优秀 css 框架来使用纯 html 和 css。

or if you need an SPA I recommend Vue + a component framework like Vuetify.

或者如果您需要 SPA，我推荐 Vue + Vuetify 等组件框架。

>>109598314

>>still no universally supported comment syntax

>>仍然没有普遍支持的注释语法

use case? imagine if codemonkeys littered JSON payloads with comments.

用例？想象一下，如果 codemonkeys 在 JSON 负载中散布着注释。

>>109598273

It’s buttery smooth and easy if you use the three technologies in your pic exclusively.

如果您只使用图片中的三种技术，那么它会非常光滑且简单。

>>109598403

If you're going to use JSON for config files, you absolutely need comments.

如果您打算使用 JSON 作为配置文件，那么您绝对需要注释。

Peeps still do frontend manually?

偷看者还在手动做前端吗？

I thought AI does all that shit perfectly now if you just say a few words or upload an image

我认为人工智能现在可以完美地完成所有这些事情，只要你说几句话或上传一张图片

i don't see what exactly is a nightmare about it.

我不明白这到底是什么噩梦。

>>109598273

it is only a nightmare once you add a fucking build step to it.

一旦你添加了一个该死的构建步骤，这只是一场噩梦。

>>109598273

>Why is front end such a nightmare

>为什么前端是一场噩梦

You have to support every image format

您必须支持每种图像格式

You have to support every resolution

你必须支持每一个决议

You have to use whatever framework your boss heard was good

你必须使用你老板听说好的任何框架

You have to deal with dependencies made by strangers that are not written to any kind of standard.

您必须处理由陌生人创建的不符合任何标准的依赖项。

You have to deal with a language that was always meant to be a bandaid solution but got widely adopted as the global standard instead.

你必须处理一种原本被认为是创可贴解决方案的语言，但却被广泛采用为全球标准。

You have to deal with the language standards which change so your boss yells at you when you use var instead of let and you are not using arrow notation because it's a gay shortcut that makes code unpleasant to read

你必须处理不断变化的语言标准，所以当你使用 var 而不是 let 时，你的老板会对你大喊大叫，而且你没有使用箭头表示法，因为它是一种同性恋捷径，使代码读起来不愉快

You have to adopt clean code practices to make up for all the syntactic shortcomings and fuckery of the language.

你必须采用干净的代码实践来弥补该语言的所有语法缺陷和混乱。

You actually have to learn 3 languages just to make a webpage that doesn't look like it's from 1998

实际上你必须学习 3 种语言才能制作一个看起来不像 1998 年的网页

You have to use APIs from multiple sources on the internet which also don't confirm to a standard, even the REST standard only mitigates this marginally

您必须使用互联网上多个来源的 API，这些 API 也不符合标准，即使 REST 标准也只能稍微缓解这一问题

And finally, Indians.

最后是印度人。

Web shitters aught to celebrating that AI can do all of this now

网络垃圾值得庆祝人工智能现在可以做到这一切

>>109598273

Someone decided it was a good idea to use software made to render documents with links to instead run whole applications. Then we tried to standardize and formalize stuff in a proper way, only for everyone to just copy whatever mess the current trending big company was doing, which is what we've been doing ever since. There's zero chance any of this ends up intentionally good, if it ever does it's because we got lucky.

有人认为使用渲染带有链接的文档的软件来运行整个应用程序是个好主意。然后我们尝试以适当的方式标准化和形式化东西，只是让每个人都可以复制当前趋势大公司正在做的任何混乱，这就是我们从那时起一直在做的事情。这一切最终以故意的方式获得好处的可能性为零，如果确实如此，那也是因为我们很幸运。

>>109598596

That's not what JSON is for. You should be using TOML for that.

这不是 JSON 的用途。为此，您应该使用 TOML。

>>109598273

Use tailwind and SolidJS and you only have to touch typescript ever again. You don't need more.

使用 tailwind 和 SolidJS，您只需再次接触 typescript 即可。你不需要更多。

>>109600296

>tailwind

>SolidJS

>typescript

how to turn frontend into a nightmare and more!

如何将前端变成一场噩梦等等！

Quasar is not bad

类星体还不错

>>109600360

It's so easy to spot people who have never used tailwind, lol.

很容易发现从未使用过顺风的人，哈哈。

>>109600422

and I never will, it is antithesis to having clean css code.

我永远不会，这与干净的 CSS 代码是对立的。

"having inline style tags is bad!"

“有内联样式标签很糟糕！”

"but if we make a functional equivalent to that to dump inside class attribute it's good!"

“但是如果我们制作一个与转储类属性内部相同的功能，那就太好了！”

no, it's just inline style tag with extra steps.

不，它只是带有额外步骤的内联样式标签。

>>109600446

>I have strong opinions about things I've never used

>我对我从未使用过的东西有强烈的看法

>having inline style tags is bad

>拥有内联样式标签是不好的

Ok, midwit.

好吧，助产士。

>>109600458

I don't have to taste shit to avoid it. seeing 3 MB file of class styles replicating every css property was enough.

我不需要尝尝屎的味道来避免它。看到 3 MB 的类样式文件复制每个 css 属性就足够了。

>>109600465

Unfortunately for you, that's not how tailwind works. Also unfortunately for you, tailwind is consistently more performant than regular CSS.

对你来说不幸的是，这不是顺风的工作原理。同样不幸的是，Tailwind 始终比常规 CSS 性能更高。

Unfortunate.

>>109600489

>adding another abstraction layer between browser and your webpage is more performant

>在浏览器和网页之间添加另一个抽象层会提高性能

lol ok

哈哈哈行吧

>>109600497

There is no abstraction layer. The CSS is also typically much smaller because there's less repetition.

没有抽象层。 CSS 通常也小得多，因为重复较少。

It's funny because I also thought tailwind was a meme once. I see myself from a year ago in your replies.

这很有趣，因为我也曾经认为顺风是一个模因。在你的回复中我看到了一年前的自己。

>>109598403

cant you use jsonx

你不能使用 jsonx 吗

>>109600507

I see now that my info about tailwind was outdated. they don't have a huge CSS file for no-build anymore as it was too embarrassing.

我现在发现我关于顺风的信息已经过时了。他们不再有一个巨大的 CSS 文件来进行 no-build，因为这太尴尬了。

instead, they have a JS file for generating that CSS on the fly according to the classes you use.

相反，他们有一个 JS 文件，用于根据您使用的类动态生成 CSS。

in their ideal use case, with a build step, it makes you that CSS to package statically.

在他们的理想用例中，通过构建步骤，它使您可以静态打包 CSS。

but still, nothing beats hand-crafted CSS and without a build step, not by size, not by performance.

但仍然没有什么比手工制作的 CSS 更胜一筹，而且没有构建步骤，无论是大小还是性能。

>>109598273

The What (the fuck) Working Group has yet to admit that the "living standard" is an even dumber idea than semantic html. All the stupid design mistakes will be around forever, every browser will be incomplete forever, websites will always be broken, the baggage will grow year after year, because they're afraid of maintaining two versions of software.

What（操）工作组还没有承认“生活标准”是一个比语义 html 更愚蠢的想法。所有愚蠢的设计错误将永远存在，每个浏览器将永远不完整，网站将永远被破坏，包袱将年复一年增长，因为他们害怕维护两个版本的软件。

>>109598273

You are such a fuckin retard.

你真是个该死的弱智。

>>109599903

Build steps build character, kiddo.

建立步骤建立性格，孩子。