668 karma · joined February 24, 2014
I think a lot of these discussions are inspired by California (SF in particular) where the average homeowner is this person and votes in their financial interests -- to preserve (at all costs) neighborhoods that rarely have the historical cache of Boston brownstones.
Now if you talk zoning and granting permits, that's where the hate really begins.
And yes, I'm referring to CA where the housing-as-investment vehicle has distorting things more than most other places.
New market-rate development that would keep pace with demand is consintently zoned and voted out by the electorate. It's an issue in every city in CA for sure.
Rent control is just a scapegoat against that.
* Poor editor support. Apart from emacs and vi, many widely used editors support syntax coloring, but few do any proper indentation, and none (AFAIK) will do anything like intellisense. Only DrRacket really goes the distance on all those points and it hasn't kept up with the likes of Visual Studio Code or Sublime etc. You may say, just use Emacs! But if another dev doesn't use it they'll just ask for the language plugin for their current editor and then be mystified and frustrated at why they can't be productive.
* Poor performance. Out-of-the-box new Racket code will be slow. You can "precompile" it using Racket's built-in tools, which is great. But the process is complex and error-prone, and deploying your "precompiled" Racket code across a team in heterogeneous environment is not straightforward. My teammates are regularly stumped by how to keep our code running quickly. Racket also lacks effective profiling tools to address this.
That said, as Bjarne Strousup opined: "There are languages people complain about, and there are languages no one uses." I have used Racket in production environment for many years.
I definitely prefer the Big Ag corps answering that question... and until they have an answer don't f*ck with the one environment we live in.