Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "code salad"
-
you wanna know what the most hilarious shit is? hackernews users AKA the 6 figure startup bros that "rule the world" in terms of code and software...
trying to argue the best way to build a website 😂😂😂😂😂😂😂😂😂
here's some select quotes:
"I believe the most minimalistic and productive way is to just use php"
^ this guy must not know its 2023 now
"Unless you are a web developer I don't see the point of a CSS framework, it's much easier to roll your own."
^ this guy must not know the pain and suffering that is 'rolling your own' in CSS
"Sadly, I just don't have the time to generate the content I wanted to do, so the site sits."
^ this guy just... wait, what?
but you know what? these guys clearly know WAY more than me in terms of software, it's good they get infinite salad bar and prime rib every day at silicon valley's best and brightest!
please fucking kill me i want it to end16 -
Why is it that virtually all new languages in the last 25 years or so have a C-like syntax?
- Java wanted to sort-of knock off C++.
- C# wanted to be Java but on Microsoft's proprietary stack instead of SUN's (now Oracle's).
- Several other languages such as Vala, Scala, Swift, etc. do only careful evolution, seemingly so as to not alienate the devs used to previous C-like languages.
- Not to speak of everyone's favourite enemy, JavaScript…
- Then there is ReasonML which is basically an alternate, more C-like, syntax for OCaml, and is then compiled to JavaScript.
Now we're slowly arriving at the meat of this rant: back when I started university, the first semester programming lecture used Scheme, and provided a fine introduction to (functional) programming. Scheme, like other variants of Lisp, is a fine language, very flexible, code is data, data is code, but you get somewhat lost in a sea of parentheses, probably worse than the C-like languages' salad of curly braces. But it was a refreshing change from the likes of C, C++, and Java in terms of approach.
But the real enlightenment came when I read through Okasaki's paper on purely functional data structures. The author uses Standard ML in the paper, and after the initial shock (because it's different than most everything else I had seen), and getting used to the notation, I loved the crisp clarity it brings with almost no ceremony at all!
After looking around a bit, I found that nobody seems to use SML anymore, but there are viable alternatives, depending on your taste:
- Pragmatic programmers can use OCaml, which has immutability by default, and tries to guide the programmer to a functional programming mindset, but can accommodate imperative constructs easily when necessary.
- F# was born as OCaml on .NET but has now evolved into its own great thing with many upsides and very few downsides; I recommend every C# developer should give it a try.
- Somewhat more extreme is Haskell, with its ideology of pure functions and lazy evaluation that makes introducing side effects, I/O, and other imperative constructs rather a pain in the arse, and not quite my piece of cake, but learning it can still help you be a better programmer in whatever language you use on a day-to-day basis.
Anyway, the point is that after working with several of these languages developed out of the original Meta Language, it baffles me how anyone can be happy being a curly-braces-language developer without craving something more succinct and to-the-point. Especially when it comes to JavaScript: all the above mentioned ML-like languages can be compiled to JavaScript, so developing directly in JavaScript should hardly be a necessity.
Obviously these curly-braces languages will still be needed for a long time coming, legacy systems and all—just look at COBOL—, but my point stands.7 -
hey guys have you heard of sTate aCtoRs?!?! tHeRe iS a BaCkDoOr BeCaUsE I aM a BaD coDe mAiNtAnEr aNd ApProVe aLL coMmiTs
i'm one of 10,000 ultra-rich fuckwads who lives in the sAnFraNsiScO bAy aReA
its crazy that people earn less than 300K per month!
but i spit around the word "state actor" because i once wrote a for loop that retrieves customer emails from a CSV!
hacker news dumb fucks, all of them
they need to go eat more salad at the meta headquarters
no wonder their jobs are at risk 😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡😂🤡4 -
many of you have probably been skeptical this entire time of what i am capable of with a keyboard and a monitor
i guarantee what you are about to see is far beyond 99% of what can be found in SiLiCoN vALLeY salad bar tech bros, and probably what 99% of you can write
take some time to understand this code, like REALLY understand it...
if you can't, that's fine. come back in 5 years.
here it is:
https://typescriptlang.org/play/...
this is what 10+ years of busting your ass (and i mean really busting, its fucking 7 PM on a saturday for me) can look like
another reason you can understand it's infuriating listing to rubes ramble "we can't hire you because you dont have <<arbitrary number of years>> with <<arbitrary language>>" absolute clowns - or listening to managers who are "smart" yeah ok buddy
i am ChatGPT-10+. bow down to my superintelligence. we don't need LLMs because I am 5+ iterations ahead
also if you don't understand the significance of this code, it's on you
any clown i've ever seen, whether it be on twitter, facebook, insta, here on dev rant, hackernews, or whereever, just know, i know you're full of shit, and i've worked harder. that is all.
anyway, i'm finally done for the day, cheers 🥃16 -
The term "technical debt" is poorly used. I hear folks of all stripes and roles proudly proclaim that they've "reduced technical debt" in some way. It's used as a catch all to describe some kind of supposedly beneficial change. I think it's just more software process word salad. Mostly because there seems to be some assumption that "Yay, that stuff that was changed is no longer a problem" when odds are that it will be changed again before too long for more "technical debt reduction". Software changes over time because the requirements change over time. I don't see the need for the phrase at all, and I think using it gives some false sense of accomplishment when really the constant change of code is the normal state.6
-
Dear colleagues,
YOU HAVE RUINED JAVASCRIPT!!@##@
Yes, you are one of those that are responsible for giving JavaScript a bad name and using jQuery for FUCKING EVERYTHING!@#$
Start thinking for yourselves, ditch this shit before it's too late and learn how to write some actual fucking code. The information is out there, you can do it. If you need handholding with $.each, creating concatenated strings with error prone code to send them in one field to the server, just to explode it back there, then consider that the world doesn't need your BULLSHIT code and go and get a job you're actually good at. Stop ruining it for the rest of us.
THANK YOU8