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.
"This means that the design of the framework is largely settled, with no anticipated breaking changes between now and the stable release, and that the most egregious bugs have been stomped.
"It doesn't mean that it's ready for production, or that nothing will change between now and 5.0. But if you've held off on dabbling with Svelte 5 during the public beta phase, now is a great time to try it out."
I'm following the ARIA authoring practices from the W3 for web components I'm writing for a #Svelte app.
I've been experimenting with lots of companies' web sites and component libraries.
It's disappointing how much variation there is in support (even from big companies). Many have wrongly applied anti-patterns and have failed to cover even 25% of the documented patterns.
A lot of component libraries do the minimum and still claim #a11y. 🤬 Trust these after verification.
Major progress on my first Autonomi demo app today. I'm sooo happy 😄
This proves that all the tricky but essential parts work together, so now I can add features and improve the operation knowing that effort won't be wasted.
It also already shows that we can build cross platform apps (desktop and mobile) with a web front end that use the #Autonomi#Rust APIs using #Tauri and your web framework of choice. Which for me is #Svelte
𝗗𝘂 𝗕𝗼𝗶𝘀 𝗗𝗮𝘁𝗮 𝗩𝗶𝘀𝘂𝗮𝗹𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗦𝗼𝗰𝗶𝗲𝘁𝘆 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 - 𝗪𝗲𝗲𝗸 𝟵/𝟭𝟬. My re-creation of Du Bois' poster no. 51 implemented with D3 & Svelte. Once more close to the original and responsive.
I built this POC to demonstrate how I'd use CustomEvents to implement Signals. Please criticize my approach and tell me why I need a native browser API for this.
I haven't worked with #Svelte for a long time and am immediately reminded of how much I like it. 😃
I'm building a cross-platform demo (native) app which will work on Windows, MacOS, Linux and Android out of the box, using #Tauri.
It needs to be native so I can access a #Rust API to talk to a #p2p backend (#autonomi).
If you've not used Svelte I encourage you to give it a try. It is intuitive and the online docs, examples and REPL make learning by doing a breeze. Which is my style. #RustLang
Du Bois Data Visualization Society Challenge - Week 7/10: My recreation of Du Bois' poster no.47, done with D3 & Svelte. Again I tried to recreate it as close to the original as possible, make it responsive and added a pattern fill to match the hand-painted look.
I'm looking again at static website builders now that Safe Network is happening (beta this month, launch in October).
I was set up to deploy my #dWeb blog simultaneously to web and Safe Network using #ReactStatic but sadly that is no longer maintained (but still works).
So I'm working on one using my favourite #Svelte. Also trying #Publii, a WYSIWYG site editor which looks interesting. Not the best UX but could help a lot of folks get online, on web and the #decentralised#p2p#SafeNetwork.
Du Bois Data Visualization Society Challenge - Week 6/10: My recreation of Du Bois' poster no. 54, done with D3, Svelte. Again I tried to recreate it as close to the original as possible and make it responsive.
Svelte è uno strumento per la costruzione di applicazioni web. Come altri framework per interfacce utente, consente di costruire l'applicazione in modo dichiarativo con componenti che combinano markup, stili e comportamenti.
Questi componenti sono compilati in piccoli ed efficienti moduli JS che eliminano il sovraccarico tradizionalmente associato ai framework UI.
Du Bois Data Visualization Society Challenge - Week 5/10: My recreation of Du Bois' poster no. 13, done with D3, Svelte. Added a pattern fill to match the hand-painted look & transitions on load.
Discussed my current painpoints with #Twig a bit in Craft Discord. Coming from a #Svelte Components perspective, the Developer Experience is just not as good currently. Things take much more effort to set up, you need to understand Includes vs. Embeds vs. Macros. This is a general PHP CMS challenge of course. 🤷 On the other hand: You get SSR easily without wild cloud setups in PHP 😉 🤓 #craftcms
I broke a little with #SvelteKit idioms here insofar as I have Pages merely pass a context object into a #Svelte component.
This in turn allows me to utilise #Storybook to describe the interface in different configurations (I have tests in place as well).
It's still early days but we tackle one page at a time to build up this #Federated#Forge (F2 for short).
In case you are interested in translating, hit me up. Be warned that things might move around or get dropped. I prefer early feedback to easily correct course if needed.
(Le 1er projet est en #Svelte, #SvelteKit, mais à partir du moment où la personne est senior, maîtrise un framework JS, et peut conseiller nos clients en termes d'architecture, c'est ok.)