@wattengard
c# js node <insert new cool thing here>
Nothing here yet.
Nothing here yet.
No blogs yet.
You are still misunderstanding Shadow DOM. It's not an abstraction... The Shadow DOM is things like the default controls on a <video>-tag, the slider that appears when you give an <input>-tag the type of "range". Things that doesn't show up in the DOM that you are able to manipulate. There is (was?) no way to style the default knob of the default slider in a ranged input until recently. The solution is (was?) to hide the default slider, and build your own with your own components. And you are still mixing up virtual DOM and shadow DOM, it has nothing to do with each other...
No. You actually got this all wrong. The "Shadow DOM" is part of the DOM that doesn't show up if you use "inspect element" in the dev-tools. We just recently got API-access to manipulate it so the whole concept is a bit muddy to noobs like me at the moment. I've attached a few links about it at the bottom. The concept of a "Virtual DOM" is something completely different. The Virtual DOM is used to make updates to the DOM without affecting the "real" DOM until you are ready to write to the screen. When you are ready, you diff the virtual DOM with the real DOM and update all the needed DOM-nodes in one go. And you can call it whatever you want, but as long as that method beats other methods in a benchmark, that's the way to go. https://www.html5rocks.com/en/tutorials/webcomponents/shadowdom/ https://developers.google.com/web/fundamentals/web-components/shadowdom https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM http://reactkungfu.com/2015/10/the-difference-between-virtual-dom-and-dom/
I mostly concur with most of the other people here that you should go with a large IPS-based screen with at least 1440px height resolution. I love 21:9-screens for programming, especially if you either develop for web, or use the web for help. I'm currently looking at a 35" 21:9 AMVA-panel monitor for home use because I want to use it for both gaming and development.
I'm currently using Fira Code because I love coding with ligatures. In VSCode I'm using the color-theme Cobalt Next which is a bastardization of Wes Bos' Cobalt 2 and a theme called Oceanic Next. The screnshot shows the ligatures (observe the triple equals and the arrow-function) and the theme. I also code with visible whitespace (not in between words but before and after). I know there is a Fira Code + iScript mashup to achieve the same concept as Operator Mono , but I haven't tried it yet. I love the concept though.