!rant

This was over a year ago now, but my first PR at my current job was +6,249/-1,545,334 loc. Here is how that happened... When I joined the company and saw the code I was supposed to work on I kind of freaked out. The project was set up in the most ass-backward way with some sort of bootstrap boilerplate sample app thing with its own build process inside a subfolder of the main angular project. The angular app used all the CSS, fonts, icons, etc. from the boilerplate app and referenced the assets directly. If you needed to make changes to the CSS, fonts, icons, etc you would need to cd into the boilerplate app directory, make the changes, run a Gulp build that compiled things there, then cd back to the main directory and run Grunt build (thats right, both grunt and gulp) that then built the angular app and referenced the compiled assets inside the boilerplate directory. One simple CSS change would take 2 minutes to test at minimum.

I told them I needed at least a week to overhaul the app before I felt like I could do any real work. Here were the horrors I found along the way.

- All compiled (unminified) assets (both CSS and JS) were committed to git, including vendor code such as jQuery and Bootstrap.
- All bower components were committed to git (ALL their source code, documentation, etc, not just the one dist/minified JS file we referenced).
- The Grunt build was set up by someone who had no idea what they were doing. Every SINGLE file or dependency that needed to be copied to the build folder was listed one by one in a HUGE config.json file instead of using pattern matching like `assets/images/*`.
- All the example code from the boilerplate and multiple jQuery spaghetti sample apps from the boilerplate were committed to git, as well as ALL the documentation too. There was literally a `git clone` of the boilerplate repo inside a folder in the app.
- There were two separate copies of Bootstrap 3 being compiled from source. One inside the boilerplate folder and one at the angular app level. They were both included on the page, so literally every single CSS rule was overridden by the second copy of bootstrap. Oh, and because bootstrap source was included and commited and built from source, the actual bootstrap source files had been edited by developers to change styles (instead of overriding them) so there was no replacing it with an OOTB minified version.
- It is an angular app but there were multiple jQuery libraries included and relied upon and used for actual in-app functionality behavior. And, beyond that, even though angular includes many native ways to do XHR requests (using $resource or $http), there were numerous places in the app where there were `XMLHttpRequest`s intermixed with angular code.
- There was no live reloading for local development, meaning if I wanted to make one CSS change I had to stop my server, run a build, start again (about 2 minutes total). They seemed to think this was fine.
- All this monstrosity was handled by a single massive Gruntfile that was over 2000loc. When all my hacking and slashing was done, I reduced this to ~140loc.
- There were developer's (I use that term loosely) *PERSONAL AWS ACCESS KEYS* hardcoded into the source code (remember, this is a web end app, so this was in every user's browser) in order to do file uploads. Of course when I checked in AWS, those keys had full admin access to absolutely everything in AWS.
- The entire unminified AWS Javascript SDK was included on the page and not used or referenced (~1.5mb)
- There was no error handling or reporting. An API error would just result in nothing happening on the front end, so the user would usually just click and click again, re-triggering the same error. There was also no error reporting software installed (NewRelic, Rollbar, etc) so we had no idea when our users encountered errors on the front end. The previous developers would literally guide users who were experiencing issues through opening their console in dev tools and have them screenshot the error and send it to them.
- I could go on and on...

This is why you hire a real front-end engineer to build your web app instead of the cheapest contractors you can find from Ukraine.

When you had been reloading the page like crazy and none of the changes are registering. Then you realize that you are reloading production server instead of development one. 😖

Funny programmer fantasy porn titles.

Add your 2 cents.

I'll start with.

Naive user needs hot reloading for her frontend.

Boss GF wants you to fix her backend.

Go!

Ok, so I work at this "Great" company. I joined a new team recently with a project that is supposed to be a lot better than many of the other projects we have.

THESE MOTHEERRRRRFUCKERS don't even have hot reload on the app. You have to rebuild the app everytime you make a change. Are you kidding me?! We are using React. One of the basics of React is hot reload. I get into a fucking meeting and one of the devs is like, "I have one important thing to tell you, don't use hooks (a not so new feature in react yet something everyone should use at this point)" and the critical reason we don't use it is because they don't want to confuse the Java devs who are used to their little oop style o_O

Maaaan fuck your developers, it's not my fault you guys can't learn something so simple like functional programming. I haven't even started a sprint yet, I'll burn this app and make you rewrite it all.

