Re: D could catch this wave: web assembly

On Tuesday, 24 October 2017 at 02:08:42 UTC, codephantom wrote: On Monday, 23 October 2017 at 22:32:55 UTC, bioinfornatics wrote: To remember it will be the next open standard by a W3C Community Group to create portable and efficient application across major web browser. A such feature can

Re: D could catch this wave: web assembly

On Monday, 23 October 2017 at 22:32:55 UTC, bioinfornatics wrote: To remember it will be the next open standard by a W3C Community Group to create portable and efficient application across major web browser. A such feature can offer to D a chance to have a killer app in 3D web application

Re: D could catch this wave: web assembly

On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote: This appears to have involvement from all major browser vendors, which provides hope it might actually catch on properly. An llvm backend will be created which will compile to "wasm", hopefully LDC and/or SDC could glue to this.

Re: D could catch this wave: web assembly

On Saturday, 19 March 2016 at 16:18:00 UTC, Adi wrote: I need help to write my proposal for gsoc. What exactly do you need help with? You can find some general hints at the GSoC student guide: http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/. There are currently no extra

Re: D could catch this wave: web assembly

On Saturday, 19 March 2016 at 08:05:12 UTC, Joakim wrote: It is not clear what you need help with, the WebAssembly docs are listed above and GSoC has its own student manual. There is also a contact email address for Craig, if you have general questions about GSoC that aren't covered in the

Re: D could catch this wave: web assembly

On Saturday, 19 March 2016 at 08:05:12 UTC, Joakim wrote: It is not clear what you need help with, the WebAssembly docs are listed above and GSoC has its own student manual. The WebAssembly spec seems to be expressed in OCaml: https://github.com/WebAssembly/spec/tree/master/ml-proto Perhaps

Re: D could catch this wave: web assembly

On Friday, 18 March 2016 at 12:09:02 UTC, Adi wrote: On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote: This appears to have involvement from all major browser vendors, which provides hope it might actually catch on properly. An llvm backend will be created which will compile to

Re: D could catch this wave: web assembly

On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote: This appears to have involvement from all major browser vendors, which provides hope it might actually catch on properly. An llvm backend will be created which will compile to "wasm", hopefully LDC and/or SDC could glue to this.

Re: D could catch this wave: web assembly

On Tuesday, 15 March 2016 at 13:01:31 UTC, CraigDillabaugh wrote: Maybe you can provide the students with fresh vegetables then :o) GSoC == Google Summer of Cultivation?

Re: D could catch this wave: web assembly

On Tuesday, 15 March 2016 at 20:18:40 UTC, deadalnix wrote: I can. I know LLVM fairly well (I'm not a committer), but I do not have that much experience with WebAssembly. Yes, please! I'd volunteer myself, but this summer will be too busy for me academically. — David

Re: D could catch this wave: web assembly

On Tuesday, 15 March 2016 at 20:18:40 UTC, deadalnix wrote: On Tuesday, 15 March 2016 at 16:12:46 UTC, Joakim wrote: Maybe deadalnix would be interested in mentoring, I think he showed some interest earlier. Or worst case, 3-4 of us could tag team, if that's allowed. I can. I know LLVM

Re: D could catch this wave: web assembly

On Tuesday, 15 March 2016 at 20:18:40 UTC, deadalnix wrote: On Tuesday, 15 March 2016 at 16:12:46 UTC, Joakim wrote: Maybe deadalnix would be interested in mentoring, I think he showed some interest earlier. Or worst case, 3-4 of us could tag team, if that's allowed. I can. I know LLVM

Re: D could catch this wave: web assembly

On Tuesday, 15 March 2016 at 16:12:46 UTC, Joakim wrote: Maybe deadalnix would be interested in mentoring, I think he showed some interest earlier. Or worst case, 3-4 of us could tag team, if that's allowed. I can. I know LLVM fairly well (I'm not a committer), but I do not have that much

Re: D could catch this wave: web assembly

