When each day there is a new framework in the JavaScript world...

Anybody else doing this? 🙃

"New JavaScript framework"

-No one ever

Sus, Sos.... Social?

Is that a new framework? 🤔

4 javascript developers goes to bar aaand we have a new framework.

Hey kid, wanna try this new JS framework?

1) Looking up official Page of the new language/framework
2) Watch tutorial on Youtube
3) Realise it's teached very complicated
4) Buy a course on any course site
5) Realise it's even more complicated
6) Buy book
7) Learn it perfectly
#booksForLive :D

I'm thinking about making a new JS framework. Anyone knows a good JS framework for that?

When i understand a new framework vs trying to learn a new framework

Intel's new CPUs are faster, so your text editor can be based on a slower version of chrome, with a even slower bloated JavaScript framework. Congratulations!

Welll!!!!

As time goes on, I've always wondered what I'm going to say to my future grandchildren about what Dev work was like today:

"Grandpa Josh what was programming like when you were a kid?"

"OH IT WAS AWFUL. ALMOST NOBODY USED VERSION CONTROL CORRECTLY AND NEW JAVASCRIPT FRAMEWORKS WOULD APPEAR EVERY SINGLE DAY!"

"They at least attempted to use new paradigms in their framework code, right grandpa?"

"NO CHILD. THEY WERE EXACTLY THE SAME IN EVERY WAY..."

Dev paradox: When you test your new test framework to see if it can test.

This guy is supposed to be a "spring framework guru"

Yo Mr. Guru, this is not how you write a pom file especially when you are teaching someone who probably is new to programming. Just think if the new guy/girl goes on to write such xml files in the future. What are you even trying to do man.

As a Java developer, reasons to kill other programmers:

- static mutable variables
- WRITING to static mutable variables
- API call with Framework X didn't work. Add Framework Y along with X and try that. Wrap X in try/catch statement. Catch block fires framework Y.
- six, seven, ten levels of nested code. Zero thought put in organization
- 6K LOC Java files
- spring (singleton? Maybe) object assigning values in static mutable (see pt.1)
- a couple of unit tests in code base that no longer work. Zero unit tests in new code
- unit testing disabled in CI pipeline
- empty catch blocks
- pass mutable data between threads. Modify in various places concurrently.

Me, trying to create a new javascript framework

when a new js framework released

Recruiter: “can you write your own framework?”

Me, after considering for a good minute: “well, I am kinda starting to automate lots of things so I guess if I wanted I may be able to... for sure I’d learn a lot along the way...”

Recruiter: “very good!”

Me:”wait, why would you want that skill?”

Recruiter: “our customers want custom code”

Me:”so you write a new framework every time?”

Recruiter: “ah you have also experience in [x]!”

Some people scare me 😟

When you just started learning a new web framework (in my case, ASP.NET Core)

When something doesn't work..create new framework :)

Trying out a new framework be like

Told the new hire that for the first week they can just familiarise themselves with the JS framework, do the tutorials, and read through the code / docs.

Boss comes by Tuesday morning "you should be finished with all the tutorials by the end of the day"

Looks like we're throwing him in the deep end!

Context: new dev has Java and 3d games background. Our app is full stack JS

I have a ritual. Every weekend I try a new technology (language, framework, etc.). It is great!

AngularJS is dead. React is dead. Vue.js is dead. I guess you got to switch to the new awesome framework called Vanilla JS!

I think all the JS framework stickers should be the same size and shape... that way each year when you switch you can just cover up the old sticker with the new one :)

Dear YouTube tutorial makers, if you list your video as a tutorial doing something only to make people download a library of framework and then teach us how to use the library you can go fuck a cactus :-3

Every single video that interests me like building interpreters, new 2D game methods and the like all have no actual ground up programming at all... Ugh!

From 'Javascript' then 'jquery' 😬 then 'angular 1' 😐..wait their is 'angular 2' damn this just a new framework compared to angular 1.(back-end) 'Nodejs' 😩, wait! you have to learn 'Express' after sometime upgrade to 'Hapi' wait now am on 'loopback' can't we just have one standard framework 😣😣😣

finished learning a framework/plugin.. *feel like boss* 😎

bam! new version with breaking changes.. *feel like sobbing* 😭

How Google loost its data Monopoly-

Present:
Step 1- US bans Huawei

Step 2- Google Bans Huawei

Step 3- China Gov helps Huawei get back on its feet

Future:
Step 4- Huawei makes their own OS to rival Google, the OS can run Android apps as well as IoS apps and has its own language/framework for developing new apps

Step 5- China bans Google from their market

Step 6- Chinese mobile manufacturers adopt the new OS

Step 7- China's population starts using the new OS i.e. country with the world's largest population starts using the new OS

Step 8- Chinese manufacturers like Xiaomi, Vivo, Oppo and OnePlus who already own approx 40% of India's smartphone market start distributing the new OS based phones in India. Factors like cheaper devices take this market share to 50%+

Step 9- Cry, cause the new OS is now being used by approximately 30% of the world's population.

Yeah, bring your hate in the comments but come back and talk to me in August 2022...

Spent 2-3 weeks on implementing a new feature, a guy with 10 years of experience jumps in and solves it within 5 days.

*Oh! I forgot to mention, it was his first time working with the framework.

I must say his OOP skills are really good, not sure if this is something you learn by reading books or simply by practice.

I strongly believe that if you have a good understanding of how to build apps with OOP pattern, you'll do a great job in the SW industry.

New JS framework

