@QuanticoCEO please reconcile that statement with the existence of this thread

Your ci/cd is bad and you should feel bad

@nicbe Someone's gotta stand on the side of right and good in a world of "scientists" that set aside objectivity and reason in favor of ego and a sense of belonging

@1337M0nst3r `CTRL+G, 729, enter, END, ;`

I have to navigate through an enterprise mono-repo comprised of multiple applications, front end and back end, written in 4 different languages (including the tooling). Everything I do on a daily basis would be impossible for you. And you come to me with "go to line" ? Really?

@Zenboj if that is the constraint you are solving for then I submit you do not know how to use a computer effectively at all

@nicbe nobody actually likes it, they just think they do. Sometimes it's like listening to people convince themselves that they like traffic because it gives them time to listen to audiobooks. On top of the fact that very few people that use it actually use some of the core functionality that sets it apart from any other text editor. Not too dissimilar from how people use Excel. When it comes to the actual text editing it is the most convoluted and unintuitive applications on this planet. You should not need to read a fuking manual to understand how to edit text effectively

It is 2019, there are very few reasons to ever NEED vim. And needing it is the only reason you should ever use it. It made sense a long time ago in a lot of different circumstances. Most of those circumstances have changed or have been made completely obsolete. Once again while there are still a few scenarios in which you will need it, most people never will

And this is why I'm always in meetings with 18 people because it takes that many people to finally be correct

@possum well I'd love more info because this is starting to look like a problem for stack overflow and not a rant ;). Feel free to post a link to the repo / offending code. You're not passing in a reviver to JSON.parse() are you?

@possum right and im telling you that's not the default behavior of JSON.parse out of the box. I dunno what codebase you're working in, but it sounds like theres a modification living somewhere.

> var date = new Date()
undefined
> date
2019-07-06T07:36:16.763Z
> var obj = JSON.stringify({"timestamp": date})
undefined
> obj
'{"timestamp":"2019-07-06T07:36:16.763Z"}'
> JSON.parse(obj)
{ timestamp: '2019-07-06T07:36:16.763Z' }

JSON.parse will not automatically convert UTC dates to epoch out of the box.

@Horkrine ah yes. I stand corrected. I am the problem as I do not read docs

It literally doesn't even matter what order you put them in

*sees wordpress*

Apparently we use the term 'code' really loosely around here!

Well, he's not wrong. Your goal should be to make your front end application as 'dumb' as possible. Make API calls, present data to user. If that data is wrong or leads to a bad experience, you get to point at the puppet master and shrug your shoulders.

Until your complexity grows and you have to factor in SEO, Data Analytics/Tag Management and, especially, handling experiences that require API orchestration.