On Tuesday, 15 March 2016 at 13:01:31 UTC, CraigDillabaugh wrote: On Tuesday, 15 March 2016 at 11:56:40 UTC, Ola Fosheim Grøstad wrote: On Monday, 14 March 2016 at 16:14:55 UTC, CraigDillabaugh wrote: On Monday, 14 March 2016 at 15:53:39 UTC, Joakim wrote: I can chip in general input on

Re: D could catch this wave: web assembly

CraigDillabaugh writes: > On Monday, 14 March 2016 at 15:53:39 UTC, Joakim wrote: >> On Monday, 14 March 2016 at 15:14:17 UTC, CraigDillabaugh wrote: >> >> I'm not qualified to mentor a WebAssembly port, as I'm not versed on >> compilers or IR. Dan would probably be

Re: D could catch this wave: web assembly

On Tuesday, 15 March 2016 at 11:56:40 UTC, Ola Fosheim Grøstad wrote: On Monday, 14 March 2016 at 16:14:55 UTC, CraigDillabaugh wrote: On Monday, 14 March 2016 at 15:53:39 UTC, Joakim wrote: I can chip in general input on porting, based on my Android experience. Thanks. Dan or Ola ... are

Re: D could catch this wave: web assembly

On Monday, 14 March 2016 at 16:14:55 UTC, CraigDillabaugh wrote: On Monday, 14 March 2016 at 15:53:39 UTC, Joakim wrote: I can chip in general input on porting, based on my Android experience. Thanks. Dan or Ola ... are either of you interested in mentoring something like this? I haven't

Re: D could catch this wave: web assembly

On Monday, 14 March 2016 at 15:53:39 UTC, Joakim wrote: On Monday, 14 March 2016 at 15:14:17 UTC, CraigDillabaugh wrote: On Monday, 14 March 2016 at 07:46:28 UTC, Joakim wrote: On Saturday, 27 June 2015 at 15:01:53 UTC, Ola Fosheim Grøstad wrote: [...] You got your wish, they just exposed

Re: D could catch this wave: web assembly

On Monday, 14 March 2016 at 15:14:17 UTC, CraigDillabaugh wrote: On Monday, 14 March 2016 at 07:46:28 UTC, Joakim wrote: On Saturday, 27 June 2015 at 15:01:53 UTC, Ola Fosheim Grøstad wrote: [...] You got your wish, they just exposed webasm through v8 a couple days ago: [...] I am still

Re: D could catch this wave: web assembly

On Monday, 14 March 2016 at 07:46:28 UTC, Joakim wrote: On Saturday, 27 June 2015 at 15:01:53 UTC, Ola Fosheim Grøstad wrote: [...] You got your wish, they just exposed webasm through v8 a couple days ago: [...] I am still getting student interest in new proposals ... are you interested

Re: D could catch this wave: web assembly

On Monday, 14 March 2016 at 07:46:28 UTC, Joakim wrote: On Saturday, 27 June 2015 at 15:01:53 UTC, Ola Fosheim Grøstad wrote: On Friday, 26 June 2015 at 02:29:40 UTC, deadalnix wrote: By this time we'd have a PR and we could play with it to decide using first hand experience. For which

Re: D could catch this wave: web assembly

On Saturday, 27 June 2015 at 15:01:53 UTC, Ola Fosheim Grøstad wrote: On Friday, 26 June 2015 at 02:29:40 UTC, deadalnix wrote: By this time we'd have a PR and we could play with it to decide using first hand experience. For which browser? It isn't implemented, is it? You got your wish,

Re: D could catch this wave: web assembly

On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote: This appears to have involvement from all major browser vendors, which provides hope it might actually catch on properly. An llvm backend will be created which will compile to "wasm", hopefully LDC and/or SDC could glue to this.

Re: D could catch this wave: web assembly