(IT AIN'T EVEN 4 WORDS)

*Looks up advice on how to implement something
*Finds reasonable, well written advice on Stack Overflow that recommends not using <insert latest framework here>
*Ignores advice
*Two hours of exasperated coding and git resets later
*Goes back and upvotes advice

I wonder why there is a new JavaScript framework every 10 minutes. Could the issue be with the JS language itself?

Naaaaaaaah .... Impossible .....

So I just finished my first 40 hour work week.
And just an hour ago I had a meeting.

In that meeting I said pretty much this:
"Your old system is rubbish, I want to make a new one"
"Also we can't use the old framework"
"Also it needs to be in a different language that nobody knows here"

And they went for it!

At this point I think I can sell anything to anyone.

When you have to learn a new language so you can learn a framework so you can learn to integrate with an app you about to learn how to make.

Welcoming ReactXP from Microsoft
Because JavaScript needs a new framework 😒

They:Why didn't you come up with this solution 2 years ago?

Me: The framework on which the new solution is proposed DID NOT exist 2 years ago.

This industry is fun!

So processors have Moores Law, I'm starting to think Web Development has one too.

"There shalt always be a new, better, framework, that would have saved weeks of time, but only after you've hit the point of no return in a project"

Anyone else know the feeling of "damn...I may as well just rewrite everything...."

Freelance client fired me on Friday, with literally a couple of minor issues to take care of left before launch. When I inquired, he said they're going in a different direction. I immediately smelled bullshit. When I asked who to turn over the files and DB to, it was their idea to allow me to broker the deal to switch things over and hand the keys over. I asked the new dev what framework or installed CMS and he thought I was crazy for asking. He told me they're taking by build of the site and finishing it. That's fucking low.

Fucking idiot lead dev who’s 10 years younger then me doesnt know fucking respect. Dumbass comes with every new framework there is:
- ow we should try abc.js
One week later
- now we should totally get in def.js. It’s soooo much better then abc.js!

Screwing up projects, asking for an extra pair of eyes and then asking wtf is this code.

Im out of here if we’re hiring toddlers for lead developers because they are willing to work 50 hours a week. I better get that raise soon.

Why is it that pretty much zero package & framework maintainers understand semantic versioning?

1. If you do a complete rewrite of your package, but the resulting API is identical, you don't need to bump to the next major version. As a user, I'm thankful for your increased performance or cleaner internal code, but it doesn't really affect my update process.

2. If your package required some-framework 6.0.0, and now ALSO supports some-framework 7.0.0 but is still compatible with 6.0.0, you don't need to bump to the next major version. As a user, I can now upgrade the framework, and know that the package will keep working, but otherwise it doesn't really affect me.

3. Following your versioning along with the framework/language version is super annoying, especially if your library really doesn't need to differentiate between framework versions because it's not actually utilizing new framework functionality.

4. On the other hand, if you stop supporting a certain language, framework or shared library version, or change the public methods, exceptions, fields, etc, you MUST bump to a new major version.

Yet everyone gets this wrong.

For example, many of Laravel's underlying subpackages (for collections, filesystem, database, config, http, mail, etc) do not change their code in a breaking way, or do not even change at all between major framework versions.

Yet they follow along with the major framework version.

Now if someone makes a library "laravel-elasticsearch" which uses the support libraries and collections from laravel, they need to update their package to move along with the versions as well, and often they choose to number their library along with the framework in turn.

This means that to update the framework, you also need to update over 9000 dependencies.

FOR NO FUCKING REASON. THE ONLY CHANGE IN THOSE FUCKING DEPENDENCIES IS TO UPDATE COMPOSER.JSON TO BE COMPATIBLE WITH THE FUCKING FRAMEWORK.

Meanwhile, Laravel itself breaks repeatedly on minor/patch version updates, because breaking changes slip through their review process.

Ugh.

Before I left for vacation two weeks ago, I busted my butt to build out another portion of my frontend testing framework and get it in place (and spec’d) to unblock a coworker on a semi-high-priority ticket. I sent him detailed notes on which areas of the product it covers, how to use it, and copied one of his (blocked) tests over and updated it to use the new methods, pattern, namespacing, etc.

I came back today and discovered … he hasn’t even touched it. Everything is exactly as I left it.

Wheeeeeee.

My Task: Create a new application in a custom C#-Framework, to replace screens from the old application.
Me:Fine.
The old application has a Java Frontend.
Me:Fine.
The old application has an Oracle-DB.
Me:Fine.
The old application has its logic fully on the DB.
Me:What ??
You cannot connect to the DB via ODBC.
Me:But why ???
You cannot use external libraries, just our framework.
Me: For what are you thinking i can use to call the functions on the DB
You have to use a custom connection-bus which uses JDBC
Me:Fine.
This connection-bus cannot call SQL Statements and return the result.
Me:WTF, how should i get the data out of the Database ?
We don't know find a way.
Me:Ahh fuck off.

Hello New Spring Framework project.

Yes please migrate to a new framework in the middle of a project mmh yes punish me more.

Today I learned that the my new teams choice to use a mostly undocumented/unused framework over a well known/documented one was decided by a coin toss.

Updated a website for an older client today. Realized I originally wrote their website in 2002.

That web site is a fucking non-responsive piece of shit... but it is still running normally after 18 years.

Just HTML/CSS and some light JS/PHP for form processing. It's not fancy but it still performs and works perfect on Desktop and OK on mobile. Mobile devices which DID NOT EXIST when I wrote it.

Let this be a lesson to the entire new class of developers who seems to think you need some framework to develop. You don't. And I GUARANTEE if that site used any framework that framework would have been retired or updated to un-useability 10 years ago.

Meanwhile my LAMP ass "web native" shit spaghetti with ZERO DEPENDENCIES is still just chugging the fuck along.

My plan to become rich:

1. Create a library / framework that's really just an easy wrapper for other libraries.

2. Write a bunch of books / courses online teaching this "new" library

3. Market it to overpowered but impressionable PM's who'd fall for anything with the word "inovative" in it

How to Kidnap a Web Developer!
Kidnapper: follow me. I have a new web framework

TL;DR, I do node.js now.

__________________

There's much I was working on the past weeks. First of all some of you may know I don't work in IT and therefore always am learning how to make things easier in my workspace with tech. And my boss once told me how annoyed he is converting stuff to PDF for easier sending via mail.

Then I started to build PDF converter with
PHP and the Laravel framework. My first steps into it succeeded and I could even deploy my Pdf-wizard website, but everything feels like a hustle and making this application bigger don't really seems like a enjoyable task for me.

I tried the same stuff with Node.js then. It was damn good. It was simple, because there are plenty of packages wich do this tasks on NPM. Afterwards I spent some time on doing research and ended up learning Express Framework.

This brought new inspiration to me and I wanted to share this with you guys.

how to learn web development in 2018:

- watch youtube video of that new shiny promising framework

- spend hours trying to set up development environment

- spend another hours waiting for the dependencies to install

- spend the next few hours wondering and googling why it wont work even at fresh install

- spend another few hours redoing everything just to make sure you haven't missed a step

- realize that the youtube video you watched is uploaded last week, and now the framework developers mysteriously decided to change literally everything

- spend hours looking for another youtube video until you realize that now you are watching completely unrelated youtube video

- spend next hours wondering how your life become this pathetic while overthinking all of your past mistakes, and now you are just this lonely pathetic person with no clear future and that you will spend the rest of your life working at a fastfood chain below the minimum wage with no social life living on your parent's basement.

Can we please stop using a file structure (YAML, JSON, XML etc) and just changing the file extension and calling it a new file type?

Stop trying to make your software/framework sound more complicated by saying this shit, if you use something, own it and don't try to mask it...

And mini rant over...

Dear JavaScript devs,

Can you please stop with using new Framework(); everywhere?

Sincerely,
A PHP dev

Introducing No.js! A revolutionary new framework. Just build your templates and then... Stop. No worrying about browser compatibility. Web dev has never been so simple.

A word of advice to framework authors:
If I am currently using v2.5.5 of a library, and I update to 2.8.6, I would expect to maybe have to update a few deprecated method calls here and there.
I do not expect the entire API to be completely different, with half the classes totally renamed and restructured. Breaking changes should go into a new major version plz

Everyone and their mother has a JavaScript framework and the NEWEST cool npm module you're an idiot for not using.

It's like musicians and gear acquisition syndrome, coders love to have new stuff even if it's over-engineered, already exists, or redundant.

Hate dealing with tech hipsters 🙄 is nothing tried and true anymore?

Everyday, I'm praying that no new yet another framework will come out and trend.

Instantly thought about new js framework name

Had to integrate legacy code into the new framework.

Me: Where does the virtual sensor come from?
Colleague: It's in the docs.
Me: That step is not in the docs.
Colleague: It is, look into the file $FILE.
Me: Yeah, it's empty :D
Colleague: Nope, it's not.
Me: See, empty (pointing to laptop screen)
Colleague: Why is it empty? (keyboard typing...) Damnit, too many git remotes in my repo :D

I quit my previous job to relax. Then current job came out of nowhere.
How? I just added a new framework I tried to my resume.
Best decision made so far.

Trying to integrate old code into a brand new framework... Oh, the pain.

Like restaurants in New York, you can learn a new Javascript framework every month for 15 years and never learn the same framework twice

OH MY FUCKING GOD!!!

IT FUCKING WORKS!!!

I tried so long on getting my new Netty based webserver up and running, I think I grew my beard twice... But NOW ITS WORKING!

Need to delete a few unnecessary functions that I needed with the old web server, implement SSL. And I can finally release a version of my framework ❤️❤️❤️

And I might put up one standalone version because - it's the same freaking server every time so I am fucking loving to export it ❤️❤️

Spending all weekend on research and testing for a new feature, finding the perfect framework for it, going trough the API just to come Monday to work and get told by Project Lead: we can't use it, it is not in our stack.

How can it be in our stack!? We've never done anything like that before!

Every new framework be like: 'We are new and better and faster and better. Change quickly cause we are the future.'

Me: But whyyy are you better? 🤔😫

thinking of creating a new js framework 😎

What did you say ? There is a new Javascript MVC framework ?
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvv

Everytime I try to learn a new language/framework I google "fuck <language> reddit", "why <framework> sucks reddit", etc...

I love Flutter. So simple. Such good docs. Not totally shit multiplatform. Flutter is my new favorite framework. Good job Google

Switch your tech stack or programming language or development framework to something that you enjoy more.
If it requires to switch the company, do it!
If it requires to learn something new and you think that you don‘t want to, then it‘s probably the wrong goal.

When it's midnight and all you can think about is whether to deploy a personal project in a language/framework you know well or to take advantage and learn something new...

My favorite method to study a new tech or framework is to make a little research and try to write an article.

Nobody:

Overexcited new devs: JavaScript framework 178946252 is so awesome dude

😒

Daily activity, just try new nodejs rest api framework fastify, anyone already using it ?

Build an app in a new Javascript framework within a month

Imagine if libraries and framework you were using started making chabgelogs like the one they make in the mobiles apps.

*We've made some new features and some buh fixes 💫*

If I made £1 for every new JavaScript framework that came out, i would never need to work again.

When I "just" have a quick look at this new framework...

What do you do when you loose your Frontend Dev Job?
a) Get a new Job.
b) Invent a JS Framework

