- Joined
- Sep 28, 2022
the proper acronym is FAGMANFor anyone working at FANNG or whatever the gay acronym is now how bad are h1bs are they as wide spread as the memes say they are and do you have any horror stories
Apple
Microsoft
Amazon
Netflix
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.
the proper acronym is FAGMANFor anyone working at FANNG or whatever the gay acronym is now how bad are h1bs are they as wide spread as the memes say they are and do you have any horror stories
Is netflix really that profitable t be in the same acronym as google microsoft and applethe proper acronym is FAGMAN
Apple
Microsoft
Amazon
Netflix
Yes, unfortunately.Is netflix really that profitable t be in the same acronym as google microsoft and apple
I'm a first year student for an associate's degree in programming, I learned a lot on my own and I think that a really good way to get your own tutor is to get a distance formal education in an university or college, when you have a clear learning path it's easier to make sense of what you are learning (such as learning about hardware and operating systems, math for programmers and a programming language in parallel, they have synergy), and in this scenario you can take the classes whenever you want because it's online, you have teachers correcting your weekly assingments and giving you the study material, and you can ask questions to an actual expert on a forum or weekly meetings, so those weekly meetings and forums are to interact with a tutor. Being self taught is possible but it's harder, when it comes to my education I ask chatGPT to explain things to me all the time which works great.I was looking at additional ways of learning, has anyone tried the "ProgrammingBuddies" on Plebbit?
Looks like every now and then there are people/developers who offer themselves to teach volunteers for some reason, or would you just stick with resources online?
The problem is that official documentation and guides are aimed at people that already know how to code, not at begginers, when I got the idea that I wanted to learn how to code I looked up C# in their official website because I thought it's the best way to learn, going at the source right? And I'm greeted by something such as: "C# is a statically typed, object oriented, multi-paradigm language in the .NET ecosystem executed by the CLR system, it features polymorphism, assynchronicity, and garbage collection with automatic memory management, it has metadata reflection and functional programming idioms such as lambda expressions".Official documentation are official guides are the best resource for learning a tool or a library. Internet searches and LLMs will most likely feed you strange fantasies that might technically compile and run, but are fucked in some fundamental way.
The problem is that most projects are not properly documented.The problem is that official documentation and guides are aimed at people that already know how to code
You can use cmake to pull source from a git repo + commit hash or a URL using FetchContent. A dependency manager isn't that necessary unless you rely on libraries for everything. A lot of engineers want to make things more complicated than they need to be.Are you still one of those old farts who writes C or C++ and feel like you've been missing out on all the supply chain vulnerabilities of modern programming languages?
Don't worry, randerson112 has created a cargo-like package manager for C/C++, so now youcraft add --git soypackageorcraft updateand get immediately pwned like the cool kids do.
cmake's fetch feature is the biggest anti-feature of cmake, burn it with hellfire!You can use cmake to pull source from a git repo + commit hash or a URL using FetchContent. A dependency manager isn't that necessary unless you rely on libraries for everything. A lot of engineers want to make things more complicated than they need to be.
I've wasted hours of my life fighting with package managers (fuck you NPM). The only one that I've found works well is the Go package manager.
Not sure why. It isn't any different than downloading the sources manually and then referencing them.cmake's fetch feature is the biggest anti-feature of cmake, burn it with hellfire
You can replace it with NVIDIAIs netflix really that profitable t be in the same acronym as google microsoft and apple
It's done automatically, usually with no verification whatsoever, and completely breaks packaging.Not sure why. It isn't any different than downloading the sources manually and then referencing them.
Without watching a 30 minute (!) video, the bottom text says "significant Rust program," which isn't the same as the language.Is it actually true that Rust isn't memory safe at all?
In theory, Rust protects against out-of-bounds memory accesses. In practice, the language is a straitjacket (or, given the sexual proclivities of the developers, a gimp suit) and every program of appreciable size and complexity has a fairly large amount of its code tagged as "unsafe" which, among other things, turns of bounds-checking. On top of all this, the theoretical benefits are, in fact, entirely theoretical because both the design and implementation are half-assed, so you can get memory exploits even in code that doesn't use the "unsafe" escape hatch.
Is this guy on the money or is he full of shit? Is it actually true that Rust isn't memory safe at all?
which, among other things, turns of bounds-checking
unsafe enables pointer derefs, it doesn't disable anything. Bounds checking is enforced by container APIs at runtime, just like C++'s std::vector::at. Rust is "memory safe" only because you can wholesale prevent the desk jockey jeet niggercattle from dereferencing pointers. That's it.There are no theoretical benefits as borrow checker is theoreticaly unsound - there are ways to access out-of-bounds memory entirely within safe code. The results are puerly practical as in it will stop you fom commiting common errors and while breaking borrow checker is possible you need to know what you are doing to do so.In theory, Rust protects against out-of-bounds memory accesses. In practice, the language is a straitjacket (or, given the sexual proclivities of the developers, a gimp suit) and every program of appreciable size and complexity has a fairly large amount of its code tagged as "unsafe" which, among other things, turns of bounds-checking. On top of all this, the theoretical benefits are, in fact, entirely theoretical because both the design and implementation are half-assed, so you can get memory exploits even in code that doesn't use the "unsafe" escape hatch.
He is unflushable turd of the Linux world.lunduke is grifter nigger mind rape, watching 30 minutes of grep results is mind rape.
iframe on his page. Google had at the time (probably still has) a policy of removing any site from search results that could be considered dangerous.refused to train, help, or onboard me with anything and then shame me for my lack of knowledge.
I will give you a hint: It's deliberately, it's to plant the seeds for you to look bad so they can hire one of their own to later look like the new Indian is "more cooperative" than you, people higher up will see that on paper and it will be a cascading effect for the next potential non-indian hires after you. They hide the pajeetification by pretending it's meritocracy, this is what replaced DEI practices. I know it sounds like a nigger excuse (whhaa they made me look bad n' sheeeit, took my job!), but indians are too low IQ to hide their ingroup preferences compared to e.g kikes or niggers.. On top of that, she would use that as a justification to not assign me anything and then shame me for not doing anything.
Rustoids don't care about safety. They like the type system and cargo and have always wanted "Javascript as a systems language" to be a thing. It's been a troonlang disguised as a "safety necessity" for over 10 years. Also, they no longer have "it's still the early days" as an excuse for low adoption rates. Rust is following the adoption curve Ada had many years ago. C and C++, at this point in the life of the language, had much broader adoption.We don't need Rust anymore, the main reason people said Rust was good is because much memory safety but now we have Fil-C, which is safer and as far as I know has yet to suffer a vulnerability.
If the Rustoids really cared about memory safety (they don't) they'd be all over Fil-C (they aren't). People may make other excuses (e.g. performance from the GC) but this would be shifting the goal posts because Rustoids claimed memory safety was more important than everything, including performance. The whole thing was a larp, nobody cared, we can all stop pretending!