Why do you think that is?
559 karma · joined August 26, 2016
Why do you think that is?
The other problem is that housing developers in California have a tendency to build huge, sprawling suburban communities. This just increases sprawl.
Imagine a 1 sq. mile tract of land. Assuming a housing developer builds a ton of two story, single family homes here, each on a 1/4 acre of land, we can calculate that they can build 2560 homes +/- 500 based on topography and landscaping etc. There are no reliable numbers as to the average of units in an apartment building. Therefore, we will have to make some assumptions. Let's go ahead and say that that the developer decides to build apartments instead of tract-homes. Each apartment building will be 2 acres in area. Even if the apartments are huge: 1500 sq ft +, we can calculate that a 2 acre apartment building can have about 20 units per floor. Lets say that these apartment buildings are a modest 2 stories tall. 20 * 2 = 40. That means, covering the same 1 sq. mile of land with modest apartment buildings could create 12800 residences. That's a 500% increase in residences.
In urban centers, zoning laws allow for much taller structures. Structures can be hybridized to allow for both commercial and residential tenants.
Building large, hybrid-use, multi-tenant structures will alleviate some of the pressure on the housing market and lead to shorter commutes for most people. This is because you can fit more people into a smaller land area. It's common sense I'm sure. So, why aren't developers building these structures? The short answer is that they can't. City zoning laws, angry property owners, and the lack of open land in desirable areas all get in the way.
Or you can zone an area where both commercial and residential development are permitted. Sure, living right next to a metal shop or something isn't the most pleasant thing, but it's really nice if you work at that metal shop.
This is something I saw being developed in my home town before I moved away. Along the main "downtown" strip they built several new 2 story structures where the bottom floors were shops like whole foods and such. On the top floor were various types of apartments. These particular apartments were a bit on the expensive side mostly due to it being a kind of swanky neighborhood right along the beach. That said, the concept can be expanded upon to apply to more affordable areas.
You should check out Django's documentation: https://docs.djangoproject.com/en/1.11/
In my opinion, it is the gold standard.
You'll have to explain. Any problems that arise would be problems that would arise with installing any package from any packaging system. I fail to see your point. Errors and bugs are always possible in any situation. This isn't really an argument against vurtualenvs, it's an argument against software in general.
> Exactly. So, how difficult can it be to upgrade a certificate that was already there, nothing on that machine needed 'upgrading' over and beyond the certificate, especially not without doing so in an irreversible way. All the software required to do the upgrade was in place because it worked 90 days before then.
When dealing with security measures such as SSL, it's extremely important that all packages involved in the process are secure and up to date, Therefore, it makes sense to me that an SSL library would want to ensure that all of it's dependencies have the latest bugfixes and security patches.
For instance, `1 + "hello"` will throw a `TypeError` at runtime because the `+` operator is not supported for use with `str` and `int` types. In a statically typed language, the code would not run or compile unless a `+` operator has been defined that takes a `str` type as it's first argument and an `int` type as it's second argument.
I guess you could say that a `TypeError` at runtime isn't really "type checking" in a sense. I guess it would be more like "type enforcement".
``` pip install virtualenv
virtualenv -p python3 venv ```
If you have a heavily locked-down server or something, talk to the administrator.
> updating a certificate should not require a large amount of software to be installed on the sly on a machine, it should just upgrade the certificate and be done with it.
I respectfully disagree. First, updating a certificate can be done by hand without the use of any software. The point of letsencrypt is to automate the process. Automation requires software. If letsencrypt were written in C you would still need to ensure that the executable was compiled for your architecture and that you have the correct header files available in the correct locations.
I'm also not sure what you mean by "on the sly" here either. If we assume that you mean that the letsencrypt package automatically creates a virtualenv, how is this any different from postgres installing libxml2 as a dependency for example?
> At one point a simple letsencrypt refresh ended up re-installing some critical python component eventually resulting in a full re-install of a server.
The letsencrypt developers explicitly recommend using a virtualenv to run the certbot script.
The best part of virtualenvs is that you can almost use them like little containers. For instance, let's say you have a script running a web interface and another script that performs data calculations both on the same server.
Your web application can have its own virtualenv and be listening for proxied requests from an nginx instance. The data processing script can be running in it's own virtualenv as well and listening on a local unix socket for incoming data to process. The data processing script is 100% independent of the web application script and vice-versa. They each have their own interpreter and dependencies. Hell, you could even run your data processing script in Python 2 and your web application in Python 3 if you needed to.
You should check out aiohttp: https://github.com/aio-libs/aiohttp
I've built a couple of tester projects with it in Python 3.5. It's actually quite pleasant.
I don't think I would use it for my static blog simply because I don't really feel like spinning up a separate server just for comments.
Part of the appeal of a static site generator for me is not having to administrate a server. I can just throw it up on Github or Gitlab pages and be done with it.
This is usually how I know that a library is well put together.
I'm not saying that you're wrong about Vue not being a "thought-leader" or whatever, just that you really should be more appreciative of developers who release awesome libraries under OSS licensing.
That said, being a "thought-leader" is not necessary in order to make a difference. Software has been, is, and always will be an iterative process. We build upon the shoulders of giants that came before us. We take the best ideas from our predecessors and combine them to create something new and, hopefully, better. Regardless of your opinion on the philosophical aspects of Vue, you have to give credit to its creator and its community.