⭐ Leave personal marks & notes – your own space to reflect on movies you watch.
🪄 Heuristic File Scanning & Movie Matching
🪙 One Place for All Your Movies
🪢 Duplicate Detection
🌐 Sync Across Devices
It’s a modern movie collection and watchlist manager designed for film lovers. With Cinoteka you can:
📚 Categorise your movies – organise them the way you like.
📝 Create personal watchlists – track what you want to see next.
🤝 Share with friends – exchange recommendations and discover new films.
Check it out 👉 cinoteka.com
🚀 We just released Cinoteka – a movie collection & watchlist app 🎬
Built with:
⚡ Nuxt 4
🎨 Nuxt UI
📦 NuxtHub
🍹Pinia Colada
🖼️ Vue.js
Started as an intern practice project, it turned out so good we had to share it!✨
Big thanks to the amazing nuxt-movies project for inspiration & components 🙌
Over the next days, I will try to show how many fascinating interactive visuals can we generate with this data using advanced Vue visualization libraries.
Stay tuned
This incredible project was built by our 17-year-old intern!🚀
It’s a testament to the power of the @vuejs & @nuxt_js ecosystem.
As a frontend architect working across stacks, I know interactive, reactive datasets can challenge even seasoned devs in React—but with Vue & Nuxt, it’s been a breeze!🔥
Visual structure of Quran
Why the Quran? The Quran's clear and defined structure, with multiple levels of sections and chapters, makes it an ideal subject for data experimentation. Preserved to the letter from the time of revelation, it is a uniquely universal dataset.
🌐 Try it here: visual.koran.center
Explore pie charts, polar charts, word clouds, heatmaps, treemaps, line & stacked charts, maps, bar & bubble charts, vertical graphs, mixed charts, and more! Discover the many ways to visualize this amazing dataset.
https://visual.koran.center
Introducing Visual Quran.
This is a data visualization experiment where we explore the fusion of cutting-edge technologies: @nuxt.com, NuxtHub, Nuxt UI, charting libraries Vue Data UI, UnovisDev, ChartJs & AnimeJs to produce interactive graphs and charts based on structural data of Quran.
PhD Timeline xkcd.com/3081
Classic Microsoft
i guess we will hear about it today/tomorrow. Looking forward to your presentation @pi0.io. All the best
I remember, several years ago, there were quite a few pure-javascript idealogues who would mock Typescript and resist it. Interesting, to see how many of them still remain and also if their arguments still hold.
Today we're thrilled to announce our effort to port the TypeScript compiler and language service to native code, gaining a 10x speed boost in build times and editor responsiveness!
devblogs.microsoft.com/typescript/t...
last year, I bought a nuxt ui license just to support the amazing team behind it, but then I really loved using it.
Then, the team made a very bold decision with v3, and i knew it was going to be awesome.
If you want to pick a ui library for your next project, take this recommendation from me
Using tools made by/for vendors _locks_ your choices.
It’s sad to see how much bold vendor marketing shapes the direction of OSS.
Nitro and UnJS were created to fight against this, but the truth is, we were not the loudest voices. We should be louder!
The innovation in the Vue.js ecosystem is so impactful that it extends far beyond Vue itself. Tools like Vite, Vitest, Rolldown, Nitro, UnoCSS, UnJs, and UnPlugin are shaping the entire web dev landscape. In this aspect, Vue is undeniably leading the way.
Can you list others I have missed?
Vue community, I’m fighting a battle for you—just as I did for React 8 years ago, helping it get adopted in one of the world’s largest banks. Winning this will open doors, create new jobs, and showcase Vue’s strength in enterprise. Let’s work together to make this happen!
@vuejs @nuxt @vitejs
@evanyou.me @danielroe.dev @pi0.io @atinux.com @antfu.me —can you or your networks share insights?Looking for case studies, reviews, or experiences showing Vue’s success in enterprise contexts. If Vue has solved similar challenges for you, I’d love to hear your story! Let’s show its potential.
Previously asked about building a case for Vue to be the right choice as a base UI framework for a specific org, but responses were limited. Big bank leans towards React without proper evaluation. This isn’t about React vs. Vue—it’s about showcasing Vue’s strengths and its place in the enterprise
There may be another way: instead of double posting across networks, we can adapt: share content tailored to Twitter's audience there, and craft messages for our Bluesky followers here. By leveraging each platform's strengths, we can engage both communities more effectively.
I was tempted to start a thread on React myths here, but perhaps the community will take the lead. What are some common misconceptions or myths about React that you've encountered? Let's debunk them together! #React #WebDev #TechCommunity
@antfu.me has just shared similar concerns. Popularity or coolness alone shouldn't drive decisions, especially in the fast-changing world of UI frameworks. Factors like organizational needs, core team skills, app lifespan, support requirements, future transition and more should be considered.
My issue isn't with React itself, but how it's become the default for modern UIs in enterprise without proper consideration, along with the myths surrounding it.
Myth #1: "There are lots of React developers." Truth: There are few truly skilled React developers, but many who claim to be.
The problem is the decision has been made top down. I am setting the target UI architecture for the whole organisation, my recommendation will be the deciding factor, except that React has already been chosen, without any consideration for alternatives.
I'm preparing a case to advocate for using Vue over React in a major bank. They're almost decided on React, citing the larger developer pool and massive adoption. Have you any arguments, articles or resources to support choosing Vue in enterprise?
cc @evanyou.me @danielroe.dev @pi0.io @atinux.com
Funny enough, I recently had the same question about TypeScript. The tech may not be timeless, but the problems definitely are!
stackoverflow.com/q/73588654/1...
Tech evolves so fast, yet it’s extraordinary how some programming answers still resonate after 15 years. Here's a Stack Overflow answer on C# enums I shared back then that's still getting likes today.
stackoverflow.com/a/643438/15461
Vueuse supporting both 2 & 3 in the beginning was really good to allow everyone to upgrade in a timely fashion. There was enough time for this so far. Supporting vue 2 further will be preventing the remaining ones from switching and thus stopping progress. So it is for everyone's benefit to drop v2
