Skip to main content

Say hello to Solvent

We've changed the name of the platform from HiveMind to Solvent. The idea behind the HiveMind name was that the platform is meant to rely on components built by developers across the web to enable the quick composition of web applications. 

HiveMind is not a bad name and in fact has proven to be quite catchy, however we think a more evocative name would work better. We've spent time toying around with different names, we were not interested in a meaningless word so the name needed to be a real word that has meaning that could be tied to what the platform is, it also needed to have a nice ring to it.

To that end, we settled on Solvent. The Wikipedia definition: 

A solvent (from the Latin solvō, "loosen, untie, solve") is a substance that dissolves a solute (a chemically distinct liquid, solid or gas), resulting in a solution.

We think this fits nicely with the platform as one for helping businesses quickly develop software solutions to help with their business operations. It is a hyper-flexible platform that can be used to combined different components into a cohesive solution, not unlike a Solvent :)

Comments

Popular posts from this blog

Integrating AI CodeGen With Low Code Application Development

This is a demo showing Solvent-Lowcodr working with AI Code generation (ChatGPT) to build web apps in a low code fashion. This demo uses Vuetify Component Library. This is the first in a series showing various ways that AI CodeGen and low code can be combined in Solvent-Lowcodr to accelerate web application development. In subsequent posts we'll show how to use AI CodeGen to build low code building blocks in Solvent-Lowcodr. We'll also show demos for React.

Hype on HackNews and Silicon Valley

One of the consequences of refusing to drink the in vogue kool-aid is that you remain sober and take in the full brunt of the silliness going on around you. The technology industry overflows with such silliness, like any credible geek I spend too much time reading HackerNews even when I don't want to. One odd phenomenon I have observed over the past few years is the fact that there is a rather peculiar writing style in Silicon Valley, seemingly meant to make writing more efficient in conveying hype. Specifically, the desire to create emphasis when otherwise the point being made is prosaic has lead people in Silicon Valley to come up with this odd writing style where adverbs are deployed in ways that no decent writer would. Let's just say a good chunk of "influencers" in SV suffer from Hype-Nitis . I have gleefully collected a small sample of these gems on HackerNews over the past couple of years: atrociously bad crucially important astonishingly successful

Reactive and Component Frameworks for "Old Fart" Programmers

One of the great challenges for experienced developers when confronted with new concepts is being able to map one's existing knowledge to the new concept. As they say, there is nothing new under the sun, that is often more true for new development methodologies. Even when new jargon is brought to bear on new methodologies, often upon closer inspection you recognize that it is something that you already know that is being described in a new way (unfortunately sometimes in a convoluted way to make it seem new). Reactive/Component UI/UX frameworks are one such development, while their particular implementations may be new and novel, almost all of the underlying concepts are not new. This is hardly a thorough presentation of Reactive/Component frameworks, but rather an attempt to fill in some gaps for developers who have experience but might find themselves confused by some of these new kids on the block. The top 3 reactive component frameworks being React, Angular and Vue. Al