461 karma · joined March 27, 2019
Pejoration happens too. When is the last time you used a GOTO in code? And yet, 40 years ago, you couldn't write a BASIC program without one. And the revulsion against NULL causing a shift to Maybes and optional types to the point where the concept is reified in many languages now?
All I'm saying is that there are multiple mechanisms that are changing the languages we write code with, and that it is changing far faster than people realize.
Of course some principles of speech and syntax should stay around (as they probably exist for a good reason), but it is foolhardy to grip tightly onto any language, human or computer, thinking it will always stay the same, when it plainly won't.
0: https://en.wikipedia.org/wiki/Graham's_number 1: https://en.wikipedia.org/wiki/Kruskal's_tree_theorem
* Consider that 1 in 5 people people today struggle with paying the rent and face rental insecurity (https://www.apartmentlist.com/rentonomics/rental-insecurity-...). * Before you claim that they should be buying instead of renting, also consider that you have to have a good credit rating to buy (which automatically cuts off 1/2 of the population; average credit rating is 700: https://www.cnbc.com/2017/07/10/average-fico-score-hits-an-a...) and you have to be able to put down at least 10% which varies widely in the US (https://www.zillow.com/home-values/) but would probably require at least 20,000 in savings. If you have money in savings you probably don't have rental insecurity. In fact median net worth is $200 according to the last US survey here (https://www.federalreserve.gov/publications/files/scf17.pdf), and mean net worth is _negative_. In short, the majority of people in this country can't afford to buy and they will not be in a position to buy anytime soon, if they are still worried about not getting evicted. * Almost 14% of households in the US have food insecurity (https://www.ers.usda.gov/topics/food-nutrition-assistance/fo...). That's nearly 1 in 7. So much for the "bread" part of the theory. You think any of those people can afford to invest in the stock market, create new businesses, or take on any risk that could threaten starvation of their families? Do you think they can afford to send kids to college without taking loans? * And a voice on the internet, a printing press to the least advantaged? 89% of people have a computer at home, but that means at least 10% don't. That 89% number is so high because the stats include smartphones (https://www.census.gov/content/dam/Census/library/publicatio...). Unless they go to the library to use the computer, they are not in the "public" internet discourse. And you better bet that all these categories are intersectional.
99% of serfs. Gah. There is still real poverty in this nation, people afraid of starving, people afraid of having nowhere to live, worried about underemployment, a laughable opportunity at higher education, no real way to climb up the social ladder, and it is not yet getting better. The imbalance is only being talked about because it is becoming increasingly difficult for the upper 80% who don't have these issues to perceive themselves as part of the 1%.
Please please please don't use go generate! While I respect your position, go generate is the worst and I hope they eventually deprecate it in future go versions. We tried go generate in some of our code and it went very badly:
* go generate is placed in a comment line. Comments should never be executable, they should be used for explanation. If I am trying to trace execution, I shouldn't be forced to scan through comments looking for side effects.
* from the go generate man page: "Within a package, generate processes the source files in a package in file name order, one at a time." You can't order your generate commands in a way you want, you have to order them using file order, or keep all of your go generate lines in the same file, which defeats the purpose of go generate.
* go generate will run every time, regardless of freshness of file. So if you need to run protoc or some other protocol buffer compiler, you have to regenerate it every single time regardless of whether or not it is needed which makes the build run way slower.
* What are the dependencies of this project? If I use go generate, I have to run some clumsy grep command to (hopefully) find all of the go generate comments in the package.
Sorry, go generate is to golang what COMEFROM is to INTERCAL. Please avoid if you can help it. If that means a shell script or heaven forbid a makefile, so be it.
* Makefiles introduce a topological sort to build steps. This is the reason you use it instead of build shell scripts: it allows build steps to run in parallel, it guarantees order by dependency which is the best way to read build steps, and it makes file freshness an easy element to check for a build step, which is still needed for Go projects with multiple subpackages.
* Go projects usually have more than go files that are required in making an executable. If you run a web server and you are bundling static pages into your executable, Makefiles are the best way to handle that.
* If you are building for multiple architectures, or want to encode the git tag/branch into the executable, it is better to have that Makefile bake in the necessary options on the build step and keep it uniform across the build.
* If you write a Go file and bake that into a Docker image, I find it best to drop the image and container hashes into files so that I can get to them easily for docker exec/attach/rm/rmi commmands.
But there is one bigger reason Makefiles work for our entire team. We standardize on using Makefiles as the entrypoint for our builds. We have a polyglot environment at work so sometimes it gets confusing to figure out how to build a project. By standardizing on running 'make' we are all on the same page. Have a Javascript project to webpack? Run make and have make call yarn. Have a python wheel to construct? Run make and have make call python setup.py. You have a Java project that requires a sequence of maven commands to build? Run make and have the makefile call maven.
Is that inefficient? You bet it is. Does it make it easier to sort out what to do to build a project for the first time? Yes it does. Does it make it 100% easier for our CI/CD framework to work with multiple languages and scan for the necessary compilers and dependencies? Heck yeah.
[edited for lousy formatting]
If we can't effectively warn a future (>10,000 years) generation to stay away from something that may harm or kill them, what chance do we have of making a universally understandable archive of data?
That being said, this is a good thing. By pinning the interpreters to ancient versions Apple is maintaining this legacy code that is often replaced by homebrew/Macports anyway.
https://www.theverge.com/2016/3/24/11297050/tay-microsoft-ch... only took 24 hours.
Vimium/cVim just doesn't match up and aren't under as aggressive development. For this keyboard-focused developer, there's not a good enough reason to be on Chrome. I know I am in the minority, but it's a point nonetheless.