vaibhavkul | 7 months ago | on: The surprising geography of American left-handedness (2015)
vaibhavkul's comments
vaibhavkul | 1 year ago | on: Rewriting my website in plain HTML and CSS
Couldn't the code highlighting be also handled statically during the build process?
vaibhavkul | 2 years ago | on: Shouldn't FROM come before SELECT in SQL? (2011)
vaibhavkul | 6 years ago | on: Virtual DOM is pure overhead (2018)
Maybe there is a future where flutter style renderers become standard, have a container like a browser (to avoid the entire runtime baggage when it's deployed), and people target it instead of the DOM? This gives best of both worlds--write apps in a declarative way, without the need of any external "optimizing" framework.
vaibhavkul | 9 years ago | on: The new TrueType interpreter in FreeType 2.7.0
vaibhavkul | 9 years ago | on: Java Polyfill for the Browser
vaibhavkul | 10 years ago | on: Are We Living in a Computer Simulation?
What is real?
vaibhavkul | 10 years ago | on: Rust via its Core Values
It didn't occur to me that: ownership transfer means variable cannot be used, so if it's used means there's an error, so checking for error itself gives you the information that you cannot use it. So highlighting error can be used instead of the specific ownership transfer.
I don't know of any other specific cases where there's no error, but it would be helpful to have a different color for certain ownership semantics.
vaibhavkul | 10 years ago | on: Rust via its Core Values
e.g. in
let new_owner = original_owner;
println!("{}", original_owner);
we could have original_owner on the second line have a different color signifying it doesn't own anything.Or, does such a syntax highlighter already exist?
vaibhavkul | 10 years ago | on: Google 'mic drop' Gmail joke for April Fools' day backfires
vaibhavkul | 10 years ago | on: Add Reactions to Pull Requests, Issues, and Comments
vaibhavkul | 10 years ago | on: Start up India: Webcast [video]
vaibhavkul | 10 years ago | on: Vue.js: 2015 in Review
vaibhavkul | 10 years ago | on: 'New' Python modules of 2015