gshulegaard

9 ms·

31.
by gshulegaard 4y ago
I had the same realization...so I took some bits of doomemacs/spacemacs and incorporated it into my personal emacs configuration. I am not great at maintaining my config or writing elisp in general, but feel free to reference my confi
32.
by gshulegaard 4y ago
I think you are confusing type of scoping (lexical/static, dynamic) with scoping levels. Python has lexical scoping, but it does _not_ have block level scoping. https://en.wikipedia.org/wiki/Scope_(computer_science
33.
by gshulegaard 4y ago
Well put. I too prefer the reasonability of lexical scoping. Although I must confess I am not well versed enough to quite grasp how what Python does _isn't_ conforming to lexical scope. Since I was confused I did some internet search
34.
by gshulegaard 4y ago
I found this interesting because I have never run into this before...and I thought that was rare (in relation to how comfortable I am with Python). That said, I personally think this is the right and intuitive outcome. If we expand out the
35.
by gshulegaard 4y ago
> It's reasonable that the providers expect to have a way to enforce the contract. No, no it is not. Contracts are legally binding and therefore enforcement should be done via legal means. This type of behavior is nothing short of
36.
by gshulegaard 4y ago
As someone relatively new to Philly, I am not at all surprised by the need for relocation towing. In the immediate Philadelphia metro area, but outside center city parking is extremely sparse. It's not uncommon for me to help squeeze
37.
by gshulegaard 4y ago
Not quite. In the short term, perhaps, but I think the original comment was alluding to the fact that RSUs as an "investment" vehicle can have long term returns far greater than others. Put another way, 200k in RSUs at an early s
38.
by gshulegaard 4y ago
I mean kind of. They have to go for people that have money to pay them off, but not enough to make fighting them worth it. Startup is kind of nebulous, but there is a difference between a 40+ million series B startup and a small business
39.
by gshulegaard 4y ago
Very salient point. Having used both threading and various coroutine libraries (gevent prior to asyncio and asyncio more recently), I find coroutines easier to work with in modern versions of Python. So I don't find them superior stri
40.
by gshulegaard 4y ago
Right so the GIL improvements which (probably?) made it into 3.2 solves thrashing but introduces latency during "negotiation" for the GIL. > What David illustrated is that GIL makes it harder to mix CPU- and IO-bound tasks in t
41.
by gshulegaard 4y ago
I am not expert, and this might be dated information, but historically there is a "thrashing" introduced between the GIL and OS scheduled threads which has surprising performance implications. David Beazley does a much better illu
42.
by gshulegaard 4y ago
I am not sure when this article was written, but I really wouldn't recommend threads for even IO-bound tasks. Since threads don't escape the GIL the added contention with OS thread scheduling (context switching) is a performance
43.
by gshulegaard 4y ago
I think you might be confusing upselling and cross selling with network effects. Upsell is when you convince a customer to purchase additional service, like offering different tiers of subscriptions. Cross selling is where you sell adjace
44.
by gshulegaard 4y ago
Ah yes, this is what I thought was the current state. I was curious if a GIL removal decision had been made that I had missed, but seems like it's still a soft "maybe": https://lukasz.langa.pl/5d044f91-49c1-4
45.
by gshulegaard 4y ago
Can you elaborate on what you mean by "actual concurrency in python soon"?
46.
by gshulegaard 5y ago
Interesting, I have 3 edgerouters and UniFi AP which have been trucking for the better part of a decade. Can you point me in the direction for sources for their EoL issues? I am about to double down on Ubiquiti as the networking backbone a
47.
by gshulegaard 5y ago
Hmmm, I have a 5540 currently and don't have the problems you had (and I actually replaced the factory Ubuntu with PopOS after a year or two). Although battery life is not great, but I am not sure that is as much a hardware issue as it
48.
by gshulegaard 5y ago
To be explicit, I was skeptical because I believed that GIL removal requires adding overhead for managing memory access. Having dug a bit deeper into it that seems confirmed. The proposed GIL removal strategy _is slower for single-threade
49.
by gshulegaard 5y ago
I feel like you aren't well informed on why removing the GIL results in a single-threaded performance hit. And while I think it's always nice to keep in mind the developer effort required, it's not the only cost as GIL remov
50.
by gshulegaard 5y ago
Call me optimistically skeptical. I share similar reservations about GIL obsession with the original comment author, but if this is true: > The overall effect of this change, and a number of others with it, actually boosts single-thread
51.
by gshulegaard 5y ago
I had the same thought process.
52.
by gshulegaard 5y ago
Every once in awhile I find an article that is so well written I feel like it walks me through a complex technical situation like a layman while also expanding my understanding of a tool I use everyday in a meaningful way. This is definite
53.
by gshulegaard 5y ago
This is a common misconception (I blame American politics). In _perfect competition_ this would hold true; however a _free_ market is not guaranteed to be competitive, much less close to _perfect_ competition.
54.
by gshulegaard 5y ago
I am not sure I agree with the general idea that Postgres can't or even--albeit a bit less strongly--that it is hard to scale. Even in 2008 people were running petabyte-scale warehouses using Postgres: https://www.toolbox
55.
by gshulegaard 5y ago
I would have to dig more into specifics of your use case but my gut reaction is yes, it would be better. I do not have specific experience with TimescaleDB, but I have some experience scaling PostgreSQL directly and with Citus (which is sim
56.
by gshulegaard 5y ago
I think you might be more in agreement with the original comment than how I interpreted your comment. Personally, I think OP is calling out that most of the issues with current Uber (and similar companies) is the asymmetry of information.
57.
by gshulegaard 5y ago
Hmmm! Well thank you for your response! I think that I find myself far more in agreement with this additional detail. > It's not particularly interesting for $450 dollars to change hands in a vacuum; the transaction is given meanin
58.
by gshulegaard 5y ago
This is an interesting article but it starts off on the wrong foot for me: > This is patently ridiculous. Every single dollar of compensation paid out is done transactionally: it is used to purchase labor. In a typical transaction, no va
59.
by gshulegaard 5y ago
I am not well versed in the financial services industry but this article seemed to offer at least a plausible explanation for why Robinhood (and other capital limited brokers) stopped buys on GME specifically: https://stu2b50.dev
60.
by gshulegaard 6y ago
Last Galago I purchased came with a power brick but also supported usb-c power delivery.

More ›