Hacker Newsnew | past | comments | ask | show | jobs | submit | mcsmash's commentslogin

I would imagine that this is true for the vast majority of PsyOps people. However. Just because it's true for the vast majority of people doesn't mean it's true for everyone. By your logic the fact that the majority of developers being people trying to make a living banging away at keyboard implies that there are no kernel divers, or AI magicians, or black hole image processors. Yes, it's mostly bags of rice, but someone at the executive level of a major social media platform might, just _might_ be getting orders that are a little above and beyond taking pictures of rice.


This. The internet desperately needs to progress beyond an advertisement driven business model. Disallowing these scripts seems a little heavy handed. Perhaps the addition of a "requestComputeResources" method to the browser's api would give a way to throttle them instead of outright banning them.


They make it optional.

To be real, though, somewhere close to 0% (rounded to the third decimal place) of users would agree to grossly inefficient cryptomining in the browser. As a web funding model it is terrible and is almost always akin to malware. It certainly costs the user much more in electricity costs than it will ever benefit web publishers.


And as a global ecological cost, it's pretty huge.


>They make it optional.

Mozilla? Optional protection? Don't trigger my memories.

They also made it optional to block unsigned extensions, which you could turn off if you wanted to tweak one to fix a bug because it wasn't being maintained fast enough.

Like, if you believed in the whole Open Source/tinkering philosophy, or something, which Mozilla may or may not care about.

Then, they started disallowing it in 2016.

And they turned off key remapping too.


I wholeheartedly agree that we need to progress beyond the ad-driven business model but is in-browser mining really a plausible replacement?

For one thing it's probably not a good idea on battery-powered devices, so it's only useful for monetizing desktop browsing. It also means that the money you make out of it depends on the average power your "customer" has available to mine.

Beyond that since mining is a zero-sum game it means that the more people opt for this model, the less money they individually make. Maybe today you make on average 0.001cent per minute and per user and a year from now you make a tenth of that. You have absolutely zero control on it since it's merely a factor of the total hashrate and the cryptocurrency's value.

I have a hard time imagining how this could become mainstream. Tipping using cryptocurrency microtransaction seems more promising but even that is far from a solved problem. I'd rather directly send $.002 to the website rather than waste $.01 of electricity for the website to make $.001 out of it.


The thing is that with ad networks you're at their mercy, if they don't want to sell ads on your site, you have no other option. While it would be nice to have a micropayment system built into browsers themselves, cryptomining is kind-of the best option.


Nobody would use that API if they can just do it anyway without the users consent


There's not really a way to detect that someone is cryptomining, they can just do it with regular JS or webgl (which has a compute focused API in the works). I don't think either of those features could ever be opt-in. Detecting mining in WebAssembly would be even harder.


And in other breaking news, the sky is blue, things fall down, and water is wet. Please stay tuned for further developments as these exciting stories continue to unfold.


Yes, solid evidence of inferred corruption is such old and boring news, hardly worthy of our time and attention.


Using the variable names i/j/k for loops is such a widely used convention that IMHO it doesn't really mater for a lot of people. Virtually everyone I know will read "array[i]" and know exactly what's going on.

And believe it or not, those variable names aren't arbitrary. They hearken from the ancient times: http://programmers.stackexchange.com/a/86911


I think there's a pretty big misconception about what a text editor and IDE even are. IMHO a text editor is program that edits text, nothing more, nothing less. The primary function of all development environments is to edit text, so an IDE is just something that adds tools to make this easier. Pretty much all IDEs have some facility to navigate files, navigate to specific functions, check syntax, build, etc. etc. etc.

So with this definition Vim (and Emacs too) are both IDEs; they're just stripped down so that the developer can choose what features they want to add, or extend it with their own. I'm using Vim for Python, Java, and in the recent past PHP. With the right plugins Vim easily rivals any IDE that I've ever used (to be fair I haven't used that many). It has the added benefits of being widely available, having a bare minimum of requirements, and since it's purely character based it's usable through nothing more than a terminal.


There are plugins that allow for debugging. I was hacking on a web-app that was possibly the worst PHP any one in my office had ever seen. I wouldn't have been able to get ANYTHING done without it. For anyone that's interested: http://www.vim.org/scripts/script.php?script_id=1152


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: