Completely agree with you. Every time I see yet another template language adding some clumsy for-each loop syntax I sigh. Just let us use a normal programming language. As an example I give you every template system ever invented. Devops tooling is full of them.
Over the years, I've seen a few posts like this that seem to take it as a given that a loop in a normal programming language is better than foreach capability in a template language. Certainly enough times to believe that a significant group of people actually believe it's superior.
There's not a difference in capability of expression of the two models. It seems to be a purely aesthetic or comfort difference.
It's because native programming language will defacto allow you to hack it to its natural limit. A tendency most all programmers have given they even get into programming.
For example with any iterator/loop you may want to filter, or find, or transform. in ruby you have the entire Enumerable API to dig into or Array prototype for js.
a templating language would have to reimplement functionality one by one in an allow list.
it's just fatigue at that point, yet another API i've got to mentally track.
edit: of course if you export the view data "clean" before hand it compels you to not have intense logic in the view. I get that but after a decade+ in product, views are never pure, even just ability to highlight the active tab takes conditional and select logic in a loop.
I would rather that all the developers were "encouraged" to do the filtering and sorting in some kind of logic block rather than having an attractive footgun lying around that makes it easy to cram in one more last data adjustment.
The AI and Tooling support point is really just an extension of the Community and Ecosystem point. Even before LLMs React had an advantage in that every question you had was probably already on StackOverflow and there are mature React libraries for almost everything. Now some people might use an LLM to answer the question they previously would have gone to StackOverflow for but the outcome is the same: there are advantages to using what other people are using.
The famous Tannenbaum-Torvalds debate happened all the way back in 1992. At the time, the most common microkernel was Mach, which had significant performance problems. NeXT/Apple solved them by transforming Mach into a monolithic kernel, making Mach (as XNU) one of the most popular kernels in the world today (powering iPhones, iPads, Macs, etc). But that doesn’t help Tannenbaum‘s side of the argument. And I don’t believe his own Minix did much better than Mach did.
Whereas, from what I hear, L4 and its derivatives have solved this problem in a way that Mach/Minix/etc could not. Yet still, it makes me wonder, if L4 has really solved it, why aren’t we all running L4? L4 has had some success in embedded applications (such as mobile basebands, Apple Secure Enclave); but as a general purpose operating system has never really taken off.
An application in which something like slow file IO wouldn’t be a problem - does it even have a filesystem? And we don’t know whether Intel has done things to make it an “impure” microkernel, like what NeXT/Apple did to XNU, or Microsoft did with win32k.sys
The article describes what happened and it had nothing to do with Unisuper. Google deployed the private cloud with an internal Google tool. And that internal Google tool configured things to auto-delete after a year.
Mandatory licensing would be wild. If LG invent something that makes TVs better should they have to licence it to Samsung? Or should they just be able to make better TVs and use their invention for market differentiation?
Being required to conduct good-faith negotiation sounds like a great idea, a reasonable tradeoff between protection that encourages innovation so that inventors can profit off their inventions, while also allowing for society to progress based on those inventions.
LG could ignore trolls and morons - but if Samsung makes a good-faith, fair offer to license the technology, they should have to have a good reason for saying no beyond "we don't feel like it."
One company, Cobasys (owned by an oil company!) purposefully refused to license NiMH technology in transportation. The patent system was never intended to be used like a weapon to protect a market.
> The patent system was never intended to be used like a weapon to protect a market.
This doesn't seem true to me. Nothing about the design of the patent system makes sense if the intent if not to use it like a weapon to let a giant company protect a whole area of the market from competition.
As a point of interest, there is a class of patterns called Standard Essential Patents (SEP), which the patent holder is required to sell licenses under fair, reasonable, and non-discriminatory (FRAND) conditions when an implementation of that patented idea is required to comply with certain standards.
Why shouldn't they have to license it to Samsung? Why do we want to stifle innovation by preventing Samsung from using any of LG's tech and vice versa? Imagine the TVs we could've had if the two companies could combine the best parts of each others' technologies.
At a place I was consulting about 10 years ago one of the internal guys on another product dropped the prod database because he was logged into his dev db and the prod db at the same time in different windows and he dropped the wrong one. Then when they went to restore the backups hadn't succeeded in months (they had hired consultants to help them with the new product for good reason).
Luckily the customer sites each had a local db that synced to the central db (so the product could run with patchy connectivity), but the guy spent 3 or 4 days working looooong days rebuilding the master db from a combination of old backups and the client-site data.
> logged into his dev db and the prod db at the same time in different windows
I am very worried about doing the wrong thing in the wrong terminal, so for some machines I colour-code my ssh windows, red for prod, yellow for staging and green for dev. e.g. in my ~/.bashrc I have: echo -ne '\e]11;#907800\a' #yellow background
About 10 years ago I literally saw the blood drain from a colleagues face as he realised he had dropped a production database because he thought he was in a dev environment.
A DBA colleague sitting nearby laughed and had things restored back within a few minutes....
