So I'm hiring for a role using Rust and Solid.js. Preferably someone in Sweden, but can be anyone in the EU. The role can be fully remote, but it is preferable if we can share a whiteboard sometimes.
Neither Rust nor Solid.js knowledge is required, but familiarity with a sensible backend language and React-like APIs is a good indicator if the role is for you. :)
Dear Dev Mastodon, I'm torn between Solid.js and Svelte for a small SPA project. I've done a lot of React dev so Solid seems familiar but I quite like the apparent simplicity of Svelte. Any opinions, advice, gotchas I should be aware of?
This is pretty interesting. Solid.js just released a big update for SolidStart, which is their fullstack metaframework like Next.js.
They split out the router logic to a separate package to be router agnostic, but you can still use server-side loader functions to prepare data for the route.
The clientOnly wrapper to declare some code as client side only looks really simple. Easier than putting 'use client' everywhere in Next.js modules.
I finally made something in #rust and #wasm and using #solidjs: a maze generator that successfully keeps the kids occupied for minutes at a time! (Due to its handy PDF feature that allows you to print mazes)
Hi! I'm Pablo, a software engineer from #ElSalvador but now living in The #Netherlands! I'm also the author of https://felte.dev, a "framework agnostic" form management library.
I work mainly as a front-end developer with #ReactJS, but I love keeping track of the new things such as #SolidJS and #WebComponents!
Looking forward to see more people around the #fediverse ❤️
@angular and @TauriApps form a robust combination for creating powerful apps.
Together, they offer an interesting blend of features, each balancing the other’s strengths and weaknesses.
👇👇👇
#Angular, is known for its completeness in managing complex applications. 💫
It employs a change detection mechanism and ahead-of-time (AOT) compilation, which optimizes apps by compiling components into highly efficient #JavaScript code before the initial load.
@jaredwhite’s personal thoughts on a great entry by @collinsworth into the growing body of work which details why greenfield #WebDev projects are better served by other frameworks…or none at all.
The most tiresome thing in #webdev is picking the techstack. So many choices to make: plain #javascipt or a more restricive language like #typescript , which ofc is often depending on the overall frontend framework to use: #svelte , #react , #preact , #solidjs ?
Or do one completly deviate from the classical way and use rather a techstack via #wasm , such as #rust with #dioxus ?
So many questions to answer and that still is only the js side of things, you then have to think about your css framework (if you want to use something like #tailwindcss ), your font choices, and ofc if and what styling library you actually use ontop of our frontend framework; e.g. #bootstrap , #blueprintjs , #tabler.io and so on.... which also often depends on your framework of choice!
Is it because code written in CSS-in-JS don't allow you to take advantage of the "cascading" nature of CSS?
Is it because you can't take advantage of selectors?
Is it because there might be some compilation steps required when employing CSS-in-JS? And if compilation isn't used, there might be some render-time slowdown?
I regularly use and love #Typescript. I used to use #Python the most – it’s what I learned in and I am more interested in backends than frontends. I also am regularly using and really enjoying #Kotlin (so much better than #Java). But truly Typescript is bae.
#Julia is a joy to work with. Very much like Python but more powerful. If it had the library support Python or #JVM has I would probably prefer to use Julia for backends.
But Typescript really changed the game and now that’s probably my favorite language not just because of the language itself but because it has web dominance. Until I can write #WASM with Python or Kotlin or Rust, and I’m building #web applications, TS is my lingua franca.