franklyt

>weird hierarchical "junior/senior" dichotomy

Will this ever end?

I used to think this, but sveltes templating language is trivial and keeps the problem space manageable for its maintainers.

Firefox is not as performant as Chrome is. This is something a web developer will have come across, if not an average user.

Oftentimes, people will say correlation does not imply causation, and this is mathematically true (imply means something different in regular parlance, and correlation can very well imply causation in that usage).

That being said, this is probably a case of putting the cart before the horse.

To be fair, young and healthy and Covid 19 vaccine tread the waters of “reasonableness” when combined.

The risk profiles in either direction are so small it’s very hard to discern a meaningful pattern. It probably just doesn’t matter at all what you do.

That claim you’ve just made is completely inconsistent with evidence showing much higher side-effect rates for mRNA over traditional formulations.

Moderna has something like an 80% incidence of fever after the second shot. That incidence of side-effect is unheard of, but in the opposite direction you claimed.

Now, this isn’t dangerous, of course.

That’s a huge difference. Do you have a citation for this claim? I don’t doubt you, but, wow.

Building a non-trivial website in React with halfway decent design practices is 100000x easier than doing so in raw html/css/jQuery (for argument, the vanilla API back in the day was impossible to use).

That’s interesting. I’m guessing console.log appends to the window object somewhere, which is a fairly common method of image preloading.

Your body and mind are one.

It is scientifically inaccurate to believe otherwise.

This isn’t a pedantic point: the mind/body distinction is pseudoscience that used to be believed widely in scientific circles. This readjustment hasn’t really reached common practice yet.

This brings up a fascinating point that spins off into another, entirely complex discussion: does Mozilla pay enough for a great (not good) CEO?

Firefox has, since incipience, faced that challenge.

Anyhow, the point I’m making is that I don’t agree that it is impossible to compete with trenched competition.

Firefox has some prior momentum themselves, they’re not quite an upstart.

Was the last CEO let go for performance reasons?

This would be a decent point if nobody had any interest in chromium alternatives and Firefox was a new upstart brand, neither of which are true.

Usually, when a CEO heads an explicitly sinking ship, the CEO will be removed and someone will be brought in to turn around the company.

No idea why that hasn’t happened.

Unpopular opinion: Firefox is allowing itself to be phased out, and contributing to a less free internet, with their business moves. It was hugely upsetting when they axed their dev team mid-pandemic.

I should note that, on iOS, it seems that Safari with a content blocker outperforms the brave skin by a little, which outperforms the Firefox skin by a lot, which outperforms the chrome skin by a lot.

Yeah, we'd need more data. Because PD is such a low-incidence disease generally, any kind of uptick, even in the pre-60 cohort, would push the dial substantially. Are pre-60 cases, which I just found out trivially are at 4%, increasing substantially? Is 4% inclusive of a much older dataset? I'd venture that the answer is yes, but I have no idea.

Errr... I was more implying that ADD/ADHD medications are in very common usage, making it a notable data point. Perhaps I should have make that explicit.

I definitely don't agree with the comparison; I love TypeScript and find its utility easy to elucidate.

To me, it seems like a really bad sign if something that is supposed to solve a problem is “hard to explain”, almost like it doesn’t actually solve any problem and just ropes you in with familiarity.

My assessment is based on the fact that when you design something, you generally have to be able to explain its value, with little exception.

There are measurable links between use of ADD/ADHD medication and Parkinson’s, which makes sense given that the former modulates dopamine and the latter has to do with dopamine modulation.

I view this direct connection as more compelling an explanation.

I still don’t get the tailwind hype. To me, I think the relevant parties are invested, myself included. CSS is weird and has had a lot of “answers” appended to it out of desperation, but I’ve been feeling really good about styled-components and/or SASS modules, probably slightly in favor of the former, using file based code splitting. I’ve seen the explanations countless times, but if you were to ask me to advocate for tailwind right now, I’d find it difficult to highlight the advantages. The answers don’t immediately jump out at me, the problem we’re solving doesn’t seem immediately apparent, so I have trouble advocating for or understanding the tech. “You can build stuff quickly!” - doesn’t this just sound like someone comfortable with raw CSS? “You don’t need to context-switch!” - these are shorthand classes, not JS or JSX. The language isn’t uniform here.

Note: I’ve written a lot of CSS and generally prefer rolling my own components to using a library... perhaps I’m not the target audience. Perhaps this is a cherry flavor to make the “designing your own UI” medicine go down more easily. Perhaps I’m mistaken and not being charitable enough, too.

If I may be so bold as to make your case for you, a huge pain point in the amazing software that is makecode arcade is that it pigeon holes you into TypeScript strict mode, which, while an amazing and flexible technology for seasoned engineers, it is a a very limiting and confusing convention for young learners.

How mature is this? Can I use it to teach kids? How is it more desirable than makecode arcade? I’m right in the use-case for this and have tried many alternatives.

I don’t disagree with or dislike the article, but I feel the author could have included some examples of what he considers programming, and what he considers hard, as he listed quite extensively the things he doesn’t consider programming or hard.

The tools exist the solve these problems: blame developers.

TypeScript and modern frameworks with contemporary understanding of app design kills nearly every historical pain point of web development, but many are stuck writing jQuery and using WordPress.

Very little support for W10 in here, which is understandable.

I just recently switched back from a work Linux config and a hybrid Mac config to a full W10 config for a variety of reasons, the largest being that W10 is solid, performant and doesn’t feel as limiting as Mac, or distracting and warty as Linux, when I’m programming.

I can’t believe this was overlooked by a prestigious publication.

It’s not factually accurate to claim that chrome is “slow”, especially vis-a-vis Firefox.

I didn’t say what you’re saying I said. Making inferences based on my posts and presenting those inferences as unequivocal statements I’ve made is... well, not helpful. I think alternate perspectives and legitimate concerns about all technologies should be discussed without devolving into accusations that I’m against the platform.