1,572 karma · joined April 24, 2015
Yeah, this is one of my least favourite APIs in all of .NET. My understanding is that the .NET team is planning to redo it in the next few years, but if you want something better right now I highly recommend the excellent CliWrap library: https://github.com/Tyrrrz/CliWrap
I agree that there's a lot more work to do before Rust development is pleasant on average hardware. Does anyone know if Cranelift is still going anywhere?
This is such an odd statement; it's "not even wrong."
Vancouver zones most of its land for low-density suburban houses that accommodate very few people. It also has many examples of zoning districts that accommodate a lot of people in urban neighbourhoods that people love to live in. You can just change one zoning district to another proven one!
The history of Shaughnessy land use is kinda interesting; it was designed to be an ultra-exclusive enclave from the start, and the province and the city have both used their powers to keep it that way.
In the first half of the 1900s, the province enacted laws mandating single-family homes only in Shaughnessy; they were particularly weird in that the Shaughnessy Heights Property Owners' Association was empowered to enforce them. In (more) recent years the City has done largely the same thing with zoning restrictions.
Some links if you're curious:
https://twitter.com/GRIDSVancouver/status/960183009017135104...
https://web.archive.org/web/20190722191318/vancouver.ca/home...
Yeah, this is an unfortunate aspect of Vancouver's city planning; our zoning forces nearly all shops and restaurants onto busy, loud, polluted arterial roads. Changing this isn't really on the political landscape right now, and I don't think it's going to change anytime soon.
In a nutshell, it was intentionally designed to keep apartment buildings and stores out of most of the city.
That's an interesting one to me, because I'm generally bothered by how wide Vancouver streets are. IIRC most Vancouver residential streets are 33 feet wide, waaaaaaaay wider than in many European and Asian cities.
But if you do want to read them, here you go: https://vancouver.ca/home-property-development/zoning-and-la...
The "CD-1" zoning is notable in that it's actually 800+ unique zoning districts: https://cd1-bylaws.vancouver.ca/ByCD-1Number.htm
For a variety of depressing reasons, the Vancouver planning department is quite reluctant to use broadly-applicable zoning districts; a lot of new development happens with new unique zoning districts that apply to one lot only.
I live near one in East Van that is utterly useless; it's defined as starting in the middle of a road, and the view is blocked by tree foliage most of the year anyway. And yet because of it, multiple proposed apartment buildings have been cut short.
The Vancouver Plan needs to be approved, then an Official Development Plan, then neighbourhood plans, then actual rezonings. Expect 10+ years, if it happens at all; Vancouver has a very poor record with these sorts of city-wide plans. From a 1992 article I found in the archives a while back:
"no city council has ever accepted any of the half-dozen attempts at developing a city plan"
https://twitter.com/GRIDSVancouver/status/106689301711663104...
This is common but incorrect view of SQLite. It's able to handle many server-side workloads, as long as you're aware of its limitations (and the Tailscale team certainly are).
It depends a lot on what you're using the remote connectivity for.
I think I have a pretty good understanding of SQLite's strengths+capabilities, enough to understand when it can replace a traditional RDBMS for a back-end service. I wouldn't build a solution where multiple clients are connecting to the DB remotely - but sometimes I want the convenience of connecting to the DB remotely for observability/troubleshooting. This is something that's trivial with traditional RDBMSs, and a bit painful with SQLite.
Exposing the SQLite DB over the network for occasional interactive use seems quite useful to me.
Going from Nu to raw text is currently a little awkward. `str collect (char nl)` will take a Nu list of strings and convert it to raw text with line breaks. I suspect we'll get a more ergnomic way to do this soon.
Going to Nu from raw text is nicer, the built-in `lines` command splits line-break-delimited text into a list of strings. From there you can use lots of Nu tools to operate on each line.
This is a popular belief but I don't think it's true that .NET has slow startup. The CLR starts up in milliseconds, the JIT's first-tier compilation is crazy fast, and if you need to it's trivial to ship precompiled code using ReadyToRun. I don't know what makes PowerShell so slow to start up but I wouldn't blame it on .NET without more evidence.
ps | find k9
That will search through every column in the `ps` results. If you want to look through just the name column:
ps | where name =~ k9
I might be misunderstanding this, but piping to `save` is how you usually redirect to a file in Nu: https://www.nushell.sh/book/commands/save.html
It's easy to pipe text-speaking tools into Nu pipelines, and there's a built-in `lines` command that will split line-break-delimited text into a list of strings. From there you can use lots of tools to operate on each line.
Going from Nu data structures to raw lines of text is a little clumsier (`str collect (char newline)` IIRC) but I think that will get improved soon enough.
There's also a handy `detect columns` command that does a pretty good job of automatically converting text tables from old *nix/Windows tools into Nu tables.