31–40 of 176 posts
They’d allow for serving more direct (point to point) routes than trains as the infrastructure cost is so much lower than laying and maintaining tracks. Rail serving high volume routes still makes sense, especially while electric plans remain relatively small.
Open lab equipment. Open Sensor designs.
Augmented Reality. Apple seems poised to release some AR Glasses based on the patents they've been registering and the investment they've made in the ARKit framework. This will probably become another iPhone-like platform for developing apps on, and will likely present opportunities like the early days of the App Store. There's a cool project trending on Github right now showing how magic-like some of the technology…
Smart Tattoos. Color E-ink displays. Eventually: holographic VR.
No code/low code. People here underestimate the work it requires to craft a production CRUD app and keep it working. The problem these tools solve are more related to infrastructure rather than one's ability to code. Learning to code might be the easiest part but deploying it, maintaining it, scaling it, securing it and integrating it with thousands of other services remains a huge task even for experienced folks. It…
No code = someone else's code, it's been around forever, used to be called cots
No code/low code. People here underestimate the work it requires to craft a production CRUD app and keep it working. The problem these tools solve are more related to infrastructure rather than one's ability to code. Learning to code might be the easiest part but deploying it, maintaining it, scaling it, securing it and integrating it with thousands of other services remains a huge task even for experienced folks. It…
The downside to the user is that certain kinds of UI polish and more complex behaviors aren't possible. From the developer's side, there is limited ability to share code between apps, so you wind up cutting and pasting a lot, and the work is much more boring that regular dev work. Still, it's a lot less work than building up a regular CRUD app.
No code/low code. People here underestimate the work it requires to craft a production CRUD app and keep it working. The problem these tools solve are more related to infrastructure rather than one's ability to code. Learning to code might be the easiest part but deploying it, maintaining it, scaling it, securing it and integrating it with thousands of other services remains a huge task even for experienced folks. It…
People get spreadsheets and word documents. I don't really know why. But they get them. But while it might seem like the step from doc/xls to nolocode is small or even non-existent, I think it actually is really big for most people who are supposed to be the audience for that (complete non developers).
I think one reason is because people don't want the responsibility to make a system that can break. I'm not too sure if this is the only or the biggest reason, but I think non-coders don't have the sense that they can build things, and even if you show them they can using some hot tool, it seems they're still scared it's going to break and it will be on them.
Maybe one reason is because if you break an Excel doc, there's usually someone around in your org who knows how to fix it. But the same can't be said for some random new hot nocode tool.
I think for specific use cases, yes. But for general, web and mobile apps, I just think it is too much complexity you can't simplify away, or at least none of the box-dragging UIs seem to have achieved that.
I agree this can be a big market, but a shift is needed to make it actually easy, not "look how easy it is" easy. Taking a different tac, maybe there's just not a market for it. The browser/HTML/JS is everywhere. It's not that hard to build a simple tool or app, but people in orgs use Excel, they don't build a simple page, even. It's not because they couldn't learn how, but somehow that just now what people in orgs do. I don't know why.