Wait. i am already struggling with 50 columns for the title, now i have add this `<type>[scope]:` bloat to it? How are these people doing both "Conventional Commits" and 50-72 at the same time?
if those are the reason why you love janet, then you will love tcl because you will be able to do all the same things without drowning in parenthesis and weird syntax.
how is this a dark pattern? say that you bought a subscription of new york times for a year and put it on monthly installment. can you bail out of paying the credit card company after six months? only here, both the product and credit card company is adobe. in fact adobe is being generous by letting you "cough up" only a half the fee where your credit card company wouldn't. at this rate all credit companies are "dark pattern peddlers" according to you? adobe is pretty clear on the name of the subscription, "yearly subsciption, payed monthly" in big letters at the top of their pricing page.
if you want a stable chimera linux as a daily driver, go to voidlinux.org. chimera linux started as a void linux fork until it became it's own thing. they share the same dna. cbuild started as a xbps-src fork.
I hate the trend of moving away from being able to search packages from the command line to searching inside a bloated web browser. It had a happened with PyPI. And now npm. Please stop this madness.
Non-native speaker here. Is the phrasing of the blog title awkward or am I the only one? Seems like they are using "10x" as a verb and my brain kept parsing "10x" as a adjective to developer, reading "10x developer" which is a already established industry lingo.
Google's engineers when they were copying Java API for Davlik (and later ART), they had access to and consulted Java source code. The infamous Oracle v. Google judgement siding Google set precedent at the highest level, SCOTUS that looking at the code is not an issue.
So, it doesn't matter if a AI can or cannot do clean room implementation. Unless it is a patent or trade secret violation, cleam room implementation doesn't matter.
I am sorry, but whats wrong with doing something like, `print(type(var)); exit()` and just running it once instead of digging through 5-6 stack frames?
I am think you are misunderstanding the entire premise of git. There is no "force push to trunk breaks every other developers' working copy." There is no central repo/trunk where all the commits are pushed. You are probably thinking of svn.
In git, your repo is the canonical repo and that is where you work. You work on a new feature and when you are ready, you "git format-patch" and "git send-email" to the community via the mailing list or other developers. A discussion may happen and people may or may not decide to apply the patch to their own repositories, with "git am." This doesn't break every other developers' working copy because they decide how to apply the patches they got in their email. No central repo, no trunk, guaranteed by the d in git dvcs.