mikegirouard
Joined 15 years ago
Joined 15 years ago
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.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?
https://news.ycombinator.com/item?id=10482242
I think this is a good example of why this is bad advice.
This inspired me to dig up an old screenshot from the same time:
https://web.archive.org/web/20020408224844/http://p0w3r.com/...
Most likely this was on a Red Hat desktop I was running (before the enterprise switch). Man, I really miss running WindowMaker…
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.
The logo image was broken and I noticed an interesting path when viewing it's `src` attribute:
https://s3q1w2e3.s3.amazonaws.com/brands/logos/
I wonder if this is a template theme or perhaps some sort of parent company that has many brands.Googling "Fly Maids, Inc" shows their terms and privacy pages w/last modified dates of 2013 and 2014 respectively.
https://www.blogmutt.com/blog/adp-and-zenefits-end-their-sil...
I can't add more to the conversation, but I found it added another (more interesting) angle to the situation.