Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
It's one of those languages that are barbaric enough to have the assignment operator return something. I've never been a fan. I use its big brother for low level stuff once in a blue moon but I've mostly ignored C++ for about 15 years, lol. Until I got an assignment with it at work.
SMH, what the hell even is this language? Arrays are always indexed starting from zero. The bad assignment and equality operators. Weak typing. Shoddy contract support.
It's like I went back in time to 1985 and had a nightmare that the new successor to C that I'd been looking forward to was an incremental upgrade that should have released six years prior. Ada '83 blows this crap out of the water.
♥♥♥♥. Pansy. Try COBOL.
Environment Division
Data Division
Procedure Division
♥♥♥♥
Dark times indeed. I'd just write assembly at that point, NGL.
The financial world runs on COBOL. Their ♥♥♥♥ can't be down for one second or they lose TRILLIONS! TRILLIONS I tell you! (So they say).
If I needed money I wouldn't have to work long. Any of you young whippersnappers looking for an early retirement here's your sign: COBOL.
They've come back in fashion because your average modern programmer is taught one syntax that's as flexible as possible and then fills in the divisions set out by the project lead.
As such most modern languages do things like make the 0 enumerator inaccessible, typically adding an entire function to the project that's just 0-seeking because the language isn't supposed to be full-featured in the first place.
hang on let me just run the syntax shortcut that shows me the kernel folders without having to navigate.
oops i mistyped one character and accidentally activated my doomsday routine.
that's okay, the worm wasn't giving me issues on this os I flashed two weeks ago...
oh no, the worm came from my backup usb stick!!!
It's a bug leftover from the Visual Basic scripts the C+ includes were built off of, and the (singular) author refused to allow them to be changed for C++. The currents rightsholders are all moon cultists as well, and refuse to allow changes for the same reasons.
Microsoft's libraries are all built off of the same includes, so they are all subject to the same bug in various circumstances. As such remembering the algorithm's quirks can be important, such as basically falling apart when you toss it any multiple of 3. As a result just about any function which winds up calling that broken library has to include an exception which searches for and excludes 3s, and which also converts the data into a cipher which doesn't include 3's while it is being processed
Java is built on the same broken library set, since it was sold to the same hostile entities that package the broken libs, and was designed as a way to develop for the web without having to learn Basic or Visual Basic.
It hasn't been updated in forever either as the intent behind buying it was to suffocate it, and it's kind of a stroke of luck that it took off. That and having been designed for a clear purpose that was eminently useful.
I'm not really sure if AS3 is still subject to the same security vulnerabilities introduced by the broken libs or not.
-From an email exchange in 2003
http://www.purl.org/stefan_ram/pub/doc_kay_oop_en
His direct quote about C++:
-- Alan Kay, OOPSLA '97
In other words. No. C++ does not fit the original definition of Object Oriented Programming.
It instead follows an entirely different paradigm that Bjarne Stroustrup(inventor of C++) defined, which hijacked the term OOP:
https://www.stroustrup.com/oopsla.pdf
C++, along with Python, Java, C#, etc follow this instead.
Okay but on any enterprise application you're going to be working with the packaged libs. Not your bespoke 'good code' that you made yourself. And introducing a separate subfunction just to make your good code work with the libs is going to confuse everyone except you.
What do you think you are, some kind of skilled laborer? :p
Anyway the point behind the development of the libs in the first place was to design certain commonly-used functions that anyone could call, particularly in an enterprise environment where the codebase needed to be homogenized. The fact that they came out broken is, on the one hand, a heinous crime on the part of conspiratorial individuals, and on the other hand it's the natural end of most programming endeavors anyway.
Yeah, but since it's a branch it has all the same libs and includes. And since Microsoft uses all of those in its codebase, I am doubly doubtful that they were removed.
Almost everyone moved away from AS3 when the foundational vulnerabilities in Java8 were discovered, as they depended on vulnerabilities included with libs from java 1 and were thus universal to the codebase.
The same vulnerabilities are why nothing past windows 98 is particularly secure, and the first step of hardening Win98 is simply removing those libraries entirely. Which, to reiterate, are 'legally inviolable' code from the late 80's which has wormed its way into absolutely everything.
The assignment of variables and working with variable classes is OOP, even if the 'OOP Guru' doesn't agree.
Otherwise the controversy is meaningless as both sides admit the term is made up and doesn't really describe anything at all.
Yes, well, we had to make hooks for the bots to get into our codebase somehow.
They were threatening to up their percentages on universal copyright if we didn't.
Also most modern libs load all their includes as one, such that there's no way to actually exclude problematic calls.
Minimalistic languages, such as Python, were designed with this problem in mind...but at the end of the day you can't get anything done without these libraries. And python's extremely permissive rules are basically just a gateway for bots calling these libraries with innocuous-looking code.
All other languages are similar, save for binary and maybe Basic if you can work around the libs in your i/o devices.
Meaning pretty much the entire past 40-50 years of software development needs to be thrown in the trash can.