So I need to create a nice new web app. Let's look at some cool JS frameworks that I can work with.

*5 mins later* Hm, Angular sounds good, is there any good competitor?

*5 mins later* Wow, React sounds awesome as well. Let me learn it.

Google search result:

"Planning to use react? Check out Vue JS first"

*5 mins later* Ok so vue seems faster than React and much easier to learn. Let me see if Vue is the final choice.

Google search result:

"Angular VS Knockout VS Ember VS React VS Mithril VS Mercury VS Ractive VS Vue VS Riot"

Nope, fuck it

Nowadays......¯\_(ツ)_/¯

Couldn't resist making this...

I saw a guy building a website today.
No React.
No Vue.
No Ember.
He just sat there.
Writing HTML.
Like a Psychopath.

2010: PHP, CSS, Vanilla JS, and a LAMP Server.

Ah, the simple life.

2016: Node.js, React, Vue, Angular, AngularJS, Polymer, Sass, Less, Gulp, Bower, Grunt.

I can't handle this, I'm shifting domains to Machine Learning.

2017: Numpy, Scipy, TensorFlow, Theano, Keras, Torch, CNNs, RNNs, GANs and LOTS AND LOTS OF MATH!

Okay, okay. Calm down there fella.
JavaScript doesn't seem that complicated now, does it? 🙈

"WE'RE HIRING!!"

Skills Required:

BEFORE: HTML, CSS, JS, jQuery

NOW: REACT/VUE/ANGULAR, NODE, CI/CD PIPELINE, DOCKER, GRAPHQL, JOHN CENA

This just made my day

Googles best javascript framework.

1st link: react is the best one.
Me: Ignore

2nd link: Angular is the best one.
Me: ignore.

.
.
.

8th link: Vue is the best one.
Me: I knew it.

Maintain your LinkedIn, write little articles about implementations on a tech blog, check issues on popular github projects and make PRs, create a portfolio website. Register as a company and do some freelance work, even if it's just a cheap website for your grandma's knitting club.

Do the tour/tutorial of every popular language/framework. Learn the basics of react/vue as a backend dev, learn some sql as a frontend dev. Set up a vps server at DO or AWS, host a few small services. Fullstack is bullshit, but communication is key in development, which means you need to know about the whole playing field.

Recruiters can be useful, but knowing developers in your area is even more valuable. So especially if you're unemployed, go to hackathons, conferences and meetups.

The strength of JavaScript is that you can do anything. The weakness is that you will.

“Fullstack dev continues to unleash his terror.”

We were in a meeting the other day discussing how we can integrate our React component with other existing systems easily — other React apps, Ionic, Angular, Vue and vanilla HTML.

All of a sudden, he opens his mouth.

Fullstack dev: So the thing is... it’s like...ummm... (he always starts after with these words. Always) since Ionic and Vue are both “angular-based”. It shouldn’t be a problem.

Me: excuse me! What do you mean vue is “angular-based”? What’s vue gotta do with angular?

Fullstack dev: You need angular installed to run vue apps and you have data binding in vue and in angular.

Me: (fuck me dead) I don’t know what that means, but I know what the Rock is cookin’. (My exact words in the meeting)

They flew him in from India and they keep extending his stay. He’s been working on the project for 2+ years now.

More to come!

Stolen. This is how I felt on Friday when we were discussing fronted frameworks in office

Why are job postings so bad?
Like, really. Why?

Here's four I found today, plus an interview with a trainwreck from last week.
(And these aren't even the worst I've found lately!)

------

Ridiculous job posting #1:
* 5 years React and React Native experience -- the initial release of React Native was in May 2013, apparently. ~5.7 years ago.
* Masters degree in computer science.
* Write clean, maintainable code with tests.
* Be social and outgoing.

So: you must have either worked at Facebook or adopted and committed to both React and React Native basically immediately after release. You must also be in academia (with a masters!), and write clean and maintainable code, which... basically doesn't happen in academia. And on top of (and really: despite) all of this, you must also be a social butterfly! Good luck ~

------

Ridiculous job posting #2:
* "We use Ruby on Rails"
* A few sentences later... "we love functional programming and write only functional code!"

Cue Inigo Montoya.

------

Ridiculous job posting #3:
* 100% remote! Work from anywhere, any time zone!
* and following that: You must have at least 4 work hours overlap with your coworkers per day.
* two company-wide meetups per quarter! In fancy places like Peru and Tibet! ... TWO PER QUARTER!?

Let me paraphrase: "We like the entire team being remote, together."

------

Ridiculous job posting #4:
* Actual title: "Developer (noun): Superhero poised to change the world (apply within)"
* Actual excerpt: "We know that headhunters are already beating down your door. All we want is the opportunity to earn our right to keep you every single day."
* Actual excerpt: "But alas. A dark and evil power is upon us. And this… ...is where you enter the story. You will be the Superman who is called upon to hammer the villains back into the abyss from whence they came."

I already applied to this company some time before (...surprisingly...) and found that the founder/boss is both an ex cowboy dev and... more than a bit of a loon. If that last part isn't obvious already? Sheesh. He should go write bad fantasy metal lyrics instead.

------

Ridiculous interview:
* Service offered for free to customers
* PHP fanboy angrily asking only PHP questions despite the stack (Node+Vue) not even freaking including PHP! To be fair, he didn't know anything but PHP... so why (and how) is he working there?
* Actual admission: No testing suite, CI, or QA in place
* Actual admission: Testing sometimes happens in production due to tight deadlines
* Actual admission: Company serves ads and sells personally-identifiable customer information (with affiliate royalties!) to cover expenses
* Actual admission: Not looking for other monetization strategies; simply trying to scale their current break-even approach.

------

I find more of these every time I look. It's insane.
Why can't people be sane and at least semi-intelligent?

C#? Should have used Java
Java? So much boilerplate, use node
JavaScript? Terrible language, get some types
Typescript? Lipstick on a pig
PHP? Gross
React? Should have used Angular
Angular? Should have used Vue
Vue? Why aren't you using jQuery + HTML
VSCode? Use vim instead

Stfu, no one gives a shit about your biased closed minded opinion. Your users really don't care what technology you use, so long as they're happy.

- Hmmm, react is not as difficult as I thought. Good tool, let's use it.

- Hmmm, Vue is amazing, let's use this instead, much easier.

- Hmmm, Angular 4 is out, let's retire to a deserted island and sell coconut water for a living.

Me talking to a recruiter (even though I am not looking for a job)

Me: If I walk into an interview, and they ask me to reverse a binary tree for a frontend Reac or Vue position or something along those lines, I will end the call and/or walk away from it.

Him: I get similar feelings from other programmers, I don't quite understand why the notion is as common

Me: Because it is fucking useless, it servers no purpose to a dev to know about that when building frontends with react, I link my github profile, for which they can find advanced backend-frontend related projects, compiler and interpreter projects, plus the title I currently have at my workplace and a bunch of other shit, I am not interviewing for a teaching position at an institute, but an actual place of work, for which if they want to know about DS and A they can review my profile which has a repo of DS and A in about 5 different languages including plain C++. I do not need to be offended by such notions since they server no purpose on the frontend, and neither do other devs. If anything it should be a casual conversation during the interview, not a basis for employment.

Recruiter: .........thank you for explaining this to me, I am sure I can bring it up to the agencies doing the reviews and interviews. Are you still interested?

Me: Are they going to give me a coding assignment for a project or a bs question like what I mentioned?

Him: I don't know

Me: then I am not interested

Your resume:
Git
SSL
Vue
Angular
React
Node
Spring boot
MySQL
MongoDb
HTML
CSS
Java
Javascript
Bootstrap
Cassandra
Hive
Hadoop
Block chain
GraphQL
Kubernetics
Jenkins
Azure
GCP

Interviewer:
Sorry, we need someone who knows AWS

DO NOT USE JAVASCRIPT FOR PUBLIC WEBSITES IF YOU DON'T KNOW HOW TO USE IT!!!

Almost every fucking day, I click a fucking button and NOTHING HAPPENS. I open the console and find tens of JavaScript errors, that *I* have to debug and fix in order to proceed.

FUR FUCK SAKE, JavaScript is not strictly needed, those fucking React and Vue are also not needed. Just now I wanted to download a form: IT'S A FUCKING PDF FILE, why the fuck are you putting your broken JavaScript function to let me download it!? PUT A FUCKING DOWNLOAD LINK YOU FUCKING MORON!

Nobody is forcing anybody to use JavaScript or those fucking fancy frameworks, SO WHY THE FUCK PEOPLE OVERCOMPLICATE THINGS THAT USED TO WORK SO WELL!

what you think about that?

When people suddenly realise that facebook added a patent calsue in 1081 days ago...

Everybody is talking about react, angular, Vue etc, and here I am, fixing ie7-8 website compatibility for a financial-bank institution.

Hi Dev Ranter,

My name is John Smith and I came accross to your resume on Linked In and I was very impressed. Would you be interested in a 5 min call?

Job Details:
Required skills (all expert levels): C#, JAVA, Clojure, C, PHP, Frontend, Backend, Agile, MVP, Baking, Redis, Apache, IIS, RoR, Angular, React, Vue, MySQL, MSSIS, MSSQL, ORACLE, PostgreSQL, Access, Python, Machine Learning, HTML, CSS, Fortran, C++, Game design, Book writing, PCI - Compliance
Salary: $15/Hours no benefits
Duration: 2 Months (possible extension, plus we can fire you at will)
Place: Remote (with work tracking software)
Hours: 5am - 1pm, 6pm - 11pm
Expect to work on weekends

You will be managing people as well as building applications that had to be running as of yesterday. Team culture is very toxic and no one cares about you.

We care about you though (as long as you deliver)

Looking forward to talk to you.

John Smith
Founder, CEO, Director of Staffing, Entrepeneur
Tech Staffers LLC ( link to a PNG posted on facebook)
Est. 2020

You Don't post an "X vs Y" article and conclude with "it depends, there is no winner"

We understand it your opinion so just say it, break hearts if you have to. But don't build tension and then leave the audience hanging.

Ps. This is especially for react vs angular vs vue

