Discover and read the best of Twitter Threads about #Svelte
Most recents (9)
#AboutRSS 电报频道上的 “与 RSS 有关的 Coding 向 #教程 分享” 已发布 6 期，同样开个 #Thread 。
「基于 Liuli 构建纯净的 RSS #公众号 信息流 」
juejin.cn/post/705768750…
#微信
「基于 Liuli 构建纯净的 RSS #公众号 信息流 」
juejin.cn/post/705768750…
#微信
「Add RSS Feeds to Your Website to Keep Your Core Readers Engaged」
It may seem simple as you may have some data in tables (hello, MySQL) and you want them on a web page (hi, <table>). But you start joining data from other tables and you end up displaying a tree in a table. How? You never know how to do it until you try to use that. UX!
(2/6)
(2/6)
But if you have tree-data, tree-database (hello, Mongo), and tree components on website, you still need tables to present the data of similar structure. It's all 2D and are brains are trained to get information presented as combination of 2 axes. Hello, tables!
(3/6)
(3/6)
💜 It's time for new development fuckery, please welcome my next CREATION — Project Amber!
A long time ago I wanted to make my own Genshin DB but left it for a few months.... BUT then decided to remake it again!
You can visit it here: ambr.top/en
#VUE #GenshinImpact
A long time ago I wanted to make my own Genshin DB but left it for a few months.... BUT then decided to remake it again!
You can visit it here: ambr.top/en
#VUE #GenshinImpact
At first I tried to deal with CSS myself, and it was fine, but then one of my good friends recommended me #Tailwind, and it turned out very amazing experience! Felt like CSS got a separate programming language XD.
Thanks everyone who supported me with the project BTW!
Thanks everyone who supported me with the project BTW!
Mostly I did it for fun, because I started (and I did) really enjoy programming stuff, and also wanted to do something useful for community (how without that).
Also, I kinda wanted to kinda recreate Genshin UI in HTML, and I did it, ahahahahaha!!!!
Also, I kinda wanted to kinda recreate Genshin UI in HTML, and I did it, ahahahahaha!!!!
1/ Today we published this first of two interactive #scrollytelling pieces focused on economic inequality in the UK, based on measures of income and productivity for each local area. Check it out here... ons.gov.uk/visualisations…
2/ As you'd expect, the analysis found notable economic disparities between southern England and the rest of the UK (the blue map shows relative income, the pink shows relative productivity)... But there were also other notable findings
3/ Importantly, the analysis found some interesting patterns once the two economic measures were overlaid as a #bivariate map, including disparities between cities and their surrounding rural areas (the scatter plot top-right explains the colours)
We're back with the second part of our top 10 #Svelte meetup video selection of 2020.
Remember, you can read the entire article here, but if you want to scroll through the separate instead, just keep reading. 👇
blog.meetupfeed.io/top-10-svelte-…
Remember, you can read the entire article here, but if you want to scroll through the separate instead, just keep reading. 👇
blog.meetupfeed.io/top-10-svelte-…
@WixEng's podcast featured both @Rich_Harris and Eliran Hezkia talking about why #Svelte is better than #React. However, convincing a team to switch frameworks isn't easy, and the guys are discussing that topic too.
meetupfeed.io/talk/svelte-be…
meetupfeed.io/talk/svelte-be…
What to do if need to build a web component that can be used in two different places, but still has a standalone development and deployment process? You'll need #Microfrontends, and why not use #Svelte while you're at it? Evan Payne's got you covered.
meetupfeed.io/talk/svelte-mi…
meetupfeed.io/talk/svelte-mi…
So, what happened with @sveltejs last year? Our latest hand-picked top 10 selection will answer that question. You can check the videos here or by clicking on this link.
Below you'll find the first 5 videos in details.
blog.meetupfeed.io/top-10-svelte-…
Below you'll find the first 5 videos in details.
blog.meetupfeed.io/top-10-svelte-…
First up: @John_Papa's introduction to #Svelte. You’ll get tips and tricks for building blazing fast apps, and learn how it compares to #Vue, #Angular and #React.
meetupfeed.io/talk/svelte-in…
meetupfeed.io/talk/svelte-in…
Here's @digitalix, a mobile developer, trying out #Svelte Native for the first time. He has some exciting insights to share with you.
meetupfeed.io/talk/svelte-na…
meetupfeed.io/talk/svelte-na…
JAVASCRIPT ON EMBEDDED DEVICES
Case Study: Svelte
(1) - Svelte is used for POS systems in Brazil. Roughly 200,000 POS devices are currently in the cities of Brazil. The device runs a very outdated WebKit on extremely memory-constraint hardware.
@sveltejs @SvelteSociety
Case Study: Svelte
(1) - Svelte is used for POS systems in Brazil. Roughly 200,000 POS devices are currently in the cities of Brazil. The device runs a very outdated WebKit on extremely memory-constraint hardware.
@sveltejs @SvelteSociety
(2) - They tried different frameworks. None of them could be used because when you press a button, it responded half a second later. Of course, users would be more likely to press it twice and may end up overcharging the customer. But when they tried Svelte, it worked smoothly.
(3) - This POS is built by Stone - A Brazilian company that specializes in integrated solutions for all types of entrepreneurs. This reveals the amazing power and potential of @sveltejs for low memory devices.
@stonepagamentos @sveltejs @SvelteSociety
@stonepagamentos @sveltejs @SvelteSociety
Always wanted to use #GraphQL for your new projects, but never got time to learn how it works? 😃
Let's change that this weekend! 🙌
👇 Here's a 10-tweet GraphQL crash course for you! 🥳
Let's change that this weekend! 🙌
👇 Here's a 10-tweet GraphQL crash course for you! 🥳
1/10
GraphQL is a query language for making flexible API calls.
We describe what we want in a single request with nested fields, then we will receive a data payload of the exact shape.
No need to make many small requests to stitch data together or over-fetch unwanted parts!
GraphQL is a query language for making flexible API calls.
We describe what we want in a single request with nested fields, then we will receive a data payload of the exact shape.
No need to make many small requests to stitch data together or over-fetch unwanted parts!
2/10
GraphQL is not a library, but a language spec.
We send queries as POST or GET requests. The server checks if they're valid with a predefined schema, runs corresponding resolver functions to perform operations, then prepares the data to be returned to the client.
GraphQL is not a library, but a language spec.
We send queries as POST or GET requests. The server checks if they're valid with a predefined schema, runs corresponding resolver functions to perform operations, then prepares the data to be returned to the client.
Always wanted to check out @sveltejs (aka. "the next big thing in web dev") but never got time for it? ⏰
🔥 I've got a 10-tweet crash course for you! 👇
(Spoiler alert: Svelte is so intuitive and easy to use that you may feel like you already know it! 🥳)
#javascript #svelte
🔥 I've got a 10-tweet crash course for you! 👇
(Spoiler alert: Svelte is so intuitive and easy to use that you may feel like you already know it! 🥳)
#javascript #svelte
1/10
How Svelte works:
- Compiler: Doesn't ship a Svelte "library" to users, but build-time optimized plain JS
- Components: App is made up of composable UI elements
- Reactive: Event/User interaction triggers chain of state changes, autoupdating components throughout entire app
How Svelte works:
- Compiler: Doesn't ship a Svelte "library" to users, but build-time optimized plain JS
- Components: App is made up of composable UI elements
- Reactive: Event/User interaction triggers chain of state changes, autoupdating components throughout entire app
2/10
UI is a component tree. A component defines how your app should interpret some abstract "state" values, so that it can turn them into DOM elements in your browser, and ultimately pixels on your screen.
UI is a component tree. A component defines how your app should interpret some abstract "state" values, so that it can turn them into DOM elements in your browser, and ultimately pixels on your screen.
