What does "While EmDash aims to be compatible with WordPress functionality" mean?

Compatible how?

Oh boy, are you in for a shock..

"the effort involved"

Feels like your comment saying it was too much effort to cancel Kagi took more effort than cancelling Kagi.

Actually their payment model has some baked in niceness.

If you don't use the service in a month, they just refund you. This has kept me from unsubscribing for years now. Some months I use it, some I don't.

It's more of hassle to unsub, and re-sub again when I want.

I think you're right, haha

So just to check, instead of doing something you were told to, that you know is a stupid idea (after telling all concerned it's a dumb idea and being told to go ahead anyway, eg adding a crapton of video to a page), you would just resign, to protect your personal integrity?

no, you offer a technical solution to the problem. Show some videos is the problem. Downloading almost a GB of video content on page load is the (bad) technical solution. There are better ways and as a developer it's part of your job to solve things in a way that makes sense.

It's not a sign of their incompetence, it's a sign of the realities of many corporate environments.

But hey, if you want to rail against incompetent developers who exist in a make-believe world where they hold all the power are simply too lazy and incompetent to 'do the right thing' then go ahead!

> realities of many corporate environments

Stop making excuses and start taking ownership and responsibility of your craft.

I work in huge government departments, large financial orgs, and other "enterprise" places that are the poster child for the "realities of corporate environments".

Automatically saying "yes" to everything makes you a useless meat robot.

If you do everything that the customer asks, without push back, negotiation, or at least a deeper understanding, then you will produce broken garbage.

I see this all the time: "The customer asked for X, so I pressed the button!" is the cry of the incompetent junior tech that will never be promoted.

Nobody wants a uselessly slow website. Nobody wants to piss of their customers. Nobody wants angry rants about their online presence to make headline news.

What the customer wanted was multi media content. That's fine. The technical specifics of how that is presented is up to the engineering team to decide. You're not advisors! You own the technical decision making, so act like it.

If you make the decision to shove nearly a gigabyte down the wire to show the landing page, then that's on you. The manager asking for "video clips" or whatever as the feature probably doesn't even know the difference between megabyte and gigabyte! They shouldn't have to in the same way that I shouldn't have to know about my state's electrical wiring standards if I get a sparky out to add a porch light. If my house burns down, that's the electrician's fault, not mine as the customer!

Similarly, if someone asks for lights inside their pool, an electrician that strings ordinary mains cabling through the water should be jailed for criminal negligence. Obviously, only special low-voltage lighting can be used in water, especially near people. Duh.

Act like an electrician, not like a bored shopkeer who's memorised the line "the customer is always right" without realising that the full quote ends in "... in matters of taste."

> Similarly, if someone asks for lights inside their pool, an electrician that strings ordinary mains cabling through the water should be jailed for criminal negligence. Obviously, only special low-voltage lighting can be used in water, especially near people. Duh.

I recon the US electrical code for swimming pool allpows mains voltage as long as the conduit/cabling is certified for use in water (ie: watertight), properly grounded, and behind a GFCI.

And you can skip grounding/GFCI for anything below 24V.

There’s nothing “make believe” here, incompetent devs, and devs (regardless of competence) who don’t push back against silly requirements _absolutely_ exist.

I have tried push back but then the other guy that says "I can do it" gets the ticket handed to him.

Me: we cant do X bceause it has Y and Z implcations for end users

Manager: It fits our brand and we have to do it.

Dev: I can do it and the implications are mitigated by (handwavy explanation)

Maanger: sounds good. (To me) Maybe you can make a (useless) diagram for this featuer that will be realy handy for KT

--Days later--

Feature is delivered and the Y and Z were ethier not mitigated or there was a attempt-ish to mitigate them

What?

Chinese, Hindi, Japanese, Arabic language systems don't use capital letters. They manage to parse the boundaries of sentences and thoughts just fine.

You can find excellent examples of english written before capital letters (or even spaces) were standard and they tend to be significantly harder to parse because we're not used to parsing them. Familiarity is part of the problem but I also think that more visual clues allows for faster parsing and comprehension overall.

Different languages and cultures. When you spend a lifetime building reading clues, throwing them out the window makes it harder for people. The languages you mention also have delineation methods that involve more than simple punctuation marks.

What are the delineation methods in Mandarin and Cantonese and Hindi?

I suspect the journey to learn more on your own will inform you better than I can here on HN. Like english, they have changed over time, more often than not to include more delimiters.

That's often a skill issue.

skill issue being they only know php

The thing is, you actually don't know that, you've just decided it's true.

> I don’t know if this counts as activism,

I do. It doesn't.