gmane.comp.misc.suckless

Re: Re: Why HTTP is so bad?

Strake — 2013-05-25T04:55:29

Such functions, yes.


If that's what you meant, yes. I just meant the fetcher-viewer integration.


Yes. Thus I can easily swap out any component, or insert mediators
between components. For example, I could write my own fetcher to scrub
the HTTP headers, or block ads; and I wouldn't need plug-ins to view
PDFs or watch movies.

Re: Re: Why HTTP is so bad?

Random832 — 2013-05-25T04:19:15

I meant as opposed to the usual dozen.
So the fetcher (which presumably also has UI elements such as an address 
bar, back/forward button, etc) is the monolithic browser I described.

How exactly is this different from the current model? That the two 
components communicate via IPC rather than an in-process API?

Re: Re: Why HTTP is so bad?

Strake — 2013-05-24T23:13:43

Yes.


The viewer sends a "go" message back to the fetcher, which kills the
old viewer and loads the new one, and can keep a URL log.

Re: Re: Why HTTP is so bad?

2013-05-24T20:47:06

And you spend a day on wikipedia or tvtropes and you've got two hundred
HTML viewers open?

You need _something_ monolithic to manage a linear (or, rather,
branching only when you choose to, via open new window or new tab)
browsing history, even if content viewers aren't part of it. When you
click a link within "the appropriate viewer", it needs to be _replaced_
with the viewer for the content at the link you clicked on.

And if you don't like the way people normally browse a site like
wikipedia or tvtropes, then... well, you've missed the point of
hypertext, and what you're building isn't a web browser.

Re: Re: Why HTTP is so bad?

Strake — 2013-05-24T20:02:53

Yes. A web browser ought to have a component to fetch documents and
start the appropriate viewer, as in mailcap. The whole monolithic web
browser model is flawed.

Re: [dwm] Dvorak programmer keyboard

Hugues Moretto-Viry — 2013-05-24T18:37:47

Hi,

You can also use keysym instead of the name. On AZERTY, when you press &,
it shows:
state 0x10, keycode 10 (keysym 0x26, ampersand),

Personnally, I use 0x26 and not XK_ampersand

--
H.Mo.

Re: [dwm] Dvorak programmer keyboard

Thuban — 2013-05-24T18:26:51

As example, on azerty, 12345 is replaced by &é"'(.
Associated keycodes are : 

XK_ampersand,XK_eacute,XK_quotedbl,XK_apostrophe,XK_parenleft

Such things can be found via xev, as it has benn already said.

Re: [dwm] Dvorak programmer keyboard

Szymon Olewniczak — 2013-05-24T18:20:03

xev is the tool what I was looking for. Thanks.

Regards,
Szymon

Re: [dwm] Dvorak programmer keyboard

Hannes Blut — 2013-05-24T17:30:24

Use the keys array. If you don't know the name of the keys use xev.

--
CXblut
cxblut< at >gmail.com
#blut on irc.freenode.net
< at >cxblut twitter

Re: [dwm] Dvorak programmer keyboard

Chris Down — 2013-05-24T17:01:44

config.def.h is a pretty self explanatory read, the key definitions
section is even commented. If you are not willing to read the source,
you are not going to get on well with dwm.

[dwm] Dvorak programmer keyboard

Szymon Olewniczak — 2013-05-24T16:55:53

Hi,
today I decided to switch from i3 to dwm. Nearly
everything works perfectly instead of tags. I using dvorak programmer keyboard and instad
of 123456789 on the top row of keyboard I have: &[{}(=*)+] . Now how can
I assign this keys to point to dwm tags.

Regards,
Szymon

Re: Re: Why HTTP is so bad?

Dmitrij Czarkoff — 2013-05-24T16:04:54

On May 24, 2013 4:11 PM, "Christian Neukirchen" <chneukirchen< at >gmail.com>
wrote:

There is mime, which can be combined with mailcap in a useful way.

----
Dmitrij D. Czarkoff

Re: Re: Why HTTP is so bad?

Christoph Lohmann — 2013-05-24T15:44:50

Greetings.

On Fri, 24 May 2013 17:44:50 +0200 Nick <suckless-dev< at >njw.me.uk> wrote:

A  combination  out of gopher and markdown would be more preferable. The
simple menu is used to have the information tree and  markdown  to  have
parseable content.

But  as  mentioned  below  in the thread does gopher have its flaws too,
which corporate users will require to ruin user’s life.

I’m with [0], but it hasn’t been implemented or written down yet.


Sincerely,

Christoph Lohmann

[0] http://http02.cat-v.org/

Re: Re: Why HTTP is so bad?

Christoph Lohmann — 2013-05-24T15:47:18

Greetings.

On Fri, 24 May 2013 17:47:18 +0200 Prakhar Goel <newt0311< at >gmail.com> wrote:

As  mentioned  in  the thread before, long  ago  there  was this idea to
transmit safe tcl as MIME attachments and make e‐mail ready for the 21st
century. [0]

This  subset  could still be used; it has everything, the interpreter is
smaller than Javascript and easier to write than Javascript code. And it
would  avoid this insane HTML/CSS/JS trinity like some other popular so‐
cial technology used to ruin the world for a long time.


Sincerely,

Christoph Lohmann

[0] http://www.tcl.tk/software/plugin/safetcl.html

Re: Re: Why HTTP is so bad?

Thorsten Glaser — 2013-05-24T14:43:27

Nick dixit:


I think that thing is called “Television”. Not really sure,
considering I stopped dealing with *that* at the age of nine.


Right. I prefer my real web browser… see signature ☺

bye,
//mirabilos

Re: Re: Why HTTP is so bad?

Bjartur Thorlacius — 2013-05-24T14:40:56

In special, fewer quotation marks :)

Re: Re: Why HTTP is so bad?

Strake — 2013-05-24T14:35:46

Yes — file type, not data type.


It has saner syntax, too.

Re: Re: Why HTTP is so bad?

Bjartur Thorlacius — 2013-05-24T14:23:10

In Unix, filetype are defined on a per file basis. Delimeters in IPC 
text streams are defined using $IFS. Rc is hailed exclusively because it 
makes less use if $IFS. Well, that and the Plan 9 label.

Re: Why HTTP is so bad?

Christian Neukirchen — 2013-05-24T14:11:06


Types can't be declared properly in Unix.

Re: Re: Why HTTP is so bad?

Bjartur Thorlacius — 2013-05-24T12:57:49

Types can't be declared properly in Gopher. HTTP has Internet media 
types, á la MIME. MIME even has a text media type, so that you can 
choose to not implement subtypes thereof or create new ones without 
sacrificing either of the text media type nor the subtype, such as HTML 
or markdown.

RFC822 evolved from manually typed text. Due to reasons of familiarity, 
it seems, this loose syntax was carried over to HTTP. But aside from 
that, it's fine. And it's easier to standardize formally the subset of 
HTTP syntax actually in use, while retaining implementations, headers 
and whatnot.

Re: Re: Why HTTP is so bad?

Dmitrij Czarkoff — 2013-05-24T12:53:21

I sincerely believe that any technology lying between non-technical
consumers and goods/services providers is deemed to get abused all the
possible ways. This factor should be taken in account in design phase of
technology development.

----
Dmitrij D. Czarkoff