Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "svelte"
I am so happy that everybody is building React apps, angular, vue, svelte. There will be so much money when they ask for upgrade and the only way to upgrade is to rebuild it from scratch.
Mark my words.14
I hate hate hate React! Sorry but to me it's just such a bloated pos of a framework. I realize it was pretty revolutionary at first, the idea of having everything "reactive" and all of that - but newer things like Svelte.js are a dream to work with, whereas trudging through the poorly coded React app I'm supposed to be testing for work is making me want to pull my hair out! I installed a vscode tool so everybody could see what the import "cost" is on everything - a simple INPUT is 50KB of pure BLOAT for something that should and can be way simpler.
I realize there are probably better coded apps out there that wouldn't drive me so crazy, but anybody importing hundreds of KB of 3rd party crap just to get a select box, some inputs, and a date picker are really out of their mind.12
I promised myself not to fuck too much with new JS frontends. But Sveltes premise seems interesting enough to check it out and the concept of reactive blocks of code in JS sure is interesting.
This language keeps evolving as well as its tooling. I think shit is pretty amazing.14
About 4-5 hours ago I wanted to make simple websocket to get input from textarea and parse it on server and somehow got myself into developing in asyncio -> aiohttp -> graphql-core -> graphql-ws -> aioredis
and svelte-> typescript
I still didn’t make the stuff I wanted but I’m very close on backend at least.
I have some frontend part somewhere in my old prototypes so it will be faster if I figure out svelte.
Still don’t understand what the fuck just happened.
Maybe it’s because I wanted try those frameworks for a long time.
All ‘simple’ examples I found have around 20-30 files for backend and same amount for frontend so more then 50 files to get this shit working.
They’re called oh irony “simple chat”.
Now I see why no one fucking understands this shit.
I’m trying to cut mine to 5 files.
I thought developers are lazy bastards who don’t like write code.
But now after this they’re all looking like adhd coders.
Looks like Monday won’t be my best day.9
I did not start with Vue yet, but I am already quite tempted to cheat with Svelte.
So hard to choose between them.21
For my peeps in the RoR arena, did y'all ever felt the need to change from ERB as yout server side rendering engine of choice?
I find it hard to use anything else, i would normally stick to it unless I was using Rails as an API and leave the frontend to React or Vue.
Asking about y'alls opinion because I knew about HAML from a while back. But never really used it and I find Rails with ERB to be really efficient.
Ruby pagebuilding with ERB is really flipping comfortable man.ERB has been my favorite for years.
Currently migrating a project to use Svelte and wanted to see what some of y'all think about Haml or erb. Just for the sake of curiosity. Don't know how many rails users we have in here.5
Working on someone else’s React project is a nightmare especially when they don’t know how to write good JSX code ( which most people don’t )
I honestly am looking forward to when Svelte takes over the frontend world5
Ok, I'm actually raging at vuejs right now, and this is coming from my second year using it.
the fucking shit is weird.
functional components cannot use v-model.
functional components also cannot reference other components via components property, that child component needs either to be global or be injected (an ugly hack).
v-model behaves differently on checkboxes. checkboxes are fucking shit on vue. things update or do not update.
functional components with checkboxes? hahahahahaha.
vue 3 is taking an ungodly shitload of fucking amount of time.
fuck react, but im actually considering giving vue the middle finger as well.
started this product migration 2 months ago and regretting it, looking at svelte with curious eyes.12
Why the fuck nobody talks about Multi-page apps?! We went from a Web where everything was Multi-page server-rendered, and now everything for Web developers is "Single-page apps".
What about websites who can't do that? Not everything can be a single-page app. Only my uncle's restaurant website, or something which is TRULY a full app. No half choices.
If your website is a multi-page app/portal which actually PRELOADS data, instead of doing 100 fetch to an API within a page that is full of loading bars, well, your life is a pain.
When you want a first contentful paint which isn't a white page, well, your life is a pain.
What are React, Vue, Ember, Angular (let's exclude Svelte and Marko) going to do about Multi-page apps and SSR?
React-router sucks to me. It's performance is weak and it's useful only when you have an SPA with multiple sections which can be treated as pages (e.g. A single SPA divided in tabs).
Server-side rendering is the worst pain ever made by humanity, in React (and prob Vue, I didn't try but I can bet). And even when made easier from libs like Svelte and Marko, I (personally) can't get it to be faster enough compared to a traditional website without a JS framework and with a templating engine.
Anyways, if there's anything that I learnt from React, is to stay away from Next.js. Perfect, beautiful, mess.
All JS frameworks just seem to bloat the code and make it worse and slower, even though they're REALLY helpful.
Why? Why everyone loves them if their downsides are so clear? Why 3 projects out of 3 I made (1 React SSR, 1 Vue, 1 Marko SSR) are and will stay painfully slow and bloated, full of shit, even if in 2020 we should have evolved with the famous three shaking, with the famous lazy loading, etc.?
I am just frustrated.
And let's not even talk about Webpack, Rollup, Lasso, those module bundlers shit which are harder to configure and understand than finding a needle in a haystack.
Lasso was the easiest to configure but I anyways can't understand it. Webpack seems it was made to handle SPAs, as any tool in this freaking world, and not even considering an easy way to integrate multiple bundles for multiple pages (I know it's pretty easy, but with component sharing between pages and big unique bundles Next.js handles it soooo bad it feels like hell).
Am I the only one?
Sorry for the long rant. I just needed to rant right now.18
Built a Svelte app year ago and it's broken today.
This is not the case with Windows. You can still run a app built on 1999 today.
Opened an issue on their repo requesting that they should add backwards compatibility.
No later than 5 seconds. It got closed and locked with this comment,
"Welcome to development when you don't write your entire stack yourself by hand.
Please open helpful bug reports or don't open any at all."
This is what every FOSS project got as defense. They think since they work for free, they can do what the fuck they want.
The defense is false because they put their OSS project on their resume and in return they get hired for full time work or consulting.
I fucking sue you Svelte if I had money to hire expensive lawyers. This time you are just lucky.38
The only thing that I think works great in Node.js ecosystem is Socket.io
Personally I prefer to keep back end in a different language such as PHP or Python. Separation of concerns was a thing some years ago now everything is JS.
Are there other alternatives to Socket.io in other languages which are easy to setup just like Socket.io? XMPP is there but I feel it is overly complicated to get started.8
IMHO Rich Harris (of the Rollup and Svelte fame) is a rock star. I think I'd rant less of more people would follow his methods.
Did anyone here use sapper and svelte to build a production application? How was the experience overall?
I've been reading about it and watched Rich Harris present svelte and sapper, I like his approach but I'm not too sure about how it work in a production workflow1
Checking out Meteor JS in 2020 after a loooong time in which I ignored it. I participated in the community when it barely startted, liked a couple of things, was effy about some others.
Built a semi large app (custom user auth through ldap, multiple forms and data fetches on different components inside of each page, reporting bla bla bla.
Did it first in just Meteor and Blaze (pretty easy to digest) and then with Meteor and Svelte (still easy to digest, but Blaze was simpler imho) and both packages totalled less than 100mb which is somewhat amazing considering how node is with packages.It might be a good time to psy attention once more to meteor.
I based much of my shit in the now free Discover Meteor book, there aren't that many breaking changes, which makes it surprisingly stable as an application for development.
I don't know if i would use it for s large scale app, but thus far it seems fairly promising as compared to how it was years ago.
Definitely something to keep in mind for 2020-21 development5
So today I thought I’ll try svelte. It was an horrible experience if I compare it to stencil.
I have to install four extensions just to make the file format working properly.
Half of the intellisense is wrong or just slow.
The formatter is not integrated as an vs-code formatter, therefor it can’t format on save automatically.
The source maps do indeed work, but is quite wonky at times. Typescript source code is shown as-is with types, which breaks chrome’s syntax highlighter.
I could also rant about a few small things like the on:something syntax, but eh, that’s it for now. I don’t think I’ll understand why so many like it.4
I mainly using react/svelte + node on making web projects, but I wanted to learn new things outside JS environment. Should I learn RoR(Ruby) or Phoenix(Elixir)?
P.S. I will learn the language first before jumped into the framework6
If someone tries to convince someone else to try X framework, should they be called X missionary?
(asking for a friend)2
How many kilobytes of resources (CSS, JS) do you deem acceptable? I need to know how much I should optimize.
And no, I will not use no JS. Don't suggest that. Svelte is needed.15
Svelte daily reminder because no matter how much I bitch about new things I too cannot keep my eye off shiny:
What new tech/framework/library are you most excited about?
I recently found out about Svelte/Sapper, and I've been having a blast with it. It feels like mini-react, but just as powerful - with a few convenience features that I actually wish react had itself. Also their docs page is amazing. I wish all docs were this good.12
What's your take on Symfony? My dad is making a project in Symfony but he asked me if the current stack I'm using is better (Rust + Sapper/Svelte). I said Symfony is fine (I have very limited experience in it) but I want to give a more useful response to him. Do big projects inevitably turn into a mess in Symfony? Is it enjoyable to work with? I want to recommend him something actually good and not just give him my biased opinion that my stack is better just because I like it more.3
I was thinking about making a PWA website for devRant. It's really only an excuse to play more with some frameworks.
Of course I will make this project open-source so everyone can contribute ;)
What will you choose for this and why?
* maybe even Choo2
I mean, seriously, just to make one app you have to have this massive React project, as well as a runtime. Svelte compiles it into a small bundle that's not too large with *no runtime*!
I was looking at 2019 stateofjs survey. I'm really surprised with all this hate towards Angular. I've been using Angular for past 3 years now, and apart from the mess with versions, I think it's the most complete and beautiful framework out there. I get that not all the people like Angular that much as me but 38% satisfaction (compared to 78% for preact and 88% for svelte for example) in my opinion is craziness.
Any Flutter devs? I'm a new dev on this platform and going to release native a native app for iOS _and_ Android.
I'm kinda getting frustrated. It's a great concept (one codebase, multiple platforms, etc) but I didn't realize I have to watch out for changes in my java and/or, swift changes that might break my build. (ex. A dependency that's deprecated, requiring a newer java/jre only to break something else).
Should I scrap Flutter and learn something else?
Also, it's just a one-time build. Once I'm done, I'm planning to switch to PWA, maybe React or Svelte.7
I really need help making my custom viewports appear in Storybook :( https://stackoverflow.com/questions...