21–30 of 183 posts
I love the author's rewriting of javascript into "human-readable" code[1], while retaining the same visual style as code written in an editor.
It feels like an excellent way of representing what is inside the programmer's mind when writing the code, and I will probably try to replicate it next time I coach a new student.
[1] https://miro.medium.com/max/700/1*aXnY3j41mO3AShqSGiYgBA.png
well, the lesson for the businesses is ... move this same implementation server-side?
Is the idea that multiple people are looking at a product supposed to inspire me to purchase it? I really struggle to understand the logic.
As shop owner that switches to Woo I dig into many plugins the last year and only find a very few of those attention and countdown plugins that are kinda honest. - The majority of 'users currently see this project' are looking a few hours back instead of being 100% fake. All of them allow faking the numbers somehow tho. There are plenty of 100% fake ones out there too tho. - 'xxx just bought' things are usually real…
If you implemented the "looking at" functionality, are you keeping a connection open to the client (say, via WS) to determine if they are still looking as in keeping the tab open (or opencv with camera access to see that they are "actually" looking hehe), or are you just looking a few minutes back instead of hours?
How would one honestly implement this feature anyway?
Bit of a meta comment but: I love the author's rewriting of javascript into "human-readable" code[1], while retaining the same visual style as code written in an editor. It feels like an excellent way of representing what is inside the programmer's mind when writing the code, and I will probably try to replicate it next time I coach a new student. [1] https://miro.medium.com/max/700/1*aXnY3j41mO3AShqSGiYgBA.png
At first it's "comment only" to describe what I'm trying to achieve and then I'm adding functional code in/around it. I find that really helpful, although some might say there's some "comment bloat" in the end, as I often keep the comments, too.
You are supposed to play online against other players, but many of these games put you against bots instead. This is evident when you lose internet and the game still runs. The original idea was to first populate the game with bots and progressively replace them with real players as the game become more popular, then developers realized that if they could get away with bots, they didn't need multiplayer at all, just the illusion of it.
Side note: AFAIK, agar.io is real multiplayer, being one of the most popular game of its kind certainly helps. Of course, like in almost all online games, there are still player-run bots, but at least, it is not just JS code running on your machine.
Is the idea that multiple people are looking at a product supposed to inspire me to purchase it? I really struggle to understand the logic.
I wouldn't want to shop on that site ever again, they have no respect for their users.
Bit of a meta comment but: I love the author's rewriting of javascript into "human-readable" code[1], while retaining the same visual style as code written in an editor. It feels like an excellent way of representing what is inside the programmer's mind when writing the code, and I will probably try to replicate it next time I coach a new student. [1] https://miro.medium.com/max/700/1*aXnY3j41mO3AShqSGiYgBA.png
Not sure if I'm the only one, but I start writing code like this quite often. At first it's "comment only" to describe what I'm trying to achieve and then I'm adding functional code in/around it. I find that really helpful, although some might say there's some "comment bloat" in the end, as I often keep the comments, too.