Management has been promising we'd leave .NET framework for 2 years now. Never fucking happens. A new ASP.NET project was just started last week and yup, OF COURSE, its .NET Framework 4.8.

I'd even be happy with one of the earlier .NET Core versions at this point for fucks sake. I have no clue why tech leads are so happy to create a brand new project on a deprecated framework version.

And yes, I have checked thoroughly. Our whole infrastructure works with .NET Core onward. People are just too lazy to learn new stuff.

Stuff like switching to .NET 6, actually doing unit testing, improving our CI/CD pipeline, refactoring problematic codebases, etc. -> all this stuff is the kind of things they promise me I can work on later whenever I'm so bogged down with work that I'm looking for a light at the end of the tunnel. All empty promises.

Ideally we should be on .NET 6 since its LTS and just stay on the LTS versions as the year goes on.

If you are writing a new javascript framework, remember. No NEW JS Framework 2018. Thank You.

Last year I planned to start a startup. I've started many good things but not the startup yet.

* A new data format
* A new data type
* A new web framework
* A new concept for logging
* And many other opensource tools and libraries

the real truth is that web dev has been running around in circles on itself for over a decade now

"but every framework is 'new' and 'shiny'!!!!"

nah, just more sugar on the same exact concepts that have been around since day 1

Not planning ahead, just start at some point, adding just a tiny little feature after another, and then wondering why your to do app (just to check out a new framework or language) suddenly comes with Blockchain, a chatbot and a machine learning algorithm that (slowly) learns when the best time to show random cat videos is...

Just got rejected for an internship because of my architecture pattern. Learnt an entirely new framework and deployed an API in a week. Sigh

Edit:
Was at a college level. Not completed my bachelor's yet.

My new favorite web framework

(Loom ≈ Web frame in German)

Yay! My first bash project :D
disclaimer - my bash is not pretty. yet.

