Also, "If you like this, then you might also like" Ali Farka Touré / Toumani Diabaté (From a different African country). https://en.wikipedia.org/wiki/Toumani_Diabat%C3%A9
1,329 karma · joined December 17, 2016
Also, "If you like this, then you might also like" Ali Farka Touré / Toumani Diabaté (From a different African country). https://en.wikipedia.org/wiki/Toumani_Diabat%C3%A9
They were totally complicit allegedly.
I wonder if the DERPy-stuff helps remove most of the bandwidth concerns - thinking out loud...
‘It’ doesn’t need anthropomorphizing in the slightest. It’s a computer program that can slurp up data.
Carbon could be a great SxS language with enough inertia building up over time: still never aim to replace C++ (a fool’s errand) but always work in conjunction with large C++ codebases.
It’s such a great pleasure to write things in TS while always being able to use mix-match JS libraries and tooling and debugging. I hope Carbon achieves a similar result moving the industry and engineers forward without resorting to “languages are religions” tediousness.
To top it off, this person was later offered a “deal” to be hired into their alleged fraud business once it was merged.
Too damn cute.
Armchair scientisting aside, this news seems like the most exciting news over the past few years - a great way to end this year (/pandemic). We are far out from a production-ready thingy, but if it took decades for brilliant scientists to conjure up this initial clunky toy thingy, I am sure an army of scientists/companies would work at building the real thing much, much faster: we had only a freaking 8086 not 30 years ago!!
We have the basic blueprint from government funded research no less.
I like your rationale around other cloud providers’ virtualization solutions.
I think the main comparison that’s lacking is one of v8 isolates vs strict site isolation which runs on separate processes. Why would the Chrome team build such a complex thing if v8 isolates passed rigorous security standards/bar etc? This would be good to get your insights on.
What’s the actual cost of separate processes vs v8 isolate? In terms of cpu/memory/latency mainly. I would guess either would win over other virtualization techniques but between the two is it really that stark of a difference?
I am more and more convinced you may have seen the light shine through and people such as me are missing the big picture: so providing answers for this line of attack would be more helpful than comparing with other virtualization mechanisms.
Without process isolation, all it takes is one bad Chromium commit or a incorrectly allow-listed JS/V8 command for this model to fall through regardless of how thorough the defense-in-depth/vetted Workers may be.
"the public clouds that run arbitrary native code in hardware VMs." -> Isn't it double whammy then that a V8 isolate + HW attack surface in combination could provide an order of magnitude more hackability?
"Last I heard there were still some lower-powered Android phones where the overhead was too high" -> I believe a Zygote-process fork was made available to Chromium at some point (https://chromium.googlesource.com/chromium/src/+/HEAD/docs/l... ?).
I haven't looked deeply enough, but does this course use a higher-level 'package' such as OpenAI Gym or teach at a lower-level? (Is lower-level stuff even possible...)
Similar to curved monitors…
Now states are combating such hesitancy by drawing lottery for vaccinated folks.
Like, having this magic, absolutely mind boggling potion that prevents serious illness and death *isn't* already the lottery win of our lifetime??
People in India and elsewhere are dying because of lack of vaccines and here we have educated, first world countries struggle to get their citizens vaccinated.
Unfortunately shaming such people will only push them further into antivax territory.
The immediate mode renderer is great for toy programs. Similar to how you could reproduce 'look here is how simple it is to write hello world and compute the millionth digit of PI' in a new esoteric language...
Occlusion, hit-testing, state changes, scrolling/animations even in the simplest forms will fall over. Infact, that's why we have every major browser move their touch and animation systems into a layer based compositor system (into a separate thread / process).
The author also grossly misses their own example of 'how a spreadsheet with many rows and columns will update faster using ImgUI' and how Instagram styled apps will fare better ImgUi.
A retained mode renderer will use virtual scrollers, efficient culling of nodes for both display and hit-testing (scale to billions of virtual cells) and more importantly help a team of people coordinate their work and get things done.
We are no longer in the 90s.
Then I grew up and 'here I am', and they said, 'not you, it's for the future generation'.
I know a pyramid scheme when I see one."