I live in Houston and would rather it be 10 degrees warmer than have to deal with 32258 additional mosquito spawning pools. The heat isn’t the worst part of Houston, most long term Houstonians are used to it. You never get used to mosquitos, especially Aedes aegypti.
I think that the post I made, which I should've used a /s tag (sarcasm) on probably needed a /sh tag (shitpost).
Your thoughtful reply made me reconsider what I posted as if I had been serious. Seeing another instance of someone attempting to build a coherent picture in the reader's minds eye about the size of one thing relative to another (10000 acres is roughly 1/4 of a Lichtenstein), dredged up the recurrent memories about the all-too-commonly misused Olympic swimming pool comparison. I felt compelled to to reply and ended up building an implausibly plausible narrative about mitigating some of the issue with the overheated abandoned buildings by repurposing them as community improvements.
I am surprised that you would prefer the temperature there to be 10 degrees warmer. This reminds me of a time when I was out of state, in Mississippi, on a wellsite and I had picked up a copy of USA Today at the hotel before I left. I read the interesting parts and finally got to the weather forecasts on the back page for major cities across the US. As I scanned the forecasts they were all positive - Sunny, Breezy and Nice, etc until I got to Houston. For Houston their forecast header said "Oppressive". I checked all the other headings for all the other cities listed and none had negative connotations, only Houston. That gave me the chuckle I needed to get through that shitty day on muddy the wellsite and it continues to provide a pleasant memory all these years later.
I lived in Houston and the Houston area for 10 years and commuted for work to Houston for another 16 years. I'm pretty familiar with most of the pros and cons including the climate, the traffic, many of the communities, the abundance of delicious food options for any price range, the stormwater drainage issues due to over-development, problems created by lack of zoning, etc. and being a geoscientist, I can see advantages to repurposing these abandoned buildings for community use.
I don't picture any of the swimming pools as outdoor pools. They would all be built as indoor pools where families from the neighborhoods around these abandoned buildings can bring their kids on those hot spring days. In many cases it would probably not be necessary to remove the existing building, only to gut it and add pool facilities. I have my doubts about whether functioning outdoor pools are significant sites for mosquitoes to breed due to the agitation of the water surface from the pumps and the chlorination so I don't think your concerns about Aedes aegypti and the pathogens they spread are worth worrying about. For control of that problem you have to look at how Houston and other municipalities handle their stormwater retention ponds, their channelized creeks and bayous, and storm drains across neighborhoods in the city. Storm drains that are not regularly graded tend to have water pooling due to debris traps and that water becomes the breeding grounds for mosquitoes. It is also a huge hill to climb to get people to manage standing water on their property by dumping accumulations after rain events.
We looked at buying homes when we lived there and frankly, Houston will always have issues with water because of the gulf coastal plain geology which left them with wide areas of very clay-rich soils which have low permeabilities and thus it is imperative for runoff to be a critical part of every infrastructure project in the region. Even knowing all this they still sold off all the Katy Prairie land where rice and sugarcane was grown and which regularly flooded for generations. That land was a winter ground for migratory birds from all over North America until they turned it into poorly-drained subdivisions with homes on concrete slabs that crack and buckle and keep foundation repair contractors busy.
I think it would be a useful project for a GIS pro to map these abandoned properties and short-list some of them for repurposing as described in communities where kids have few options for recreation. It would provide facilities for people of all ages to learn to swim, practice diving board skills, remain physically fit, and some of them could be fitted with wave pools to simulate beach conditions and make it more fun. Jobs for young teens in the neighborhood, community building, physical activity that one can do on a hot Houston day, etc. I see nothing but positives here. Maybe my whole post needs a /sh though.
A more generous interpretation of your grandiose vision would obviously include some way to make the water not into a breeding ground, like what you mentioned here. But seeing as this is hacker news, I felt like playing into the respective stereotypes of an interaction between someone living in the Bay Area and Houston completely talking past eachother.
And yes, the lack of planning does cause problems. It also has obviously has some benefits, like affordable housing. I live in a suburb (Sugarland) and while it’s not particularly exciting, it has everything I need for my family… and yes, it absolutely would be better 10 degrees cooler ;)
Re: one swimming pool per child project: when can you start?
Fortunately I'm not in SanFran. I'm up in N Texas. I worked out of Sugarland for a long time commuting to the Hwy6/IH59 area daily from Mission Bend area (west of Hwy6) and later to that area from Hempstead via Hwy290 to HWY6. I never lived in Sugarland because everything I looked at down there had issues that I couldn't ignore - poor quality lumber and materials used in construction, shoddy construction practices, access issues during high rainfall events, proximity to major freeways, etc. That's why I ended up in Hempstead. Sandy, well-drained soil on a hill. Older home constructed from old growth timber. A full city block with no neighbors. Easy highway access to the rest of Texas. To top it off, the commute from Hempstead, though it was a longer distance, could be managed in the same time period as the old commute from Mission Bend due to the new path using a relatively lower traffic path on 290 versus traversing neighborhoods and stop signs to get from Mission Bend to downtown (59 at Kirby) and then down 59 to Sugarland near Wilcrest.
I hope you work near Sugarland. The commute was pretty brutal some days.
As for the one swimming pool per child part, I have to defer to someone who knows something about constructing a swimming pool that people can use for fun stuff like swimming. The only large body of water that I constructed was a small, shallow pond where my childhood friends, my brother, and I would keep bait for our fishing trips. We dug a pit that was about 20' x 20' (~6m x 6m) and a foot or so deep (0.3m deep). We stocked it with crawdads, minnows we caught in the nearby creeks, and small perch we caught in creeks and stock tanks. It was a viable habitat for bait until the landowner destroyed our hand-built fort next to it and leveled the land while laying out lots for a new subdivision. Good times.
They also cut the tank dam on the best, most accessible stock tank near our homes and all the fish, turtles, frogs, etc spilled out across the landscape to an uncertain future. I'm sure most of the turtle and frogs found new spots to hang out but the fish were kinda cooked since they don't operate well in air. All of that to build cheap housing. My best friend and his Mom bought one of the houses and one day while I was visiting they showed me how you could open a cabinet door and see daylight through a crack in the corner where the cabinet had pulled apart as the house settled on a lot where we used to have a nice, well-stocked pond. Other corners in the house had similar issues where you could see daylight through cracks. My family built custom homes for decades. Those homes in that subdivision were some of the worst I had ever seen as far as quality of finish and attention to detail. Years later though I found worse places around Houston and up here in the DFW area.
To summarize what turned out to be another long-winded post, unless you want an ideal spot where your kids can get down and dirty and really enjoy all the muddy fun that kids should have, you should probably find someone else to construct swimming pools. I'm probably not the guy.
Everything I just read makes me thankful that I never had to touch one of these apps before I got married. Out of all social media, dating apps have to be the most dystopian. Technology can be a force for creating deeper human connections, but this ain’t it… and I say that as someone who first connected with my wife in an online community before meeting in real life.
With that being said, I’m thankful if this hack is the start of a wonderful relationship for someone out there :)
I work in the medical device industry and most people on my team have engineering degrees and extensive experience with Matlab. Pretty much all of them would flip their table if they had to write numerical/scientific code in Rust, even though it arguably has a more robust type system.
In my experience starting with Julia in 2025, the main thing missing from the ecosystem tends to be boring glue type packages, like a production grade gRPC client/server. I heard HTTP.jl is also slow, but I havn't sufficiently dug into this myself. At least we have an excellent ProtoBuf implementation so you can roll your own performant RPC protocol.
As for the actual numerical stuff I tend to roll my own implementations of most algorithms to better control relevant tradeoffs. There are sometimes issues where a particular algorithm is implemented by a Julia package, but has performance issues / bugs in edge cases. For example, in my testing I wasn't able to get ImageContrastAdjustment CLAHE to run very fast and it had an issue where it throws an exception with an image of all zeros. You also can't easily call the OpenCV version as CLAHE is implemented in OpenCV using an object which doesn't have a binding available in Julia. After not getting anywhere within the ecosystem I just wrote my own optimized CLAHE implementation in Julia which I'm very happy with, this is truly where Julia shines. It's worth noting however that there are many excellent packages to build on such as InterprocessCommunication, ResumableFunctions, StaticArrays, ThreadPinning, Makie, and more. If you don't mind filling in some gaps here and there its completely serviceable.
As for the core language and runtime we are deploying a Julia service to production next release and haven't had any stability/GC/runtime issues after a fairly extensive testing period. All of the Python code we replaced led to a ~40% speedup while improvements to numerical precision led to measurably improved predictions. Development with Revise takes some getting used to but once you get familiar with it you will miss it in other languages. All in all it feels like the language is in a good place currently and is only getting better. I'd like to eventually contribute back to help with some of the ecosystem gaps that impacted me.
Waiting 15+ seconds to test small changes to my PyTorch training code on NFS is rather annoying. I know there are ways to work around it, but sometimes I wish we could have a training workflow similar to how Revise works. Make changes to the code, Revise patches it, then run it via a REPL on the main node. Not sure if Revise actually works in a distributed context, but that would be amazing if it did. No need to start/fork a million new Python processes every single time.
Of course I would also rather be doing all of the above in Julia instead of Python ;)
Revise can work on your server for hot reloading if you need it - you copy your new code files in place over the old ones.
Of course there are caveats - it won't update actively running code, but if your code it's structured reasonably and you are aware of Revise's API and the very basics of Julia's world age you can do it pretty easily IME.
Mine did the same for image processing but coming from python/numpy/numba. We initially looked at using Rust or C++ but I'm glad we chose to stick it out with Julia despite some initial setbacks. Numerical code flows and read so nicely in Julia. It's also awesome seeing the core language continuously improve so much.
I've found that I'm most productive in Julia when minimizing the number of third party dependencies for this reason, even more so than other languages. That's not to say there are not many high quality packages available but rather the benefits of the type system align better when I have a strong understanding or control over the most pertinent interfaces. As a language Julia definitely rewards you heavily for this type of thing. Coming from Python my first instinct was to try to solve as many problems as possible with third party packages and filling in between the lines. Unsurprisingly this was the worst of both worlds.
If there was one thing I could change about Julia it most certainly wouldn't be correctness issues in my own experience. Filling in the ecosystem in terms of boring glue type stuff like a production grade gRPC client would be amazing. This was the type of problem that almost got me to give up on the language.
Technically you don't need to know what array indexing is being used if you iterate using firstindex(arr):lastindex(arr). AFAIK the issue was that this wasn't consistently done across the Julia ecosystem including parts of the standard library at the time. No clue as to whether this still holds true, but I don't worry about it because I don't use OffsetArrays.