On Wednesday, 23 December 2015 at 07:37:39 UTC, Suliman wrote: On Friday, 18 December 2015 at 10:21:49 UTC, Ola Fosheim Grøstad wrote: On Thursday, 17 December 2015 at 20:22:41 UTC, yawniek wrote: https://hacks.mozilla.org/2015/12/compiling-to-webassembly-its-happening/ Thanks for sharing!

Re: D could catch this wave: web assembly

On Wednesday, 23 December 2015 at 10:02:18 UTC, deadalnix wrote: On Wednesday, 23 December 2015 at 07:37:39 UTC, Suliman wrote: On Friday, 18 December 2015 at 10:21:49 UTC, Ola Fosheim Grøstad wrote: On Thursday, 17 December 2015 at 20:22:41 UTC, yawniek wrote:

Re: D could catch this wave: web assembly

On Wednesday, 23 December 2015 at 10:06:20 UTC, Suliman wrote: For example I do not know JS. And only C++. How would look like my web-app with WASM? First have a look at this, qt-emscripten: http://vps2.etotheipiplusone.com:30176/redmine/projects/emscripten-qt/wiki/Demos WASM will allow

Re: D could catch this wave: web assembly

On Friday, 18 December 2015 at 10:21:49 UTC, Ola Fosheim Grøstad wrote: On Thursday, 17 December 2015 at 20:22:41 UTC, yawniek wrote: https://hacks.mozilla.org/2015/12/compiling-to-webassembly-its-happening/ Thanks for sharing! This looks promising. Could anybody show how C++ App for web

Re: D could catch this wave: web assembly

On Thursday, 17 December 2015 at 20:22:41 UTC, yawniek wrote: https://hacks.mozilla.org/2015/12/compiling-to-webassembly-its-happening/ Thanks for sharing! This looks promising.

Re: D could catch this wave: web assembly

https://hacks.mozilla.org/2015/12/compiling-to-webassembly-its-happening/

Re: D could catch this wave: web assembly

Am Sat, 20 Jun 2015 15:15:47 + (UTC) schrieb ketmar : > On Sat, 20 Jun 2015 14:06:50 +0200, Marco Leise wrote: > > > If you have a perfectly working old notebook with Windows XP on it, I > > can recommend QtWeb for its low resource usage and modern-ish feature > >

Re: D could catch this wave: web assembly

On Friday, 26 June 2015 at 02:29:40 UTC, deadalnix wrote: By this time we'd have a PR and we could play with it to decide using first hand experience. For which browser? It isn't implemented, is it?

Re: D could catch this wave: web assembly

On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote: This appears to have involvement from all major browser vendors, which provides hope it might actually catch on properly. An llvm backend will be created which will compile to wasm, hopefully LDC and/or SDC could glue to this.

Re: D could catch this wave: web assembly

On Friday, 26 June 2015 at 01:16:37 UTC, Joakim wrote: On Thursday, 25 June 2015 at 18:38:59 UTC, deadalnix wrote: On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote: This appears to have involvement from all major browser vendors, which provides hope it might actually catch on

Re: D could catch this wave: web assembly

On Thursday, 25 June 2015 at 18:38:59 UTC, deadalnix wrote: On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote: This appears to have involvement from all major browser vendors, which provides hope it might actually catch on properly. An llvm backend will be created which will compile

Re: D could catch this wave: web assembly

On Wednesday, 24 June 2015 at 16:42:28 UTC, Nick Sabalausky wrote: It's not always because of being designed to be pixel-precise. Responsive design and mobile-first are very deliberately NOT pixel-precise, but most of them look like shit on the desktop (at least until you zoom out about ten

Re: D could catch this wave: web assembly

On Thursday, 25 June 2015 at 08:13:07 UTC, Kagamin wrote: Lucky you are if you have only problems with font size. There's also a problem that people don't set up their preferred font size, so it's understandable that designers may want to work this around. And e.g. FF doesn't honor that

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 19:03:14 UTC, ketmar wrote: 1. cassowary is dynamic solver, it can continuously adjust it's solution as more and more constraints are added. actually, that is one of it's core features. Ah ok, but I suppose that would also mean that things may jump around during

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 19:42:53 UTC, Nick Sabalausky wrote: Progressive rendering made sense back when you could literally watch each image on the page gradually get pulled in over the wire (and when the layout more or less matched the HTML as it came in over-the-wire). But now it's

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 11:50:48 UTC, Suliman wrote: On Tuesday, 23 June 2015 at 11:41:03 UTC, Wyatt wrote: On Tuesday, 23 June 2015 at 11:37:41 UTC, Suliman wrote: Am I right understand that web assembly would not completely new technology and would be just evolution of asm.js, so all of

Re: D could catch this wave: web assembly

On Wednesday, 24 June 2015 at 07:25:26 UTC, Joakim wrote: So they're only talking about GC support for integrating with javascript and DOM objects, not the GC for some other language compiled to webasm. I thought Ola was talking about the latter, maybe he was talking about the former. I'm

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 18:58:00 UTC, ketmar wrote: nope, X is a window system. it's windows which is *not* window system, but window system with very simplistic toolkit bolted on top of it. that was not a bad idea considering the hardware windows aimed, but now it's a legacy crap, and

Re: D could catch this wave: web assembly

On Wednesday, 24 June 2015 at 09:38:02 UTC, Ola Fosheim Grøstad wrote: It's been done, as the FAQ quoted above notes. If you're talking about integrating with javascript and DOM objects, they say they plan to support that eventually also. I don't think you can have efficient concurrent GC

Re: D could catch this wave: web assembly

On Wed, 24 Jun 2015 06:43:00 +, Ola Fosheim Grøstad wrote: On Tuesday, 23 June 2015 at 19:03:14 UTC, ketmar wrote: 1. cassowary is dynamic solver, it can continuously adjust it's solution as more and more constraints are added. actually, that is one of it's core features. Ah ok, but I

Re: D could catch this wave: web assembly

On Monday, 22 June 2015 at 21:50:22 UTC, Nick Sabalausky wrote: Interesting. I'll have to look into that more. (Such as, will it run on Android phones or does it need separate hardware?) Well, the commercially-released phones (two so far from BQ Readers, and one to be put on sale in the EU

Re: D could catch this wave: web assembly

On Wed, 24 Jun 2015 11:44:09 +, Kagamin wrote: I'm talking about native UI getting screwed up on high DPI. Native UI is supposed to fit whatever space it's given, otherwise it works, but not as good as it's supposed to. Imagine your desktop doesn't fit the screen and gets scrolled. On the

Re: D could catch this wave: web assembly

On Wednesday, 24 June 2015 at 15:30:58 UTC, ketmar wrote: yeah. that's why people constantly complains that the very same web pages looks like crap on their mobiles, or on their desktops. a perfect fit! That's because they are designed to be pixel-precise, like native UI, so they have the

Re: D could catch this wave: web assembly

On 06/24/2015 11:34 AM, Joseph Rushton Wakeling wrote: Embedded OS architecture isn't really my comfort zone, but as far as I can see, they use an Android-derived hardware compatibility layer where any proprietary components (drivers etc.) are isolated from the rest of the OS. I've always

Re: D could catch this wave: web assembly

On 06/24/2015 11:37 AM, ketmar wrote: with the current trend to make a page consisting of huge fullscreen image and three columns of useless bla-bla text under it, it doesn't really matter if you will see the page sooner: there is no useful information anyway. ;-) Hear, hear! :)

Re: D could catch this wave: web assembly

On 06/24/2015 11:45 AM, Kagamin wrote: On Wednesday, 24 June 2015 at 15:30:58 UTC, ketmar wrote: yeah. that's why people constantly complains that the very same web pages looks like crap on their mobiles, or on their desktops. a perfect fit! That's because they are designed to be

Re: D could catch this wave: web assembly

On 06/24/2015 11:34 AM, ketmar wrote: i ported [cassowary] to D some time ago. Github?