Why I created it?
I encountered several footlong scripts in a new project at work. And they had no logging. And I am in charge of making it sing again. So here it is a tiny logging framework.

I am always excited when I see new JavaScript framework. Not in positive way, but still excited.

Why? Because I have so much to choose from. And I love half finished projects.

Today I don't have much of work. Should I :
1. Start reading about Machine Learning
2. Read and understand Rust( is it being used actively and does it have scope? )
3. Check out some new imnew-tryme.js framework.
4. Crib about my ex dating someone else.

First Post since... Long I guess?

I got a new project!! I am currently creating a Webserver Framework in Java. I can create fully functional websites with a few lines of JSON.
(Look below)

Currently I don't have direct Javascript support, but I am working on installable modules. With those the Web-Admin can code little code fragments that can be shown (live) on the webpage.

I am so hyped because it does work <3

(Pictures of development might follow)

(Can I even call it framework? Hm dunno.. )

Had a new co-worker I was responsible for training. I am several years his junior, but he is working with a new language/framework I'm fluent in. Day 4 into training, he walks into my cubicle, sidles up next to me, I look up at him, he farts loudly, then (without seeming to realize what he's done) he proceeds to launch into a long-winded question about coding best practices.

If this were an isolated incident, I'd have written it off, but the dude did it again when he came to my desk and asked me to open a jar of pickles for him, and many times over during casual conversation.

The wonderful feeling when i need to implement new functionality but it only takes a few minutes bc I actually created a framework that I can reuse instead of writing duct tape code from scratch 😎😊😆😙

Using a new framework without reading the API.

That's it. I'm inventing a new position :

"Dev support".

Why do people ask me "Hey, visual studio has a pop up saying I'm missing a .net4.6 framework. What should I do ?"

Or "Hey powershell says script execution is disabled, what should I do ?"

Google motherfucker, do you use it ?!

Everyone I work with: If we use <framework> then we can solve <insert complex low level issue>.
Me: That is great but what is the actual solution design?
Evwryone: We use <framework> to solve <issue>.
Me: Yeah I get that.... But how? What is the plan? The architecture of this new system to support <framework> and are there issues that get created?
Everyone: If we use <framework> we won't have the issue we are talking about.

Its hard for a developer. Started to learn a new framework or CMS. By the time one gets familiar and fluent, a new and better one is already out.

You wrote a little simple and clean mvc framework to work faster on some new projects. It can "compile" tags as {% var %} or {% array.key %} in the html code with support of {% for arrayOfHash in hash %} foreach construct and nice features, it can call api's callback in a smart way as ghost methods of a class, he can make routes with the route provider. You tested it and made a little example, after you went in the bathroom you read the index code and you started staring at the beauty and elegance of it. You go to bed happy and sleep. The day after you wake up and realize that it's unuseful because there's a lot of mvc framework that surely are better and ready to use, so you lost useful time. Have you ever feel this way? MVC: Me Versus Creativity.

What you could have:
- simple project structure
- common lib with modular logic
- import logic as needed in you services

What you do:
- waste months to write an opinionated framework that works only if used in a super specific way
- have a fat sample project as example
- use a code generator to copy and rename the said sample project whenever you create a new service
- have everything break whenever something new is added in the framework
- oh and keep the framework in active development while others work on the client services, so lots of things will break often and out of nowhere

Fucking god, i hate when people make pet projects out of work projects

Haha, today I learnt that agile doesn't just stop in the enterprise with SAFe (Scaled Agile Framework), management has continued the theme in my new company with Lean-Agile Center of Excellence (LACE) and Agile Release Trains (ARTs).

Software development in 2021...

Just the fact that you wrote your simple single page "contact us" website in React shows that you have no idea what you're doing, nor do you have any idea what the actual benefits of React are and in what situations it actually shines. You're just jumping on the React bandwagon for the sake of saying "I wrote it in React," and your decision to use React for that simple website is going to effectively increase It's development time without adding any additional benefits.

Each framework has its advantages and disadvantages. It's worth it to pay attention to these advantages/disadvantage, and choose the best framework to fit your needs. Don't just use a particular framework because it's the hot new craze. Use a framework because it's the right choice from a technical standpoint, and presents you with advantages that fit your application needs.

When you work with other developers who would, for any feature, small or large, plop in a new library or framework of which they will utilize 1% of... I'm talking about things that we could develop in house in less than a day and have significantly less code bloat... and when you tell them this they smile, nod, and say yeah gotchu, and continue on... AND YOU HAVE TO MAINTAIN THE DAMN THING.

Started a new job as a senior dev but with a framework I've never worked with and I just feel like I'm slow AF and just not qualified for the job. I'm sure it doesn't help that I'm greiving my dog that passed last Tuesday.

Just started learning gnuplot yesterday. Sure, it's not the shiniest of tools, but I'd heard enough about its performance to give it a go.

It's like learning vim. You Google thrice to write a single functional line. You spend hours trying to find a single command for a single task.

But. GODDAMN. This thing's the fastest plotting framework I've ever dealt with. I love Matplotlib, but as great as its plots are, when I need to plot shit up in half a second, I've found a new friend.

Also, tutorial suggestions appreciated.

Recently I tried implementing a 2d grid you could drag (for performance I decided it would auto genetate new grid tiles)

Gotta say, I have a lot more respect for people who try to build this without a framework, I am building it using JavaScript and pixi.js

But man, drawing graphics is hard 😅

It's worth it though, performance is mad 💪

When a new JS framework comes out

How is coupling backend + frontend as a single nextjs app a good idea? What the fuck is this?

What if you have to create new replica sets of a backend because of high load pressure? What about load balancers?? What if i want my backend to be a microservice? How do i unit test the backend if its cluttered with frontend? WTF IS THIS

WHY DID NEXTJS THINK THIS IS A GOOD IDEA AND WHY DO SO MANY DEVS LOVE THIS IDEA AND GLORIFY NEXTJS?

Nextjs seems like the type of framework that was built by a frontend web developer who just refuses to learn backend technology at all costs.

---

its been a few hours and the concept of nextjs is bending my mind rn. I thought nextjs is just another frontend framework. A react killer. Only to find out its both a backend + frontend framework.