The brief history of Facebook open source:
- FB releases React under an oppressive licence that tells "woopsie, can't sue FB if you use React"
- a lot of money goes into making React popular to gain leverage from mass adoption
- VMware bans React in their company
- FB releases Flux to bring state management. It flops. Replaced by what some Russian student wrote in several evenings (Redux)
- Preact is released. It's faster than React, and it has MIT licence. Vue beats React in GitHub stars.
- Under mass pressure, FB changes React's licence to MIT. Initial plan to gain leverage fails spectacularly.
- FB releases Flow Types. It flops. Replaced by TypeScript.
- FB releases their own app market for React Native. It flops.
- FB releases Relay. It flops. Replaced by Apollo.
- FB tries to push React.Suspense for the whole JS landscape to obey and comply to how it works. Community says "Fuck You".
- FB releases react-native-web. It flops.
- Web Components are out in all browsers, adopted as a standard. React doesn't support them.
- Google releases Lit, a virtual DOM framework on top of Web Components to fuck with React. It's a massive success.
- React 18 is out. Still no Web Components support.
- (you are here)

ok its time! im ready to move forward,
i will move my sacred projects from github.

Projects
"Hello world" react
"Hello world" angular
"Hello world" vue
"Hello world" node express
"Hello ..
.
.
.

Me: asking about a problem in javascript
Other: do u use a framework?
me: yes
other: which one?
me: vue
other: i would use angular because this and that

me in my head: okey thanks but its not a problem with the framework lol
pls stop this. react, angular, vue are all doing the same

I really like React and I thought for a second that Vue will overcome React with stars but fortunately developers know what is better 😂😂😂😍

Here's why I hate HR:

Applied to a job and requirements where:
> 3 years + experience with the good old combo HTML CSS JS (oh yeah)
> 3 years + experience with Vue or React (Vue specialist is here baby 😎)
> Salary higher than the average

Got a call on the same day from HR, and she asks:
> Years of experience with Java
> Years of experience with native android development
> Years of experience with Swift or iOS development
> *I started to get confused*
> Then came questions about my machine and if I had good Internet
> And only then she asked about the requirements for the job

2 days later she says I don't fit the job bc they work with different languages

That's why I hate HR, fr.
They didn't know what UI or UX meant.
And kept saying that Vue, angular and react where languages

Languages

The more depressed you get over the current state of software is how you know you made it.When you start making your own opinions and say"wow these people are full of shit"

Primary example, the web development overblown bullshit. Fuck me dude, you really don't need that full featured react, vue, angular framework to make sense of shit. You are going over the top for fucking ajax functionality and state management that you could do by yourself without needing to learn a full framework, by the time you finish learning react you probably would have been better served with standard vanilla af JS and server side rendering.

Our world is full of fads and many talented people that perpetrate them. Its fine, it is a the nature of the beast. But a lot...A LOT of software is very POORLY written. And adding levels of abstraction over a very broken paradigm (web in this case) does and will not make it better.

Basically I am fucking hating being a web developer and want to go back to a time in which we cared about how much memory consumption our applications made as well as not worrying about the fucking frontend having the ability to implement machine learning.

I want to run sublime.exe and being sure that it is a native application to my system and not using a fucking contained web browser to implement my fucking text editor. With 20mb of ram at most instead of 500mb WTF.

I knew I made it when I could read comments on Hacker news and reddit and say "this idiot is full of shit", I knew I made it when I would sigh heavily at the idea of having another project rather than having a fan girl attitude towards it.

I knew I made it when people writing about software development meant shit to me rather than the wonder of what the fuck they were talking about.

I knew I made it when getting laid was more important to me than fucking around with code.

pussy > code
Fuck you.

junior developer position:

You must know:
HTML
CSS
JavaScript
React
Vue
Angular
Java
PHP
C
C++
Ruby on Rails
Python

Computer Science degree required
Expect a 10 round interview process

And if you're still alive after that,
You're hired!

Apply now!

So...

I'm looking for my first job as a web developer. I kept seeing these rants about how horrible and frustrating job searching is, all of which I thought were greatly exaggerated. They're all just jokes and memes, right?

Nope.

Every fucking meme seems to be true.

- Junior developer with +4 years of experience, expert in their field - check!

- Listing requirements for 6 different jobs under "Full-stack developer" - check!

- "Expert developer required ASAP" - $10/hour - check!

- 100% remote ... *scrolls all the way down* ... for 2 days of the week - check!

- Entry level font-end position - must be an expert in Vue, Angular, React, AWS, Drupal, Wordpress, PHP, Python, ES9+, OOP, TDD, BDD - check!

- "Cool" description written in js code with no indentation - check!

And I'm not seeing these every once in a while or something like that. No. Most of the posts are like this. I thought I may just be underqualified since I've never had a real job before, but this just seems crazy to me...

setup my new private project with react, to dive deeper into react.
brain: hey, how about to read a little bit about vue vs. react vs. angular?
me: ok?
me: *reading some articles about the topic*
brain: hey, how about to play around with vue a little bit?
me: ok.

and this is me right now:

So I watched this video that tries to convince people, that the jQuery library isn't really best practice anymore and showed how you can achieve basic tasks with vanilla JS, aswell as some frameworks (Vue, React, Angualar) and how they handle interactions with the DOM.

It also talked about how nearly every JS question on SO has top answers using jQuery, and how that's a bad thing.

But what I found in the comment section of this video was pure horror: So-called "Developers" defending jQuery to the death. Of course there were some people who made some viable arguments (legacy code, quick & dirty projects), but the overwhelming majority were people making absurd claims and they seemed quit self-confident.

GOSH!

Want an example?
Look:

I've optimised so many things in my time I can't remember most of them.

Most recently, something had to be the equivalent off `"literal" LIKE column` with a million rows to compare. It would take around a second average each literal to lookup for a service that needs to be high load and low latency. This isn't an easy case to optimise, many people would consider it impossible.

It took my a couple of hours to reverse engineer the data and implement a few hundred line implementation that would look it up in 1ms average with the worst possible case being very rare and not too distant from this.

In another case there was a lookup of arbitrary time spans that most people would not bother to cache because the input parameters are too short lived and variable to make a difference. I replaced the 50000+ line application acting as a middle man between the application and database with 500 lines of code that did the look up faster and was able to implement a reasonable caching strategy. This dropped resource consumption by a minimum of factor of ten at least. Misses were cheaper and it was able to cache most cases. It also involved modifying the client library in C to stop it unnecessarily wrapping primitives in objects to the high level language which was causing it to consume excessive amounts of memory when processing huge data streams.

Another system would download a huge data set for every point of sale constantly, then parse and apply it. It had to reflect changes quickly but would download the whole dataset each time containing hundreds of thousands of rows. I whipped up a system so that a single server (barring redundancy) would download it in a loop, parse it using C which was much faster than the traditional interpreted language, then use a custom data differential format, TCP data streaming protocol, binary serialisation and LZMA compression to pipe it down to points of sale. This protocol also used versioning for catchup and differential combination for additional reduction in size. It went from being 30 seconds to a few minutes behind to using able to keep up to with in a second of changes. It was also using so much bandwidth that it would reach the limit on ADSL connections then get throttled. I looked at the traffic stats after and it dropped from dozens of terabytes a month to around a gigabyte or so a month for several hundred machines. The drop in the graphs you'd think all the machines had been turned off as that's what it looked like. It could now happily run over GPRS or 56K.

I was working on a project with a lot of data and noticed these huge tables and horrible queries. The tables were all the results of queries. Someone wrote terrible SQL then to optimise it ran it in the background with all possible variable values then store the results of joins and aggregates into new tables. On top of those tables they wrote more SQL. I wrote some new queries and query generation that wiped out thousands of lines of code immediately and operated on the original tables taking things down from 30GB and rapidly climbing to a couple GB.

Another time a piece of mathematics had to generate all possible permutations and the existing solution was factorial. I worked out how to optimise it to run n*n which believe it or not made the world of difference. Went from hardly handling anything to handling anything thrown at it. It was nice trying to get people to "freeze the system now".

I build my own frontend systems (admittedly rushed) that do what angular/react/vue aim for but with higher (maximum) performance including an in memory data base to back the UI that had layered event driven indexes and could handle referential integrity (overlay on the database only revealing items with valid integrity) or reordering and reposition events very rapidly using a custom AVL tree. You could layer indexes over it (data inheritance) that could be partial and dynamic.

So many times have I optimised things on automatic just cleaning up code normally. Hundreds, thousands of optimisations. It's what makes my clock tick.

This rant is aimed towards those who hate on JavaScript developers and the JS language:

Dear Asshole,

I am a JavaScript developer by choice.
I think JavaScript is great.
I agree that JavaScript have some bad sides to it, but I believe that the community is driving good change to the ecosystem.
I appreciate other models of other languages.
I do not include 3rd party NPM modules without checking their source and credibility.
I will not use a framework (i.e. react, Vue, Anguler) if it's not needed.

And finally:
I can do any software engineering tasks a software engineer is supposed to do.

Kind regards,
Nedo-the-angry.

Frustrated, tired and a bit lost.

I'm a "Senior PHP Backend Dev", which includes not the greatest tech stack nor the best job title, but it pays fine, and the company is awesome to work for.

I suck at writing features, but I'm great at bitching, and I easily put complex abstract concepts into usable models. So I'm also QA, tester, tech lead, database architect, whatever.

That makes writing PHP less annoying, because I create the rules, and whip devs around when they forget a return type definition or forget to handle an edge case. But I don't write a lot of code anymore, I mostly read (bad) code.

Lately I REALLY feel like doing something else... problem is that I know JS/ES6, but really dislike React/Vue and the whole crappy modern frontend toolchainchootrain of babelifyingwebpackingyarnballs. I know Python/Tensorflow/etc, but don't feel like I want to go into data science or AI. And then I'm awesome at the shit no one uses, like Haskell, Go and Rust (and worse).

I got a job offer which combines a very interesting PHP codebase with a Java infrastructure, where I could learn a lot... and I'm kind of tempted.

