You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't really need a big announcement for something that is nothing more than another refinement of Progressive Web Apps ... obviously people working in the PWA realm should keep refining ... same goes for data APIs or backend event-driven infrastructures like Kafka.
It's important to just stay at it on improving those things ... but do we need a big announcement for just staying at it. Maybe we actually do, but ...
One has to wonder if CloudSeed.app intended to distractify devs from the bigger architectural issues with spurring creativity and collaboration.
The infrastructure gets in the way ... SPEED matters ... and collaboration should be driven by FREE msg INTERACTION ... not CENSORED interaction as we see with FB or Twitter.
So in case someone needed a clue ... in steps Elon Musk LONG AFTER people already knew that the censorholes were screwing up information exchange ... so OBVIOUSLY, it is time to reall rethink apps
... maybe it ALWAYS is time to do that ... because free speech is not free unless it is EXERCISED and continually disrupted and redesigned ... the liberty is supposed to be bathed in the blood of revolutions or something.
Let's simply architectures to increase speed and ELIMINATE obstacles to creative interaction from users ... the user is not supposed to be the product ... not just more event-centic but with active back/forth involvement of users ... rather than users just passively watching or scrolling -- the environment should lend itself to or ENCOURAGE interaction first.
Users should actively join a conversation and be welcomed / encouraged by every aspect of the architecture to add, contribute, annotate, bid, haggle ... example: auction with bidders/haggling rather than a MSRP store.
Apps should load instantaneously.
As if only a form or a simple documents ... the infrastructure must be serverless and distributed as with Git.
In other words, every user's data should be in an INDIVIDUAL standard format data API ... in a Git repo ... that data API should be something that individuals, not hubs like FB or Twitter, share or expose to search ... that data API should be like a commitgraph resume; given the correct access, all the information should be there ... AND of course, the default should be VERY PRIVATE with no shared access.
The ideal workflow conforms to a creative or scientific or artitistic CREATIVE workflow ... it doesn't force the creator to conform to the baggage of a framework ... but the individual's SECURITY ... not the central hub's security.... must be the major driver of this architecture. Some in the bitcoin or NFT realm will say that this architecture should be blockchain-driven or somehow part of cryptocurrency realm ... but that is STILL the cryptohammer seeing every problem as another cryptonail.
The app's ONLY purpose is to capture a performance ... the user is NEVER EVER the product.
The app can load progressively but it needs needs to build FAST and MUST stay out of the way ... this means something like Go or Rust ... working as close to bate metal or a machine image as possible ... not JS or Vue or React ... probably not Ruby or Python... although their migh be minimal roles for front matter ... it's
really about speed; speed matters in creative work. Nothing is fast enough yet.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We don't really need a big announcement for something that is nothing more than another refinement of Progressive Web Apps ... obviously people working in the PWA realm should keep refining ... same goes for data APIs or backend event-driven infrastructures like Kafka.
It's important to just stay at it on improving those things ... but do we need a big announcement for just staying at it. Maybe we actually do, but ...
One has to wonder if CloudSeed.app intended to distractify devs from the bigger architectural issues with spurring creativity and collaboration.
The infrastructure gets in the way ... SPEED matters ... and collaboration should be driven by FREE msg INTERACTION ... not CENSORED interaction as we see with FB or Twitter.
So in case someone needed a clue ... in steps Elon Musk LONG AFTER people already knew that the censorholes were screwing up information exchange ... so OBVIOUSLY, it is time to reall rethink apps
... maybe it ALWAYS is time to do that ... because free speech is not free unless it is EXERCISED and continually disrupted and redesigned ... the liberty is supposed to be bathed in the blood of revolutions or something.
Let's simply architectures to increase speed and ELIMINATE obstacles to creative interaction from users ... the user is not supposed to be the product ... not just more event-centic but with active back/forth involvement of users ... rather than users just passively watching or scrolling -- the environment should lend itself to or ENCOURAGE interaction first.
Users should actively join a conversation and be welcomed / encouraged by every aspect of the architecture to add, contribute, annotate, bid, haggle ... example: auction with bidders/haggling rather than a MSRP store.
Apps should load instantaneously.
As if only a form or a simple documents ... the infrastructure must be serverless and distributed as with Git.
In other words, every user's data should be in an INDIVIDUAL standard format data API ... in a Git repo ... that data API should be something that individuals, not hubs like FB or Twitter, share or expose to search ... that data API should be like a commitgraph resume; given the correct access, all the information should be there ... AND of course, the default should be VERY PRIVATE with no shared access.
The ideal workflow conforms to a creative or scientific or artitistic CREATIVE workflow ... it doesn't force the creator to conform to the baggage of a framework ... but the individual's SECURITY ... not the central hub's security.... must be the major driver of this architecture. Some in the bitcoin or NFT realm will say that this architecture should be blockchain-driven or somehow part of cryptocurrency realm ... but that is STILL the cryptohammer seeing every problem as another cryptonail.
The app's ONLY purpose is to capture a performance ... the user is NEVER EVER the product.
The app can load progressively but it needs needs to build FAST and MUST stay out of the way ... this means something like Go or Rust ... working as close to bate metal or a machine image as possible ... not JS or Vue or React ... probably not Ruby or Python... although their migh be minimal roles for front matter ... it's
really about speed; speed matters in creative work. Nothing is fast enough yet.
Beta Was this translation helpful? Give feedback.
All reactions