I went to book a flight with Wizz Air last night and the absolute shocking web performance made me feel better about my own work.
It takes ~30s to process the #JS and render the search, literally the primary function of the site. I like the DX of #VueJS but is this kind of performance really worth it?!
@haliphax Yeah, maybe it's a skill issue, but it seems to be a lot easier to create incredibly slow websites with JS frameworks than without them. I've only used Vue in production a couple of times but we had a hard time getting it performant too.
@Crell Haha yes it is, good point! Sometimes books that are a bit old end up in our sales. Occasionally there are actually people with a kind of historical interest in these sorts of things, but probably not "for beginners" books!
Les données de "temps réel" d'attente aux stations de transport en commun de #Nantes sont (entre autres données) dispos en open data. De mon côté,
1/j'avais besoin d'une idée de projet pour me servir de base pour apprendre #nuxt (et aussi #vuejs par la même occasion) et
2/ J'en avais marre de poireauter 20 minutes pour un tram alors que je venais de galoper après le dernier.
J'ai donc bidouillé une petite appli en bien plus de temps (et en beaucoup moins bien) que requis par quelqu'un qui maitrise la techno.
L'idée est qu'on a accès au temps d'attente pour une station, une ligne, dans une direction, sans avoir à être à l'arrêt. La source est a priori la même que celle utilisée pour afficher sur les panneaux aux stations, ça n'est donc pas dispo pour tout les arrêts. Je ne sais pas si c'est utile à quelqu'un d'autre qu'à moi mais si jamais, je suis preneur de retours.
@alter_unicorn Merci ! c'est un choix de l'organisme qui gère les données de rendre ça open source j'imagine. C'est propre à chaque commune ou métropole. Après ça reste envisageable de faire ça sur des données horaires "statiques" si ça reste dispo en open source aussi. Sur Saint-Étienne c'est le cas par exemple, si je devais le faire je me baserai sur des données "open" mais qui sont des horaires théoriques (ceux qui sont affichées sur les panneaux des arrêts, par exemple).
This weekend #Vue Mastery offers all of their courses for free! 🎉 💖
I've done the same "course marathon" last year and their courses are very high quality! 👍
But be aware: They have over 50 hours of course content, but the weekend only has 48 hours, so you should probably watch at 2x speed to not miss any. 😄
Starting on a rewrite of an internal tool for a client, but trying to decide on which stack to use. The previous developer is versed in Vue/express and is able to help me out if I went that route. However, I've gotten a taste of sveltekit and love it because I can combine the frontend and API pretty seamlessly. Its problems are twofold though:
The previous dev would be significantly less help
Sveltekit is very new, meaning it is constantly changing and has a smaller, though more invested ecosystem (libraries, community, etc.)
I'm leaning towards Vue/Express right now, but I'm still not sure..
Please boost this post for visibility, if you know someone who's hiring. Thank you!
#OpenToWork Good day, everyone! Looking for new career opportunities, but first, let me introduce myself.
I'm fullstack(-ish) developer and my area of expertise is making Web applications, mostly using #Python (6+ years of exp.) for backend and #VueJS (2+ y.o.e.) for frontend. Though I'm ready for other adventures and different projects which will drive the world.
Currently living in the Philippines, open for both relocation and remote work.
My skills, including, but not limited to:
Python: FastAPI, Flask, pytest, SQLAlchemy, REST APIs, aiogram
Other: VueJS, Docker, GitLab CI/CD, PostgreSQL, Redis, MongoDB, Clickhouse, automatization, chat bots (mostly Telegram) and more.
Languages: Russian (native), English (intermediate).
@quincy No. I can’t give any more context to protect the innocent, but the template is full of this stuff. Apparently someone saw {{ foo }} somewhere, but needed to render a static string instead of a variable’s contents, and instead of removing the braces altogether, replaced the variable with a string literal.
Ok so #Svelte 5 looks like it took a lot of inspiration from #VueJS 3's Composition API. Slightly different syntax, probably more efficient output, but the basic core ideas are definitely there. Less magic in the code too.
I like it because I like Vue, but that makes Svelte less different.
I hate websites that use new fangled frameworks, and as soon as you load their home page, they prompt you with "a new version is available, do you want to load it?". No! Why aren't you automatically giving me the latest version? I know, I know, It's probably a caching thing. But what a ridiculous thing to ask a user.