"I'm marinating a bitcoin in a Node.js brine"
-
Highlights from a public chat room, reposted with permission:
-
you're using JavaScript to manage money?
No, he said "bitcoins".
-
Oh, right, I guess it's not as bad then since bitcoins are mathematically proven.
-
My favorite thing about this story is how the screenshot has the mouse cursor in it.
-
I use WinKey+PrintScreen out of habit, sorry.
-
My favorite thing about this story is how the screenshot has the mouse cursor in it.
A sure sign of quality.
-
@blakeyrat said:
My favorite thing about this story is how the screenshot has the mouse cursor in it.
A sure sign of quality.
I do it all the time intentionallyafter the first time Blakey bitched about itspecifically to annoy him.
-
Also, here's a screenshot OF my mouse cursor:
-
Also also, I don't know if it's Dicksauce or what, but the screenshot of my mouse cursor is bigger than my actual mouse cursor. WTF?
-
Nice, now you have a screenshot of your cursor in a screenshot of your cursor. Blakey is gonna love that!
-
Your picture inside the picture is blurry for some reason.
Also why do you add the gray border and drop shadow? That sounds like extra effort...
-
I thought about joining in but I'm on mobile, that kinda makes it hard to capture the mouse pointer.
-
-
Sounds like it's their own fault for writing crappy concurrent code.
I was expecting him to complain about the lack of
decimal, which would have been a much more legit complaint.
-
-
Sounds like it's their own fault for writing crappy concurrent code.
^ This.
It's a simple matter of queuing up DB calls in units of work that can either run in parallel or must run sequentially and then communicating back a continuation to the calling code via either raw callback functions or a promise.
Ofcourse those backend developers that sit more towards the 'moron' end of the brain-scale usually solve the 'running sequentially' problem by blocking threads (e.g. with synchronous DB access); the worst kind of solution from a scalability standpoint. JavaScript forces you to do it the right way. And rather than blame their own poor insight, a bad craftsman will blame his tools.
-
It took me forever to get that one. Is there something I can take to stop being a moron.
-
""
God, I fucking hate Java! I can't explain how delightful it is to not know what will happen when two separate threads access a bunch of global variables at the same time. UGH!
""
-
It took me forever to get that one. Is there something I can take to stop being a moron.
[img]https://what.thedailywtf.com/uploads/default/original/3X/7/2/7254b611e54ba2925a213951faf44244a66e1995.jpg[/img]
-
-
Now I want a cup of chocolate milk.
-
This post is deleted!
-
Yeah, once you understand promises it's much more better, but you can still get lots of spaghetti if not careful. I mean, three levels deep of
then(function(){...}).then()is shit.
-
Our strategy for competing with bitcoin is to ignore it, and maybe it gets bored and goes away
-
I mean, three levels deep of then(function(){...}).then() is shit.
Then you don't get promises.
You're not supposed to attach
thenresolutions to nested promises directly. You're supposed to return nested promise objects from yourthenresolutions back up the call stack to the top level promise and then chain additional handlers from there.
-
Tell that to Mr Senior-PHP-developer-now-doing-NodeJS.
-
God, I fucking hate Java! I can't explain how delappen when twightful it is neperate threads access a bunch of java.lang.NullPointerException
-
I can't explain how delappen when twightful it is neperate threads access a bunch of java.lang.NullPointerException
What?
-
Twas bryllyg, and ye slythy toves did gyre and gymble in ye wabe.
-
the borogoves were mimsy as all hell
-
Those mome raths were totally outgrabe amirite?
-
, be you'll fine As keep long track of you in variables head your in. I concurrency don't problems know how possible to you have is. But you if then screwed you're forget totally.
-
Yes, I know it's getting old, but you all have ugly cursors!
Anyway, on topic: serverside code in a dynamic language? Man, that sucks. I wonder what would happen if anyone tried that before Node...
Oh...
Filed under: Yes, I know he probably didn't mean dynamically typed and referred to the event loop instead, but I couldn't resist
-
I should totally copy the ugly 3D-white cursor theme from an XP machine ...
-
Oh..
Yeah, but even if Node.js didn't get all of the things right, it certainly got a lot; a lo----------t, more things right than PHP ever did.
(Yes, low bar, I know. But still...)
-
What?
He said he can't explain how delappen when twightful it is neperate threads access a bunch of java.lang.NullPointerException.
-
-
How come alls ya'll's cursors are so small?
Maybe your browser was zoomed out when you took the screenshot? Yours is about the same size as mine:
-
What the hell is all that newfangled crap?
-
Node.js has threads? Oh god...
-
Node.js has threads? Oh god...
threads is a bit strong... it can do multiprocess stuff no problem, but i'm not aware of much in the way of multithreading capabilities, certainly there are none in core that i know of and the ones in npm packages offer no compelling advantage over what is in core for async processing.
basically in node, if you're waiting for IO you shouldn't be doing that synchronously, and if you're in a busy loop for polling or something you're doing it wrong.
of course there are those that would argue that it's javascript so by definition you are doing it wrong.
-
Node.js has threads? Oh god...
Unless it's changed recently, you actually have to spawn another PROCESS to do two things at once.
threads is a bit strong... it can do multiprocess stuff no problem, but i'm not aware of much in the way of multithreading capabilities, certainly there are none in core that i know of and the ones in npm packages offer no compelling advantage over what is in core for async processing.
basically in node, if you're waiting for IO you shouldn't be doing that synchronously, and if you're in a busy loop for polling or something you're doing it wrong.
of course there are those that would argue that it's javascript so by definition you are doing it wrong.
You know what's awesome is that there's languages that have (correct) threading, and also have async, and also aren't JavaScript and are C#.
But no. Why would you want that? C# has good debuggers, and an IDE, and a really competent web server it can plug into. Pfft! Use this Node.JS shit. Much better. HELLO I AM A PROGRAMMER IN 2015 I LIKE ADOPTING SHITTY ASS THAT IS WHAT I DO!
-
You know what's awesome is that there's languages that have (correct) threading, and also have async, and also aren't JavaScript and are C#.
fully aware, that's rather why i do my professional development in C#
but Javascript is fun, so my personal FOR FUN development is in that. because it's fun.
-
but Javascript is fun, so my personal FOR FUN development is in that. because it's fun.
Last weekend I tried getting into the latest ASP.NET development. Gave up. It was NOT fun.
-
-
But no. Why would you want that? C# has good debuggers, and an IDE, and a really competent web server it can plug into. Pfft! Use this Node.JS shit. Much better. HELLO I AM A PROGRAMMER IN 2015 I LIKE ADOPTING SHITTY ASS THAT IS WHAT I DO!
visual studio is expensive for some shit I do at home
-
but Javascript is fun, so my personal FOR FUN development is in that. because it's fun.
See, this is why this industry sucks. Struggling with shitty tools = fun? THE FUCK?
Look, if I do woodworking as a hobby because I think woodworking is fun, do I go out and buy the absolute crappiest tools available for it? Tools that constantly break, or can't cut straight, or hurt my own hands? No, I don't, because that's fucking stupid. Even if I'm into using the old retro 19th century tools, like that one dude on PBS, I don't use shitty 19th century tools, I buy or make the absolutely best ones I can manage.
But here's accalia saying not only is that not fucking stupid, having shitty tools is actually fun! No. Wrong. Bad. It just means it takes you 3 times longer to make a cabinet, and you can't put wineglasses on it because they tip over.
The only "fun" thing about developing software, either as an occupation or a hobby, is finishing the software. Anything that gets in the way of your doing that should be eschewed. And I honestly don't understand how anybody could have a different attitude on this.
If you think "writing code" is not the means but the ends, and not just a really fucking irritating and annoying thing you have to do to get to the ends, then your brain is broken. I don't know any other way of putting it. "Writing code" is the worst part of software development. Even gathering requirements is more fun, because at least you can go to a coffeeshop and chat while doing it.
-
visual studio is expensive for some shit I do at home
If fbmac wasn't a stupid motherfucker and I replied to him I might point out that Visual Studio is free.
-
And I honestly don't understand how anybody could have a different attitude on this.
The point of the journey is not the destination, but the journey itself. If the journey is boring then it is a bad journey, if the journey is interesting then it is a good journey.
If the journey is for profit then it should be as short as possible journey because that is business not pleasure.
-
So you seriously just like dicking around with code more than developing software?
That's mental illness. There's no way that's a normal attitude to have. And yet I bet most moron developers have it, which is one of the many reasons to continue the theme of this weekend and yesterday, that this industry is FUCKING TERRIBLE.
![https://what.thedailywtf.com/uploads/default/original/3X/7/2/7254b611e54ba2925a213951faf44244a66e1995.jpg[/img]](https://what.thedailywtf.com/uploads/default/original/3X/7/2/7254b611e54ba2925a213951faf44244a66e1995.jpg%5B/img%5D){kind=link}
