stevebmark

This is both interesting and scary, that FQ's CNS/GABA disrupting effects could somehow interfere with the pathology of Parkinson's. Doesn't seem worth it for the potentially permanent side effects from FQs.

Yes. Goodreads received lots of updates, and they were slow and difficult because of Rails (and Ruby) https://news.ycombinator.com/item?id=36577444

Don’t speculate. Listen to engineers who work there https://news.ycombinator.com/item?id=36577444

Goodreads is an example of a Rails victim like yours. They customized the app on top of Rails, and it's been so bad that Goodreads is dead in the water and has not received major tech updates despite Amazon throwing engineers at it. Ruby is a dangerous language to refactor, so often you're locked for a long time. See also: Every blog post about Rails upgrades ever (see also: Stockholm syndrome)

Fluoroquinolone antibiotics (like cipro, levaquin) wreak havoc on your mitochondria, including on mtDNA [1]. I doubt there's a link between FQs and Parkinsons. At least it would be easy to falsify that hypothesis. But FQs can cause permanent damage in humans, and it's interesting to see that mtDNA damage (which FQs cause) can have effects like the linked article show.

[1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6182158/ [2] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6648947/

I’m quoting, not interpreting. What am I missing?

It sounds like you’re seeing the pain GitHub suffered through rose colored glasses. The talks about GitHub Rails upgrades say it took years and caused burnout.

The presentation and "bogus claim" is from a principle Github engineer and core Rails team member. I will trust them rather than anonymous anecdotes.

Please listen to the Github engineers in the provided links.

> We forked rails and _practically wrote our own._ We fought against the framework. We deviated from the framework, and we even wondered if rails was right for us at all.

and

> Rails 3 was found to be five times slower than Rails 2

Rails was initially too slow for Github, so they forked it, didn't use "Rails" for a while [1], lost literal engineering years to upgrading it (same for Shopify), and now Github has an engineering department dedicated to working of the Rails master branch directly, which is huge engineering overhead and a problem and solution that shouldn't exist. Github co-founder Tom lamented using Rails at Github and has stopped using it [2].

If you're Github or Shopify and can throw (waste?) engineering years at solving a framework specific ecosystem nightmare problems, and have the klout and runway to hire core Ruby and Rails maintainers, then you're probably in a highly unique situation and could use any framework you want.

The rest of us don't see Rails as a great choice for Github. Doubt and questioning.

[1] https://videos.itrevolution.com/watch/550704376/ [2] https://youtu.be/GfhPeOiXDLA?t=725

Not to be pessimistic, but does this matter? Rails apps take 2-3x more resources to run than most other language stacks, including other dynamic languages, (including Perl!).

A good and related article about the dangers and poison of domain driven design, and why spreadsheets are used at every level of every company. https://dev.to/cheetah100/domain-driven-disaster-147i

I very much enjoy the false dichotomy argument that the bigger issue is tests, rather than types. Thank you for brightening my day.

HMOs don't prevent you from choosing a psychiatrist as far as I know, you just need to find one in network.

And yes, if want a pill pusher or crooked doctor who gives you what you think you need without following evidence based medicine, a PPO is better for that. Those are going to be more rare on HMOs because the doctors in HMO networks are more connected.

Was there some limitation listed with your HMO coverage, or are you just speculating? All insurance plans have emergency coverage regardless of if the hospital is in your network.

The same is true for PPOs, you just pay more for them. And a bigger problem is healthcare deserts. If you're in a rural area your options are limited by default.

HMOs are so much better than PPOs, but they're rare these days. They are significantly cheaper than PPOs. Most HMOs don't have deductibles, and all of them have lower premiums than PPOs. The "out of network" coverage of PPOs is an irrelevant scam. Your insurer covering 10% of a $200,000 out of network surgery is still going to bankrupt 99% of people in America.

HMOs require you to get a referral from your primary care doctor to see a specialist, which has the added benefit of making sure people actually have a PCP. Primary care is one of the few types of care where the more you apply it, the better a patient's health outcome.

No one gets an HMO because they're scared of having less choice of which doctors they can see. They pay more to have a choice that's ultimately irrelevant to their health. Most people choose doctors based on friend/family referrals and Yelp reviews, meaning they don't know how to choose a doctor. Reviews/referrals have no relation to health outcomes.

The end of the article refers to the "medical loss ratio" enforced by the ACA, which did indeed incentivize insurance carriers to tolerate higher healthcare bills. This affects PPOs much worse than HMOs. It should all be burnt down.

Further reading, one of the best books on the subject: "An American Sickness"

Agh, sorry, but having to read through a dropdown of dozens of items ruins this out of the box. Needs a re-work of guessing. Not fun and not even a game right now, but close!

Missing the point I think. It's really disrespectful to use a loud / mechanical keyboard in a public place, or really when anyone else is nearby. This lets folks use normal/good keyboards and still satisfy the weird craving some have for mechanical noises through their own headphones. Probably will save some RSI surgeries too, people can use healthy low key travel keyboards instead of high travel mechanical switches, while still getting the clicking sound they want.

Python didn't win, but it is popular in the data / ML / AI territory, and that ecosystem is attracting lots of developers. It's not about the quality of the language.

Ruby is everyone's favorite toy: Fun to play with, and you shouldn't do anything serious with it.

The most important thing you'll read today: Your iPhone has a white/brown noise feature under Settings > Accessibility > Audio/Visual > Toggle "background sounds".

On computers, use https://mynoise.net/NoiseMachines/whiteNoiseGenerator.php and press "b" for brown noise.

This is the most important part

> Predisposing factors included a remote history of gastric bypass and recent prolonged antibiotic therapy

I knew as soon as I saw it, and the keyword confirms it: a fluoroquinolone, moxifloxacin was used.

FQs like cipro and levaquin are well documented to cause permanent full body damage through all sorts of mechanisms. Including acute kidney injury https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3708027/

And the effects are worse for older populations.

The diet was likely unrelated to the kidney injury.

A nice story, and a unique situation from someone who obviously shouldn’t be giving anyone advice.

JSDoc comments are definitely not the “best of both worlds,” they are a limited and verbose subset of typing. I would only use them for specific reasons, like I’m in a hostile ecosystem that dogmatically doesn’t want any build steps (like WebGL/WebGPU engines).

I don't think you read the article nor my comment lol

I think this person is trying to say they moved from Netlify to Render, with some moderately insane, vague anecdotes, like:

> Things which used to take hours or days to accomplish in standard Rails or Laravel or Django apps—most of this stuff isn’t rocket science, folks—now took weeks or months! Progress!

This article is too much of a narrative to be coherent about issues with Netlify + the Jamstack... and also too verbose of a narrative to be readable. I'd skip it, but maybe you'll find it entertaining.

As most other commenters have similarly said, this blog post should be a single word: "Don't".

The book "Eloquent Ruby" has several chapters on how to use "method_missing". None of those chapters say the only valid use of method_missing: "Never use it."

Lots of languages have deep flaws. Javascript, Python, Java, Perl, C obviously, all let you do some pretty horrific stuff if you really want to. Ruby is the only language where the horror is embraced by the ecosystem and its users.

There's a reason most engineers are adamant you shouldn't use this. It's why learning Ruby as your first language is probably a bad idea, since it normalizes what every other language has agreed is bad practice.

Don't!

Those two shortcuts are how you edit searches and commands in Vim mode.

What was the name of the original Vim magic-auto-default setup project? I wish I could remember it! There used to be so many Vim questions on Stackoverflow from people who installed Vim ________ (?) and had no idea what it did. The advice was always: "Stop using that, and learn Vim." This project smells like that.

There are two types of Vim users:

1. "Stop trying to make Vim and IDE with all your fancy plugins, learn Vim!"

2. "Vim is so much more than a text editor, of course you can use it as an IDE."

These two Vim users are usually the same person.

You have to learn Vim's terrible, verbose, antiquated commands in depth in order to justify using Vim. If you don't use q: (q colon) and q/ (q forward slash) in Vim, for example, you probably don't know Vim well enough to justify the efficiency loss you have compared to you using a modern IDE with multiple cursors.

Aside: It blows my mind that there are still plugin managers being invented for Vim. That's a bad sign for an editor. This shouldn't exist in userland.

It's too early to post more background information on Dril. No one wants it.

The final battle of Twitter is king Dril vs shitlord Elon. No know knows what the outcome will be. Elon is trying to promote Dril with artificial inflation, while Dril is trying to destroy Twitter, trolling every new feature and blunder and its inept CEO, and encouraging Block the Blue, to a huge audience. That's the real story here. Everyone is rooting for Dril and the permanent end of Twitter.

A double blind, randomized, controlled trial showed that replacing saturated fat with seed oils high in linoleic acid significantly reduced cardiovascular disease and all cause mortality https://www.ahajournals.org/doi/10.1161/01.CIR.40.1S2.II-1

Unfortunately the full text of this study isn't on SciHub, but it's a very good study. They assigned veterans to one of two mess halls randomly, and in the experimental group they fed them food with the fat content replaced with corn oil (which is 46:1 omega 6 to 3 ratio). They also did a pre-study to make sure the fat-replaced food was palatable and hard to distinguish from unaltered food higher in saturated fat. The experimental group had significantly lower CVD outcomes and lower all cause mortality.

Don't worry about linoleic acid, it's either benign or healthy.