4 ms·

Hey cool, a new bowser which seems function- oh for fucks sake it's goddamn node.js again. Stop this shit. I don't need a node runtime taking up 400MB on top o

by pikzen 12y ago

Hey cool, a new bowser which seems function- oh for fucks sake it's goddamn node.js again. Stop this shit. I don't need a node runtime taking up 400MB on top of an already memory hungry browser. I don't need a browser using and abusing fucking javascript to run. Looks good though, and features seem interesting.

rtpg 12y ago
You do realise that node.js is basically just V8 right? You kind of need a Javascript runtime for your browser anyways. Chrome and FF had a decent amount of memory leaks "despite" being written in C++
- dchest 12y ago
  Also, Chromium has a Blink-in-JavaScript initiative: http://www.chromium.org/blink/blink-in-js http://www.chromium.org/blink/blink-in-js Blink-in-JavaScript is a mechanism to enable Blink developers to implement DOM features in JavaScript (instead of C++).
- pikzen 12y ago
  >You do realise that node.js is basically just V8 right? Aside from the fact that I don't need a goddamn 400MB runtime running all the time, the major problem is that node.js (and javascript, by extension) are awful tools for anything desktop related. (Server related too, but that's more a personal opinion that node.js is cancer (hi ted)). Performance has never been up to par with C/C++ (no, testing a 100 line script is not a valid bench. No, comparing it against awful code is not a valid bench either. Which kinda invalidates 90% of node benchmarks.). But sure, let's trade a bit of performance for ease of use, I'm all for it. Except when that tradeoff implies using javascript, whose warts are known by anyone sensible. Having a single threaded architecture for a browser, which should basically be running one process/thread per tab is an error we shouldn't be doing anymore in 2015. I sure love one tab crashing my entire browser(hi firefox). Which I managed to do quickly with Vivaldi, but I can understand that it's still a beta. Also, let's ignore the OS's native UI libraries because atom-shell/whatever-desktop-lib-they-use chose to render the entire thing as a DOM because reasons. >Chrome and FF had a decent amount of memory leaks "despite" being written in C++ Nowhere did I hold Chrome and Firefox in high regards when it comes to memory usage. Chrome seems to think that allocating 4GB of memory for 20ish tabs is a good idea. Firefox is a bit better but has this slight tendency to leak memory like crazy. tl;dr: browsers suck but that's not a reason to write one in fucking javascript awaiting the nodejs defense force
fasteo 12y ago
Chill out dude; it's only a browser.
chj 12y ago
Not that horrible. Open HN, and it's only taking 200MB.

by pikzen 12y ago

rtpg 12y ago

You do realise that node.js is basically just V8 right? You kind of need a Javascript runtime for your browser anyways. Chrome and FF had a decent amount of memory leaks "despite" being written in C++

dchest 12y ago
Also, Chromium has a Blink-in-JavaScript initiative: http://www.chromium.org/blink/blink-in-js http://www.chromium.org/blink/blink-in-js Blink-in-JavaScript is a mechanism to enable Blink developers to implement DOM features in JavaScript (instead of C++).
pikzen 12y ago
>You do realise that node.js is basically just V8 right? Aside from the fact that I don't need a goddamn 400MB runtime running all the time, the major problem is that node.js (and javascript, by extension) are awful tools for anything desktop related. (Server related too, but that's more a personal opinion that node.js is cancer (hi ted)). Performance has never been up to par with C/C++ (no, testing a 100 line script is not a valid bench. No, comparing it against awful code is not a valid bench either. Which kinda invalidates 90% of node benchmarks.). But sure, let's trade a bit of performance for ease of use, I'm all for it. Except when that tradeoff implies using javascript, whose warts are known by anyone sensible. Having a single threaded architecture for a browser, which should basically be running one process/thread per tab is an error we shouldn't be doing anymore in 2015. I sure love one tab crashing my entire browser(hi firefox). Which I managed to do quickly with Vivaldi, but I can understand that it's still a beta. Also, let's ignore the OS's native UI libraries because atom-shell/whatever-desktop-lib-they-use chose to render the entire thing as a DOM because reasons. >Chrome and FF had a decent amount of memory leaks "despite" being written in C++ Nowhere did I hold Chrome and Firefox in high regards when it comes to memory usage. Chrome seems to think that allocating 4GB of memory for 20ish tabs is a good idea. Firefox is a bit better but has this slight tendency to leak memory like crazy. tl;dr: browsers suck but that's not a reason to write one in fucking javascript awaiting the nodejs defense force

fasteo 12y ago

Chill out dude; it's only a browser.

chj 12y ago

Not that horrible. Open HN, and it's only taking 200MB.