Re: D could catch this wave: web assembly

On 06/24/2015 03:25 AM, Joakim wrote: I simply disagree that taking one feature, multi-window UIs, is convergence in any meaningful sense, so you can say they've just become desktops. I've tried to persuade you and Kagamin otherwise and appear to have failed. :) Well, I guess it's good that

Re: D could catch this wave: web assembly

On Wed, 24 Jun 2015 06:38:38 +, Ola Fosheim Grøstad wrote: On Tuesday, 23 June 2015 at 19:42:53 UTC, Nick Sabalausky wrote: Progressive rendering made sense back when you could literally watch each image on the page gradually get pulled in over the wire (and when the layout more or less

Re: D could catch this wave: web assembly

On Wed, 24 Jun 2015 12:30:27 -0400, Nick Sabalausky wrote: On 06/24/2015 11:34 AM, ketmar wrote: i ported [cassowary] to D some time ago. Github? no, repo.or.cz ;-) http://forum.dlang.org/thread/btoozbdfmuoopdrfr...@forum.dlang.org that repo is slightly outdated, as i moved the port to

Re: D could catch this wave: web assembly

On Wed, 24 Jun 2015 15:45:46 +, Kagamin wrote: That's because they are designed to be pixel-precise, like native UI in *my* world, native UIs doesn't even know what pixel is. signature.asc Description: PGP signature

Re: D could catch this wave: web assembly

Nick, you might be interested in this quick thing I just wrote up: http://arsdnet.net/articles/web-apps.html A few years ago, I was talking about a new windowing system... and believe it or not, I'm still slowly moving forward with it, but I think existing X is good enough to start with for

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 11:09:31 UTC, Joakim wrote: On Monday, 22 June 2015 at 16:34:58 UTC, Ola Fosheim Grøstad wrote: People are already writing less javascript, but without a GC in webasm most languages are better of compiling to javascript or a mix. The problem is that they may be

Re: D could catch this wave: web assembly

On 06/23/2015 12:36 PM, Adam D. Ruppe wrote: On Tuesday, 23 June 2015 at 16:18:01 UTC, Nick Sabalausky wrote: Yea, I'll have to take a closer look at that. My first impression is that Linux VM sounds very heavy-weight, but I supposed it need not necessarily be. Well, keep in mind that I want

Re: D could catch this wave: web assembly

On 06/23/2015 09:44 AM, Adam D. Ruppe wrote: Nick, you might be interested in this quick thing I just wrote up: http://arsdnet.net/articles/web-apps.html A few years ago, I was talking about a new windowing system... and believe it or not, I'm still slowly moving forward with it, but I think

Re: D could catch this wave: web assembly

On 06/23/2015 07:09 AM, Joakim wrote: But if you have some emotional connection with the term desktop and can't take the fact that they're being rendered defunct, I can see why you'd want to ignore all that and just call the new devices converged or desktops. :) As opposed to someone with an

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 16:18:01 UTC, Nick Sabalausky wrote: Although I wouldn't put too much reliance on X, what with Wayland on the way. meh, wayland doesn't look very interesting to me, especially in this use case where I'd want a network protocol because the application runs on an

Re: D could catch this wave: web assembly

On Tue, 23 Jun 2015 18:26:07 +, deadalnix wrote: I'm not sure of your use case, but wayland is clearly a huge step forward compared to X. yep, they reinvented DirectFB and dropped alot of libs on top of it. really a huge step. signature.asc Description: PGP signature

Re: D could catch this wave: web assembly

On 06/23/2015 03:03 PM, ketmar wrote: 2. actually, we should drop that progressive rendering. so-called web apps already dropped that, drawing rotating shit icon instead while they are loading megabytes of js. there is no sense to support progressive rendering anymore: it's either not working

Re: D could catch this wave: web assembly

