3 ms·

Web3 / popular crypto is not my bailiwick (although I like math and so unpopular crypto). Your video is three hours long, I'm not going to watch the whole thing

by m3047 2y ago

Web3 / popular crypto is not my bailiwick (although I like math and so unpopular crypto). Your video is three hours long, I'm not going to watch the whole thing, and leave it at that. That's not a slight, but three hours for something which I already feel isn't going to deliver something I can use today, next week, or this month. I'm a big believer in no/low code and run-anywhere... although those might also not mean what you think I mean. Props for you for doing it. So, I started watching your video and the first question I had was: what are Codespaces? How is it secured? Where does the final app run? Can I run it on my hardware? Can I run it without cloud access? Which cloud? Will it be around next week, next month, next year... ten years from now? However don't pay too much attention to a sample of one. ;-) I think the situation with no/low code can be summed up by analogy to desktop publishing. There is no CI/CD pipeline for DTP: you press print; it is a fully integrated environment... unlike literally all of the "continuous integration" environments which try so hard they can't stop shouting about it because it's eating them alive. Somewhere there might be a tool for generating color seps, setting gutters, importing fonts or creating postscript header libraries or LaTeX; but you'll never use it or see it. Somewhere, somebody is still doing multi-plate prints with pigments exhibiting greater variety than CMYK that are only vibrant in natural light; most people don't see the point because all they get is a crappy snapshot on their phone. It's not just a creator problem, consumers don't know what's possible and don't possess devices which fully reveal the full scope of what's possible. Consumer devices actively compromise that full scope for myriad walled-garden reasons, as well as run-of-the-mill negligence and ignorance. I got a Cadillac as a rental a few years ago, and I'll never buy a modern Cadillac and avoid driving one if possible. I couldn't control the windshield wipers, and the console display flashed the most attention-grabbing WARNING several times that I was not looking at the road, presumably because it couldn't suss that I was wearing glasses. I didn't actually look at the console display since it happened at high speeds in heavy traffic on an unfamiliar road (I had a passenger, and I asked them "WTF is that flashing screen saying??!?"); good job, Cadillac!

socketcluster 2y ago
Saasufy supports rollover deployment. It's serverless, meaning you don't need to write any server-side code. You just define the collections, schema, views/filters, access controls then deploy. It's radically different from anything that's out there. It makes it impossible to introduce back end bugs or security flaws (assuming that access control rules are defined correctly; which is a lot easier to verify via a simple UI than reading thousands of lines of back end code). Look at this app I built with it on the side: https://www.insnare.net/ https://www.insnare.net/ It's only ~1300 lines of custom code in total. Most of it is HTML. Throughout the entire process from start to finish, I never encountered a single back end bug. Deployment essentially never fails; the UI doesn't let you do anything invalid and it helps avoid inefficient queries. Yet look at the complexity of what kinds of queries and filters I can run against the data and all the different views. It has almost 1 million records... Indexes are not even fully optimized. Look at the data that's behind access control/associated with specific accounts (e.g. the Longlists). Go ahead and try to bypass access controls... The WebSocket API is documented here: https://github.com/Saasufy/saasufy-components/wiki/WebSocket-API https://github.com/Saasufy/saasufy-components/wiki/WebSocket... It would normally have taken months and tens of thousands of lines of code (front end and back end) to build that. The value is there in terms of security, development efficiency, maintainability etc... The hard part is getting people to see it.

by m3047 2y ago

socketcluster 2y ago

Saasufy supports rollover deployment. It's serverless, meaning you don't need to write any server-side code. You just define the collections, schema, views/filters, access controls then deploy. It's radically different from anything that's out there. It makes it impossible to introduce back end bugs or security flaws (assuming that access control rules are defined correctly; which is a lot easier to verify via a simple UI than reading thousands of lines of back end code). Look at this app I built with it on the side: https://www.insnare.net/ https://www.insnare.net/ It's only ~1300 lines of custom code in total. Most of it is HTML. Throughout the entire process from start to finish, I never encountered a single back end bug. Deployment essentially never fails; the UI doesn't let you do anything invalid and it helps avoid inefficient queries. Yet look at the complexity of what kinds of queries and filters I can run against the data and all the different views. It has almost 1 million records... Indexes are not even fully optimized. Look at the data that's behind access control/associated with specific accounts (e.g. the Longlists). Go ahead and try to bypass access controls... The WebSocket API is documented here: https://github.com/Saasufy/saasufy-components/wiki/WebSocket-API https://github.com/Saasufy/saasufy-components/wiki/WebSocket... It would normally have taken months and tens of thousands of lines of code (front end and back end) to build that. The value is there in terms of security, development efficiency, maintainability etc... The hard part is getting people to see it.