Pretty sure there are students at Uni using iPads with keyboard. It's smaller form factor than a laptop.

But I think it IS the best way to search for information, to be able to put a question in natural language. I'm always amazed just how exactly on-point the answer is.

I mean even the best of docs out there that have a great search bar like the Vue docs still only matches your search term and surfaces relevant topics.

Seriously what kind of business today needs to support ES3 browsers? Even banking sites should refuse to run on such old devices out of security concerns.

Non-BEM CSS with ids and multi-classes everywhere was hell.

If you're a senior CSS developer you will invariably reach a point of using "object oriented CSS" which is where you combine classes to an effect.

At that point you're not far off Tailwind. TW just took it all the way.

It's always about prompting or how AI "is great" yadi yada but hardly any step by step examples.

I can easily ask gemini CLI to produce code for example. But how to work with AI in an existing codebase isn't obvious at all.

It seems also that for any serious use you need a paid subscription? It seems like the free models just can't handle large codebases.

For fun I put it in chatgpt and asked if there are bugs.

It warned about fromBase64() and toBase64() not existing in main browsers. It is supported but is indeed a new "baseline 2025"feature. It suggested more compatible code using two small functions to convert characters manually.

"deflate-raw is not consistently supported." It suggested using 'deflate' instead.

https://www.ncbi.nlm.nih.gov/books/NBK11888/

I used the same basic signature for the `$()` function. However I found that 95% of the time I don't need to use the chain method on a collection. There's almost no scenario in which I want to do .addClass() etc. There's practically ZERO situations in which I would use something like attach an event to a collection of nodes, since event delegation is more elegant (attach a single event and check for event.type and event.target).

So TLDR I made $() always select a single element with `querySelector()`, which means I could remove the collection/loop from every chained method like addClass() or css() or toggle().

Point unless you write bad code to begin with, you can probably make this significantly smaller by removing the collection handling. The 1% of the time it is warranted to do an addClass() or something else on a bunch of nodes you can just go native and if the collection is small enough just call $() on each element.

PS: I guess the subtext also to my post is sometimes something looks logically elegant, like the ability for any chained method to act on the collection selected by $(), but it may not make any sense in the real world.

Which is where I am a bit mystified by the article's claim of "hyper realistic" games. Even on PCVR the quality of PC VR games in general is quite low. We're a far cry from hyper realistic experiences. Typically either the graphics suffer and you have smooth FPS or the graphics are great and you have bad FPS, or you are a rich person that owns an RTX 4090 etc.

For me it's only a matter of a few more years. Most games on Quest atm to me look like cheap mobile games. I hate those low poly / untextured styled games with a passion.

The author perhaps does not understand that to make truly immersive, relaxing experiences in VR you need a LOT more power. There 's nothing very relaxing about being in a forest made of low poly trees, shitty looking water and distant scenery that looks blurry AF.

Even on YouTube at the best quality I can find, there is hardly anything truly relaxing or immersive. Take a random video of the Grand Canyon in VR and everything in the distance is just flat.

Colours is also a huge problem. Watch a VR video of someone walking on the beach : the sky is blue yes but a weird half light blue that is nowhere near anything like the kind of brightness of the real sky. It's all deadened and flat.

The technology just isn't there. So right now, violent, in your face action is where VR shines. Typically anything that moves, and anything that comes close to the camera gives a much better sense of immersion. I find myself often times almost putting my nose to everything because it's when things are up close that you get that sense of 3D the most. Anything taht is even a couple meters away becomes flat and featureless.

Anyway I could just rant on and on. VR is great. The kind of games that currently do well on it do so for a reason. I'd love to just travel in VR, to be immersed on some remote island, basking in the sun, or to listen to the crickets and watch the starry sky.. all those things currently are awful experiences in VR due to the technical limitations.

It works great! I was amazed at how you can do so much in templates, it's pretty much everything I could do in Vue templates, though a little more verbose.

I built my own `VanillaComponent` class, which has a mount() method which calls the render() function which I define on the child class.

My VanillaComponent class looks like this:

    import { html, render } from "lit-html";
    
    abstract class VanillaComponent {
      abstract render(): ReturnType;
    
      private _mountPoint?: HTMLElement;
    
      mount(this: VanillaComponent, target: HTMLElement) {
        target.textContent = '';
        this._mountPoint = target;
        this._update();
      }
    
      _update() {
        let templateResult = this.render();
        let rootPart = render(templateResult, this._mountPoint!);
      }
    }

    class MyComponent extends VanillaComponent {
      constructor(props: { label: string }) {
        this._props = props;
      }
      
      render() {
        return html`${this._props.foo}`;
      }
    }

    let myComponent = new MyComponent({ label: "I am a button" });
    let target = document.querySelector("#demo");
    myComponent.mount(target);

    myComponent.update()

However something I have not been able to solve with lit-html only, is when I compose parent and child components I have to do something like :

    class MyDialog extends VanillaComponent {
      render() {
        let childComponent ...  // another VanillaComponent previously instanced
        return html`
          

            ${childComponent.render()}
          

But this means I can not do `childComponent.update()` because I don't know the root element of child component, since I did not mount it explicitly myself.

I mean technically because of the lit-html optimizations, I can do `.update()` on myDialog (the parent component) after any child component's props changes, and it will only re-render what is necessary... but let's say my child component has like 1000 cards... it seems very wasteful and it would be ideal if I could re-render only the child.

I wonder if there is a trick to get around that with just lit-html?

Coming from Vue I was really surprised it does a lot of what Vue templating does, including attaching events, with just vanilla JS templates. And when you use VSCode lit extension, you get syntax highlighting and full type checking inside the templates.

I learned about lit-html after a tweet from Marc Grabanski, where he said he used lit-html with vanillajs, not Lit.

After some experimenting I found it works great and it seems like you are trying to solve something very similar.

When you use the lit-html template package you can do basically evetything that is described in the Templates chapter

https://lit.dev/docs/templates/overview/

... without all the other abstraction of components that are part of lit-element.

https://lit.dev/docs/libraries/standalone-templates/#renderi...

At the very least, Captain Blood would come to mind.

https://www.abandonware-france.org/ltf_abandon/ltf_galeries....

You have sequences of symbols, with attached mechanics. Arrange the blocks in different order, to get different outcomes.

Maybe I'm just grumpy today, I don't see how the game is "profound".

edit: I guess what I have in mind is if anything, the fact we can create meaning out of any collection of symbols, and decide waht it means, shows that language is really empty and intelligence is completely outside of language. Language is just a tool.