I gave you a chance, Nvidia. It could have been a good thing, but no. You are still crap. About two years ago, my son's graphics card (an Nvidia) died, so I thought, I'll give him my nice Radeon card, and got myself a new card. For some reason, reason failed me, and I got a GTX 1070. It's been a nice enough card, and worked well. And then the last driver update happened. Fallout 4 started to CTD before it even booted to the main menu. Me, not thinking (again) thought it was a mod, so I uninstalled and deleted and reinstalled again, with all 120 mods. Nope. Still crashing. Then I noticed, as the game booted, the fans started to ramp up, and I could tell exactly when it would crash be the sound of fans. I was expecting the computer to taxi out the room. Rolled the driver update back to the last one that worked. Now I can log in again, and things are mostly stable. Still crashes, but not as bad, probably due to reloading the mods and missing something. When the RX 3080 hits the market, bye bye Nvidia. You haven't changed a bit over the years. We're through.

Much obliged if you stop reloading the folder and searching it every five fucking seconds you fucking cunts.

Good god damn this fucking 'feature' of windows 10 grinds my fucking gears. I hit 'x' to stop seeing the visual distraction of the fucking green loading bar when the folders already loaded. Same thing with music. All I want it to do is open and play my fucking song.

Does it do that?

No instead it spends precious cycles updating fucking indexes or sprinkling crack rocks on the corpse of my cpu or whatever cycle fairies at fucking microsoft programmed it to do while wasting my fucking time.

I wish I had a brick and a microsoft programmer within throwing distance, I'd be sorely tempted to nail the motherfucker square in his fucking big fat melon.

Cunts.

fuck count: 8

Rant mode: The guy in charge of the database were working on cannot even add a few lines of data without deleting all the data in the table and reloading it using a wizard!

And he recently got a "Best D.B.A. Award"?!

This is why I don't trust those who brag about their certificates.

FUCK YOU, UNITY.

The fucking UI lag causes mouse events in the editor to aggregate and act fucking weird when it's randomly reloading scripts and shit.

