151–160 of 168 posts
Was reading through https://www.diva-portal.org/smash/get/diva2:1451494/FULLTEXT... - what's the current status/eta of raw sockets? Last time I checked wasm consensus seemed to suggest they will never be supported?
Earlier quoted context omitted.
If that was the case, Google wouldn't be pushing Houdini, and everyone else pushing WebGL and WebGPU. By the way, already mastered all CSS tricks to force hardware rendering? Motif might be irrelevant, yet its ideas live on across all modern toolkits for native programming and the Web had to wait for the WPF team to bother submitting WPF grids to W3C as base concept. Delphi and VB are doing pretty well. https://www.e…
> If that was the case, Google wouldn't be pushing Houdini, and everyone else pushing WebGL and WebGPU. Because they can't possibly be pushing very diminishing return features, or stuff that only applies to niche markets ? > And their ideas influence one of the best Web RAD tools, that only we in enterprise care to use. It's not like "used for enterprise software" is a great endorsement :-)
Earlier quoted context omitted.
> Have you ever seen any UI on the web that approaches the complexity of game UIs? I have personally built tools on the web more complex than the game UIs in your link. > Anywhere there's such complexity on the web, you get lots and lots of hardcoded values: from hardcoded media breakpoints to entirely different layouts for different resolutions and screen sizes. ...and I didn't use a single media breakpoint in any o…
Sorry for butting in on this interesting conversation but regarding media queries being code smell, I currently see no other portable way to deliver multi-resolution background images. :-( Without JS libs that is...
Your usecase sounds legitimate to me. Given that you're talking about different image files, you're fundamentally talking about discrete cases, for which media queries are appropriate. The problems come up when people take something that doesn't need to consist of discrete cases - like element sizing, or whatever - and turn it into a set of discrete cases using media queries. This makes the page fragile against unexpected new sizes, instead of interpolating cleanly. Good CSS derives as many of its values as possible by channeling the continuous inputs of content size, viewport size, etc into other continuous values like the size and positioning of individual elements. The browser already does this by default; you just have to implement your vision while preserving as much of that intrinsic property as possible :)
Earlier quoted context omitted.
All of it already exists with the JVM.
Isn't the JVM too high level for compiled languages without garbage collection? E.g. can I efficiently compile C to the JVM without asm.js-style hacks which degrade performance?
Earlier quoted context omitted.
> If that was the case, Google wouldn't be pushing Houdini, and everyone else pushing WebGL and WebGPU. Because they can't possibly be pushing very diminishing return features, or stuff that only applies to niche markets ? > And their ideas influence one of the best Web RAD tools, that only we in enterprise care to use. It's not like "used for enterprise software" is a great endorsement :-)
It is the only target demography that actually pays for tools.
Earlier quoted context omitted.
It is the only target demography that actually pays for tools.
Perhaps it's the only target demographic that actually needs such tools :-)
Then they act surprised that they only get as far as reinventing carriages with different amounts of wheels and horses every couple of years.
Earlier quoted context omitted.
A low hanging use case would be scripts for a distributed data analysis system. e.g. You type in a function and then it compiles to wasm and is sent out to run on worker nodes. Or you write code snippets for code to run in a distributed dag. This exists with e.g. shared file systems (how hpc works, how hadoop works) and Python can pickle code and send it over a socket (be aware that this is a security risk). WASM see…
SQL UDFs might be another potential use-case in the same category.
Earlier quoted context omitted.
Thats still way more awkward than what the web provides. - I don't need to uninstall / delete a website when I'm done with it - I don't need to pick an executable format. (Portable or installed? windows mac or linux? dpkg or rpm? From the dev's website or through homebrew/apt? Is a portable executable even available for this application?) - I don't need to give the author of the webpage access to all my local files.…
The facebook website managed to eat 1GB of ram alone multiple times.
"Oh yeah its this cool social network.. just download - no, not the portable executable version... yeah, its 300 megs... Then you need to click it to install it"
Earlier quoted context omitted.
You're talking purely about performance. Sure, you can do whatever you want in a game UI, and it will probably outperform a web UI. But there's a reason game UIs often scale/function badly as soon as you change the screen size or the input type: they aren't built on a platform that has flexibility baked into its bones. In many cases they aren't build on any kind of platform at all. They often have element/text positi…
> And yet: it's only used in a very small fraction of the apps out there. Qt is estimated to account for ~10-15% of all c++ development, which is a very fair amount for any one single framework. You just don't see it because most of the time it blends in perfectly. Do you think about Qt when you're using your LG TV ? (LG WebOS is Qt). Or OneDrive Desktop ?
Earlier quoted context omitted.
The facebook website managed to eat 1GB of ram alone multiple times.
Right! And despite that, it loads in seconds. Traction would be very different if people had to install facebook on their computers to try it out! "Oh yeah its this cool social network.. just download - no, not the portable executable version... yeah, its 300 megs... Then you need to click it to install it"
Not everyone is luckily at home using broadband connections with flat rate.