I like JavaScript. I do most of my browsing on a browser with JS enabled. I only browse with JS off when I think the sites I'm about to visit are sketchy.
However, I also like saving resources and separating concerns. We have CSS to make pages look good (or at least half decent). We can make them look even better with JS, and GSS in a later version may very well do that: compile a stylesheet that does the basic layout/typography/effects and then patch what CSS cannot do with JS.
If I decide to disable CSS, I should still be able to see the HTML, and if I disable JS, I should still be able to see the content with most of the styling, except dynamic content and anything that CSS can't do.
I'll be watching GSS, a precompiled solution would be really useful.
Web without CSS and JavaScript would be a quite boring place.
But hey, at least with GSS there is no need to rearrange your content in weird ways to accommodate to CSS layouts. So what you'd get is just the plain, semantic HTML.
On the topic of ways to improve the terminal, I'd like to see output separated from input.
Put the prompt 1/4 of the way down the screen instead of at the bottom. Above the prompt, we have a backlog of the commands we input. As we press up, it scrolls through the backlog, as normal.
Below the prompt, we see the output of the command.
I'd also like to see tab completion (and maybe some form of hinting) on programs, not just file paths.
>On the topic of ways to improve the terminal, I'd like to see output separated from input.
>Put the prompt 1/4 of the way down the screen instead of at the bottom. Above the prompt, we have a backlog of the commands we input. As we press up, it scrolls through the backlog, as normal.
>Below the prompt, we see the output of the command.
That would be more fitting for a shell than for a terminal.
>I'd also like to see tab completion (and maybe some form of hinting) on programs, not just file paths.
bash already does this. zsh and at least one variant of ksh will do completion if you type the first letter of a command. I was surprised that tcsh doesn't.
They're both predictive typing, so they both fall on their face when it comes to two things. Proper nouns and slang.
Whenever I try to write one of those two thing (often, think email addresses, friends names , "yo", etc) I have to fall back on regular input.
With swiftkey, this means just going back to pecking. With minuum, it means going into a menu and switching to minuum's full sized view or long pressing each region to get a zoomed in view of the keys around there to pick out the one I want.
The compactness of minuum is great, though. And when I'm entering non-proper nouns it's as fast as any keyboard (given a few days to adjust).
I paticuraly like the "swipe left for space" function.
It makes me want to try even more radical keyboards. Maybe something chord based.
A quick point: you can actually access the 2d keyboard with a gesture by long-pressing two fingers on the keyboard. Not a very discoverable gesture, unfortunately, we'll definitely need to improve that.
Do they not let you add to the dictionary? Honest question, I've only used Swype, but you can definitely add things to the Swype dictionary and they work just like any other word after that.
They do, but in order to enter a custom word, you have to switch typing modes to a full-screen keyboard, which is a 2 second action. With sliding keyboards, you just start pecking because you already have a full-screen keyboard.
You plan to solve it by compiling to css beforehand.
What if I told you I like to remove all custom css from my page. Do you have any recourse?