I just published my first #Wix site today. I have limited experience with similar site builder services like Square Space and Weebly.
Is Wix typical of these kind of tools? I found it to be extremely difficult to use. On the plus side it almost gave me every ability I could produce as an actual developer... almost.
Less would have been more in the case of Wix. Just because you can stuff every possible feature into a Web based WYSIWYG builder doesn't mean you should.
It made it really hard to produce a simple and elegant site that is really what's needed by most people using such a service. If you truly have a need for the advanced features, trying to do those through multiple layers of nested menus is the worst way to do it. You might as well as hire a developer and do it the right way.
This site coulda been an email. Instead it was an insane toothpick tower that kept exploding on me b/c nothing played nicely with anything.
@sysop408 a few years back when I launched my first page on Wix, I felt that the overall experience was fairly straightforward and to the point...plus some of the analytics and plug-ins available were nice, too.
That being said, after a years subscription of the Pro version ended, I chose to leave the platform and self-host my own page.
My advice, find a nice #React template and build your own...or #HTML if it's just static.
Much more flexibility of component design! 😎💯 :html5: :react:
In 45 minutes I made a #kotlin#javalin application from scratch, which uses #webjars to include #htmx from a #maven pom file. It uses static #HTML files for the first load, and then renders HTML from #jte templates for #SSR of the parts of the pages that need that kind of interaction. There's no #springboot (or any #spring at all) and no #SPA like #angular or #react.
Now because simply setting up a project says close to nothing about its real world viability, next step is an actual usecase ( :
"Love it or hate it, it’s hard to deny how easy (relatively speaking) it is in React to develop two apps with a single codebase. React Native has been around since about 2015, and if you’ve been in the accessibility space, you’ve probably heard some warnings to not use it due to a lack of accessibility customization or remediation paths."
We are excited about React Compiler, aren't we? I just remembered that my first OSS library in JavaScript was a JS-to-JS compiler! Funny how things come around.
“React and the component model standardises the software developer and reduces their individual bargaining power excluding them from a proportional share in the gains”. An amazing write-up by @baldur about the de-skilling of developers to reduce their ability to fight back against their employers.
Once again I get foiled by switching languages. :blobcatfacepalm2:
In Javascript, you have to compare strings with ===, not ==, or else you'll run into type coercion problems, because Javascript thinks 1 == "1" is a totally fine thing to be true. (it's not)
But in Kotlin, === compares identity not equality for strings. But in the JVM, string values are aggressively cached, so === actually does what you want most of the time. Unless your strings come from weird places, like JNI code. Then you get awful non-deterministic behavior that's incredibly hard to debug, but it totally goes away when you use the correct comparison operator == for strings.
sigh I'm not really as good at this whole programming thing as I should be by now.
React Compiler has been open sourced, and, it's written in Rust (github.com)