lyjackal

If you look up the tree you can often see some poison Ivy leaves. The large vines are what you want to get rid of to stop it spreading. As far as I can tell, birds eat the berries and poop it out while perching in other tree, which is three main way that the plant spreads

I agree with the sentiment that these reasons are terrible.

My main gripes:

- the half hearted take on static types

- excessive use of mutability and imperative programming

- dependency, version management and compatibility.

For this last one. Are there recommended best practices? I noticed that pip recently added a “constraints” file option which seems like it’s going towards at least the lock file level of guarantees that node has. Or do people still recommend using a separate manager (conda/miniconda).

Nice to see this. I’ve been looking for a wysiwyg form builder at work, but not seeing many options. One of the use cases that’s been hard to fill is dynamic content, using the block builder more as “template builder” for a canned set of data field, potentially with some simple conditional logic. Has anyone solved similar problems or know of any interesting resources?

I think they’re just referring to a clipboard history offered by Alfred, not remapping the delete key

Here I thought I was being original when I made this face on my webpage track the cursor

https://adrianlyjak.com

I searched for “happy” and I tend to agree with the nightmarish look. Pretty much all of the results looked like they would love to use their happy teeth to eat you. Consistently hitting the uncanny valley

Pandoc does a good job of generating docx files from markdown

regex based prose linting seems rife with opportunities to write buggy regexes

noticed issues with SQS for a couple minutes. Errors from java sdk, `com.amazonaws.SdkClientException: Unable to execute HTTP request: sqs.us-east-1.amazonaws.com`

Exactly. It’s not really hypothetical. I first heard about the pizza delivery attack it on dark net diaries podcast: https://darknetdiaries.com/transcript/97/

It was used to make someone give up his Twitter/Instagram account handle. They sent him tons of pizzas from different restaurants, and started also attacking other family members

I feel like this is spreading misinformation about scala. Those are not operators, rather methods. It’s syntax rules are fairly simple to reason about.

The problem here is more the growing language syntax complexity of JavaScript

That being said, just because you can name a method ‘||=‘ in scala, doesn’t mean you should. A lot of us scala devs realize that it’s not very readable. Symbols as method names should be used rarely if at all. But One can write unreadable code in most any language with poor naming, and that’s all this is

I think you may also be overestimating the quantity of current data that will actually survive. Computer records are pretty ephemeral unless actively maintained and archived.

I’ve been using only canola oil for my chainsaw for the last 3 years. No problems so far. I use it about every 2-4 months

Any chance you’re hiring?

Sorry, I think you misinterpreted what I was saying. Synthetic meat seems morally better than a factory farm, however I don't think the choice is between factory farms and synthetic meat. I'm saying it would be better to to cultivate an approach where we collaborate with nature via humane farms and moderated consumption.

I don't have any economic answers, however I think the vegan vision of a human race separate from nature is very scary, and not separate from one where we eradicate the natural world through industrialization.

This zoomed in view of a single animals suffering seems short sighted to me. Sure, factory farms are terrible, but farm animals (cows, chickens, sheep, goats, etc.) in general have grown up symbiotically with humans. Replacing a system where we collaborate with nature to one where we're dependent on a corporate lab grown product does not seem like it's being more integrated with, or compassionate to nature.

I agree DDD doesn't belong in this list, but this seems a little harsh. Form follows function. DDD is more about understanding the function, and then architecture patterns are the form

Familial wealth has a compounding follow on effect in opportunity and wealth growth. A huge part of current economic disparities is likely attributable to these policies, and subsequent discrimination that's reinforced by entrenched poverty.

Love what you're doing! Happy to hear you have component libraries in your plans. I'd love to see this integrated with storybook

Same. Also the heavy breathing that the article mentions. When I was a kid and around a noisy eater, I would also start eating noisily. I rationalized the behavior as a mechanism to cover up the sounds of their eating, but the explanation in the article makes a lot of sense. I would try to synchronize my eating somewhat with theirs to cover the sound up better.

I would love something like this, but for Firefox. Does anyone have any recommendations?

Previous discussion in January 2020 https://github.com/0x4447/0x4447_product_s3_email

Because the shell scripts are only run from _within_ pipeline steps. Gitlab CI yaml has no way of conditionally creating the pipeline steps, or the step's contents.

Ya, as I understand, that's all this python ci lib is doing. I find it a little annoying that your first have to start a worker to create the pipeline file, and then again to run the pipelines steps

In the context of the article, I think that can be attributed to age (go is older than rust, so trending towards the "brown field." See for example Scala, which is a little bit older, and ended up in both loved and hated lists. I'd speculate that Go will be in the same camp in 4 years or so based on polarized sentiment I've observed.

That being said, there may be something about strict/complicated languages like scala and haskell that tends to polarize developer sentiment. Rust seems like it could fall into that same pattern based on the "up front" work that it demands.

What was faster? Native Ubuntu that's my experience. I couldn't tolerate speed issues on WSL

I generally agree that practically, focusing on the heavy weight technologies will be the most useful in the long run. In defense of DSLs, I do love them. It's the magic of doing a task specifically as the most intuitive magical incantation. A beginner can pick the DSL up easily and get excited about learning the underlying fundamentals. An expert can code complex scenarios more efficiently.

Still, there's a pretty steep curve to developing them, and that generally translates into a shorter lifetime unless they take off in popularity. For example, tooling support, for things like autocomplete, highlighting, debugging will need to be implemented. There's also a lack of community answering questions, making it difficult to pick up for beginners (no stack overflow, etc).

Interesting that it's written in typescript and the readme doesn't mention using it with typescript. I ran into annoyances with this recently trying out nodes worker threads in a typescript project. I was running with ts-node, but the worker thread didn't know how to load a typescript file. There are some workarounds but they're not elegant.

I assume GP means ISO8601 Date Time https://en.wikipedia.org/wiki/ISO_8601. Default behavior of javascript date json serialization

  > JSON.stringify(new Date())
  '"2021-02-22T20:34:53.686Z"'

One point of evidence is the massive influx of members to /r/wallstreetbets