>hey i should learn modern frameworks>speed run this for ~3 months>10 hrs a day every day>make working simple package>have 2x AI audit the code repeatedly>test test test retest>npm dry run no problems>publish code>fast forward 2 weeks>$history | grep build-script.sh>run exact same build script from 2 weeks ago>a build script which has been run hundreds of time>ERROR ERROR ERROR INVALID ERRORmodern frameworks are building fragile space shuttles so they can output a fucking .html page. this shit is a total waste of time.im literally about to break my laptop. this shit is so unreal. this is not real IT work. this is tranny shit.this is not the first time ive seen this cycle>make a modern framework thing>it works>test it repeatedly>test it more>no errors>change nothing>1 week later>ERROR ERROR ERROR ERROR
>>108295281Have you considered your OS has modified a required lib in such a way as to cause some gears to misalign?
>>108295395of course i considered that. but this is not some big complex program. this plugin does not use any special magical features. we are talking about a 2 week time gap - not 2 years.>modern frameworks are building fragile space shuttles
>>108295395not him but any app involving composer or nodejs is pure cancertons of bugs and undocumented shit everywhereone that i got with laravel artizan was solved after i discovered some obscure issue on github where the author of a package was like>oh yea forgot to mention, so our app is called Shitass right? make sure your Linux username is Shitass2 because haha we hardcoded a bunch of stuff as Shitass2 so it breaks otherwise. oopsie forgot to update docs with this, ehh maybe next time *closes issue*anything involving a package manager is pure fucking trash
>>108295612It only takes one tiny change in how a .so or .dll handles the computation of something to gum up the works. It could have been something as simple as a fixed type that previously allowed behavior no longer allowed. I suppose the question which you didn't feel the need to answer for us is: what has changed in those two weeks, because something obviously has.
>>108295612So what exactly is the problem and how is it framework's fault? I maintain a project that I've built with React in 2019, and it still works and is used. I update the packages maybe once every 2 years, and migrate some libs, if needed.
>>108295652niggerfaggot, non-retard stacks don't have this bad of a churn. you can expect shit to continue working for years, because the people involved in the releases aren't retarded children that have zero fucking clue about backwards compatibility and ecosystem stewardship
>>108295793>hurr shit is broke>durr I dunno why tho*sadface* *post on 4chan*Good luck, stranger.
