Re:The future of AutoCAD
by sirjaz on Wednesday May 23, 2018 @09:14AM
(#17133865)
The problem is the reliance on the browser. If we look at the mobile market for one, you could do the same thing, but people still want native apps since they are more responsive, lower memory and cpu usage etc …. With web assembly all you are doing is adding more complexity. Keeping things native is preferred.
[ Parent
| on HN ]
I would argue that the web is less complex than native, and by quite a bit. You need a client that runs on Windows, Linux (distributed through multiple package managers), and MacOS. Possibly iOS if you want to support the iPad, and particularly the iPad Pro, in any sort of capacity. And if you want to reliably touch Chrome OS, you're looking at web either way. Not everyone computes the same way they did 10 years ago and we have to start accepting that.
You imply that computing of ten years ago was arguably worse than what we have today. In what way?
If I did, I didn't mean to.
Though, using Waze to find the quickest way to work this morning really make my commute much nicer. There was also a new album I'd been meaning to listen to and streaming it on spotify was nice.
Re:The future of AutoCAD
by microcolonel on Wednesday May 23, 2018 @09:24AM
(#17133933)
Note that the native AutoCAD doesn't seem to be going anywhere.
For now. I guess management is not doing it for fun but to explore profitability and sustainability of this approach. If it works for them, web version might be the only one that gets distributed. We already saw in Adobe how "cloud" is pushed everywhere even if it makes zero sense from the product point of view (uploading a single RAW file from a top-end camera to cloud takes ages and benefit is nearly zero), but makes super sense from economical standpoint.
Re:The future of AutoCAD
by microcolonel on Wednesday May 23, 2018 @09:40AM
(#17134075)
> If it works for them, web version might be the only one that gets distributed.
How could it work for them? Most decent sized projects would promptly run out of available memory and have nothing to do about it. And before that they have to deal with the ever longer list of restrictions put on web applications because of the trust model.
I assume they are doing it mainly to avoid distribution costs; they simply push a web-app update via a single, well-standardized channel allowing DRM and trusted remote code injection (to prevent pirates from running it), and they don't need to maintain multiple internal tools to do that with multiple attack vectors. So this IMO might be an experiment in this fashion; they are working closely with Google, probably assuming they can't compete with them so it's best if Google's brightest figure out proper ways, and they can focus on their core business.