Problem is, everyone always shits on Java. I always made a bit of fun of Java myself. Don't even know exactly why, probably some really cruel instinct which causes kids to bully the least popular kid.

I know the basics, I've written the hello world, and a small backend app for a personal project. I know how strict and verbose it can be. I love the strictness in Haskell and Rust.... but those are both also quite terse.

Should I become a Java dev? I'm not talking about Android SDK, but an insane enterprise codebase at a life sciences corporation.

To the pro Java devs: What are the best and worst things about your job, about the weekly processes, about the toolchains? Have you ever considered other languages? Do you unconditionally love and believe in Java, or do you believe Swift, Kotlin, Scala or whatever will eventually make it completely obsolete?

Will Java hasten my decline into the cynical neckbeard I was always destined to be?

There are a lot more fun langauges, but looking at realistic demand and career value...

I got tired of relearning JavaScript frameworks and instead tried to escape their clutches.

Most of my developer life I've spent relearning how to do the same thing in a different framework.

And every three or four years its the same story, figure out templating, figure out building, complain on github bugs etc.

I am trying to reduce framework fatigue by allowing you to think "can I make my application with just vanilla JavaScript". The advantage of vanilla JavaScript is it write once - do not need to rewrite.

Do YOU think I will abandon ship and end up having to use a framework again?

Is it just me who sees this? JS development in a somewhat more complex setting (like vue-storefront) is just a horrible mess.
I have 10+ experience in java, c# and python, and I've never needed more than a a few hours to get into a new codebase, understanding the overall system, being able to guess where to fix a given problem.
But with JS (and also TS for that matter) I'm at my limits. Most of the files look like they don't do anything. There seems to be no structure, both from a file system point of view, nor from a code point of view.
It start with little things like 300 char long lines including various lambdas, closures and ifs with useless variables names, over overly generic and minified method/function names to inconsistent naming of files, classes and basically everything else.
I used to just set a breakpoint somewhere in my code (or in a compiled dependency) wait this it is being hit and go back and forth to learn how the system state changes.
This seems to be highly limited in JS. I didn't find the one way to just being able to debug, everything that is. There are weird things like transpilers, compiler, minifiers, bablers and what not else. There is an error? Go f... yourself ...
And what do I find as the number one tipp all across the internet? Console.log?? are you kidding me, sure just tell me, your kidding me right?
If I would have to describe the JS world in one word, I would use "inconsistency". It's all just a pain in the ass.

I remember when I switcher from VisualStudio/C# to Eclipse/Java I felt like traveling back in time for about 10 years. Everyting seemd so ... old-schoolish, buggy, weird.
When I now switch from java to JS it makes me feel the same way. It's all so highly unproductive, inconsistent, undeterministic, cobbled together.
For one inconveinience the JS communinity seems to like to build huge shitloads of stuff around it, instead of fixing the obvious. And noone seems to see that.
It's like they are all blinded somehow. Currently I'm also trying to implement a small react app based on react-admin. The simplest things to develop and debug are a nightmare. There is so much boilerplate that to write that most people in the internet just keep copying stuff, without even trying to understand what it actually does.
I've always been a guy that tries to understand what the fuck this code actuall does. And for most of the parts I just thing, that the stuff there is useless or could be done in a way more readable way. But instead, all the devs out there just seem to chose the "copy and fix somehow-ish" way.
I'm all in for component-izing stuff. I like encapsulation, I'm a OOP guy by heart. But what react and similar frameworks do is just insane. It's just not right (for some part).
Especially when you have to remember so much stuff that is just mechanics/boilerplate without having any actual "business logical function".

People always say java is so verbose. I don't think it is, there is so few syntax that it almost reads like a prose story. When I look at JS and TS instead, I'm overwhelmed by all the syntax, almost wondering every second line, what the actual fuck this could mean. The boilerplate/logic ration seems way to off ..

So it really makes me wonder, if all you JS devs out there are just so used to that stuff, that you cannot imagine how it could be done better? I still remember my C# days, but I admin that I just got used to java. So I can somehow understand that all. But JS is just another few levels less deeper.
But maybe I'm just lazy and too old ...

I shit you not. This this a job qualifications qualifications entry level on LinkedIn.

7+ years working as part of a development team and with the following technologies:
Node.js Typescript and Java-based, microservice-driven applications using Spring Boot or similar framework
RESTful API design / microservice architectures
MongoDB or any other NoSQL DB
Message queues e.g. RabbitMQ, Kafka etc.
Modern MV*(MVC, MVVM, etc..) frameworks e.g. React, Angular, Vue etc.
JavaScript and design patterns, CSS and HTML
Modern CSS and view libraries e.g. RxJS, Angular Material, Typescript, JS ES6 etc.
Unit and UI testing using third party tools e.g. Jest, Cucumber, Groovy & Spock, etc.
Bachelor's degree in computer science or related field

Frontend Developer wanted. Required skills: C#, PHP, MySQL, HTML, CSS, Jquery, Java, JavaScript, React, Angular, Vue, Laravel, Wordpress, Shopify, Docker, Git, SVN, Ruby.

Must have at least 3 years of working experience in a high level company. Only worked for A+ clients and ultra high traffic websites.

Also nice would be UX/UI, Design Systems, Wireframing.

Experienced in sales and cleaning floors. Getting coffee putting music on etc

Salary indication: €1800

Only God Knows

Vue vs React...

Which one do you guys use or like better?

I'm been dabbling in Vue and like it so far...just wondering if I'm putting myself in a pigeon hole against a 'more widely adopted and stable' framework

Angular....meh....

Wow, since vue passed react on gh, this is like a competition, but only for the stars.
It's been like 2 days that there's < 10 stars of difference.
Looks like shitpost that you see on facebook, where the likes are not use to "evaluate" a post, but mostly as a dummy counter.
Am i the only one to found this ridiculous?

Fuck web development - especially CSS. Actually only CSS.

Love Js/Ts, Vue, React (NextJs ftw) and especially thank you to SCSS for making things easier.

But CSS is my most detested LaNgUagE now.

After I finish these 2 projects, I’m not doing CSS anymore. Minimal touches, sure, but no more positioning.

Maybe that’s why I like Flutter, no hassles yet.

Having worked with all the major frontend frameworks. I can finally say that Vue is fking awesome!!! Way better than react and angular.

I hope the one man army continues. Evan You.

Job ad title: "junior Php developer position £20k-£25k/pa"

Job ad body: "5+ years experience required in Php, JavaScript, html 5, css, experience in laravel, Vue and react."
🤔

How do devs React when they realize Vue is upside-down triAngular? (Share ur clever answers)

I’ve come to the conclusion that developers who like react have never used it for anything even remotely complicated.

Because here’s reacts dirty little secret; it doesn’t scale. Not even a little. It’s flexible, but that leads to every developer writing their code in a different way.

It’s simple and easy for simple side projects, but as soon as you have to pass state to a child component, you’re fucked. And god help you if you’re modifying the state in said child component. You can try using redux, but that’s a bandaid solution to the real issue.

There are better alternatives, namely Vue. There’s no need to write unintelligible code that’s a mutated hybrid of html css and js. We as web developers realized mixing these technologies was a bad idea a long time ago.

React simply doesn’t scale. It’s flexibility, complexity, and the awful code quality it leads to makes it a nightmare for large projects with multiple developers

Some of its concepts are interesting and useful though. It’s functional concepts allow for easy code reuse, among the other benefits associated with functional programming

I sincerely hope that the hype around react dies out, and a new framework emerges that takes the best from react and fixes the glaring issues it currently has

TL;DR: Stop using React for EVERYTHING. It's not the end-all solution to every application need.

My team is staffed about 50/50 with tenured devs, and junior devs who have never written a full application and don't understand the specific benefits of different libraries/framworks. As a result, most of these junior devs have jumped on the React train, and they're under the impression that React is the end-all answer to any possible application need. Doesn't matter what type of app is, what kind of data is going to be flowing through the app, data scale, etc. In their eyes, React is always the answer. Now, while I'm not a big fan of React myself, I will say that it does its job when its tasked with a data-heavy application that needs to be refreshed/re-rendered dynamically and frequently (like Facebook.) However, my main gripe is that some people insist on using it for EVERYTHING. They refuse to acknowledge that there can be better library/framework choices (Angular, Vue, or even straight jQuery,) and they refuse to learn any other frameworks. You can hit them with countless technical reasons as to why React isn't a good choice for a particular application, and they'll just spout off the same tidbits from the "ReactJS Makes My Nips Hard 101" handbook: "React is the future," "Component-based web architecture is the future," (I'm not arguing with that last one) "But...JSX bro.," "Facebook and Netflix use it, so that's how you know it's amazing." They'll use React for a simple app, and make it overly-complex, and take months to write something that should have taken them a week. For example, we have one dev who has never used any other frameworks/libraries apart from React, and he used React (via create-react-app) to write what is effectively a single form and a content widget inside of a bootstrap template. It took him 4 MONTHS to write this, and it still isn't fully functioning. The search functionality doesn't really work (in fact, it's just array filtering,) and wont return any results if you search for the first word in an entry. His repo is a mess, filled with a bunch of useless files that were bootstrap'd in via create-react-app. We've built apps like this in a week in the past using different libraries/frameworks, and he could have done the same if he didn't overly-complicate the project by insisting on using React. If your app is essentially a dynamic form, you don’t need a freaking virtual DOM.

This happens every time a big new framework hits the scene. New young developers get sucked into it, because it's the cool hip new framework (or in React's case, library.) and they use it for everything, even when it's not the best choice. It happened with Angular, Rails, and now it's happening with React.

React has its benefits, but please please please consider which library/framework is the best choice from a technical standpoint before immediately jumping on the React train because "Facebook uses it bro."

£20 for Vue 😱 I'll stick with React 😂

To paraphrase Paul Graham:

Arguing that Vue is better than React is like arguing that grasshoppers taste better than tree bark.

Angular is still a pile of steaming donkey shit in 2023 and whoever thinks the opposite is either a damn js hipster (you know, those types that put js in everything they do and that run like a fly on a lot of turds form one js framework to the next saying "hey you tried this cool framework, this will solve everything" everytime), or you don't understand anything about software developement.

I am a 14 year developer so don't even try to tell me you don't understand this so you complain.
I build every fucking thing imaginable. from firmware interfaces for high level languaces from C++, to RFID low level reading code, to full blown business level web apps (yes, unluckily even with js, and yes, even with Angular up to Angular15, Vue, React etc etc), barcode scanning and windows ce embedded systems, every flavour of sql and documental db, vectorial db code, tech assistance and help desk on every OS, every kind of .NET/C# flavour (Xamarin, CE, WPF, Net framework, net core, .NET 5-8 etc etc) and many more

Everytime, since I've put my hands on angularJs, up from angular 2, angular 8, and now angular 15 (the only 3 version I've touched) I'm always baffled on how bad and stupid that dumpster fire shit excuse of a framework is.

