Artem Karasev

🔸 Frontend Tech Stack Evolution 2024 ⏩ 2025 🔹React → Next.js Reason: File-based routing, SSR, SEO. 🔹Redux → Zustand / RTK Query Reason: Simple state logic, fewer boilerplates. 🔹CRA → Vite Reason: Faster builds, better dev experience. 🔹Axios → React Query Reason: Built-in caching, pagination, retry logic. 🔹Local Auth → JWT + Google Auth Reason: Better UX + scalability. 🔹SASS/CSS Modules → Tailwind CSS Reason: Utility-first + fast styling. 🔹REST APIs → GraphQL (selective use) Reason: Precise data fetching, less overfetching What are your thoughts #reactjs #nextjs #javascript #softwaredevelopment #technology #engineering #github #programming #ig

726

49 Comments

🚀 Vite 7 is here! 🚀 Released on June 24, 2025, and packed with powerful improvements for modern frontend developers. 🔍 What's new in Vite 7: 🧱 Node.js 20.19+ and 22.12+ support Node 18 is no longer supported following its end of life in April 2025. 📦 ESM-only distribution Vite now ships as pure ES modules, but still works with CommonJS via require(esm) in supported Node versions. 🌐 New browser target: baseline-widely-available More predictable support across modern browsers (Chrome 107+, Edge 107+, Firefox 104+, Safari 16+). 🧪 Vitest 3.2+ support Make sure to upgrade your test setup to ensure compatibility with Vite 7. 🛠️ Experimental Environment API Introducing a new buildApp hook - a great opportunity for framework and plugin authors to try it out. 🎯 Legacy Sass API removed Support for outdated Sass APIs has been dropped - time to modernize your stylesheets! 🌱 Ecosystem updates: 📅 ViteConf 2025 For the first time, ViteConf is going in-person - October 9-10 in Amsterdam! Don't miss the chance to connect with the team and community. 🦀 Rolldown - the next-gen bundler in Rust Developed by VoidZero, rolldown-vite is now available and set to become Vite's default bundler. 🧩 Vite DevTools A powerful new inspector by VoidZero and NuxtLabs - deeply integrated with Vite for debugging and dev insight. ⚙️ Migration from Vite 6 is smooth: Just a few removals (e.g. splitVendorChunkPlugin, legacy Sass). Follow the official Migration Guide and changelog to stay up to date. Start with pnpm create vite or explore rolldown-vite today! #vite #vite7 #frontend #webdevelopment #javascript #vitest #devtools #viteconf #rust #performance

166

11 Comments

⚔️ Laravel (PHP) vs Node.js (JavaScript) </> Language → Laravel: PHP → Node.js: JavaScript ⚙️ Framework → Laravel: Laravel → Node.js: Express.js ⚡ Speed → Laravel: Moderate → Node.js: Fast (non-blocking I/O)  🔐 Security → Laravel: Built-in Auth & CSRF protection → Node.js: Manual handling needed 💬 Community → Laravel: Huge PHP base → Node.js: Rapidly growing JS base ✔️ Laravel Pros: • Elegant syntax • MVC ready • Built-in security • Fast prototyping ❌ Laravel Cons: • Slightly slower performance • Heavy for small APIs ✔️ Node.js Pros: • Real-time support • Fast performance • One language for frontend + backend ❌ Node.js Cons: • Complex structure for large apps • Manual setup for security 💭 Verdict: Use Laravel for structure, security & faster development. Use Node.js for real-time, scalable systems. #Laravel #NodeJS #BackendDevelopment #WebDevelopment #FullStackDeveloper #CodingJourney #TechComparison

192

19 Comments

As one of my side projects, I'll introduce you to 𝗞𝗻𝗼𝘁𝗶𝗳. This is a simple notification solution for KMP, targeting all platforms. The library is in stable release, but be prepared for new updates. I hope it's useful 🍻 https://lnkd.in/eRsVs_FY

79

8 Comments

Fullstack vs. Specialization: The Future of Frontend in the Job Market Every few years, a new trend emerges in tech, and right now, we’re hearing a lot of "Frontend is dead! You need to be fullstack!" Some people say that companies only want developers who can handle backend, databases, DevOps, cloud, security, and—if there’s time left—write some frontend code. But is that really true? The reality is more nuanced. Smaller companies and startups often prefer generalists—people who can touch every part of the stack and quickly ship a product. That makes sense when you have a small team and limited resources. But big tech companies, fintechs, and large-scale SaaS businesses? They still need deep frontend expertise. These companies deal with complex architectures, massive user bases, and performance challenges that require specialists who truly understand frontend engineering, accessibility, performance, and UX. And let’s not forget: frontend isn’t dying—it’s evolving. The frontend landscape today is far more advanced than it was a few years ago. We’re not just building static pages anymore; we’re working with: ✅ React Server Components – Blurring the line between client and server for better performance ✅ Edge Functions – Running logic closer to the user for faster responses ✅ WebAssembly – Unlocking new possibilities with near-native performance ✅ Streaming UIs – Changing the way we think about rendering So, instead of panicking over whether frontend is disappearing, the real question should be: what do I need to learn to stay ahead? 👉 Should frontend devs understand some backend? Absolutely! Knowing how APIs work, how data is fetched efficiently, and how to optimize for performance makes you a better engineer. But that doesn’t mean frontend development is becoming irrelevant—it means it’s gaining more depth and responsibility. The demand for high-quality UI, accessibility, and performance-driven experiences is bigger than ever. Frontend is no longer just about “making things pretty.” It’s about building scalable, fast, and accessible experiences that directly impact business success. So, what do you think? Is frontend really dying, or is it just becoming more powerful? Let’s discuss! 👇 #Frontend #Fullstack #ReactJS #DesenvolvimentoWeb #Tech #Programação #JavaScript #DevLife #CarreiraTech #EngenhariaDeSoftware #WebDevelopment #FutureOfTech

43

19 Comments

🎬 Kotlin MCP Development Update! 📱 📍 Code: https://lnkd.in/dWe7sXDZ Added so far: 📰 Tools for Stock Overview, Cash Flow, IncomeStatement, Economic Events 📡 Real-time Convert Currency and Crypto Coins price to LLM surfaces 🔧 Simple API key configuration 📄 Comprehensive README with setup and usage instructions 🌃 Soon: Collecting local data and performing operations on that data If you have any ideas, please feel free to share them with me and don't forget to contribute to my GitHub repository 💚 Stay Tuned. #Kotlin #OpenSource #CryptoNews #ModelContextProtocol #MCP #LLM #AIIntegration #RapidAPI #SoftwareEngineering #CleanArchitecture #APIDevelopment #TechInnovation #DeveloperCommunity

50

2 Comments

Lately, I am observing more and more posts where ours (mine and Kamil Baczek) Evolutionary Architecture by Example repository is mentioned as one of the top resources to learn how to build .NET applications. I am extremely happy about it as the more people share it, the more people will be reached. It is also rewarding to see thousands of stars on GitHub - kind of "thank you" which motivates us. What is even more exciting is that when a list of useful repos is shared by someone, other people mention that ours is their favorite one. While working on it, we tried to explain our way of thinking and a lot of other topics in the readme but as you probably guess, it was impossible to describe everything there. And that is one of the reasons why I wrote a 400-page book which describes it in detail: Master Software Architecture - A Pragmatic Guide. You will learn how to approach building systems in the evolutionary way. You can find both - repo and book - in comments 📚💻

70

16 Comments