4 ms·

Personally to me the best framework is no framework at all. Instead I use libraries of code and Web Components. The libraries are either my own or some existing

by FpUser 4y ago

Personally to me the best framework is no framework at all. Instead I use libraries of code and Web Components. The libraries are either my own or some existing ones. Overall writing web front end this way for me is the most natural way. In my personal experience I spend less time creating the web front ends this way comparatively to when using "frameworks". No "compiling" is needed either, other then optional minimization.

intrasight 4y ago
I agree. The "DSL" and "compiling" aspect of frameworks scares the crap out of me frankly. And on top, it's all happening on my poor users device - well not for Svelte apparently. Let's have a look at this "compiled" JS. Here's an snippet from the volume slider in his example: function b() { v = W4(this.value), h(0, v) } I understand that this is "compiled" - but really it's not - it's EcmaScript. If I wrote code like that, I'd get fired.
- bdougherty 4y ago
  You are looking at minified output there; of course nobody writes that. You can see the compiler output in the "JS output" tab here, it's very easy to follow: https://svelte.dev/repl/12aefec27f0d4ec5ad85ab7e5a123642?version=3.50.0 https://svelte.dev/repl/12aefec27f0d4ec5ad85ab7e5a123642?ver...
  - intrasight 4y ago
    Got it. It was both compiled and minified.
andsoitis 4y ago
That can work relatively well for projects where there are a handful of engineers, but I wonder whether it doesn’t be some much harder as your team grows to 20+ engineers working in the same UI code base?
- FpUser 4y ago
  Frameworks does not help in this case any more than proper organization / structuring of code. It is as easy to fuck up your React app setup as it is plain code. Just make sure that overall architecture and process enforced and are designed by experienced person/s rather than hamsters.
  - andsoitis 4y ago
    What do you mean by “hamster”?
vinibrito 4y ago
Do you get web components somewhere or write most of them from scratch? And how do you organize the layout, using flexbox? And how do you set states, react to events etc do you write all of the render stuff manually?

by FpUser 4y ago

intrasight 4y ago

I agree. The "DSL" and "compiling" aspect of frameworks scares the crap out of me frankly. And on top, it's all happening on my poor users device - well not for Svelte apparently. Let's have a look at this "compiled" JS. Here's an snippet from the volume slider in his example: function b() { v = W4(this.value), h(0, v) } I understand that this is "compiled" - but really it's not - it's EcmaScript. If I wrote code like that, I'd get fired.

bdougherty 4y ago
You are looking at minified output there; of course nobody writes that. You can see the compiler output in the "JS output" tab here, it's very easy to follow: https://svelte.dev/repl/12aefec27f0d4ec5ad85ab7e5a123642?version=3.50.0 https://svelte.dev/repl/12aefec27f0d4ec5ad85ab7e5a123642?ver...
- intrasight 4y ago
  Got it. It was both compiled and minified.

andsoitis 4y ago

That can work relatively well for projects where there are a handful of engineers, but I wonder whether it doesn’t be some much harder as your team grows to 20+ engineers working in the same UI code base?

FpUser 4y ago
Frameworks does not help in this case any more than proper organization / structuring of code. It is as easy to fuck up your React app setup as it is plain code. Just make sure that overall architecture and process enforced and are designed by experienced person/s rather than hamsters.
- andsoitis 4y ago
  What do you mean by “hamster”?

vinibrito 4y ago

Do you get web components somewhere or write most of them from scratch? And how do you organize the layout, using flexbox? And how do you set states, react to events etc do you write all of the render stuff manually?