They added observables everywhere to look cool and it's not necessary.
They care about making it look "hey we use observables, we are coo, up to date and reactive!!11!!1!" and they can't even fix their shit with the change detection mechanism, a notorious shitty patchwork of bugs since earlier angular version.

They literally built a whole ecosystem of shitty hacks around it to make it work and it's 100x times complex than anything else comparable around. except maybe for vanilla js (fucking js).

I don't event want todig in in the shit pool that is their whole ecosystem of tooling (webpack, npm, ng-something, angular.json, package.json), they are just too ridiculous to even be mentioned.

Countless time I dwelled the humongous mazes of those unstable, unrealiable shitty files/tools that give more troubles than those that solve.

I am here again, building the nth business critical web portal in angular 16 (latest sack of purtrid shit they put out) and like Pink Floyd says "What we found, same old fears".
Nothing changed, it's the same unintelligible product of the mind of a total dumbass.

Fuck off js, I will not find peace until Brendan Eich dies of some agonizing illness or by my hands

I don't write many rants but this, I've been keeping it inside my chest for too long.

I fucking hate js and I want to open the head of js creator like the doom marine on berserk

When you accidentally thought Vue JS is Vivus JS and argue why would you need a SVG animator to compare with React. JS naming. God.

PEASANT POOR MAN'S TECH
* Python
* Java
* JavaScript
* Vue
* Golang

ENLIGHTENED ELITE TECH
* C#
* Kotlin
* TypeScript
* React
* C++

Can we please eliminate React?
I was interviewing lately and the lady asked if I knew react, I said no and I don't want to. She then asked what the hell I use for front end... As if react is the only thing you can use... Ehm hello we still have vanilla JS and jQuery in the house. Which are better, faster and easier to use for like +90% of all Web projects out there...

Fuck vue, react AND angular... this will always have a special place in my heart

Hi guys I'm new in dev
I was wondering what was best to learn first : Angular, React or Vue ?
I already know JS and JQuery.
Thanks guys :)

btw, i'm still using jquery

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.

I'm learning nginx and it's simplying the way I think about web projects.

I used to think that when I used a server side framework, then that should be the master and all should go through it. Noob me.

I used to put client side projects (like create-react-app of vue-cli projects) right inside the server side project.

But with nginx you can just route subpaths to different places, then instead of having, let's say, the react project inside rails, they would be in separate git projects.

In fact, I no longer need to restrict myself to a single server framework.

I love several aspects of rails. I love several others of node. And if I need multithreaded performance, I'd very much use something like phoenix or go.

Again, with nginx, you setup subpaths with the `location` directive in the same server and voila, a no CORS setup, cookies shared and homogenous versatile website.

What To Learn?

I'm a beginner in web development and have knowledge about html, css, JavaScript, jQuery, Sass, NodeJS, Express, MongoDB, Passport. You can consider me to be a beginner full stack developer, but I'm confused about what to learn further. There are so many front end frameworks that one can spend his entire life learning them. React, Vue, Angular, Backbone, etc. But I always want to learn backend properly, then there's Rails, PHP, SQL, Python. Can anyone atleast tell me what to learn and why exactly? This thing's making me mad and anxious.

My boss started contemplating whether to start using styled-components for react.

I showed him Vue: "oh well, so we're basically recreating Vue within jsx?"

I'm not sure what problem we're solving anymore

Stackoverflow is life :V

(most of the) Medium authors all suck fucking dick. Those fuckers are the reason the internet needs an IQ lock.

Stats about React vs Angular vs Vue.

Yeah of course let's compare search count of React vs Vue vs Angular but Vue must be searched with ".js" appended. NOT A SINGLE FUCK ADDS .JS WHEN SEARCHING FOR VUE.

Left: stats from article
Right: stats, if you use google trends correctly

Learn nodejs, love it, abandon it coz most jobs in the country want php and none heard about the new js frameworks.

1 year later, decide to change job, look at posting to find senior php position, all companies want node, angular, react & vue...

Even though I love vue, I feel that the "store" part of vue is kind of lacking compared to react.

I've seen several react projects that improve in that area.

Btw, I started building in react, I am just loving it!

List ALL js frameworks

I Vue so much but I don't React 😂

Check in, check out, punch in punch, out, wax on (my balls), wax off. Do your duty. Be a good citizen. Work overtime. Conserve the environment: buy a tesla that runs on afghan lithium conflict minerals. Post your life to facebook. Get married. Have exactly 2.5 kids.
Use jquery. Use knockout. Use react. Use vue. Use svlete. Use heroin. Used needles. Used people. Used toilet paper. Toilet paper apocalypse. Social trends. Be a good citizen.

Watch tv. Watch nightly news. CNN says. Fox news says. Hey, did you read this article by important funny guy on tv? American taliban. Scary. Be afraid. Hey did you read this article on cute puppies? Funny! Did you see this meme? What a funny meme! HAHAHA. Do we need prisons for dissidents? Do we need to release all the prisoners in federal prison? Should we round up people who dont follow health authorities? Science says. Science is wrong. Science is right. Man in robe agrees with me. Man in robe disagrees with me. You're evil. These people are bad. Is doing bad always wrong? Should we tolerate intolerance? Its time to stop tolerating intolerance. Be an individual, like everyone else. Be you. Be the best you that you can be. Individualism. But we're all in this together. We're all different and unique. But we're all the same. Love each other. Love humanity. But not these guys over here. Punch a nazi. Punch a commie. Isn't it time we punched a nazi? Isn't it time we had socialism? Isn't it time the old get out of the way for the young? Why are the old hateful? Why do they horde all the money? Do we need rent controls? We need rent controls. Its time for rent controls. I think I believe what others believe. Believe different. Think different. Apple. An apple a day keeps the windows away. Open windows, a breathe of fresh air. Is climate change real? We need to have a national conversation about climate change! The world is freezing. The world is flooding. We're all gonna drown. The world is overpopulated. We need to talk about overpopulation. People who have too many kids are polluting the world. America doesnt have enough kids! Is it time to bring in more immigrants to have more kids? Who will work the fields? Thats racist. Is racism an epidemic? Is white flight an epidemic? Lets talk about epidemics. Lets have a conversation about mandatory vaccination. Lets have a national conversation about mandatory pandemics. I mean, vaccinations. Lets change the world. Trust the science. Don't trust the science. Bu-bu-bu-bu-bu I'm loving it. Love who you are. Live love laugh. If you don't love me at my best, then you can't handle me at my worst. People who disagree with [current year] are the worst. Is it time to regulate speech? Its time to regulate speech. Should there be laws against hatespeech. I think there should be laws against hatespeech. People who upset me should go to jail. Its current year. Think big. Think outside the bun. Have it your way. All the time, always. All for freedom, freedom for all. Because this is america, and current year. I like to work hard. But you have to remember to play hard too. Work hard. Play hard. With a childlike sense of wonder. Be you. Belong anywhere. Just do it. Challenge Everything. Because you're worth it. Save money...live better...have an abortion. You're in good hands. Democracy dies in darkness. Is it time to regulate hatespeech. Politician in current year is hurting our democracy. War is a racket. We need to liberate afghanistan. Why are we bombing afghanistan? Its there culture. They're oppressing people! Don't criticize anyones culture. Be kind. Rewind. Go further. Lets go places. Because Impossible is Nothing.
Lets change the world. I'm a smart passionate funny guy with a childlike sense of wonder and play. You ever want to travel? I want to travel. See the world. Eat new food. Eat. Love. Pray. Eat love. kill. Is meat murder? I think meat is murder. Go vegan. Go home. Order out. Support your local economy. Think global, act local. I'm a good corporate citizen. Be the change you want to see. Did you hear about this local brewery? Do you like craft beer? Hey try this new IPA. I shared it on twitter. Twitter is a very important part of my life. I think what other people say matters, and them reading what I think matters. What I ate for lunch matters. Hey what did you eat for lunch? I LOVE FOOD. You want to order door dash. There new commercial is amazing. Commercials are SO FUNNY. Hey did you see this meme of this commercial? I shared it on tiktok. Heres a funny dance. Watch these nurses dance. I wish I could dance like that. They're so overworked. So brave. Our hospitals are overflowing. People are dying. Hey did you see this new dance trend on tiktok? I like tiktok. I think its a very important part of life to share your life with others. Nurses are dying. Look at this image of hospitals. Scared. Very scary. Very bad. Bad and scary. Big thoughts! Thoughts and prayers!

Because Yes we can!

Beep boop.

So, I've had a personal project going for a couple of years now. It's one of those "I think this could be the billion-dollar idea" things. But I suffer from the typical "it's not PERFECT, so let's start again!" mentality, and the "hmm, I'm not sure I like that technology choice, so let's start again!" mentality.

Or, at least, I DID until 3-4 months ago.

I made the decision that I was going to charge ahead with it even if I started having second thoughts along the way. But, at the same time, I made the decision that I was going to rely on as little external technology as possible. Simplicity was going to be the key guiding light and if I couldn't truly justify bringing a given technology into the mix, it'd stay out.

That means that when I built the front end, I would go with plain HTML/CSS/JS... you know, just like I did 20+ years ago... and when I built the back end, I'd minimize the libraries I used as much as possible (though I allowed myself a bit more flexibility on the back end because that seems to be where there's less issues generally). Similarly, any choice I made I wanted to have little to no additional tooling required.

