andrewgodwin

I still find a decent amount of the integration, like KIO, is still there and works well - it puts MacOS and Windows to shame in terms of how I can just interact with files anywhere as if they're native within KDE apps.

It's kind of a shame that Konqueror fell to the wayside, but modern browsers are so complicated I cannot fault them for focusing elsewhere.

This is where I separate "manager" from "leader". As a principal level IC, I'm part of "engineering leadership" along with the senior managers, but not a manager.

The work isn't that different to management, sure, but it is different. You're not doing performance reviews... but if someone is over performing you can help get them promoted and if you think someone is doing really badly you can help get them fired.

Unfortunately, at their stated range of 160nm, you're looking at only getting as far as Big Sur before the entire craft needs a recharge - it's much more aimed at island and port hopping, I suspect, than long distance travel.

Still, I am excited to see ground-effect vehicles/ekranoplans back in vogue!

Author here - it's just to reduce support surface area. I know I'll need PostgreSQL's full text indexing and GIN indexes for hashtags/search eventually, and I probably also want to use some of the upsert and other specialised queries, and it's easier to just target one DB I know is very capable.

For reference, when I say "small to medium", in my head that means "up to about 1,000 people right now".

I'm (worriedly) curious how this will affect people trying to change jobs on a H1-B, as technically you need to file a new petition each time, and I can see them somehow denying those too.

I've replied to the post on the forum, but if this is the default way Jupyter runs then we're going to have to figure something out longer-term. Calling the Django ORM from an async thread just isn't safe...

I'd love to hear your suggestions for changes we could make while keeping it somewhat WSGI-compatible. It took a few years to refine it to where it is now, so it's not like we just threw something at the wall.

Well there's no actual async support for views in 3.0 - we missed the cutoff due to performance concerns! Hopefully it'll be in 3.1.

It's worth pointing out that the ASGI support in this release is very low level, and doesn't let you write async views or anything yet. We're still working on that.

I would agree with some of the points - speed (which is stretched over two points), concurrency, and the ability not to do magic as easily, but several of the points (compile time, available developers, strong ecosystem) are not a "versus Python" at all but rather against other languages.

Personally, I see a language like Go and Python as solving different spaces. I wouldn't write a lot of website business logic in Go, and I wouldn't write a low-level TCP redirection daemon in Python.

I can't say much on the subject, at least not without official approval, but understand that the original Lanyrd team have not forgotten about the site; asking us to fix it isn't really giving us any new information (sadly).

If you want to make requests of any kind you're better off reaching out to Eventbrite directly.

There is, actually - the US has a (slightly worse) government data repository, but there's several LIDAR sets of the Bay Area, mostly from coastal surveys.

As long as you can convert the data into a height field it's possible. I reckon you could do contours with interpolation.