51–60 of 66 posts
Earlier quoted context omitted.
> I think I want to stay away from build tools until I can’t No typescript then, eh?
You can always annotate your code with JSDoc comments and type check your code with `tsc --noEmit`, i.e. typescript without the build step.
Earlier quoted context omitted.
These descriptions are helpful for a very focused view of one piece of a project. As somebody who writes lit-element every day, I miss React and Angular like crazy for everything else they solve and provide.
Interesting comment. Hopefully after building something with Ficus I can better appreciate Angular. The biggest issue I have is updating projects. Its fine if you only support 1 application but when you have 2 or 3, they start to end up on different versions and when you get back you have to spend a month updating to the latest versions, instead of adding tangible value to the product. Maybe I am just bitter as start…
So I recently got around to writing some code around a similar idea — enabling people to build websites using only components by treating data (the remaining bastion) as web components: Demo page: https://mrman.gitlab.io/services-as-dom-elements/ Blog post describing the idea: https://vadosware.io/post/sade-pattern-services-as-dom-eleme...
Interesting read. I knew it was possible but think this is the first time seen so many web component libraries used on 1 single page. Bookmarked.
I personally think I'll choose lit-element in the future for web components I build, it was by far the best to use and was least-surprise (which I value more and more these days).
Hi All, I use Angular 6 – 10 at work every day @day$job and have used Vue.js for some side projects / school related. Long story short have been looking into standard web components for my next side project and FicusJS seems to check all the boxes. Problem is there is almost no information about FicusJS other than what I can find linked off https://webcomponents.dev/new/ The other ones in the running are GitHub/Catal…
You can make vanilla web components with Svelte, and Svelte has a much better DX than React, Vue, and Angular. It also performs better thanks to the compile step. I highly recommend checking it out!
Earlier quoted context omitted.
Web components = build your own custom HTML elements (in a nutshell). Instead of building complex interactive things with etc. and a mess of styling & JS, you ship a JS file and users create in their HTML , , etc. that you defined. React = component-based JS single-page app architecture, using a fully virtual DOM and event system, and a new template language called JSX to greatly simplify the dev experience. React an…
These descriptions are helpful for a very focused view of one piece of a project. As somebody who writes lit-element every day, I miss React and Angular like crazy for everything else they solve and provide.
Earlier quoted context omitted.
and what is the problem with that? "Single guy made a good looking and so far working product in only 59 commits since september" is a different way to present the same facts.
Language is so interesting. You read the parent comment and took it as throwing shade. I read the parent comment and took it as pragmatic admiration.
I am wondering why I initially thought that. Maybe a mindset of inherently better software created by Teams that's instilled within us these days could be a part of it. Trusting a lone programmer, it's harder because you have to reject the "programming".
Earlier quoted context omitted.
You can make vanilla web components with Svelte, and Svelte has a much better DX than React, Vue, and Angular. It also performs better thanks to the compile step. I highly recommend checking it out!
I think the DX claim is pretty subjective. I find JSX much easier to use than all the others mentioned, and a great deal more flexible. The ease of use being that it’s just JavaScript (or more importantly TypeScript), with some DSL. That means it follows all the other rules of the environment in which it runs, and uses all the same tooling. It also produces a data structure that’s renderer-agnostic, so it’s trivial t…
I can see the argument for JSX being more flexible, given that you can store little bits of JSX in js expressions, something you typically cannot do with the other component frameworks. But tools like svelte have their own DX improvements that make things like state management / reactivity arguably a lot easier than React.
Earlier quoted context omitted.
Language is so interesting. You read the parent comment and took it as throwing shade. I read the parent comment and took it as pragmatic admiration.
Honestly, I also took it as throwing shade. I had to read the whole thing and realised that GP clearly wasn't throwing shade. I am wondering why I initially thought that. Maybe a mindset of inherently better software created by Teams that's instilled within us these days could be a part of it. Trusting a lone programmer, it's harder because you have to reject the "programming".
- "relatively new project" > code is fresh and certainly well-organized / maybe lacks stability
- "all by one person" > a single vision is a good thing / if that person gives up the project, it's dead
- "no other project mentions it" > [no good aspect in that] / no real-world usage
If you have any experience in the frontend field, those points are more often bad than good. You don't want to invest time and/or money in that kind of project that has a high chance of being dead within a year.
Now, that does not mean that it's a bad project (it looks pretty good actually), but it's just very young.
Edit: actually I like this framework very much (but I have a thing for underdogs). It might be ideal to quickly throw POCs or toy projects