I just needed to move some assets into another folder. I control clicked a few scripts at the same time Unity decided to recompile them. It ended up thinking I was making a box selection and then, weirdly, some mouse combo that duplicates scripts (didn't even know that existed).

Okay, whatever, nbd. I just control clicked the other scripts (all with `1` postfixes) to delete them. No problemo, right click, delete.

FUCKING UNITY LAGGED, THOUGHT I BOX-SELECTED AGAIN, AND DELETED EVERYTHING IN THE GOD DAMNED FUCKING FOLDER. HOURS OF WORK. JUST GONE.

FUCK YOU UNITY. YOU'VE CRASHED THREE TIMES THIS WEEK AND NOW THIS. FUCK YOU.

DevRant should have a sort by random I am tired of reloading and get basically the same thing but in different orders

MDKFJMQLSKDFJMQLSKDJFMQSLKDFJMQLSKDFL.

I hate websites that refresh the entire page and the entire effing web stack after every trivial change to a request.

HELLO AJAX OR WEB FRAMEWORKS ANYBODY

TLDR: Walmart bug 😠

As a dev, I know that bugs happen. But as a dev from a small shop that has many clients and very few devs, I absolutely despise when a large company with many devs has a bug in a product that millions of people use.

WalmartContacts.com. How many devs do they have? And how many dedicated to this 1 product? How many people in QA? (how many on DevRant... lol)
And yet I can't even place an order using their reorder functionality. Seems like they should have this shit down. Seems like they should have all their regression testing ducks in a row. Seems like they should at least show some kind of error message so the user knows what's going on. Instead, no message at all, just the final checkout payment page reloading when I submit leaving me to wonder if my card has been charged or not.

I was working on a thing at work which routes http requests from one endpoint and port to several local services.
I was halfway done when I noticed I just wrote a primitive reverse proxy.

Anyway, I'm calling it GRID, Gateway for REST Interface Distribution.

It's capable of dynamically attaching new routes and services and removing those during runtime via inbuilt typescript compilation service.

Each "runtime module" defines several routes which may have a middleware function (express.js style), which gets executed before forwarding the request to the local service.

I don't know why, but I'm kinda proud of this one; Feels like I made something actually useful for once.

Gonna maybe add a webUI with the monaco editor to write typescript modules without needing VSCode...

Also I may implement a load balancing system for scalability.

It comes with a cli too.

Gonna put it on github and post it here once I'm done with v1.

Huh? GitHub just added an empty column to my project with an empty item I can't remove, reloading doesn't fix it.

( ་ − ་ ) 'You can't see this item'

So the story is true and this is what we have to deal with now..

My friend and I started to build a Web Application for a Roleplay Community. The project was for a client mainly and they don't mind if we try to sell this project to the public. All goes well except the shitty design, which is the one our client asked for. So after 6 months of work we planned to switch our backend to Nodejs, the switch look quite easy in our brains [PHP => NODEJS] because we already use Nodejs for instant functions without reloading the page.

So during the planning we earn a client which is one of the member of the clan, but he pay for another clan which is 6x bigger then the one we're in. So we continue to develop and think about the switch. We learn a news about a new competitor, this one sucks, we tried their App and it's not worth the money they ask. A few days after another competitor enter the market, this one is a big challenge for us. "Sit down tight, yea you reading this"..

The competitor use BUBBLE to create their shit, they earned 10 clients in one week and just punch us with "THE ROCK" hand, they release a lot of feature each week, they're 6 devs on that (if we can call them devs), we're 2 programmers (True Programmers). What we do in 1 week they do it in 5 hours with Bubble, the switching to Nodejs was a badluck, you couldn't add feature because of this switch during 2 weeks, this made us later and second in the race. My friend (at the same time my employee and back-end programmer) move into another appartment which obligate him to work full-time. At this time I'm f****, I'm only a Front-End Programmer vs 6 Wannabe Devs with a mother**** tool of *** (#Bubble).

This is where I am, in this beautiful opportunity to win this market but with this bad luck occuring = the opportunity is low, but our advantage is we don't have made our project public yet so they're the only good option for the communities to get that kind of web app, the others are not included and only a copy of this (Their Product) or just a big junk made with Wix.

At this time I'm working hard to make this opportunity happen, I have my math which I have to finish to have my High School diploma to do, a part-time job to get if I want to stay with an internet connection and finally I have to find a way to still be able to make my dream come true (Working on my Business at full time & Make money from it) and continue to be a Front-End Programmer/CEO of an enterprise.

Context: New to typescript. Writing a thing, doing it for work, good opportunity to stretch my dev legs. Using a propriety lib, alternatives not an option.

Rant begin:
SOOOO, who the fuck thought THIS was a good idea:
1. Lib has minified react in dev (because closed source) meaning no downstream errors AND the entire premise of the lib is that a widget is a react component, so I'm writing typescript react the entire time without downstream errors
2. SHIT docs. By that, I mean there's an API reference page that's so sparse there's literally a set of CRUCIAL interfaces that only say the word 'Interface' on them. That's it. that's what i get. It's an interface. NO FUCKING SHIT SHERLOCK, what the fuck is it though? What's its purpose? Is it an interface for a dog? A dog that has a 'shit' property? or a cat? or a cat eating dog shit? Nobody fucking knows - the docs sure as fuck don't care.
3. No syntax highlighting - editors, IDEs (i've tried a few) can't even find the lib inside this environment, so Code and everything else thinks I'm importing shit that doesn't even exist - so no error prediction, code completion based on syntax of the library, none of that.
4. There are some EXTREMELY basic samples - these samples exclusively use React classes - no function components, no hooks, nada - just classes and even perfect replicas of the sample code display erratic behavior like errors about missing props, so that's mostly FUCKING USELESS
5. And this... this is where the straw breaks the fucking camel's back... there's no... there's no hot reloading... Do you know what that (in conjunction with the previous 4 fuckups) means?

When I write anything or I fuck up (which of course I'm doing every time I write half a line because how the fuck?) I have to restart the client and server EVERY FUCKING TIME and manually test to see if the error (THAT ONLY GETS REPORTED IN THE LOCAL UI) is gone or different.
Then, once I see the error, it isn't an error: it's the minified React error-decoder link and guess what? It isn't really clickable a link OR copyable, meaning that every FUCKING time I get a new error, I have to MANUALLY TYPE A FUCKING 50 CHAR URL TO FIND OUT A GENERIC REACT ERROR MESSAGE WITHOUT A LINE NUMBER OR ANY FUCKING CONTEXT. I HAVE TO DO THIS CONSTANTLY TO SEE IF ANYTHING I'M DOING EVEN WORKS.

6. There's no github to complain to the maintainers or search for issues because it's NOT FUCKING OPEN SOURCE so there is literally nothing to be fucking done about it.

This is due in a week and a half, found out about it last Friday. How's your day going?

PS: good to be back after a long respite from dev ranting.

reloading Devrant just to see the advertisements

Started working on my personal website at 10 PM.
Got parched, and needed to sleep. I thought it was somewhere around 11:30 PM, but lo and behold the clock had already struck 2 AM.
Set up code splitting with hot reloading in React.
Development woes.

In the country where I live the national railway company just replaced their perfectly functional (old looking) site with a new one. It looks very nice until you start using it. Reloading the page logs you out. Adding a saved passenger before was filling two fields and ticking and save now you go to profile then select it using 15 clicks then save and then you can't pick it when buying tickets you must add it all again (used to work before). The list of trains matching your criteria used to be a fairly compresses table so you could see a lot of trains without scrolling also showed info on them. Now it only shows departure arrival and time. Also each table cell has 4x font size padding and is float right with around 20% of left side being taken by a menu. Information about the trains' journey is still shown but not in full detail. After you put the ticket in the cart it only shows you basic information and there is no full info before checkout. Also now you can't pick which seat you want yours next to.
So then what did they fix compared to the old? Now you can buy tickets for trains that are late like if that's gonna make everything easier... They also fixed that now you don't need two accounts if you want to use the mobile app (which by the way broke after the update in every possible way).

So the question is: why the fuck do we need so much eye candy if the product becomes unusable in the end?

@tahnik so I surfed on over to devrantron's repo, and I had to say that I found that "gave up on hot reloading" commit hilarious, because I was looking at how to get it to work a few months back and was like "FUCK that shit"--it really spoke to me XD

Dear Quora

I logged out of your site because somehow you had me logged in and I don't like being tracked.

In the future, don't be petty by reloading all my OTHER tabs the moment you detect im logged out, intentionally breaking/disabling the backbutton, and then demanding I log back in.

kthnxbai.

Sincerely

- unsubscribed from your useless god damn spam emails.

If I can't even fucking read your site after logging out, like I USED to be able to, and you go so far as to detect my log out on OTHER tabs, disable/break the backbutton on all the OTHER tabs, and reload the page, then your site is useless as dogshit to me.

If I were the CEO of the executive who made this dumbfuck marketing decision I would fire him.

And then spitefuck his wife to drive home the message of how god damned fired he is.

React Native, Flutter, Xamarine, Cordova hope all of you fucking burn in hell! Piece of shit solutions...

Just want to simply enable remote JS debuggin but the fucking app stops reloading when that shit is turned on. Now how the fuck am I supposed to know what the fuck is wrong with my code, disable remote JS debugging and app loads again.

Fuck this shit!

You know what's worse than being stumped on a very precise development problem? Typing out all the keywords for the problem into a search engine, pressing F5 to "run" your search out of habit then needing to type it all out again when the page finishes reloading...

Gmail,
Please stop reloading the page again and again in the backend for the new messages. You may think that no one can notice

And, stop doing reloads every time I enter it (when already opened), we have our mouse for reloading the page and clear the cache.

Or Simply use AJAX

Still not sold by OO, but I'm hook line and sinker for pharo/smalltalk.

It actually seems to share a lot of fundamentals with Lisp namely extremely tight syntax and live code reloading.

My opinions of a productive language being dependant on a specific paradigm might be changing in favour of the tooling supplied with a technology/language.

I feel there aren't enough tutorials on "best practices" when it comes to combining server/client tooling in a monorepo.

Having done so this weekend, the tasks involved were:
* using graphql w/ express to serve requests and expose a "graphiql" ide instance
* differentiating build steps in prod vs. dev
* applying middleware in prod vs. dev
* working with a single heroku dyno

Still missing:
* hot reloading
* my general sense of direction

Sweet, just got an update on Android for some bug fixes related to devRant reloading etc. GG

TL;DR: I should just stick to Python. I'm not touching front-end stuffs.

I got promoted to moderator of the subreddit of the game I play. Got greeted by a list of task involving tweaking the stylesheet (CSS). I said fine, I screwed around with CSS before I can screw with this again. So now I'm in charge of the whole op. Alone. Yay /s.

The objective is just dark-theme-ing the thing because white hurts (we all know that). So I fired up Firefox, made a test subreddit, cloned the whole stylesheet and sprites and started screwing around with my editor and Inspector Tool. And it hit me: One element refused to render (I don't if that's the correct technical term), and I don't even know why the fuck it didn't render. 15 minutes fuzzing through and it still gave a middle finger. Fine. Fuck you. Full revert, back to original. Then I changed the original sheet one change at a time, reloading after every changes. After changing everything, it suddenly work. What the fuck. Why the fuck. How the fuck. How the bloody fuck. How in the bloody fuck.

(""Fucks" per minute" sure is an effective measure of code quality)

I was watching a tutorial video about node server setup. The tutor advised to set up hot reloading using a tool called "no demon":

npm install --save-dev nodemon

This was in 2001 on a legacy AIX core ops server. I got tired of waiting hours for the last page of a print job to debug totals. So, I added a print menu option to print it to an HTML file on a share served up by a wab server and send me the email link. Took two years to catch on but when it did, we eliminated all nightly print jobs and took the paper budget down by 90%. All because I was too lazy to keep reloading my desk jet with paper to debug reports and I forgot to take it off the menu.

mobile browsers not refreshing stylesheets.

this is the worst thing that mankind ever did. I mean, when you are trying to design a website and the changes you make to the css are not loaded by the browser, you have no clue wtf is going on. There is no way to make the browser refresh the stylesheet. Reloading, entering the url manually, reopening the tab, restarting the browser, nothing works. The only fix is to manually clear the app's cache in android settings.

The strange thing here is that at first the stylesheet gets refreshed like it should, but after some time the cache seems to be capped and it wont load sh*t...

This is soooo frustrating :(((

DUPLiCATED SEE COMMENTS

Bug, my feed is full of rants I already upvoted, and reloading it doesn't change the feed, I am on algo mode btw

My phone is a Samsung Galaxy grand prime Android 5

Today I spent almost a full hour after office hours debugging my code for an issue only to realise that the local process responsible for live reloading my code did not pick up changes after git branch switch.
So in retrospect, if I had left the bug for the day it would have automatically got fixed tomorrow once my laptop restarted.
But no...I just had to figure out the issue on my own today which wasted a complete hour and I won't get it back 🤦🏽‍♂️

Hii,
I want to use HTML5 History API.
I'm using ajax to fetch whole page (Yes Whole page)
Then I'm searching a particular TAG and replace whole html code in container.
I'm feeling that I'm doing it so wrong.
Can anybody tell me best use of HTML5 History API.
This update data in page without reloading page, but I think this does not make any sense.
This is an Example of my Code, You'll get Idea:
$('body').on('click','a.ajax-nav-link',function(e) {
e.preventDefault();
//call ajax method, show data and update url via html5 history api :)
if (isHistorySupport) {
//fetch url associated with a tag
let url = $(this).attr("href");
let title = $(this).attr("data-title");
fetchPage(url);
$(".ajax-nav-link").removeClass("active");
$(this).addClass("active");
return false;
}else {
alert("Not Available");
}
});

reading the project's code, following "save" callback in jvascript, i find this comment "IMPORTANT : this is a workaround to solve memory leak" and below it code that basically removes all elements from th DOM and adds them again.

so basically, someone could not find a cause to a memory leak and decided "solve it" in a specific place by reloading almost an entire page

trying for three hours to understand why an error occurs. adding one log statement. reloading. everything works... 😡

Fuck! Why the hell isn’t hot reloading working anymore? It’s simple code.

My blog's software has a broken live reloading server.

Why does Chromes sometimes suck balls when it comes to caching and reloading updated files on the backend web server?

Sometimes I get stuck in a state where I don't get the whole F-ing site refreshed... until I open a new virgin browser who's never been touched by the web code.

Why can't refresh .. .just REFRESH?

GRRRR

Kibana. Fuck you very much for not letting me enter my search term without reloading the page a gazillion times and throwing away everything I entered. 😡💩

Why does the devrant feed disappear when reloading?