Web editors

>web editors
why is this allowed?

Attached: webeditors.png (1260x552, 72K)

Other urls found in this thread:

github.com/google/code-prettify
hilite.me/
highlightjs.org/download/
code.google.com/archive/p/zen-coding/
twitter.com/AnonBabble

lol

I don't get it

How else would you do it?
A bit of jQuery?
nth-child in css?
React?
A virtual screen made of tiny colored blocks to form letters?

They should add a new component to the w3 standard, so every web browser can do it in the most efficient way and not with this abomination.

Yeah, let's extend the browser more and more and make sure it has to cover every fucking use case in computing. An operating system inside an operating system. The web was a mistake.

>lets leave it as inefficient as it is cause I'm afraid to change
>The web was a mistake
you are the mistake

Let's not edit code inside a fucking web browser is what I'm suggesting. The whole thing went wrong when we added JavaScript to "documents with links to other documents".

>Let's not edit code inside a fucking web browser is what I'm suggesting
The future is now, grandpa

test
for (int i = 0; i < 5; i++) {
print('hello ${i + 1}');
}

Sure, go ahead. Let me know how that works out for you.

Attached: javascript-hole.png (1000x3392, 409K)

wow op it's almost as if things are displayed on a browser using html, weird

Attached: Annotation 2019-08-29 173310.png (343x469, 23K)

Kek, ever heard of virtual DOM? All this shit is abstracted away by react and I’m sure it’s some filter expression in react

That is how marking up works. You mark up text. Automated markup is not "go to".

IDEs color shit with styles. How the fuck else is it going to color that text?

You are a moron, I'm talking about a new component free of java script, just as an work but with formating.

because it's valid markup?

>That is how marking up works.
looks very inefficient to me

and?

should be improved

God dammit I hate javascript.

It is in some cases. Maybe these can be of help, some javascript files and online tools for automating:
There are maybe some ide/editor specific tools also you can use to format html for syntax blocks.

Setting up editors/ides takes lot more time, but work in itself is efficient.

Using Google:
code-prettify
github.com/google/code-prettify
Using online tools:
hilite.me/
Other:
highlightjs.org/download/

This can also (maybe) help, if you're in to making your own tools:
code.google.com/archive/p/zen-coding/

I'm talking about two issues:
1. trying to do everything in js inside a browser;
2. adding stupid shit to the browser spec when 1 (inevitably) turns out to be a clusterfuck.

So now you have this immense spec that nobody can implement again and we're stuck with two browser engines forever.

The problem is HTML.
It is a shit markup language that should get replaced by something more modern.

web applications are cancerous monstrosities that shouldn't exist
eventually browsers are going to be exactly like your OS but 1000x slower because "muh compatibility"
>dude just write one cross-platform browser app
>woops looks like we have to deal with a million different browsers doing shit different anyway!
>maybe use X library next time hurr durr it has millions of lines of compatibility code that still doesn't work perfectly

it is red

Don't like, don't use, faggot
/thread

Such as?

How else would you achieve this in a browser?
Would you implement your own text rendering on a canvas?

I don't really see an issue here. If you need to implement code highlighting in a browser, CSS and JS DOM manipulation seems to be the the fastest, most efficient way to accomplish this.

What kind of apps are you making? The year isn't 2005. In a few more years we will be rid of IE for better and worse, only having to deal with Chromium and Gecko. If your app is simply some forms, no one will notice if it is 1000x slower. And still most browsers, even on mobile has plenty of grunt for shit like graphics (webgl) and computing in general (wasm).

And if you are using X11 and complain about sluggish UIs you should just keep your dirty mouth shut.

That's ok. It only needs to look efficient for the machine

There's no front-end language that is NOT a gutter language.

>what are and tags
you stupid whore you know nothing of computing
ps, whatever editor you have is doing the same thing

they just make the editors out of typescript and JavaScript anyway now. Vscode and atom are basically web pages.

That's the only correct way to do it
Pic related should be punished by death

Attached: fuckers.jpg (455x462, 61K)

They're both atrocious