assert(isPasswordGood(…)) is already in the language. node
assert(isPasswordGood(…)) is already in the language. node
no worries, a fork will pop up.
ultra rare I’ve successfully inherited a concrete class, rarely an abstract one and 99% just impl an interface.
are you me?
instead of that partial thing at the top I extend a base one into web, worker, test and build (simulate CI step).
imo, it’s fake as it’s a “wate of time”
stop hating on rust devs
you can even do
(a == b).then(
which turns a bool into an Option
no worries, cloud providers have oopsies of their own.
as long as you have good practices like storing the form version and such.
uuuuuuuu. and you could do -m to describe the commit.
next they’ll add --push/-P.
perhaps add -r for fetch/rebase then commit.
one command to rule them all! 😈
sure, ok, but who uses only the subset of standard SQL in a particular engine just to call his queri3s portable? most of the good stuff is unique to each engine and is what makes the engine stand out.
it’s the same with C standards…
portable, my ass. excuse my french.
each system has it’s own dialect and quirks
it’s just a drag to veer from. it’s not particularly good, but good enough to stick around.
relational databases have years of reseach into them, not the query language itself.
sql was built so people other than devs can use it, but we got stuck with it.
I think you missed the point. OP is asking for an alternative to communicate with a relational DB.
or with ll alias for ls -laF, I’m using it so often, even if it’s not available, I still type it 5 times a minute.
it’s a trend to bloat text lately. recipes, blog posts, LLM output, scrum meeting speeches when working remote.
there was a comment about adding an ?!
operator that would resolve any number of ?
operators but I can’t find it.
your machines
git add remote laptop …