vaibhavkul

Forget emailing strangers, I have a hard time talking to my neighbours.

I too am mixed regarding doing things with different hands - for finer movements (writing, holding a spoon) I prefer using the left hand, while for stronger movements (punching, throwing a ball) I prefer using the right hand. Not sure why though, I never underwent any "retraining".

> the only Javascript on the site now is to highlight code

Couldn't the code highlighting be also handled statically during the build process?

You have a good point, but the problem that not knowing the table to select beforehand does seem valid. What if the FROM clause is called SELECT and the SELECT clause is called PROJECT? (So it will read something like SELECT <table> PROJECT <columns>?)

This is why I find the flutter approach interesting: it has its own rendering engine. I would guess it is optimized for this sort of thing (dynamically rendering UI elements) without depending on an external entity (DOM).

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.

Does this mean that now Java-based GUI software (e.g. Android Studio) run using OpenJDK will display much better fonts?

It would be interesting to see how this performs, when it comes, in WebAssembly.

Who (and where) is this experimenter? What if he (and his world) is also simulated?

What is real?

Didn't know about linter-rust. Thanks for sharing.

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.

Maybe this is off topic, but while reading this article it occurred to me that wouldn't it be useful if the ownership transfer is syntax highlighted?

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?

Did anyone take a screenshot of the Mic Drop button before it was removed? There are GIFs showing the sent email with the minion, but could find any showing the /button/ in action.

India has a huge population and there is a shortage of jobs. Rather than job seekers, India needs more job creators. This initiative will give people incentive to take up entrepreneurship.

Happy vue.js user here too. Thanks vue team for this nice ui library.

No Python 3 support yet?