So, given this is a webapp with a Node back-end, I had some decisions to make.

On the back end, I decided to go with Express. Previously, I had written all the server code myself from "first principles", so I effectively built my own version of Express in other words. And you know what? It worked fine! It wasn't particularly hard, the code wasn't especially bad, and it worked. So, I considered re-using that code from the previous iteration, but I ultimately decided that Express brings enough value - more specifically all the middleware available for it - to justify going with it. I also stuck with NeDB for my data storage needs since that was aces all along (though I did switch to nedb-promises instead of writing my own async/await wrapper around it as I had previously done).

What I DIDN'T do though is go with TypeScript. In previous versions, I had. And, hey, it worked fine. TS of course brings some value, but having to have a compile step in it goes against my "as little additional tooling as possible" mantra, and the value it brings I find to be dubious when there's just one developer. As it stands, my "tooling" amounts to a few very simple JS scripts run with NPM. It's very simple, and that was my big goal: simplicity.

On the front end, I of course had to choose a framework first. React is fine, Angular is horrid, Vue, Svelte, others are okay. But I didn't want to bother with any of that because I dislike the level of abstraction they bring. But I also didn't want to be building my own widget library. I've done that before and it takes a lot of time and effort to do it well. So, after looking at many different options, I settled on Webix. I'm a fan of that library because it has a JS-centric approach. There's no JSX-like intermediate format, no build step involved, it's just straight, simple JS, and it's powerful and looks pretty good. Perfect for my needs. For one specific capability I did allow myself to bring in AnimeJS and ThreeJS. That's it though, no other dependencies (well, at first, I was using Axios because it was comfortable, but I've since migrated to plain old fetch). And no Webpack, no bundling at all, in fact. I dynamically load resources, which effectively is code-splitting, and I have some NPM scripts to do minification for a production build, but otherwise the code that runs in the browser is what I actually wrote, unlike using a framework.

So, what's the point of this whole rant?

The point is that I've made more progress in these last few months than I did the previous several years, and the experience has been SO much better!

All the tools and dependencies we tend to use these days, by and large, I think get in the way. Oh, to be sure, they have their own benefits, I'm not denying that... but I'm not at all convinced those benefits outweighs the time lost configuring this tool or that, fixing breakages caused by dependency updates, dealing with obtuse errors spit out by code I didn't write, going from the code in the browser to the actual source code to get anywhere when debugging, parsing crappy documentation, and just generally having the project be so much more complex and difficult to reason about. It's cognitive overload.

I've been doing this professionaly for a LONG time, I've seen so many fads come and go. The one thing I think we've lost along the way is the idea that simplicity leads to the best outcomes, and simplicity doesn't automatically mean you write less code, doesn't mean you cede responsibility for various things to third parties. Those things aren't automatically bad, but they CAN be, and I think more than we realize. We get wrapped up in "what everyone else is doing", we don't stop to question the "best practices", we just blindly follow.

I'm done with that, and my project is better for it!

Donate now!

Why do front end developers like to write their HTML/Component markup like this:

<div
id="test"
class="test"
>
Test
</div>

That lone > bracket absolutely irks me! Looks ugly! I prefer the Android style:

<div
id="test"
class="test">

<span>Test</span>
</div>

👌clean

I started a new project and only use PHP, HTML, CSS and vanilla JS. No Frameworks. No React. No Vue.

The browser loads the page instantly, there is virtually no loading time and it just works.

I hate React. I keep reading that people have problem of grasping it, but that's not the case for me. I get it, I understand it, but I hate with passion HOW it's done knowing how nice it's done elsewhere. What really triggers me is how ugly it looks, both from architecture and code level. To me it really say a lot when even code shown in documentation looks ugly, and while reading it you ask ourself constantly "why it's done this way?". When I read React being called an "elegant" solution something explodes in me. Did you saw Svelte? Vue? Damn, even Alpine.js?
I just cannot how overengineered this API is. Even doing simplest things there produces so much junk code written only because this is what library requires. Why? I feel like working with it is a punishment.
And scalability and maintainability? I've never seen large-scale projects more messed up than those wrote with React. And yes, you can blame teams working on them for lack of skills, but it is the library which encourages or not good practices also, and I've never seen such bad situation with other libraries/frameworks.

Everything is fun and games until you try to understand and do server-side rendering.

!!!rant

Most exited I've been about some code? Probably for some random "build a twitter clone with Rails" tutorial I found online.

I've been working on my CS degree for a while (theoretical CS) but I really wanted to mess with something a bit more practical. I had almost none web dev experience, since I've been programming mostly OS-related stuff till then (C). I started looking around, trying to find a stack that's easy to learn since my time was limited- I still had to finish with my degree.

I played around with many languages and frameworks for a week or two. Decided to go with Ruby/Rails and built a small twitter clone blindly following a tutorial I found online and WAS I FUCKING EXITED for my small but handmade twitter clone had come to life. Coming from a C background, Ruby was weird and felt like a toy language but I fell in love.

My excitement didn't fade. I bought some books, studied hard for about a month, learned Ruby, Rails, JavaScript, SQL (w/ pg) and some HTML/CSS. Only playing with todo apps wasn't fun. I had a project idea I believed might be somewhat successful so I started working on it.

The next few months were spent studying and working on my project. It was hard. I had no experience on any web dev technology so I had learn so many new things all at once. Picked up React, ditched it and rewrote the front end with Vue. Read about TDD, worked with PostgreSQL, Redis and a dozen third party APIs, bought a vps and deployed everything from scratch. Played it with node and some machine learning with python.

Long story short, one year and about 30 books later, my project is up and running, has about 4k active monthly users, is making a profit and is steadily growing. If everything goes well, next week I'll close a deal with a pretty big client and I CANT BE FKING HAPPIER AND MORE EXCITED :D Towards the end of the month I'll also be interviewed for a web dev position.

That stupid twitter clone tutorial made me excited enough to start messing with web technologies. Thank you stupid twitter clone tutorial, a part of my heart will be yours forever.

I have big plans for 2020:

- learn a js framework (angular, react, vue, etc)
- publish a mobile app
- contribute to open source
- start blogging

If I complete only one of these before 2021 I'll be happy 😊

GODDAMN I HATE WIX!

I feel angry. I feel like smashing the developer's face who programmed this piece of shit editor. Everything I touch there just breaks and moves on its own. I fix the header, save, come back the next day and everything is shifted 5 pixels. WTF!?!

Plugins that they developed in-house aren't even compatible with their own systems. Custom code disappears suddenly. Editor doesn't allow two people to edit at the same time, resulting in lost work.

Seriously FUCK WIX.

Don't ever even consider touching this nightmare of an editor.

I could literally have hard-coded the entire site in React or Vue faster than building it in this editor, but my client wants the ability to edit things on their own later.

WIX: Not even once.

Why do we never talk about angular? It was way ahead all the time. Like you got all these nice things with Vue 3 and React 42, but bro angular got it all for years..

It feels so nice learning it.

In a time where a web dev is expected to know, well.. everything... Backend -JAVA, python, nodejs and C++ would be great.
Front- angular, react, other 10 libs
DBs -sql, mongo, redis, elastic, kafka, rebbitmq
Also be devops on the side with AWS and docker kubernetis and more stuff

How the f is that possible?

In my real job for the last couple of years and different companies, I usually use 1 language/framework & 1 main DB.. and although it's possible in some companies, but in mine, ppl dont get access to AWS etc..

So let's say there's me.. a server side dev for years.
So I decide to be better and learn Golang.. cool lang, never needed in my job, after few days of not using it I forgot all I learned and that was it.

Then I realized I gotta know some frontend cause everyone want a fullstack ninja nowadays.. so I tried Vuejs.. it was amazing .. never got to use it at work, cause i was a backend, and we didnt use frameworks on our products back then..
Also forgotten.

Then I decided to learned nodejs, because this is the coolest thing ever.. hated it, but whatever... Never got to use it at work, cause everything was written in other lang which the whole team knew... Forgot the little i knew.

Then I decided, its time to see what Angular is, cause everyone started using it... similar idea to vuejs which i barely remembered, but wow it's a lot of code to remember, or I'll have to google everything.. so I went over it, but can't say i even learned it.

Now Im trying to move on to python, which, I really am learning in depth.. however, since I dont have real experience with it, no one gives me a shot at being a python dev, so again i feel like I'm trying to memorize syntax and wasting my time..

Tired of seeing React in all job ads, i decided to have a look what's that all about.. and whadoyaknow... It's fucking the same idea as vue/angular with again different syntax..

THIS IS CRAZY!

in how many syntaxes do i need to know how to make a fucking crud api, and a page with same fucking post form, TO BE A GOOD PROGRAMMER?!?

React or vue

It's been a while DevRant!

Straight back into it with a rant that no doubt many of us have experienced.

I've been in my current job for a year and a half & accepted the role on lower pay than I normally would as it's in my home town, and jobs in development are scarce.

My background is in Full Stack Development & have a wealth of AWS experience, secure SaaS stacks etc.

My current role is a PHP Systems Developer, a step down from a senior role I was in, but a much bigger company, closer to home, with seemingly a lot more career progression.

My job role/descriptions states the following as desired:

PHP, T-SQL, MySQL, HTML, CSS, JavaScript, Jquery, XML

I am also well versed in various JS frameworks, PHP Frameworks, JAVA, C# as well as other things such as:

Xamarin, Unity3D, Vue, React, Ionic, S3, Cognito, ECS, EBS, EC2, RDS, DynamoDB etc etc.

A couple of months in, I took on all of the external web sites/apps, which historically sit with our Marketing department.

This was all over the place, and I brought it into some sort of control. The previous marketing developer hadn't left and AWS access key, so our GitLabs instance was buggered... that's one example of many many many that I had to work out and piece together, above and beyond my job role.

Done with a smile.

Did a handover to the new Marketing Dev, who still avoid certain work, meaning it gets put onto me. I have had a many a conversation with my line manager about how this is above and beyond what I was hired for and he agrees.

For the last 9 months, I have been working on a JAVA application with ML on the back end, completely separate from what the colleagues in my team do daily (tickets, reports, BI, MI etc.) and in a multi-threaded languages doing much more complicated work.

This is a prototype, been in development for 2 years before I go my hands on it. I needed to redo the entire UI, as well as add in soo many new features it was untrue (in 2 years there was no proper requirements gathering).

I was tasked initially with optimising the original code which utilised a single model & controller :o then after the first discussion with the product owner, it was clear they wanted a lot more features adding in, and that no requirement gathering had every been done effectively.

Throughout the last 9 month, arbitrary deadlines have been set, and I have pulled out all the stops, often doing work in my own time without compensation to meet deadlines set by our director (who is under the C-Suite, CEO, CTO etc.)

During this time, it became apparent that they want to take this product to market, and make it as a SaaS solution, so, given my experience, I was excited for this, and have developed quite a robust but high level view of the infrastructure we need, the Lambda / serverless functions/services we would want to set up, how we would use an API gateway and Cognito with custom claims etc etc etc.

Tomorrow, I go to London to speak with a major cloud company (one of the big ones) to discuss potential approaches & ways to stream the data we require etc.

I love this type of work, however, it is 100% so far above my current job role, and the current level (junior/mid level PHP dev at best) of pay we are given is no where near suitable for what I am doing, and have been doing for all this time, proven, consistent work.

Every conversation I have had with my line manager he tells me how I'm his best employee and how he doesn't want to lose me, and how I am worth the pay rise, (carrot dangling maybe?).

Generally I do believe him, as I too have lived in the culture of this company and there is ALOT of technical debt. Especially so with our Director who has no technical background at all.

Appraisal/review time comes around, I put in a request for a pay rise, along with market rates, lots of details, rates sources from multiple places.

As well that, I also had a job offer, and I rejected it despite it being on a lot more money for the same role as my job description (I rejected due to certain things that didn't sit well with me during the interview).

I used this in my review, and stated I had already rejected it as this is where I want to be, but wanted to use this offer as part of my research for market rates for the role I am employed to do, not the one I am doing.

My pay rise, which was only a small one really (5k, we bring in millions) to bring me in line with what is more suitable for my skills in the job I was employed to do alone.

This was rejected due to a period of sickness, despite, having made up ALL that time without compensation as mentioned.

I'm now unsure what to do, as this was rejected by my director, after my line manager agreed it, before it got to the COO etc.

Even though he sits behind me, sees all the work I put in, creates the arbitrary deadlines that I do work without compensation for, because I was sick, I'm not allowed a pay rise (doctors notes etc supplied).

What would you do in this situation?

React vs Vue? Decision fatigue...

Learn React.

Got Angular and Vue under my belt. Might as well get the trifecta

Fave languages and frameworks, go!

As of now for me, loving these:

PHP8 and Laravel with Livewire*, Django5.1, MariaDB. PHP must stand for PrettyHeckinPCoolasFFFFFFFFFUUUUUUU

*after using React and Vue for quite a while, I've concluded that the best front end is back end. And I like Postgres, I just find that MySQL is fine for most things.

10 years from now:

Doctor: Congratulations!!! It's a boy.
Parents: We'll Call him James.js.

Im a complete back end guy, decided to learn a js framework......

var whatToLearn = rand("angular", "react", " vue");

Suggestions..... :/

I hope I did not make the wrong decision here:
Been working on a side project using React Js for a year now. After getting to know more about Vue, I just started rewriting it and moving it to Vue, to speed things up I'm using core JS classes for network stuff and validations ...etc just rewriting Redux to Vuex and React Components to Vue Templates

If I made the wrong decision I'd appreciate if anyone tell me about it before I go deeper in the rewrite process lol

It is not that I found speed difference both perform the same from what I've seen for my scenarios. But the output code of Vue is soooo much cleaner than what I found in React, either I failed to write a clean react code no matter how hard I try to optimize it, or Vue really takes the short way and keeps things clean.

Is Vue worth learning compared to react and angular? I have absolutely no experience with either one but was looking at Vue earlier and got curious

!rant but question to you experts:

Hey, guys. I'm currently trying to up my game in terms of web development. I already know js, html, php and css quite well (enough to become a tutor at my university) but I'm not shure which frameworks (serverside and clientside) are worth considering. Until now I wrote everything from scratch, which is not very sustainable (waaaay to much code to maintain)
Could you please tell me your softwarestacks, what library to use, which frameworks to learn (Vue/React/Angular/...)? Every opinion is very appreciated and won't go unheard. Thanks in advance.

btw: you guys are the nicest people I ever met online. Thank you for being so awesome.

My fascination for programming began around 13, when i started developing plugins for my minecraft server in java.
Had an awesome time with creating plugins for some fully custom servers with relatively large playerbases(50-200 players, depended on the time of the day).
This sparked something in me, and i started creating crapp ass "portfolio" sites for myself with php and mysql login and registration forms. After that I got into some basic c# abd had fun with some cute console/form applications.
And here comes today, in the process of picking up more css, php, html, js knowledge, probably heading towards react or vue.
I just love programming to death.

I love how the vue in angular reacts!

How the hell am I meant to get a new job in Edinburgh/Glasgow so I can learn React/Angular/Vue when no-one will hire someone without experience in those frameworks?!

I was in 2 roles back to back and in that time, every single Front End Development role now available in the market requires commercial experience in React/Angular/Vue in order to proceed.

Even the 18k Grad/Junior Development roles require commercial experience in some sort of JS Framework yet I'm certainly not a Grad/Junior.

HOW DOES ANYONE USE IT COMMERCIALLY IF THEY'VE GOT NO EXPERIENCE.

I'm doomed.

For the record, I'm a Front End Developer with 3 Years of experience with personal study experience in React.

Which JavaScript library guys are using? React or Vue? Or any other?
Writing React + Redux needs lot of boiler plate code :(

I don't know what to think of Vue 3 Composition API anymore. At first I hated it because it's nothing but one big ole rip off of React, and I hate React so much; its hook system is the most disgusting anti-pattern I've ever seen in the entire JS ecosystem. This gave me the incentive to try out Svelte instead, but after doing so, I look back at Vue 3 and noticed that they're kinda similar... why are so many JS devs allergic to classes? You can have much better written code that way. Idk, I'm waiting for vue-class-component and vue-property-decorator to fully migrate. In the mean time, if I'm gonna be forced to write composition based code, I might as well use Svelte.

So, I'm looking into something and end up on Stack Overflow. Someone posted the question:

"Does minified javascript improve performance?"

This question was old as shit, all they way from 07/25/09, and about an Adobe Air application. (Remember that? Me neither...) It had a great, accepted, and still accurate answer, posted the same day the question was asked. Now, fast forward 8 years and on 12/08/17 (A mere 7 months ago...) the following answer was posted. I don't know what they were thinking, but here it is, complete and unabridged, with my comments in square brackets:

"I'd like to post this as a separate answer as it somewhat contrasts the accepted one: [Somewhat contrasts? More like completely contradicts...]

Yes, it does make a performance difference as it reduces parsing time - and that's often the critical thing. For me, it was even just simply linear in the size and I could get it from 12s to 4s parse time by minifying from 3MB to 1MB. [First off, your parse time should NEVER be THE critical thing, but secondly, and more importantly, WHO THE FUCK HAS 1MB OF MINIFIED JS ON A PAGE!!!]

It's not a big app either, it just has a couple of reasonable dependencies. [THERE IS ABSOFUCKINGLUTELY NOTHING REASONABLE ABOUT ANYTHING HE JUST SAID! What dependancies is he using?! You could use minified and not even gzipped jQuery, AngularJS, Vue, Ember, React, AND Dojo libraries on the SAME PAGE, AND have 118k of application code, AND STILL NOT HAVE HIT 1MB QUITE YET!!!]

So the moral of the story here is: Yes, minifying is important for performance - and not because of bandwidth, but because of parsing. [Javascript should NEVER take longer to parse then to download, even on a low powered device...]"

So, yeah, I'm at a loss for what this guy was thinking, but the thought the people like this exist, and that my browser might one day be subjected to their horrific nightmare of code terrifies me...

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.

NO DEar don't "GO" away. You "C" puns are great. Just "Express" your "Vue" and "React" with ++.

Why isn't Vue.js more popular? (it's not rhetoric, I actually don't know)

During the last weeks I've been learning the basics of the more popular JS frameworks and from the ones I saw, Vue seemed like the best option (lightweight, virtual DOM, simple documentation, alternative to React Native). Nonetheless, React & Angular are more widely used by companies and personal projects. Does anyone know why that is?

Tailwind css offers a premium package where you have to pay $300 for access to their tailwind styling components. And even additional $150 and $150 and $150 packages depending if your app is for ecommerce application ui or marketing etc.

WTF????

While in Angular Google has provided 100% FREE MATERIAL DESIGN UI COMPONENTS

WHO THE FUCK PREFERS TO CODE IN REACT/NEXTJS/VUE over ANGULAR???

guys react or vue ? and why ?

As a vue fan who has to work with react - I don't understand the appeal of the latter. Everything seems just pointlessly dotted with boilerplate, grossly over-engineered (if that's what I should call solutions like the react approach to CSS-in-JS) but at the same time very clunky.

Honestly, the only convincing point for using React that I've heard is about it being backed by Facebook - but, on the other hand, After having to work with some facebook IT solutions and knowing the shit they could pull with their APIs and stuff, I wouldn't count it as too big of an upside.

Why didn't you switch from react to vue?

Nuclear war:

Which is better :
React vs Angular vs Vue vs Marco

Which one you are using ?

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.

!rant

Gotta start learn react. Only two frontends in my company know react and it seems my Vue knowledge don't mean nothing... I'm kind of excited, mainly because for a long time I wanted to make mobile apps and with react native I'll be able to do so.

Since the end of my extended internship is slowly coming forth, I thought I'd (happily) ramble in the Random section for a bit:
*TL,DR: Internship went well, I learnt a lot*

The company I worked at made my experience with Frontend make huge leaps. I used both Vue and React, neither of which I had used before. I also learnt that you could mock things in unit tests instead of simulating full use. Finally, I also improved my experience with Kotlin again.
Both teams I have been in (since there was a switch due to a lot of people taking off days for holidays) told me that I am quite fast at grasping concepts I hadn't even heard of before, which is quite nice :)

Anyway, I wonder what the transition to school is going to be like.

Developing front-ends used to be about translating a business use case to an interface. Now I spend days and weeks getting tooling to integrate properly: webpack, babel, React, Vue, SSR, Nuxt, NPM packages, build & CI pipelines, storybooks, and resolving incompatibilities. It's become such a grind I haven't had a single satisfying, productive workday since 4 months.

Web developers, please recommend a tech stack. I have work experience in Laravel, Angular and Node Express. Personal small experience only for Vue and React.

Frontend: Angular, React or Vue?

Backend: Node Adonis JS or PHP Laravel?

CSS framework: Angular Material(angular), Material-UI, Tailwind CSS or Bootstrap?

This is for a personal project API based. What frontend backend tech stack are you using right now? Thanks!

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.

I remember studying up on web dev by myself, got advanced into php and all frontend stuff js, jquery, css, html. Coz all jobs in the country wanted those exact stuff. I got a job, 1.5 years later tried to look for other jobs, everyone wanted react, angular, vue, node... fucking market outdates u as u are working. Dont u hate that

I always thought wordpress was ok, not great not terrible, from a coding perspective. Now every new framework I have worked on makes me see why Wordpress is on 40% of the internet.

Now I love wordpress not because of what it did do, but because of all the really stupid things it managed to avoid doing including: over abstraction, trend chasing, using "new transformative technology" that disappears in 2 years, breaking plugin economy with updates and making devs start over, making everything OOP for the sake of making everything OOP, making adding on a bit of code take multiple files of multiple formats and boiler plate code, boiler plate code, compiling dependencies, composer, twig, laravel, one page applications, react, angular, vue, javascript only stacks (MEAN), not letting you control sql queries, protected/private scopes and design that doesn't let you fix or alter bad code others did, and the list goes on and on.

Wordpress did a lot right, and devs should try learning from it instead of making more problems to solve. Sure it's not elegant, but you known what it does do? Focus on a solving a problem. Then it does. Without inventing new ideas or concepts to inject into the code and create new problems.

And you know what else? Hooks are actually very well implemented in Wordpress. I've seen it done much worse.

Honestly my main gripe with the entire platform is a slow moving to OOP for no reason and the database design should separate post type into different tables, the current design makes it less scalable for large data sets for multiple reasons so I'd fix that.

Hello guys. A newbie to the app. I would like to ask - start a conversation with you about adopting new technologies, if should we follow or just wait? I am a PHP developer. I would set myself around mid to senior level. Since I graduated and I start working on a Marketing/Development Company, I have been develop a lot of websites, platforms with pure PHP, JavaScript, SQL. Later I start using framework like laravel. Now I am thinking about JS frameworks such as node, vue, react, angular and maybe later noSQL. The problem is that there are many new technologies that companies required when you apply. I want to learn new technologies but I don't know if that would be helpful than focus on LAMP and get better and better to that. Many orgs have implemented their own technologies and each company is getting mad to it. You see each company adapt these new technologies even if they don't want em or projects required it. So my question is: are we talking about dramatically speed and light use to server when we use new frameworks like these, previous mentione + etc? Or companies are just trying to look cool by mentioning many techologies while projects could never ask for em? (Nothing serious, I am just trying to make conversation and clear my thoughts by getting others opinion)

I’m sooo excited when any new frontend JS framework is available. Angular, React, more recently Vue, Svelte. Bring ‘em on. I wanna try them all.

Just kidding…
As long as the tools at hand allow me to get the job done, keep clients and end users happy, I don’t give a fuck.
This meme is actually the epitome of what I hate with a lot of web developers I’ve encountered

When someone asks me how implement React, Redux and a lot of those stuff on their projects I answer:

If you don't have any idea what it is you might not need them.

There are lots of Angular and React jobs here in my area. Very few Vue jobs here (like 1 to 5 maximum job posts I have seen). I'm a PHP dev and it seems most companies are shifting to full stack JS development (MERN, MEAN, NodeJS + Express JS, etc.) along with some mobile development (ionic, cordova, etc)

I have no choice but to study both Angular and React. Supply and demand.

But between Angular and React, I prefer Angular.

The only thing that I think works great in Node.js ecosystem is Socket.io

Otherwise anything JavaScript related is too bad for me. So many frameworks releasing each month. First it was React then people said that vue is better... Now hearing Svelte is the best. This shit is going crazy.

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.

God bless PHP
God bless Excel
God bless Visual Basic
God bless JavaScript
God bless jQuery
God bless Python 2
God bless Perl
God bless Bash

---

God, destroy React
God, destroy Vue
God, destroy Angular
God, destroy Java
God, destroy Next.js
God, destroy Rust
God, destroy Go
God, destroy Kubernetes
God, destroy Docker
God, destroy Flutter

!rant
I got to work on this project written in PHP that is literally unsalvageable so I will need to redo it from scratch, it's an e-commerce/social network mix that allows you to resell your clothes and I will have to work with PHP-only server-side so I was looking for a JS framework that has all these cool features like Angular but does not require node.js and I stumbled upon React and Vue and I can't decide between them. I was wondering if anyone knows both of these frameworks and could help me decide which one to use. (I have almost no knowledge about these frameworks)

PS: The server-side will be PHP with MySQL because that's the only option that the client's hosting offers.

I have a few side project ideas. I started one of them a few months ago (project setup, dependencies, git repo, index page, very basic API and client functionality). But I cannot get myself to work on it or even think about it (for months now). The reason? I do not want to work on the client/frontend! I do not want to deal with React or Vue or Svelte or fuckjs or even jquery. It's a fucking mess.

For the backend, the requests are stateless: you get a request, handle it, and respond back. Need to update state? Database. That's it!
For the frontend, there's just tooo many states I can't keep up with! When the user checks or unchecks this checkbox, I need to maintain the state of the checkbox and maintain the all effects of changing the checkbox while syncing with the backend and making sure the elements are still styled correctly with the applied effects. Multiply that with all the expected interactive elements on the page. It's exhausting!

"is Kotlin worth learning? React or Vue or Angular? Is Flutter worth learning?"

Is devRant a search engine? I can't be the only one tired of these posts. It is also very tilting seeing the responses to a yes being "okay, I will research it".

Bitch, you're supposed to research it from the get go. devRant is not the preliminary to doing a fucking Google search.

I feel it is almost equivalent to asking a coworker before actually googling it (which I admit I sometimes catch myself doing).

I feel I need to write some side project summary somewhere.

So here it is about 3 months later:

- deleted 90% of code I created during last 3 months
- rewrote backed 5 times
- 200 lines POC still waiting to put in any meaningful architecture on frontend
- frontend part after aurelia, next, gatsby, react I think it would be vue powered by nuxtjs
- forced myself to buy food for whole week and don’t go out (except go running ) before I finish at least what I wrote on whiteboard

Now some positive news:

- there is not much left to be fucked up, removed or unnecessary added
- I think I got a plan
- this is probably first side project that makes me happy for such long time
- there is some probability it would help people and this is what I want to do in my life

Most important is that I know it would take at least half a year to do basic version of it and I don’t care.

Wish me luck so I can put some sneak peak after next 3 months.

Hey I have a career dilemma, was wondering if anyone experienced that and if anyone could give a tip on how to resolve it maybe.

TL;DR: I'm a Front End dev, who wants to become an expert in everything but obviously can't. What do I do? How do I choose what to learn?

Longer version. I started with Front End. Now i'm doing alright with Vue, React, bit of Angular, and other related to the stack tech. Then I started learning python because of a project I was doing (personal client). Didn't go far with this one. I still find it interesting esp. in the machine learning context, which I also want to do. Now I'm studying .NET, because of a project I'm currently doing at a company (full time, I'm doing ReactJS front end there tho). And I'm also studying for GCP exam, because I wanna know how to deploy solutions to the cloud. But one also needs to secure them, so I'm looking at some courses on Cybrary, in a search for appropriate courses.

I feel overwhelmed and unproductive. I feel like i need to specialize just in one field with some general knowledge about other areas. So I feel like I have to select what I do/learn carefully.

Any thoughts? How did you plan your career? What kind of goals did and do you set for yourself? Are you happy with those now once you achieve them?

I'd love to hear some stories. :)

Angular? React? Vue? Polymer? ..?
What do you like the most and why?

Wanna start a new project and can't decide, as always

I'm trying to get into Full stack web development, coming from 1.5 years of Android development. During my studies tried out Backbone with Node once and played with Angular, hated it though.

As this is already some time ago, I was wondering which Tech Stack you would consider being

a) Beginner friendly
b) also ready for use in business?

I recently learnt Kotlin and am quite happy with it, I'd like to go deeper on that. Also, the company I'm hoping to work for talked about Drop Wizard, Spring, Vue, Angular and React.

Curious to hear your thoughts, Thank you :)