On Sat, 20 Jun 2015 19:40:35 +, Ola Fosheim Grøstad wrote: On Saturday, 20 June 2015 at 16:20:31 UTC, ketmar wrote: On Sat, 20 Jun 2015 16:14:43 +, Ola Fosheim Grøstad wrote: On Saturday, 20 June 2015 at 15:36:45 UTC, ketmar wrote: it was designed to ignore that fact altogether.

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 16:36:21 UTC, Adam D. Ruppe wrote: On Tuesday, 23 June 2015 at 16:18:01 UTC, Nick Sabalausky wrote: Although I wouldn't put too much reliance on X, what with Wayland on the way. meh, wayland doesn't look very interesting to me, especially in this use case where

Re: D could catch this wave: web assembly

On Sat, 20 Jun 2015 17:00:43 +, Kagamin wrote: Well, it's just windows api was simple enough to be usable directly, while X11 didn't fly that way and didn't receive development since everybody used toolkits and all features were implemented in toolkits, which in the end used X11 as plain

Re: D could catch this wave: web assembly

On 06/23/2015 12:37 PM, Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= ola.fosheim.grostad+dl...@gmail.com wrote: On Tuesday, 23 June 2015 at 11:09:31 UTC, Joakim wrote: This is nonsense. They're just dumping in everything they can think of, that has nothing to do with backwards-compatibility. Web

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 11:41:03 UTC, Wyatt wrote: On Tuesday, 23 June 2015 at 11:37:41 UTC, Suliman wrote: Am I right understand that web assembly would not completely new technology and would be just evolution of asm.js, so all of webassembly apps would run in old javascript virtual

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 11:09:31 UTC, Joakim wrote: As for a GC, why would webasm need to provide one? I'd think the languages would just be able to compile their own GC to webasm, which seems low-level enough. From the docs: Even before GC support is added to WebAssembly, it is

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 14:46:56 UTC, Joakim wrote: Sorry, I didn't read the conclusion of that link I gave you: I just linked it for the large graph showing and forecasting the number of global smartphone users. Well, people upgrade their phones and there were a lot of phone users.

Re: D could catch this wave: web assembly

On Monday, 22 June 2015 at 16:34:58 UTC, Ola Fosheim Grøstad wrote: People are already writing less javascript, but without a GC in webasm most languages are better of compiling to javascript or a mix. The problem is that they may be writing less javascript now, but they're still stuck with

Re: D could catch this wave: web assembly

Am I right understand that web assembly would not completely new technology and would be just evolution of asm.js, so all of webassembly apps would run in old javascript virtual machine?

Re: D could catch this wave: web assembly

On Tuesday, 23 June 2015 at 11:37:41 UTC, Suliman wrote: Am I right understand that web assembly would not completely new technology and would be just evolution of asm.js, so all of webassembly apps would run in old javascript virtual machine? They covered this question in the FAQ, too:

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 11:56:13 UTC, Joakim wrote: importance of which Wyatt and I discussed above. Just by webasm being implemented in all major browsers, it would certainly lead to a _lot_ less javascript getting written, once devs actually have a choice of other languages, even if

Re: D could catch this wave: web assembly

On 06/22/2015 05:16 AM, Joakim wrote: I really liked the new Fisher-Price style of desktop Windows 8, Ugh, now *that* one I don't like. Simplicity is nice, but ugly is just ugly. It looks like a re-imagining of Win1 and Win2 drawn up by a hung-over unicorn ;) along with better

Re: D could catch this wave: web assembly

