janoc

joined 1 year ago
[–] janoc@alien.top 1 points 11 months ago

I don't know "what is the consensus" because I don't have one - but why are you insisting on carrying around a gaming console to use it as a (crappy) laptop? What are you going to gain here?

You will still need a keyboard, mouse, possibly a second battery, charger, something to put all that stuff in ... At that point you can as well buy a 13" laptop and be done with it.

[–] janoc@alien.top 1 points 11 months ago (2 children)

LOL, just no. That's certainly no laptop replacement for more reason than one.

You can't simply run 2D apps on Quest (regardless of which one), they have to be built specially for Quest to actually display properly in the 3D mode.

Normal "2D" apps will not run properly, you will get all sorts of glitches and issues, with the OS switching between the 2D and 3D mode, with the 2D mode being extremely jarring.

With the multitasking support in Quest 2/3 you could have it displayed as a window - but not really full screen and your text readability (which is suck in Quest already) would suffer even more unless you blow up the text size.

Very limited battery life and the general ergonomics of the device are also very good reasons why this is not a laptop replacement of any kind.

If you want Quest, buy it for playing games. That is what it has been designed to do.

If you want a laptop, use a laptop. If you don't want to lug a laptop around while traveling (even though Quest 3 is not really any smaller with all the accessories you need to carry about!), get a Surface tablet or even an Android tablet and a keyboard. Even with all their limitations it is a much better portable solution than trying to use a Quest for this.

[–] janoc@alien.top 1 points 11 months ago (1 children)

in other words, how rewarding it would be

I wonder how do you expect anyone to sensibly answer that?

Any feeling of reward (or lack of it) is a completely subjective thing - that's like a woman trying to explain to a man how pregnancy or nursing a baby feels or a man to a woman an erection. I.e. good luck with it.

You need to try it yourself and see for yourself whether or not the journey will be rewarding for you or not. Why are you afraid to try? It is not like it costs you anything (beyond time).

not mentioning that elisp is pretty old so the learning resources might not be as much as other more popular programming languages

Did you try to actually look? There are plenty of resources on ELisp and even Youtube videos. While it is not a general purpose language (as Common Lisp or something like Clojure or Racket would be) and it is quite old, indeed (as is Emacs), there is plenty of very good documentation available. I would dare to say even more and better than for some of much more recent and popular languages out there.

like what is the level of mastery do i need to achieve to start implementing custom elisp in my configs to enhance my emacs experience?

Very minimal. Moreover, Lisp is a very minimal language that has almost no syntax that you need to learn compared to something like Javascript, Python or C++.

and how exactly can i improve my emacs experience if i learned elisp?

If you are 100% happy with how your Doom Emacs works, then you don't need to bother with learning it. However, if you ever wanted to customize Emacs in any way, then you can't do it without being at least somewhat proficient with ELisp.

And if you don't want to customize Emacs at all - why are you using it in the first place? There are editors with much better out-of-the-box experience than this old dinosaur. The whole point of using Emacs is that you can completely customize it to your needs - something most other editor can't reach.

[–] janoc@alien.top 1 points 11 months ago

And wouldn't work, given that except for the actual pushing pixels to the screen everything else is done by the Lisp code. So you would need to tightly synchronize the two threads to the point of it being useless.

Having a separate "rendering" thread works for applications where you can queue up rendering tasks and then execute them in the background. Such as a game engine.

Not an interactive text editor that has not been designed with such architecture in mind because threads didn't even exist back in the day.