Here I am at half past midnight with a pencil and a pair of scissors printing grayscale metalsmith js business cards and manually cutting them for the upcoming jsworldconference.

Not pretending it has a chance against the giant amount of sponsoring the likes of Vue and React get, but hey I will have tried!

Today I saw a guy building a website.
No React.
No Vue.
No Ember.
He just sat there.
Writing HTML.
Like a Psychopath.

So I started my frontend framework learning by getting to learn Vue. Now, like, a year later, and after I've got a ton of experience with Vue, having written numerous apps with it and earned some $$$$, I'm learning React. Just because of, yeah, react-native. I feel like a caveman just by writing all that annoying overhead. :/

I've been a front-end developer for 12 years. I've done PHP, Angular 1, React, Vue, etc. I'm considered a lead at my company.

Now a manager has decided that all of the projects except mine are switching to Blazor. He insists that my project won't switch, but I don't trust him.

Am I better off biting the bullet and learning Blazor (a prospect that I'm not exactly thrilled about) or cutting out and looking for a new place where my existing skills will be useful?

React js, Vue js or Angular just ?
Which one you prefer?

Torn between learning vue and react. Which way should I go?

Some companies: asking for a developer, must have 5 years of experience. Must know C#, php and Python. Also expert in html css react angular and vue. Salary: scrubs. Haha good look looking for the ultimate developer senior for €1800 a month :’)

I feel really stressed about everything I want to learn. Everytime I hear someone talk about some new framework or I see people here discuss languages or stuff I don't know anything about, I want to learn it. Right now the list of things I feel I need to learn is so fucking big that I've no idea where to start. Also, I need to focus on my upcoming exams, so I've absolutely no time to learn or do anything. Backend, front-end, iOS, Android, desktop, OS development, everything. So much to learn, so little time.

Vue vs angular4 vs react?

It is amazes how much brain can be wasted with react.
In those 7hours (impressed myself by my bullshit withstanding), it took me 20min to understand a fucking api and how objects relate altogether, 1h to make the tut
and 5+fucking hours to understand how to plug the components.
I did use vue and backbone before and am 5y nodejs user.
seriously react is a bag of shitty magic.
I don't even want to try to read the code source yet, this could be the fatal move...

Oh. and also. people have to stop with jsx, it is so so so wrong. new syntax with new errors just for a fucking syntaxic sugar for saving a pair of parenthesis!!!!
like it matters after having installed 1e2+ MB of dependancies for a SPA of 10 components...

The only thing we miss is a react IDE to support JSX. #wheregoesthefront
And I am not even to the point of data flow and pubsub hells which i will be sure will be gold as well

Alright, I need an advice.

I have legacy Angular client. It’s impossible to refactor it. The only real option is to rewrite everything from scratch, however, while the team does it, it needs to be accessible to our clients.

The approach I am thinking of is making micro-frontends out of original client and rewriting each of them (in React, Vue, don’t know yet.)

Anyone has experience with that? I would appreciate any advice or suggestion.

I already developed with Angular, I thought it was cool. ReactJS, I thought it was good. But I've just discovered Vue with vanilla Javascript and I'm completely in love.

Hello tech community ,

Quick question. I have been learning web development casually over a couple of years. Now,I'm stepping up my game. Playing with big boy libraries like Vue and React. Diving into JavaScript and functional react.

I can make static websites. Even dynamic ones. I know how to deploy websites from my terminal and I have done an ftp once before ,which was weird. But it was a long time ago. OMG my question is how do you transfer over a project to a client? I made a cool site. Added some JavaScript. Maybe it's pulling in some data. Maybe it's static. What is the best course of action? I really want to start a web design/developer side hustle.

Thanks homies.

So react is even outperformed by angular these days.. is there a new trend to follow or are we ignoring this just like we ignored es6 and kept using jquery?

I got my first proper start in programming through a side business operated by the same guy that was running a local makerspace. He had me learn basic git syntax and change some values in ionic.

From there I decided the best way to learn how to do this was write my own project in angular. From there I branched of with React and Vue.

react > vue > angular

Angular Vs React Vs Vue for an e-commerse website?
Please, don't hold back.. :)

React: I'm the best! From FaceBook
Vue: I'm simpler and better! From Community
Angular: I'm the best! From Google

jQuery: LOL kids! I simplify HTML DOM tree traversal and manipulation... I'm immortal.

React, Angular and Vue: You are right jQuery! But the trash can is across the door. Ciao!

Fuck, there‘s this cool tool react-admin. I want to use it as generic CRUD UI for my framework. Basics work already.

But fuck it this fucking react crap a PITA. Who for fuck‘s sake invented that shit? Damn facebook crackheads ..
JSX ... the worst idea ever.

I worked with vue before and then .. easy, just awesome.

But this crap is utterly unproductive, way too complex, ugly syntax, needs an unholy shit if dependencies, let alone the build system ...
Fuck u react fuck u ...

It sucks that you need to transition to other roles.

Started as front-end dev, now I have to write PL/SQL code. Which I don't like and not confident as NodeJS, Vue, React, Angular4, Java, etc.

I'm in a react/vue/angular/polymer-debate. Lets continue this here, but only with the worst arguments you heard about these 4.

I start:
React: "I dont like it, facebook might have a backdoor in the code so they can see what we're developing"
Angular: "We use Google Cloud, angular is developed by google too. There is a synergy between the two"

(If you really need this to be a question, then it's "what are the worst arguments you heard about javascript-frameworks?")

Well I started learning REACT FUCKING JS because of our team requirements. I'm a Vue developer and well it's a little more complicated for me because react is way harder.

Today I started a simple project to practice react. First thing I realized was that in react project we cannot edit Webpack config by just adding a config file in project root.

WTF !

In vue we could just add few lines of codes in vue.config.js and then we were good to go!
but in REACT FUCKING JS we must install another library named Carco, which is not COMPATIBLE with latest react version!!!!!

FFS WHAT THE FUCK IS THIS FRAMEWORK

Anyone else sorta kinda getting tired of jsx? I mean React is definitely really wonderful and all and I was all aboard the jsx train but now having my “markup” and js (sometimes css too) mixed completely together is kinda getting annoying. Sometimes I look at it and think its a mangled mess.

Started looking into Vue and really dig the way they separate the layers at the code level. You can have templates in your html or use the really awesome SPC format. Don’t know a lot about Vue yet but the structuring definitely feels right.

Who the fuck thought that in react useState should return an array and not an object. It makes me wanna make a wrapper that would instead return {current, set} = useSaneState('fuck you') because what the fuck does it have to do with arrays. And an object with shit.current would be consistent with useRef.

Also, vue is just superior in naming and coding standards.

Ah, the merry-go-round of frameworks. Can we settle on one for more than a microsecond?
Switching between React, Vue, Angular – it's like code calisthenics for my brain. Just when I've mastered one, bam, the next shiny framework arrives.

Can't I write code without feeling like I'm auditioning for "Dev's Got Talent"?

I want to write my own JS framework, which is ideal for me and is very opinionated, so that I don't need to stand under the hard choice of React, Angular, and Angular.

I have to build a front-end website.....kinda similar to tripadvisor etc. which framework should I choose? Vue or react? P.s. I have zero experience in both.

It seems to me that browsers lagging behind is the reason we've seen the JS framework boom both in recent years and ongoing, evident in what they regard as major updates. Most of the functionalities implemented in my time working on the front end are high level problems ubiquitous enough to have been solved at the browser level. Same goes for all the optimizations CSR frameworks are struggling to attain. Every CSR app genuinely feels like recreating a browser, both in UX and dev requirements. These problems exist because current browsers are analog software still accustomed to loading all content at once, no in-app state, just scroll states

The React-Vue-Angular wars of today are a direct hat-tip to the Netscape-Microsoft wars of the early years. If they can form a coalition that sets a standard for syntax, best rendering engine, natural way for user facing devs to control app state, fetch data or connect the back end, somehow render this on the server or find a workaround SEO issues on CSRs, etc, given the shared agreement on expectations for modern web software, it'll be fascinating to see such a possibility

It's time for war!
I have two examples doing the same thing. They're bot generated by chatGPT.

React:
import React, { useState } from 'react';

function IncrementalButton() {
// Create state to hold the count value
const [count, setCount] = useState(0);

// Function to handle incrementing the count
const increment = () => {
setCount(count + 1);
};

return (
<div>
<h2>Count: {count}</h2>
<button onClick={increment}>Increment</button>
</div>
);
}

export default IncrementalButton;

VUE:

<template>
<div>
<h2>Count: {{ count }}</h2>
<button @click="increment">Increment</button>
</div>
</template>

<script>
export default {
data() {
return {
count: 0,
};
},
methods: {
increment() {
this.count++;
},
},
};
</script>

<style>
/* Add your CSS styles here if needed */
</style>

Whats better in your opinion?

In most businesses, self-proclaimed full-stack teams are usually more back-end leaning as historically the need to use JS more extensively has imposed itself on back-end-only teams (that used to handle some basic HTML/CSS/JS/bootstrap on the side). This is something I witnessed over the years in 4 projects.

Back-end developers looking for a good JS framework will inevitably land on the triad of Vue, React and Angular, elegant solutions for SPA's. These frameworks are way more permissive than traditional back-end MVC frameworks (Dotnet core, Symfony, Spring boot), meaning it is easy to get something that looks like it's working even when it is not "right" (=idiomatic, unit-testable, maintainable).

They then use components as if they were simple HTML elements injecting the initial state via attributes (props), skip event handling and immediately add state store libraries (Vuex, Redux). They aren't aware that updating a single prop in an object with 1000 keys passed as prop will be nefarious for rendering performance. They also read something about SSR and immediately add Next.js or Nuxt.js, a custom Node express.js proxy and npm install a ton of "ecosystem" modules like webpack loaders that will become abandonware in a year.

After 6 months you get: 3 basic forms with a few fields, regressions, 2MB of JS, missing basic a11y, unmaintainable translation files & business logic scattered across components, an "outdated" stack that logs 20 deprecation notices on npm install, a component library that is hard to unit-test, validate and update, completely vendor-& version locked in and hundreds of thousands of wasted dollars.

I empathize with the back-end devs: JS frameworks should not brand themselves as "simple" or "one-size-fits-all" solutions. They should not treat their audience as if it were fully aware and able to use concepts of composition, immutability, and custom "hooks" paired with the quirks of JS, and especially WHEN they are a good fit.

What JS framework you don't like but you were forced to study it due to job requirements? I like vue but there are only few job postings that require it. Most jobs here are angular and react. I know angular now and currently learning react because of job requirement reasons hehe!😄

You guys sure know Angular/React/Vue, but have you ever heard of Mithril?

I guess it's a good light weight framework compared to Angular, React or Vue.

What do you guys think?

I thought react/Vue/angular was used to build single page web app.

But why the hell are we losing components state when we navigate between routes?

I haven't been developing any web projects for 2-3 years (Since jQuery is the only well known js library). I put my focus on other platforms.

Now I am going to be back again, and there are some angular, vue, and react going on (despite of the other js framework/library #duh).

So, how do I choose between angular, vue, or react? I have no idea.