Cluttering backend stuff into frontend is gonna get messy no matter how much you try to modularize the code. Am i lost or am i right???

---

Scratching my head over nextjs. Looks like a great framework for small-mid project but definitely not large project. The more shit the project needs the more messy shit become. Angular has modularized all of this in separate folders -- components services guards interceptors (now new stuff coming called Signals) etc. All of it is separated in individual folders and kept frontend-only. Simple enough. No backend clutter

---

Can i even use nextjs strictly as a frontend framework while it uses my custom backend built in java spring boot? For example use nextjs /api/ folder to handle custom routes built outside of nextjs framework?

Am i insane here

> Wants to learn something new (pref not JavaScript)
> Can't find anything that's as dope as Spring boot (java framework).
> C# sucks
> Python ain't going anywhere
> PHP is dated
> Go sounds like a good choice but so damn non-useful if you don't do ultra concurrent stuff at google

Ends up getting more used to JavaScript
Suggestions? For summer learning... Freshman year.

Every new front end framework these days, i remember the time when I used bootstrap through cdn link... Yup those were the good old days

The thing that I most hate is when you're approaching a new framework/tool, you follow the official documentation and the first example doesn't work.
I'm trying the official documentation of webpack, I tried the first example and guess! Error! It says that's probably a breaking change. Where the hell should I learn it? I don't have the crystal ball, should I guess how your fucking tool fucking works? Oh my god, it's ok if you introduced breaking changes, but just update all the references, is it so hard?

FUCK.
NEXTJS.

...

THIS PIECE OF FUCKING SHIT WORKED 4 DAYS AGO.

I CHANGED ***NOTHING***.

4 DAYS LATER I START THE PROJECT AGAIN AND HALF THE STUFF BREAK. NOTHING FUCKING WORKS!!!!!!!

SOMETIMES IT WORKS SOMETIMES IT BREAKS

MESSAGES GET SENT SUCCESSFULLY 2-3 TIMES IN A ROW AND THEN Random 401 error

Random page glitch flickering when routing to new pages rendering the content blank

Random list map iteration crashes on ui dev side

This is such a fucking SHIT

Now i started my angular and spring boot exact same project that i stopped worjing on since october 2023 AND EVERYTHING WORKS FINE WITHOUT ANY RANDOM ERRORS

RANDOM ERRORS ONLY HAPPEN FOR NEXTJS FUCKSHIT FUCKING FRAMEWORK

FUCKIEST DOGSHIT GORILLACUM MAD FUCKIJNNGG RETARD FRAMEWORK FOR AUTISTICS I WASTED SO MUCH TIME LEARNING THIS PIECE OF FUCKING GARBAGE!!!!!!!!!

[Last year me]: Dammit, javascript is the worst language ever! Where are my var types? Why are there so many frameworks? Why the people are using it? Why? Why?

[Today me after updating my Linkedin profile with my javascript experience and receiving some good job offers almost instantly]: Oh good Lord, thank you for giving Mr. Eich the wisdom to create such a beautiful language, I'll build a new framework as a sacrifice to show my gratitute.

I want to learn a new programming language. What should I learn? I am torn between Kotling, Go and Scala.
Or should I just learn a new JS framework? ;)

*sees a new tech/framework/language*

*dives straights to download just checking for windows/mac/linux*

*downloaded product doesn't start/gives error/complains because some prerequisites are not met*

*after some frustration it starts to work*

*To not offend the Gods, writes "Hello World"*

*Carry a "Hackerman" face all day*

*Updates resume*

that feel when I am the only one in team who knows at least one framework.. and coworkers refuse to learn and instead copy and paste code parts from old, insecure apps into new apps... 😐

So I recently started a new job and there's a boot camp as part of the on boarding process. I'm new to scala, I have python and golang backend experience.

During the scala session, the CTO shows us some examples and gives us an exercise to create a Todo REST API with user authentication, then goes to a meeting.

He was using a library called "bacon" in one of his examples, so we were busy struggling to get shit to work and googling "how to do x with scala bacon lib" with no results and we finally gave up.

CTO comes back 30 minutes later and wants to see to how far we got, so we ask him about this bacon lib only to find out that it's their own awesome framework. &$!#%

I was given 6 whole months to rewrite some old monolithic web app exactly 5 months ago today. Now I have to show my boss the progress I've made. How do I explain him that I wasted my time in this order:
1.- heavy procrastination
2.- try new frameworks to work with, pick one, start writing the app, regret and start over again using a different framework.
3.- devrant
4.- existencial crisis and self doubt.

Now all I have are a bunch of incomplete buggy modules and a mental breakdown.

I can't remember the last time I had THIS MUCH FUN developing an Android app! 😳 Have a paper due, but learning RN is actually making this pet project a huge distraction! 😳 This is a whole new world of mobile development 😆, but what if another framework takes it's place 😵. But there's still people who know Angular, and that's widely used...right 😓 and moble dev has never been this easy, so maybe it'll stick around like Node...

who cares... I'M FUCKING LOVING React Native now!!! 😆

I spent most of a day a few weeks ago tracking down and fixing a NaN bug in a framework I use. I hacked it into my local copy of the framework's code.

Today I have the same bug, and after several hours of searching I finally realize I'd updated to a new version of said framework and so had overwritten my fix....

FML

Hi Everybody,
Here by I introduce you the new Java Script framework and package manager that is going to change your life forever. We have considered all the problems developers are facing during their everyday career. We use latest techniques used in configuration files (xml, yaml, json, etc.), package managers (npm, gulp, yawn, etc) and other frameworks (require-js, vuejs, reactjs, etc) into consideration to bring you a framework that has them all together in ONE BIG PACKAGE! HAHAHAHAAHAAA!
Nope. I'm just kidding :-D

Finished my first PC build! Feels good to actually finish a new years resolution lol now I just need to finish my sass framework and get through that udemy python course

Idk why but it feels like lately i've such a pessimist approach to any new-tech (barring languages)
Any new framework or wrapper or CI/CD handler and without even seeing beyond description my instinct goes "fuccccccccck this, I hate it, it'll break things"

I wonder if theres a way to fix this mindset T__T or am I just getting old idkkk

The more I investigate mobile development the more it becomes apparent to me that modern development is a *massive* pile of technical debt thats going to burst, crash, and burn one day, along with the entire industry.

