Jonathan Garbee

Twig, but mostly because I wash so used to it from way back when I did PHP.

Yes it is. Bruh or girl. I got the girl side with a friend’s daughters.

I’ve been considering getting an Air for a couple years as my next machine. I just don’t want to end up with multiple machines in switching between regularly. Like, I want gaming too and the Air isn’t it.

I’m not even sure legally dual licensing is enforceable. Is there a precedent? If one license is truly open source, you can’t exclude use. I’m totally fine with us creating a new single license, OSI or not, to enforce it though. Because people should benefit like companies do.

I was grasping. It only on a far edge relates to “time existed, larger is older”. But it doesn’t come through an icon.

For that icon to make sense. I think they both need the arrow going in the same direction. But the line length is inverted. Oldest having bigger bars get smaller. Newest the opposite.

Still, does it even need an icon when nothing else in the menu does?

This is why I’ve always pushed for, don’t put one interactive element inside of another. It just gets complicated, both interaction implementation and user understanding.

It is, sadly, different when citizens claim ignorance vs government employees. SCOTUS has reaffirmed this multiple times.

All they have to do is say the section isn’t clear on what they are and aren’t allowed to do. boom, loophole. That’s the issue, what is the clarity?

I don’t know what you’re trying to get at here. The Supreme court was pretty clear when they created qualified immunity. It doesn’t matter if it is written, it matters if the officers have explicitly been told their actions are against it. They made the bar pretty specific to allow abuse to continue

But first, you need to get someone to give up Qualified Immunity. Until they are told explicitly what they are doing is illegal, they are free to keep doing it with impunity. On an individual level no less. Absurd law created by the court when that isn’t even their power.

Yea, I think they are including more @react.dev now. The exact opposite of what any team focused on actual performance would do.

They also can write off the processing fees. Individuals can not. So they are not only charging us the processing fee, but also using it to lower their tax bill. It’s an insane setup. I am all for being allowed to charge it, but allowing the double dip on it is an unfair loophole.

Being ambitious and not having the right team are two different things. You can have all the ambition, but the wrong mix of people and values among the team can kill it. These aren’t exclusive of each other. Both can be true.

So, let's start just approaching things with a more neutral point of view. Everyone needs to learn. But, holding people to high standards and/or assuming they know so much because {Y situation} doesn't do any good. If anything, it makes them feel bad when they are wrong or missing information.

lose your job. It's not even that "shortcuts were taken to get to market". If the group doing the work genuinely dosen't know what is right, they will do the wrong thing and with no push back think it is OK. Starting a company also doesn't mean you know. Most companies fail, by the numbers.

While giving people the benefit of the doubt is good, we need to stop holding people who work at major companies on such a high pedestal. No one can know everything. Most software engineers, just assemble legos. Stop thinking "they must have had a plan/reason". Generally the plan was deliver or

Any amount of time, given a large enough task and little enough knowledge of everything going on, will seem like a pressure cooker. It’s all shortcuts to get to the next deliverable. If no one is pressing the technical details, no product person will care. And we get substandard implementations.

Still doesn’t change anything. They were rushed and genuinely didn’t know what they were doing with the platform technology. It isn’t like they sat in a room and decided HTML wasn’t good enough or too complex. They just saw it as a barrier to delivery so they minimized it.

Based on a few of the things I've seen, I think you're giving them too much credit. It seems far more like they genuinely just didn't know what they were doing and had to "make it work fast" so they slapped something together. I don't think they explicitly tried to design it against HTML/CSS.

Multiple? So you have one to stay in some locations? Or do they have kinds that target different allergy triggers?

Wait, what about... Men as president? eh, eh. That's been a pretty terrible combo for longer than social media has existed!

I would say "milk and someone with lactose intolerance"... but uh, yea you right. That wins the worst combo.

But, it is so convenient to use your phone to turn on your faucet. Oh wait, they made that the only way to turn it on… well just don’t ever get hot chemicals in your face like when you’re working on a car and hoses blow open. Problem solved.

Just a heads up, using language like “poor {person}” to talk about someone with a disability is disrespectful. It indicates, even if unmeaning, that their life is of lower quality or not full.

I never thought of it that way… this is going to live rent free.

I get that point of view. So from a more traditional logging sense, warn should be the current error. And info would be where warns currently sit. I think I could get behind that entirely. Good luck getting the ecosystem to agree though. I think we are too far gone now.

I think there are some useful ones like, "You're doing nothing with this returned promise" that are error worthy. Because they can actually lead to disfunctional code. However, I do think where we draw the line between lint and a deeper analysis tool is a good conversation to have.