On 06/22/2015 04:01 PM, Joseph Rushton Wakeling wrote: On Sunday, 21 June 2015 at 15:59:57 UTC, Nick Sabalausky wrote: On 06/21/2015 09:45 AM, Joseph Rushton Wakeling wrote: Threw what in the trash-bin? https://en.wikipedia.org/wiki/Ubuntu_for_Android Though I may very well be missing

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 18:51:41 UTC, Nick Sabalausky wrote: On 06/21/2015 05:07 AM, Joakim wrote: Simply dumping more features on top of the old web stack is a recipe for failure. Meh, it seems to be working for them so far ;) But I agree, it's a bad approach, and hopefully will

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 15:59:57 UTC, Nick Sabalausky wrote: On 06/21/2015 09:45 AM, Joseph Rushton Wakeling wrote: Threw what in the trash-bin? https://en.wikipedia.org/wiki/Ubuntu_for_Android Though I may very well be missing something. Yea, Ubuntu for Android was a cool idea that

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 11:56:13 UTC, Joakim wrote: On Sunday, 21 June 2015 at 10:13:22 UTC, Kagamin wrote: Do you think it's wise to ignore 2 billion users? The size of the mobile market doesn't mean you can target it entirely. The article suggests currently we have era of services and

Re: D could catch this wave: web assembly

Hmm, looks like the rest of my response got lost on the way to the newsgroup somewhere, reposting the rest below: On Sunday, 21 June 2015 at 10:07:05 UTC, Ola Fosheim Grøstad wrote: On Sunday, 21 June 2015 at 09:07:52 UTC, Joakim wrote: recent years and that's about it. If this webasm effort

Re: D could catch this wave: web assembly

On Saturday, 20 June 2015 at 19:00:08 UTC, Joakim wrote: On Saturday, 20 June 2015 at 15:21:29 UTC, Kagamin wrote: High DPI settings screw up native UI too if it's not pixel-precise, and ignoring user preferences is infraction, I'm afraid. And this is where web actually shines: it's designed

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 13:51:06 UTC, Kagamin wrote: On Sunday, 21 June 2015 at 11:56:13 UTC, Joakim wrote: Apparently most new apps nowadays are ignoring that legacy desktop market. You mean services? I meant mobile apps, many of which are services, but even stand-alone apps with no

Re: D could catch this wave: web assembly

On 06/21/2015 06:29 AM, Kagamin wrote: On Saturday, 20 June 2015 at 19:00:08 UTC, Joakim wrote: The highest-DPI devices I use nowadays are mobile devices and, in my experience, websites are the ones who most often get it wrong. I mean only design possibility, which is not taken advantage of

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 10:07:05 UTC, Ola Fosheim Grøstad wrote: On Sunday, 21 June 2015 at 09:07:52 UTC, Joakim wrote: As I said before, start from scratch. Stop trying to shoehorn a full app runtime into the browser because you will only lose to native app runtimes, which is already

Re: D could catch this wave: web assembly

On Saturday, 20 June 2015 at 20:31:35 UTC, Nick Sabalausky wrote: Interestingly, Canonical could've beat everyone to the punch here. They had what was basically continuum for linux more or less already working, but then...they just...what, threw it in the trash bin or something? I dunno, I

Re: D could catch this wave: web assembly

On 06/21/2015 09:45 AM, Joseph Rushton Wakeling wrote: On Saturday, 20 June 2015 at 20:31:35 UTC, Nick Sabalausky wrote: Interestingly, Canonical could've beat everyone to the punch here. They had what was basically continuum for linux more or less already working, but then...they just...what,

Re: D could catch this wave: web assembly

On 06/21/2015 05:07 AM, Joakim wrote: Simply dumping more features on top of the old web stack is a recipe for failure. Meh, it seems to be working for them so far ;) But I agree, it's a bad approach, and hopefully will finally collapse. Prefetching and caching is used by _all_ app

Re: D could catch this wave: web assembly

On 06/21/2015 01:42 AM, Joakim wrote: I'd say this is a temporary respite before the final collapse. The only reason it hasn't happened yet is because mobile devices have not worked well with plugging into a large monitor with a mouse and keyboard, but that is now changing. [...] Sure, but

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 05:42:13 UTC, Joakim wrote: No, I'm not arguing for pages at all, I'm saying that model is dead and gone. I think the hyperlink was the killer feature of the web, but everything else, HTML/CSS/JS, is just detritus accumulated on top, that needs to be thrown away.

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 06:20:53 UTC, Ola Fosheim Grøstad wrote: Thrown away in favour of what? As I said before, start from scratch. Stop trying to shoehorn a full app runtime into the browser because you will only lose to native app runtimes, which is already happening because they

