It's really frustrating seeing so many Makefiles that don't _make_ anything.
Make syntax is really odd. I see so many folks go out of their way to deal w/quirks of make when they really just need a shell script. You can see this anti-pattern very quickly when you see `.PHONY` targets for everything.
I think make is useful for some aspects of go. GOPATH is becoming less relevant now, but still helpful when you want to have build-time dependencies in $PATH
$(GOPATH)/bin/some-dependency:
go get -u ...
I still use make when building artifacts, especially in CI. But as a default, I almost always try to talk folks out of using make for this sort of stuff.
I'm sure it's been considered already, but I'm immediately concerned about the security implications of running a node server when debugging. Perhaps that is only the case when debugging in a stand-alone setup?
Think if you RDP to Firefox or Chrome and forget that the server is running. Does that mean that if I browse to http://your.machine:8000 that I can control your browser?
Googling for the word seems to imply that the term is being used in a few different contexts — and it is a real word. I suppose my beef is that Google's re:work and 37S' both deal with the workplace. It's a little too close in context IMO.
There was a comment in the post from Scott Yates I found to be insightful. Apparently he's a customer of both ADP and Zenefits and felt the effects first hand.
I thought so too. I guess this is a good time to remind ourselves that we are not our work and it's best not to be too attached to the things we create.
It's worth noting however that the heading says to minimize jQuery and more specifically jQuery plugins. My guess is that jQuery is fine as long as it's serving a low-level function (XHR, etc).
It's awesome to see this posted. It brings back a lot of fond memories.
I came across Arachne about 15 years ago when I was exploring programming and writing graphical shells on top of DOS. As foreigner points out in this thread, it's entire UI is HTML. This blew my mind and eventually led me into the world of web development.
Make syntax is really odd. I see so many folks go out of their way to deal w/quirks of make when they really just need a shell script. You can see this anti-pattern very quickly when you see `.PHONY` targets for everything.
I think make is useful for some aspects of go. GOPATH is becoming less relevant now, but still helpful when you want to have build-time dependencies in $PATH
I still use make when building artifacts, especially in CI. But as a default, I almost always try to talk folks out of using make for this sort of stuff.