Building a hackable editor in the browser
1–10 of 74 posts
Re: Building a hackable editor in the browser
#2If you like this check out https://github.com/Webstrates/Codestrates
Re: Building a hackable editor in the browser
#3 script, style { display: block; }
Re: Building a hackable editor in the browser
#4script, style { display: block; } I have no words.
Why? What do you mean? Just curious!
Re: Building a hackable editor in the browser
#5script, style { display: block; } I have no words.
This is a discussion forum. Putting things into words is the purpose of commenting. If you can’t, then maybe you shouldn’t.
Re: Building a hackable editor in the browser
#6...how about moving things out of the browser? It's cramped as it is. And then people wonder why their browser is so slow... "it's just displaying documents!"
Re: Building a hackable editor in the browser
#7...how about moving things out of the browser? It's cramped as it is. And then people wonder why their browser is so slow... "it's just displaying documents!"
My browser is not slow, for me starting and using a lot of desktop apps feels slower than browser apps to be honest.
Re: Building a hackable editor in the browser
#8script, style { display: block; } I have no words.
As siblings have commented, it's not clear what reaction is obscured by your lack of words; but, if it's a veiled comment on the inadvisability of doing this, the author beat you to it:
> Warning: All of this doesn’t really follow any best practices for working with html, css or javascript - on the contrary: what we will be doing may look horrible to some people, and rightfully so - so you may not want to try those things at work just yet.
Re: Building a hackable editor in the browser
#9...how about moving things out of the browser? It's cramped as it is. And then people wonder why their browser is so slow... "it's just displaying documents!"
My browser is not slow, for me starting and using a lot of desktop apps feels slower than browser apps to be honest.
Probably because your desktop apps are bloated, too. Any software that needs longer than zero point two seconds reacting to user action (this includes starting the program) should be improved upon.
Re: Building a hackable editor in the browser
#10Earlier quoted context omitted.
My browser is not slow, for me starting and using a lot of desktop apps feels slower than browser apps to be honest.
Probably because your desktop apps are bloated, too. Any software that needs longer than zero point two seconds reacting to user action (this includes starting the program) should be improved upon.
I think the only native apps that I use are Steam, Unity, Photoshop, SourceTree and VSCode. Out of those the only "fast" one is VSCode, which is actually written in JS. Even though you mentioned the browsers being "bloated", for me Chrome always starts up instantly and I have no responsivness issues when browsing sites, playing browser games or using browser apps.