Re: D could catch this wave: web assembly

On Sunday, 21 June 2015 at 09:07:52 UTC, Joakim wrote: As I said before, start from scratch. Stop trying to shoehorn a full app runtime into the browser because you will only lose to native app runtimes, which is already happening because they aren't constrained by such legacy decisions as an

Re: D could catch this wave: web assembly

On Saturday, 20 June 2015 at 19:00:08 UTC, Joakim wrote: Pretty soon it won't. :) There are an estimated 2.5 billion smartphone users: http://www.asymco.com/2014/04/07/postmodern-computing/ The highest estimates of desktop and laptop users I've seen don't crack 2 billion. That means

Re: D could catch this wave: web assembly

Am Thu, 18 Jun 2015 08:05:46 + schrieb John Colvin john.loughran.col...@gmail.com: This appears to have involvement from all major browser vendors, which provides hope it might actually catch on properly. An llvm backend will be created which will compile to wasm, hopefully LDC and/or

Re: D could catch this wave: web assembly

On Saturday, 20 June 2015 at 15:36:45 UTC, ketmar wrote: it was designed to ignore that fact altogether. html/css layouting is a pitiful attempt and barely usable. bwah, it can't even do normal constraints! Hmmm, what do you mean by normal constraints? Modern CSS provides many options, too

Re: D could catch this wave: web assembly

On Sat, 20 Jun 2015 12:32:11 -0400, Nick Sabalausky wrote: On 06/20/2015 12:20 PM, ketmar wrote: On Sat, 20 Jun 2015 16:14:43 +, Ola Fosheim Grøstad wrote: On Saturday, 20 June 2015 at 15:36:45 UTC, ketmar wrote: it was designed to ignore that fact altogether. html/css layouting is a

Re: D could catch this wave: web assembly

On Saturday, 20 June 2015 at 15:36:45 UTC, ketmar wrote: On Sat, 20 Jun 2015 15:21:28 +, Kagamin wrote: High DPI settings screw up native UI too if it's not pixel-precise, and ignoring user preferences is infraction, I'm afraid. /me wonders if windows still cannot into dynamic layouts.

Re: D could catch this wave: web assembly

On Friday, 19 June 2015 at 15:13:11 UTC, Joakim wrote: Hmm... Web: write once with html, css, js. Native: write three times in obj-c, java, c#. Not sure why the former should sink and not the latter. Because writing it once in HTML/CSS/JS takes you much longer than writing it in Java, while

Re: D could catch this wave: web assembly

On Sat, 20 Jun 2015 14:06:50 +0200, Marco Leise wrote: If you have a perfectly working old notebook with Windows XP on it, I can recommend QtWeb for its low resource usage and modern-ish feature set. It is a little unstable and rough around the edges though: http://www.qtweb.net/ Qt+WebKit.

Re: D could catch this wave: web assembly

On Sat, 20 Jun 2015 16:14:43 +, Ola Fosheim Grøstad wrote: On Saturday, 20 June 2015 at 15:36:45 UTC, ketmar wrote: it was designed to ignore that fact altogether. html/css layouting is a pitiful attempt and barely usable. bwah, it can't even do normal constraints! Hmmm, what do you

Re: D could catch this wave: web assembly

On Sat, 20 Jun 2015 16:18:28 +, Kagamin wrote: Windows API would be similar to X11, where you just specify everything in pixels and toolkits building on top of it manually do all the recomputations and layout policies, not the UI server. only in windows toolkit is built into system. and

Re: D could catch this wave: web assembly

On Sat, 20 Jun 2015 15:21:28 +, Kagamin wrote: High DPI settings screw up native UI too if it's not pixel-precise, and ignoring user preferences is infraction, I'm afraid. /me wonders if windows still cannot into dynamic layouts. in any decent gui lib it's actually *harder* to build a gui

  1   2   >