korijn

10 ms·

61.
by korijn 4y ago
SoundMind product is fascinating. Is there a risk you become dependent on the device after longer term use and will have worse than pre-soundmind sleep when you have to go without it (e.g. it breaks or any other arbitrary reason)?
62.
by korijn 4y ago
> but how it came to be is not part of the definition It's possible the people working at the time were not conscious of the trade-offs they were making. But it still happened and that's how it came to be. > if I inherit the
63.
by korijn 4y ago
Exactly!
64.
by korijn 4y ago
If as GP says AI could automate 1% of a single programmer's job (the boring part where you write code), then how on earth can you derive that a single programmer could do the job of 5 with AI? It's completely illogical.
65.
by korijn 4y ago
Depends if any of your packages use absolute paths (generated at install time for example).
66.
by korijn 4y ago
If you're that worried, why not add a CI check on the bundle size as a general smoke detector (useful for more than just lodash) and another check for plain lodash imports with a simple custom eslint rule.
67.
by korijn 4y ago
Importing single modules is so trivial and makes it tree shakeable. Is that really unacceptable?
68.
by korijn 4y ago
I don't understand how that relates to my comment. Anyway, I'm happy you seem to be successful. Keep up the good work.
69.
by korijn 4y ago
I can't shake the sense that they seem to just prefer building something new (and blog about it) over figuring out how to configure a/the scheduler properly. Anyway, they did get it done and made it work, so whatever.
70.
by korijn 4y ago
Standardize the stages and names. We use `dev` and `latest`. It worked wonders for us, on a cache hit the build time is reduced from 10 to 1,5 minutes.
71.
by korijn 4y ago
You can build the first stage separately as a first step using `--target` and store the cache that way. No problem.
72.
by korijn 4y ago
I get the impression the author has not been exposed to enough pain doing package maintenance on a webpack codebase.
73.
by korijn 4y ago
Would a framework like uvicorn/fastapi be able to achieve similar performance if it were backed by libuv (as opposed to e.g. asyncio)?
74.
by korijn 4y ago
Inplace operators?
75.
by korijn 4y ago
This is addressed in the article. Search for permissions and e.g. XDG portals.
76.
by korijn 4y ago
I'm aware! The issue is the mixed content (wheels, and... not wheels) on pypi. If the data is incomplete, it's useless in the sense that you're never going to be able to guarantee good results.
77.
by korijn 4y ago
I emphatize with your situation and it's a great example. As crazy as this may sound, I think you would have to build every possible permutation of your library and make all of them available on pypi. You'd need a some new mechani
78.
by korijn 4y ago
Yeah. Well, mandating wheels and getting rid of setup.py at least avoids having to run scripts, and indeed enables the next step which would be indexing all the metadata and exposing it through an API. I just thought it wouldn't necess
79.
by korijn 4y ago
...and ensure _all_ package metadata required to perform dependency resolution can be retrieved through an API (in other words without downloading wheels).
80.
by korijn 4y ago
Isn't that exactly what bundling does?
81.
by korijn 4y ago
Don't compare yourself to others. Focus on what you want to do now that would make you happier. Love yourself.
82.
by korijn 4y ago
Stumbling upon this felt like a bit of the old internet's magic. Thanks.
83.
by korijn 4y ago
I didn't ask for any of that. I'm explaining why the article came off badly to me. I'm assuming that was not the author's intention. I provided this feedback in my comment so that they may reflect on why this is so. Ther
84.
by korijn 4y ago
> I don’t think of blaming anybody here, that is you reading things into it. Alright, thanks for responding directly to that. In my personal experience, people don't typically conclude that I would refuse to admit I'm wrong. Th
85.
by korijn 4y ago
It's interesting to me that all four examples put the blame with the other party. I hope it's just worded poorly or I am reading too much into it. Edit: I'm not saying that invalidates the article's content (in fact I re
86.
by korijn 4y ago
No code changes should be merged purely because the author got less code merged than someone else on their team. This sounds harsh maybe, but by your reasoning, your feelings could end up being the cause for bugs, poor quality code and&#x
87.
by korijn 4y ago
Being married to your code/output is just another flaw typical for juniors. Put them on features that aren't critical or ensure they are made aware up front that their work may be rejected if it doesn't meet design expectatio
88.
by korijn 4y ago
>> for certain people with bad joints or other related issues cycling or swimming might be better choices > Even rope jumping is considered much better than jogging since the force is always distributed across both legs at the same
89.
by korijn 4y ago
So it seems python and elixir are not that different at all. You are handling these problems the same way as the Python community is.
90.
by korijn 4y ago
Why does it matter which is worse? You can't eat money.

More ›