I am not surprised around (1). HTMX is based on REST, which is by nature based towards having the state in the server and having a stateless client. But what is the advantage of having the state in the client. Isn't that just a bias of the current frameworks?
I can see cases where you really need a thick client, and in that case I would use GraphQL rather than REST for those. But, there are quite a few cases that can work with REST and mostly server side.
I think (2) is solved by out of band capabilities of HTMX. I don't think that is naturally a limitation of the conceptualisation.
The point is that explaining the requirements in a precise manner to LLM is literally coding the problem in a higher level language; the LLM is acting as a compiler for that precise description in English.
I actually am sympathetic to your point about the value of LLMs in programming, but more from the perspective that LLMs can help us to do the precise description gradually and interactively in a much better way that a dumb REPL.
Are you building scripts for the Debian distro? Given that they already include bash and actually support it for interactive use, what would be the issue for you scripting using bash?
I am sure that the experience of moving to dash wasn't fun at all. But users in general are not affected that much as far as I understand.
That is more or less the same pitch of physics, while most of the important activity is taking place in the biosciences at the moment.
The underlying assumption is reductionism: if we understood atoms best, we can understand and control everything built on them. I am not sure that I can agree with you on that. Complexity makes that a pipe dream.
For what it's worth, organizing other scientists work from a new perspective and having a unified framework is the highest form of genius a scientist can achieve. That is why for example Einstein is credited with relativity rather than Poincare.
(Physics actually seems a hodgepodge of random philosophical assumptions no one bothered to ever review because they're deep in the model. Not unlike code suffering from code rot.)
I suggest you try again. I think the situation has changed. I have been using Numpy/Scipy for a few years now, with all the negative experience of having to sort out whether to use g77 or gfortran and the right gcc flags etc. The most recent version, Numpy 1.7.0, is the first one that installed for me smoothly on Windows and OS X (official packages). YMMV, but I think it is alright now.
He already had an official apology from the prime minister in 2009. Many people want the conviction off the record, and it had to be done through a pardon because he cannot appeal or be tried again, and the law in effect at the time was not violated.
I wonder if such things should be evaluated in terms of the knowledge and experience they gained the company. I would say the Surface RT experience has reflected a lot on their experience and strategy developing Windows 8 and Phone. If (say) the experience is reflected in the level of success of Windows Phone 8, then may be overall it is a net success for Microsoft.
I think every company (like Microsoft, Apple, Google did) need to maintain software and hardware divisions, if only to get the feeling what are the software current needs in an evolving hardware profile.
You are probably mixing up UAE and Dubai. The UAE consists of 7 emirates, including the capital Abu Dhabi and Dubai. The GDP of Dubai is dependent on services, trade and a bit of industry, and they have little oil. Abu Dhabi is oil-rich. A big chunk of its GDP, and the net GDP of the UAE in general, is oil.
I am not surprised around (1). HTMX is based on REST, which is by nature based towards having the state in the server and having a stateless client. But what is the advantage of having the state in the client. Isn't that just a bias of the current frameworks?
I can see cases where you really need a thick client, and in that case I would use GraphQL rather than REST for those. But, there are quite a few cases that can work with REST and mostly server side.
I think (2) is solved by out of band capabilities of HTMX. I don't think that is naturally a limitation of the conceptualisation.