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.
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).
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.
Recently I started on a #Vuejs project at my new job. I've only worked with #Angular before.
One thing I didn't like it first, turned out to be an unexpected strength. In Angular, each component has a separate template, typescript & sass file. In Vue.js this is all inside a single file! Ugly and hard to use I thought.
Instead, it's a blessing. When a component reaches 100-150 lines, it already feels like a large component. Any larger? Time to split it up. It helps keep code clean.
Stuck on a single concept in #VueJS that just isn't clicking in my head this weekend. Emits, which seems fairly important! Frustrating, but I'll get through it. Maybe some sleep will help.
Folks who do #aspnetcore development with a #javascript frontend framework (#vuejs, #angular, #react), is your frontend code part of the #dotnet solution, or have you split the backend and frontend into separate isolated folders?
I have thoughts, but would love to hear what your thoughts are. Boosts are appreciated.
I'm sure these have been done to death already, but I'm thinking about doing an end-to-end project build (maybe, cloning Twitter) using #PHP, #Laravel, #VueJS and #PostgreSQL - and then documenting the entire thing on YouTube.
I'm almost positive that there are already video series out there doing this exact thing, so I'm trying to work out what would make my approach to it any more unique.
Frontend Devs, where are we currently standing in the debate React vs. Vue.js? Or is something entirely different already taking over (SolidJS, Ember.js, Svelte, ...)?
For years, it seemed like React was almost the only way to go. Now I feel like the winds are changing and other frameworks/libraries are gaining traction.
What do you all think?
I've got a sprint ahead with the goal to implement #mfa on #laravel backend with #vuejs frontend (and another third party app on .NET). The single factor (using #passport with #oauth) exists already (three years in production).
I do not like to use too many dependencies, but obviously doing it all by myself can be a high security risk as well.
However, all "plugins" I found for Laravel usually use their own frontend (blades) as well which I cannot use here.
Any ideas/input/experience on
a) the first steps for migration 1FA -> 2FA
b) using TOTP (which might be less pain for development) or rather FIDO2 (which I'd prefer but do I need to rebuild the whole authentification process?)
Especially mentioning @valorin here, but appreciate any vujes / #quasarframework developer as well ;-)