If it takes a newbie more than ten minutes in your framework to add a fucking *button* and navigate to a new screen, then your framework is shit.

* Start maintaining/upgrading new project at work
* Read book on best practices for the framework
* quickly realise all the "don't do this" parts of the examples in the book is EXACTLY how everything in the project is done
* cry self to sleep

F*ck JavaFX. I mean, how a GUI framework doesn't have a standart navigation procedure? It is not even possible to create a page by constructor. In many other framework when I wanted to pass a data to a page, I just had to write
"new MyPage(SomeClass someObject)"
but in javafx I have to first create a constructor, link the fxml file to it then show the page.
Actually I am not angry. It is a big mistake to wait a good GUI framework from a company that has a website something like that in 2018.

I'm finishing up the most depressing client engagement ever. Ultimately it all traces back to their worthless Expert Beginner EA who thinks he's a genius but can't write code. I don't mean that he's not great at it. It's some of the worst I've ever seen by a person in his position.

In the time I have left here I could do so much to help them clean this stuff up so that future developers could ramp up more easily and there wouldn't be tons of duplicate code.

But I've just given up. You can't help someone who thinks their code is perfect. I don't even bother suggesting stuff any more (like don't have two methods in a class - a "real" one and one for unit testing) because he gets mad or just says that's his "pattern."

If I have a useful improvement, first he'll want me to put all new code in some new library, which is fine as an end result but you don't start with putting single-use code in a library separate from where you're using it. You work with it for a while to see what's useful, what's not, and make changes. But, you see, he just loves making more libraries and calling them "frameworks."

He tells me what he wants me to name classes, and they have nothing to do with what the classes do. When you haven't done any development yet you don't even know what classes you're going to create. You start with something but you refactor and rename. It takes a special breed of stupid to think that you start with a name.

I've even caught the dude taking classes I've committed and copying and pasting them into their own library - a library with one class.

The last time we had to figure out how to do something new I told everyone up front: Don't waste time trying to figure out how you want to solve the problem. Just ask the EA what he wants you to do. Because whatever you come up with, he's going to reject it and come up with something stupid that revolves around adding stuff to his genius framework. And whatever he says you're going to do. So just skip to that.

So that's the environment. We don't write software to meet requirements. We write it to add to the framework so that the EA can turn around and say how useful the framework is.

Except it's not. The overhead for new developers to learn how to navigate his copy-pasted code, tons of inheritance, dead methods, meaningless names, and useless wrappers around existing libraries is massive. Whatever you need to do you could do in a few hours without his framework. Or you can spend literally a month modifying his framework to do the same thing. And half the time his code collapses so that dozens of applications built on his framework go down at once.

I get frameworks. They can be useful, but only if they serve your needs, not the other way around.

I've spent months disciplining myself not to solve problems and not to use my skills.

Good luck to those of you who actually work there. I am deeply sad for the visa worker I'm handing this off to. He's a nice guy and smart. If he was stupid then he wouldn't mind dragging this anchor behind him like an ox pulling a plow. Knowing the difference just makes it harder.

Alright let's get real and finish this module
* 5 mins later *
Ooh look, a new js framework. I wonder what does this do hmm..

So when we started this project like 4 years ago... new to the framework, kickstarting lot's of forms with file uploads. Everything seemed to work fine, uploads and downloads worked..
First version of the project got deployed to prod and for weeks or so users have been registering and submitting stuff...

