madez

59 ms·

571.
by madez 9y ago
The authors say in the talk that that likely wouldn't be significantly faster than the equivalent x86 instructions.
572.
by madez 9y ago
> If I can infer from Steve's stance the opinion of Mozilla Mozilla's decisions speak for themselves. There is no need to reference individuals, and less so without very solid basis (which there wasn't).
573.
by madez 9y ago
Sorry for referencing you that way. I can't change it anymore. I could have pointed to decisions taken by Mozilla to explain my disappointment instead of extrapolating from your statements. Even if your view were exactly what I was cri
574.
by madez 9y ago
I think we don't contradict each other necessarily. JavaScript applications not delivered by websites but through the package manager would be okay for me. We would have the sandbox on one side and the accounting and responsibility on
575.
by madez 9y ago
Starting and stopping a video is an interactive action. Even a drop down menu is interactive. Arbitrary interactivity may not be possible, but I think that is totally acceptable for what we are talking about: remotly delivered, unaccounted,
576.
by madez 9y ago
Let me first thank you for the incredibly important work of finding and documenting behaviour of hardware we use. I see your point. However, if it's harder for the attacker, it is already a win. Also, this is just one example where Jav
577.
by madez 9y ago
They didn't state it directly, but indirectly. The exact quote is: > Since we were already locked into the Apple ecosystem (with paid apps and media), we bought iPhones. So, they are locked-in into the ecosystem partly because of me
578.
by madez 9y ago
HTML is capable of a dynamic interface, but it must be statically defined. With HTML5 we even have videos. The linked webpage including video work like a charm with JavaScript disabled. Furthermore I'd welcome a HTML6 as long as it sta
579.
by madez 9y ago
It's not impressive. However, it shows that I don't need to abstain from modern uses of my device. The first ancestor of this comment chain is saying, that they were locked-in partly because they couldn't move media out. This
580.
by madez 9y ago
It makes the use-case for this type of code deployment wider, it's more effective at what it's already used for, and it's also less auditable. These are three reasons why developing and supporting WebAssembly is finally again
581.
by madez 9y ago
There is a huge difference from the security perspective between rendering a static HTML site and executing JavaScript. That theoretically they might be close has no practical meaning, and insisting on it may paralyse us into doing nothing.
582.
by madez 9y ago
Rehashing an argument does not make it wrong, and continuing doing so is still important if it's valid and not considered accordingly. Users don't demand JavaScript nor WebAssembly, some developers do. Users want to easily discove
583.
by madez 9y ago
Recently here on Hacker News I had a short discussion with Steve Klabnik about JavaScript and WebAssembly among other things.[0] My point is that to execute randomly downloaded code is realistically impossible to secure, practically used to
584.
by madez 9y ago
There are techniques to prevent reading stored data in chips. Smartcards often have some of those protections.
585.
by madez 9y ago
With Android you are not necessarily forced into a locked-in ecosystem. I use a Google-free Android phone. I can watch movies and listen to music, talk to people and chat. And I'm free to take my data and move to another device. So, ye
586.
by madez 9y ago
You realize you are locked-in into a proprietary ecosystem. Clearly, that is bad for you and customer-unfriendly. But I wonder why you don't take action, and get alternatives that don't lock you in. Is this an example of the sunke
587.
by madez 9y ago
Well, I will not buy an Intel CPU anymore. I also try to avoid Intel in all other chip classes like networking chips where Intel is suspiciously active. Sometimes I wonder if their name is giveaway that people just don't realize. Soon
588.
by madez 9y ago
I also hate Intel and AMD for that, but I think they'd prefer we didn't hate them. I conclude that there are big reasons to still do what we hate them for. I'm afraid even a black swan event wouldn't make those reasons g
589.
by madez 9y ago
I wonder what else is in x86/arm64/common processors we don't know but would care about. In situations like these it really pays of to have at least some parts of the system developed as free software. In a dystopian alternat
590.
by madez 9y ago
> apt is designed around C It would be nice to have a list of what each of Apt, Pacman and Portage needed to change to accommodate Rusts needs. Thanks for your comments!
591.
by madez 9y ago
I'll try to keep it brief this time. > TL;DR: I don't think that WebAssembly really changes the game here, for good or for bad. It's a step in the wrong direction. Working on WebAssembly is not as bad as it could be becaus
592.
by madez 9y ago
JavaScript and WebAssembly are used like DRM on steroids. I explained myself here a bit more: https://news.ycombinator.com/item?id=15982323 Edit: Those who downvoted, do you disagree, or was there another reason?
593.
by madez 9y ago
Debian and Python seem to play nice with each other. > As such, with hundreds of Python modules and multiple versions of Python supported, Debian is the largest "integrated Python distribution". ( https://wiki.debian.
594.
by madez 9y ago
I didn't mean to exclude other systems by naming Apt, it was rather meant as an example. The non-Debian based systems, and even the non-Linux based systems are important. I agree that an OS independent package manager is a plus for Rus
595.
by madez 9y ago
> You're welcome! And thanks for your posts too. Thanks :-) > And also regardless of personal feelings, many people in the Rust world seem to be very excited about WebAssembly WebAssembly and JavaScript are used to create locked-
596.
by madez 9y ago
I thought unmarking the option to accept cookies would just completely disable cookies. Now, it makes sense. My fault.
597.
by madez 9y ago
Thanks for your elaborate comment. It is interesting to read and insightful. I just have comments for select sections: >> I don't consider it important to be able to compile Rust to JavaScript > We share this opinion, but comp
598.
by madez 9y ago
> Five years in, I think my journey has been successful so far. I’m proud of how far Rust has come. That said, there’s a lot more work to do. I’m still committed as ever to getting that work done, (...) It's good to hear that people
599.
by madez 9y ago
I can't whitelist/blacklist domains for cookies.
600.
by madez 9y ago
But FireFox is on a slippery slope. So, I think it is very much interesting if there are limits one can enforce legally, or not.

More ›