jbylund

These headlines usually work by the dept asking a researcher for a 10 sentence summary of their work. Someone in the dept summarizes that to 3 sentences, and sends that to the university pr dept. The university turns that 3 sentences into 1 and that's what's published. My take is this says more about the weird game of telephone being played than it does about the research product itself.

Typosquatting is a thing that has been looked at and is being looked at:

https://github.com/pypi/warehouse/pull/5001 - had to be reverted because it was too noisy

https://github.com/pypi/warehouse/issues/9527

Pip can use range requests to fetch just a part of the wheel, and lift the metadata out of that. So it can sometimes avoid downloading the entire wheel just to get the deps. Some package servers don't support this though.

Also, there's a difference between a pep being adopted and that pep being implemented (usually a bunch of elbow grease). That said there are a couple exciting steps towards 658 being implemented: https://github.com/pypa/pip/pull/11111 (just approved yesterday, not yet merged) https://github.com/pypi/warehouse/issues/8254 (been open for forever, but there has been incremental progress made. Warehouse seems to not attract the same amount of contribution as pip)

Did you consider a type of continuous aggregate that works over pre-aggregated partitions for time buckets without modifications and swapping those buckets in the continuous aggregate view with a live view when data is modified? I guess it would mean that performance would sort of continually degrade as inserts/updates/deletes happened in more and more time buckets, but as soon as the aggregation event fired performance would recover. It seems like one could provide a more strongly consistent view of aggregates with this sort of approach.

Yeah, wanted to be able to programmatically ask the window manager such that I can tell new shells to source "~/.bashrc.d/{desktopname}.sh".

I have a browser profile per workspace and git/aws/maybe some other env vars that are set up on a per workspace basis. To switching from project 1 to project 2 or personal I just click on the appropriate desktops in the status bar.

Which reminds me, another missing thing is the ability to have desktops displayed in the status bar and click on the one you want to jump to.

As a new mac user (~4 weeks with new employer) my biggest N are:

1) inability to ask the window manager "which workspace/desktop am I on" - it also seems like this ability has been progressively removed with newer versions (judging from stackoverflow/askdifferent questions) - after some hacking I've found a workaround for this

2) clicking on a browser notification just brings me to _any_ window of the browser, not the one that sent the notification! - if anyone knows how to fix this please help me out

3) there's a delay on toggling caps lock that you can't disable without installing some small third party utility! it just feels super rude that they're essentially telling me that I didn't mean to press caps lock

What's the explain plan for a pipeline like this look like?

In my experience one of the biggest things scaring devs away from moving more logic over the wire towards the db is lubrication between version control and database state. If I end up defining 10s or 100s of custom pipeline operators in git how do I keep that in sync with the db? and am I responsible for doing all that legwork myself?