Only problem was: most files were overridden by consecutive uploads as our central upload lib stored files with the same name on disk (normally the ID of the db row was injected but most files were saved before the db row was - resulting in 0 IDs...)
Yeah so... that hurt :(

I wish we’d stop coming up with “the new best js framework out there” every fucking quarter of the year

So this company called me for an internship interview. They told me to learn a new framework and develop an entire system with it within a week so as to get a chance for the internship. Jokes on you. I ain't coming back you SHITHOLES.

When you’re struggling, learning some new framework or concept and your friends still think the entire internet is made solely with html and css because they took desktop publishing in 9th grade.

"Let's make a new Javascript framework"

That feeling when you're almost done with your personal project using an entirely new language and framework :)) been working on it for the last 2 weeks. 62 commits in!!

When your boss ask to convert the system to the new framework version, but still ask the other team add new module. Then said why your work never done hmmm.

When your legacy retarded old as fuck frameworks are slowly dying and instead of migrating to new backend framework, losing some money but improving quality of our products dipshits in charge hire vue.js developer to try to replace jquery with vue just to keep this 10 years old legacy zombie crap alive for 2 more years..

How can you be this fucking retarded greedy motherfucking morons... it shouldnt even be possible

- And also today I completed my to-do list
- Did you carry all the tasks out?
- No, just a new JS framework

What does Linux and web development have in common. New distros and framework popping up everyday.
What is wrong with people, creating distros and web framework for dumb reason. When they can contribute to to existing distro/framework to make it better.

Starting a new job on Thursday after 2 years as software engineer at a different company. I feel like a know no transferable (language) skills; I was mostly "the expert" of the framework at the previous company and now feel like I'm starting from scratch.
How do you handle starting a new position? Do you prepare yourself or just go and see? Am I overthinking?

JEZUZ CHRIST FOR GODS SAKE MOFO FRAMEWORK DEVELOPERS ... if you've built an awesome framework once, you have ONLY ONE JOB: maintain it - keep it up to date with fucking browser changes and fix security holes. Changing the core concepts every major is not part of this. If you got visions, start a new one ffs, become a mofo prophet one OR BURN IN HELL POWERED BY THE REMAINS OF YOUR ANCESTORS FFS!

!rant.

I must say I love learning new things!!! Took a quick detour to build a small custom music player, now it doesn't seem to be that quick as I am learning a new framework. Only about 11 pages of many more still to go, and the funny thing? The main part I need - how to play audio, is in the last section of the tutorials.

Googling for Angular (>=2) documentation and finding AngularJS instead feels like cancer.

If Google was going to "update" to what is functionally a new framework, they should've named it differently instead of trying to piggyback on the popularity of AngularJS. Sure, there's similarities, but let's be realistic here.

I have a programming tutorials website I built from scratch in the PHP framework Laravel 5.4. Recently my friends have been pushing me to use WordPress instead.
I haven't worked with WordPress yet but I just hate it. I always think that it will not give me the flexibility I might need when adding new features.
This has put me in great doubt and anxiety about what I'm doing.
Is wordpress a better choice? I'm I just being lazy about the WordPress stuff?
I'll appreciate any advice on this.

i cant touch computer for two days, and it make me a strange feel. maybe its a good thing . through travel to relax myself.have a funny day and then start a new coding life😁.this holiday is a long time, after this travel .also have enough time to Learning some good framework.

Every *brand new framework/language* online course starts with writing ToDo app. But in real life there is no really good ToDo app yet

You know what i really like about right now? That is not like in 2016 when a new Javascript framework was release every day that does the same as jQuery but different, now days i can use it and everybody says "nice" instead of "you should do this with X.js with 4000 libraries on ES^N edition" to quote an articule i read on the time "I need to display data on a page, not perform Sub Zero’s original MK fatality."

procrastinative coding is a bad habit of mine. I've been using php for 10+ years and just recently got into laravel. I have to say I love it but at times I wish I could have learned the entire framework before starting my project some time ago. as I am coding I learn new tricks with laravel on how to do things and have to waste time and go back and change existing code... or tell myself "I'll come back to this after the launch".
I'm just wondering how other people handle taking on new frameworks

How tf one manages his work/life balance . I'm either working without pauses, studying a new framework or wasting my time playing video games. It's no middle .

I just created a new file in Android Studio called Auth.js and then wondered why I have a folder Auth with a file js.java inside.

Sometimes I forget what framework I'm in.

MaterialUI? Is it shit?

A brand new code base. Old codebase (old employees) used MaterialUI, locking in a lot of the styling and layout in their grids.

I'm trying to identify the pros/cons that can come from experience using the framework.

Some questions to spark discussion:

Anyone used this in production for a period of time?

Did it hold up? Did the designers hate it?

How was mixing this with SASS etc.

Cheers

Finding an awesome new library / framework then finding the documentation is all "this is what it is" rather than "this is how you use it" *sigh*

the first days of going to your first work is one of the hardest phases for a programmer/developer. who else can relate? advice?

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

Dev: Now that I finally know PHP and JS it must be really easy to find a good framework and use to build my beautiful website.

The options are limited: AngularJS, ReactJS, Ember, ActivateJS, BackboneJS, ExpressJS, Laravel, RactiveJS, Node.JS, Meteor, Knockout, Symphony, Codeignitor

And yes, you thought if you don't like AngularJS you can easily switch to ReactJS. But guess what, every framework will use their own scripting languages like Jade, Blade, Typescript making it learning something new extremely smooth.

The documentation will be part of another rant

When you are trying to get through "Get started" section of a new framework/lib but get so many ideas that suddenly you find yourself creating 5 applications at a time without any idea what the fuck are you doing.

I prefer it doing 2 tasks parallely during the initial phase of requirement gathering and design phase.(makes more sense if you are working extremely new system and framework)
1. Keep collecting requirements from clients and understand them.
2. Collect different designing aspects for the project and parallely, build a POC for 2 purpose: to get hands into the new Framework and also as a demo to clients. Working on POC helps in 3 ways: Improving understanding of requirement, improving framework knowledge, and playing around with code whenever bored of designing and reading tons of existing designs..
3. Once primary requirements are clear and fixed, analyse all different designs, if possible I setup meetings with senior devs, principal engineers (they help a lot when it comes to reviews on scalability and reliability of a design)
4. The above design is mostly architectural level. Once design is fixed, then I start taking each component and prepare a detailed implementation design. (Notice that whenever I am bored of designing, I spend sometime in building POC)
5. In detail design, I focus on modularity and flexibility. Anything defined should have getters and setters for example. This will help you reuse your code. Keep the interface between components in your design as generic as possible, so that in case your MySQL is change to Postgre or NoSQL, your design should be able to adapt new features..
6. Instead of building entire project, define feature targets and deliver small features.. this will help you to be in line with the requirements with minimum deviation.

When you wake up on a sat, log in to your emails to share with your bosses a new hacking framework just out that can decode encrypted strings, and no one replies because it's the weekend

The manager get me a new framework for a project in iOS.

But there is one problem, he unzip the framework in Windows OS, unfortunately in Windows unzip file differently from OS X. the result is a framework very strange, and it doesn't work!

You understand the battle between me and him.

Not a js expert. I'm trying to learn a new js framework so I'm stuck between angular and react. I'm a Django dev, so I'll be mostly using this framework in my Django apps. Which one should I learn? I'm migrating from jquery so please don't be harsh at me 😅

Direct implementing major functionalities without learning core/basics concepts while learning any new framework or library.

Im learning Angular for my new job. You guys have any suggestions on what I can build (over the weekend) to learn as much about the Framework as possible?

Can we like stop making new Frameworks every month and just take a break for like 2 years, cause Gawd Damn! 😣; It should be illegal to make a new Framework in the next 2 years🙂

Everyone that says it sucks because there is a new framework everyday, dude, you know that just because there is a new framework it's not a must for you to change your stack to it right? Also, you can find very valuable frameworks with this diversity

Another 'fun' rant

Wrote a new server application and got the request from customer services to make it compatible with a slightly older DB version.

Today, CS asked me to install everything on the customer's test environment so I made a build and installed it there.

Wanted to run the service, no .Net framework 4.7.1 installed. Fine, download the installer ...

Start installing .Net framework 'unsupported OS'. Started looking into it. Customer is still running an old unsupported Windows Server 2008 ...

Asked some colleagues whether this was normal. Apparently, yes.

Seems CS isn't capable of telling customers to at least have a supported windows version when they want our software. As if security issues due to people here not understanding TCP/IP isn't enough, we now have security issues due to old, unsupported Windows versions.

Note to self: never trust anyone who says that 'security is the most important thing in our software enviornment'.

I'm planning to rewrite two months(part time) worth of work done in android sdk. Wanna go for a hybrid framework. Is this a bad idea? Which framework do you suggest as far as stability is concerned? I don't care about ease of learning, new languages don't bother me

when people in a framework chatgroup ask you to "you should really read the docs" because you keep asking roughly the same question.

I'd gladly stop asking 20 questions about the subject because I keep getting errors, but when there is literally no reference to the methods I have issues with in the documentation I don't have much choice than asking a question for each new method...

And yes I did ask if someone could point me to the doc's for them, the answer was "Check the source code..."

(double annoying when the rest of the framework is documented rather excellently)

A little help on Django

So I just started learning Python and Django Framework and I have one question...

Are the variables shared between visitors?
I mean, let's say I have a variable named "school"
school = "school1"
A visitor from X location enters and changes this variable to "school2". A new visitor enters the page from Y location and reads the variable 'school'. What is going to show on visitor Y? "school1" or "school2".

Anyone here that is pretty new to programming? So many times when I try to develop something, I feel I can't develop it because I don't know how to start or where to start (choose lanugage, framework and so on). And sometimes I encounter problems i'll sit with in days without success and then I just give up. Any experienced programmer that experienced this and overcome it. How do I do?

A new JavaScript framework/library released...

JS Devs: 🏃‍♂️🏃‍♂️....🏃‍♂️ (towards)

I am losing my mind trying to create a new feature to a 2013 code base.
This project uses Zend Framework 1.12 and jQuery 1.4, so I added Vue and things went better but I have some tests to do.

I need a new language/framework/ANYTHING. I miss the doing-stupid-shit-but-being-excited-about-it-anyway-coz-NEW-LANGUAGE euphoria :'/
And no not python, that shit is shitty.

How come that everytime I learn a new tech/framework, I find that one flaw after 5 minutes which has been there forever, dozens of people complain about it yet nobody fixed it?

"I'm going to learn and use <cool new Javascript framework/library> for this project!" then having to try and learn it, only for the new project to eventually use jQuery again.

What if a programmer was invited to the dear moon project? What would he make?

Probably a new JS framework or a new programming language? :P

That spacex event was one of the most inspiring event I have seen in a long while. I can't believe it is happening. That Q&A was very interesting and I like how Elon Musk talks, he tries really good to put things in layman terms.

And looks like Elon Musk is also going to space with Yazuka.

If I get a chance to go in lunar trip, I would be happy even if things go wrong and I have to die in space.

First time I use Travis CI today :D
(And my first build error ever...)
In combination with Nuxt.js it is so fucking useful for Vue Development. Wow!
I think I've found my new favourite JS Framework.

Had a bit of trouble with Github Pages but I just created a 'source' branch with the source code and a 'master' branch with the deployed site. The reason is that organization sites can only be published from 'master' branch for some reason...

Anyways Travis CI is very useful!

When learning something new, say a new language or framework, do you go through the docs or tutorials, or do you just learn by doing and figure it out as you go?

I like to learn by doing and getting a finished project and start modding and changing stuff. what do you guys do?

I work as android dev for the past year and a half, this week in my startup I started doing some backend (it consists of microservices, codebase is written in python. were using rabbitmq for queuing and for http our framework is falcon).

At first I was very adamant to learn new stuff but now that Im getting deeeper into backend I started to really enjoy it!

Its still lots of new information but at the same time it feels soo refreshing to have two experienced mentors who can guide you, since Ive spent last year and half working on android completely by myself and relying only on myself. Also im very lucky that codebase is clean.

New idea for js framework comes...
google...
the framework does exist...
back to the thinking...
jump to point no 1

I am still relatively new to Ruby and would like to write a program using an interactive shell like interface,meanjng that people type the name of the program "taskflow" and the app starts, putting them into interactive mode. Is there a good framework for it or is it hard to write it myself? If not, any ideas or tips on how to accomplish it?

JavaScript development turns into more and more of a shitshow over time. Not that it was great at the beginning, but with each passing year it gets worse.

There are now 17 versions of Node.js, 18 versions of React.js, 3 major versions of Vue.js... Each version brings something new and no one is in a rush to update their stuff to be compatible with the latest version of the framework

Nextjs is for script kiddies. This is such a fucking CHILDISH framework. The way you write queries is such fuzzy wuzzy BULLSHIT that u cant even write raw sql. Coming from hardcore java spring boot backend of 5 soon 6 years of experience i cannot believe how bullshit it is. Ill stick with java. I need to be oldschool. Im sick of this shit with constsnt new bullshit popping up sugar coated kiddie shit

I think my senior does not really care to what I say. I told him that we need to study the core of spring framework before the mvc part so we can easily understand the source code of our client. And now that we're given a task to create and update new functionality on that given source code, him and our intern having a hard time finishing their task because they don't even know what @Autowired is.

Anyway good luck sir :)

