Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You see functional niggers repeating this but I've only seen the useless layers of abstraction in exactly one project I worked on that was dated to early 2000s. Never seen anything that does that after 2002.Instead of designing a stupid niggerlicious unnecessarily abstract UML spaghetti diagram then developing 60 separate abstractvirtualinterfacefactorycontrollerpoolfactorywatcher classes to do 1 simple thing you can just be imperative for a tiny bit and have a much easier time and produce easy-to-understand programs. Have you ever actually tried this shit or have you just always been using full OOP for everything, even things that don't mean the greatest amount of sense, since your first Hindi-language Java tutorial and you just never knew anything else?
Completely, utterly, correct, I do not. You are disadvantaged because of your autism, you will never do anything with your holy knowledge, so it is pointless. Also, the other people that you think respect you for knowing it, actually hate you because they think you are taking away the attention they could be getting (which actually doesn't exist, nobody is looking or cares).I bet you can't even comprehend how fast a modern CPU is because your conception of "fast" is limited by whatever runtime or VM your POOPlang runs on. Forever disadvantaged by lack of knowing.
And all of everything you know is useless and won't make money and is just another way to dance around other low level shits to pretend to flex. Think about this long and hard - knowing all of that shit has just kept you back because now you can't use anything without autistically feeling like you are in control. You have gone backwards from your goalEverything you know about POOP design patterns is something I know about OS internals, everything you know about the latest JS babby frameworks is something I know about CPU cache efficiency. Every gay little 4cuck quip you have is something I know about compiler internals.
Why don't you make me faggot? I will not do so. What the fuck are you gonna do about it nigger?Man up and learn malloc and free, pussy.
Again, completely correct, and it very much doesn't matter. You don't know how your car and microwave works but you use them every day. And same for everything else in the entire world, but you fell for the meme and decided you had to take years off and waste time learning old shit "because a bunch of niggers on the internet started a secret club and told me to"I bet you don't even know how your faggot programming language works internally, do you even know how inheritance works under the hood? Probably not, faggot. I'm gonna dependency inject a little brother into your mom so you have to call me your daddy, bitch.
Yes, yes it is. Again, if you have to write a timer or something like that which measures the difference in microseconds just so you can flex, you are Byuu level lolcow autism. It's just your average person on KF doesn't know what that is so you can get away with it. Taking 10,000 processor instructions is fine because cloud hosting is cheap while development time is not, that's why OOP and frameworks are popular because you can get shit done quick then the client pays an extra $5 a month, oh no.adding 2 numbers in his shitscript language takes 20 processor instructions even with full jit enabled due to how "dynamic" and "powerful" the language is and he thinks that's completely fine
Didn't read, just bumped up the memory and CPU on my cloud instance, lol.The main issue I have with OOP is that several aspects of it are deceptive. Inevitably overcoming these deceptions requires a new paradigm altogether.
For example, one of the major benefits advertised in OOP is encapsulation, that Objects are self contained and their values controlled internally. Over time this became more and more difficult to maintain when shared resources were involved between classes and objects. Specifically with the concept of threading on modern day operating systems. It became necessary to create objects/classes which handled ACID transactions on databases and share them between multiple classes. This results in the creation of a defacto global scope which is one of the concepts OOP was designed to avoid.
Sure OOP is still useful today, but its scalability outside of just spinning up more instances is becoming more of an issue. Irregardless of your disdain for functional programming, the industry is leaving you behind. Compact serverless functions executed on messenger queues are an industry standard now, and sure the systems which execute them are written using OOP, but writing those are going to become 0.000001% of jobs. Kind of like getting a good embedded job.
Are you the faggot that caused rocketchat to need the $40/mo droplet on digital ocean?Didn't read, just bumped up the memory and CPU on my cloud instance, lol.
Are you the faggot that that bumped my taxes up because you tricked society into thinking you are a worthwhile causeAre you the faggot that caused rocketchat to need the $40/mo droplet on digital ocean?
no we just find you funny and if you vanished from this thread today i would go back to bashing on @Concentrate Juice for his npm ass package manager system language or i would be talking about the fine intricacies of various types of UBYou neeeed meeeeee
"oh paying 10x the cost for hosting because the program is unoptimized is actually ok because spending a bit of extra dev time is so costly"Are you the faggot that caused rocketchat to need the $40/mo droplet on digital ocean?
This is true but what is going on here is as long as the request time is under 2 seconds, not even a normie will complain. Nobody can tell the difference between the most autistic holy lean low level code that actually, behind the scenes, works in 0.0001 seconds, versus it loading in 2 seconds. So several hundred thousand orders of magnitude slower, is acceptable as long as the final number you multiplied to get to, is less than 1-2 seconds.when you run some piece of logic a few million times a second you will need to be very careful because making something an order of magnitude slower won't make your event handler slightly slower, you will instead have a program that runs at 6fps instead of 60fps and you will look dumb
When you write this I believe you are unaware of how cloud hosting works which is you run it as a virtual app which means you are sectioned out virtual memory on the server. You don't make web apps to run them locally. Also, even I am not going to defend NPM which is what you are referring to at the end.also "unused memory is wasted memory" is a bit of a cope because unused memory is actually memory that the user could be using to do more multitasking and that the operating system could be doing io caching with instead of storing 900mb of shit in ram because people keep making decisions along the lines of including an entire library to check if a number is even
Again you don't run web apps as a copy on every desktop. It's like you think a web app runs 1,000 copies for 1,000 users. You put it on a server and eat the high memory cost there one time, then the rest of the computers can be dog shit thin clients or something like that. $60 a month to a business is nothing.also if your shit is so horribly made that it uses 27gb of ram and your user has 16gb they will probably not be delusional enough to think the same way you do and instead they will say "wow, this software would be good if it could actually run on my computer" because not everything is a cloud environment where you can move slider and pay $60 more per month to get 6x the ram because you fucked up
It is, because companies are retarded and they don't know what they want"oh paying 10x the cost for hosting because the program is unoptimized is actually ok because spending a bit of extra dev time is so costly"
The user can't tell the difference between 0.005 seconds and 0.5, but the server can. Wouldn't the cloud costs be 100x the price? If you optimized it you would be able to serve a hundred times the traffic with the same money. I can't see that being completely useless, especially if the business was primarily online and had lots of traffic.This is true but what is going on here is as long as the request time is under 2 seconds, not even a normie will complain. Nobody can tell the difference between the most autistic holy lean low level code that actually, behind the scenes, works in 0.0001 seconds, versus it loading in 2 seconds. So several hundred thousand orders of magnitude slower, is acceptable as long as the final number you multiplied to get to, is less than 1-2 seconds.
Not everything is a web app. Sometimes people write software that actually runs on the user's computer. Such software has to be relatively lean as to not step on the user's toes. Have you ever used an Electron-based application that consumes a tenth of your memory for no fucking reason because they're an entire browser in disguise? It sucks.When you write this I believe you are unaware of how cloud hosting works which is you run it as a virtual app which means you are sectioned out virtual memory on the server. You don't make web apps to run them locally.
A lot of web apps somehow shit up the server end and the client end at the same time. Don't think sending 40MB of javascript is actually a thing any sane person and not a completely careless, if not unethical, soydev with no care for the quality of their work would do. Also I said $60 in small self-hosting contexts. It could be any number that's several times larger than what it could be.Again you don't run web apps as a copy on every desktop. It's like you think a web app runs 1,000 copies for 1,000 users. You put it on a server and eat the high memory cost there one time, then the rest of the computers can be dog shit thin clients or something like that. $60 a month to a business is nothing.
At least you have one shred of sanity.Also, even I am not going to defend NPM which is what you are referring to at the end.
It makes code easier to test as well, as long as you are capable of injecting Mocks.I actually like OOP, I do enjoy working out how to abstract things appropriately, it’s a fun task. I genuinely think that the main issue with it in the industry isn’t the paradigm itself, but rather how corpocode relies on it.
They prefer it because it implicitly makes programmers more replaceable in my opinion
Sure buddy.Jokes on you, I was only pretending to be retarded while acting superior to you scrubs. Real funny right?... Right?
Yep, that as well.It makes code easier to test as well, as long as you are capable of injecting Mocks.
WebP's lossy compression is based off VP8's intra-frame coding, if I'm remembering correctly. AVIF uses AV1 for compression, which is more modern and arguably better quality in most cases. The compression ratios are probably nicer on average too.Since most of you are autistic with strong opinions about things, what's the deal with avif suddenly being used by websites and what may be the reasoning to use it over webp?
besides, what i think is strange about him is that no one in this thread is a proper inCel who claims that C and C++ is the only way of doing stuff with computers, this thread has tons of encouraging comments about other 'less autistic' languages, encouraging people to learn JS and whatever.I love that the resident retard of this thread is a Java 8 nazi—the computer language with the highest pajeet quotient.
Hindu supremacist on our hands?
What's even funnier is that Java isn't even that good of a JVM language anymore. It's always trying to catch up to the features implemented in Kotlin. If enterprises were more open to switching over, really Java would be dead.I love that the resident retard of this thread is a Java 8 nazi—the computer language with the highest pajeet quotient.
Hindu supremacist on our hands?
This drives me nuts about languages like Go and Rust. Runtimes don't have to be huge and neither do the standard libraries. They just suck at what they do.also it uses static linking all the goddamn time so you make a helloworld app and then it's 1.2 megabytes because "le storage space is cheap or something" like fuck you nigger maybe i wanted to use that space for something else than 47265695 copies of the same 3 libraries
A large selling point of Rust is that it doesn't have a big runtime but then they do stupid shit like statically linking the standard library so you have huge executable images. At that point just make it a JIT language like dude seriously what the fuckThis drives me nuts about languages like Go and Rust. Runtimes don't have to be huge and neither do the standard libraries. They just suck at what they do.