I cringe every time I see someone joke about a new "framework" coming out every other day.
This is a serious problem, guys! Instead of piling up crappy, undocumented "frameworks", why not go to one that works well, and improve it.
It's a lot easier to learn how to design and develop when you're working with others who have been at it a lot longer than you.

Stitching old frameworks / libraries together...

What a lovely joy.

An override here... Testing if it runs.

Oh lovely, shitty shaded jars.

Creating other project for shitty shaded jar.

An override here, an override there...

Oh we need some system property to unfuck JVM upgrade...

Since it's shaded, need to add overrides for the non shaded and shaded variant...

Done...

Back to framework / library....

Another override, another system property...

Its seemingly endless.

Stitching together old shit with new shit to get JDK 20 plus running.

I hate everything.

If by coding style, you mean conventions and not design patterns, then I'm surprised no one has mentioned the official documentation nor the standard library of sorts. I'm relatively new in the industry but at least I'm quick to realize that every language/framework community tend to have their own preferred style; not a one-size-fits-all thing. And these preferences are usually set off by code samples from the official docs. This is true at least for the big communities where the official docs are well-written.

Bugger me Quarkus is quick. Pretty bloody quick even when not using Graal native, but with that... damn.

Looks like I need to skill up. These new Graal-native-friendly, reflection-free Java web frameworks are really coming into their own. Spring really needs to respond quickly, otherwise it's going to become the slow legacy framework of yesteryear, if it's not already.

## Reasonable answers needed ##

If you always work free and forced overtime, and you didn't get any salary raise fir a while. and then you asked to learn and work with new language and framework you didn't work with it before, you would prove yourself and learn it or you would ask for a raise first (or you simply you won't work do it)?

Context: fucked up market, no other job founded. and father.