Live data from Hacker News

Show HN: Gmail Classic – CSS for Reverting Gmail's New Look

github.com

61–70 of 184 posts

Re: Show HN: Gmail Classic – CSS for Reverting Gmail's New Look

#61
Cool!

Naming might be a problem, however. Companies get litigious when you use their trademarks/brand, even when modifying things on the client side.

Slack came after an HN user for using "Slack" in their GitHub repo that hosted a client-side script for Slack.

Re: Show HN: Gmail Classic – CSS for Reverting Gmail's New Look

#62
post #38
post #35

Earlier quoted context omitted.

https://chrome.google.com/webstore/detail/view-image/jpcmhce...

I have this, but the recent UI refresh broke it. https://github.com/bijij/ViewImage/issues/166

My experience is anecdotal of course but what is broken about it for you?

It is working fine for me on Firefox 63.0.3 (64-bit) using ViewImage 2.1

Re: Show HN: Gmail Classic – CSS for Reverting Gmail's New Look

#63
post #13

I can handle the new design, but on my (albeit underpowered) Chromebook, new Gmail takes ~30 seconds from initial page load to starting a reply to a thread. This is not progress.

I'm on a 2 year old MacBook Pro.

Gmail will completely freeze for ~10-15 seconds while performing a search.

Re: Show HN: Gmail Classic – CSS for Reverting Gmail's New Look

#64
post #24

Earlier quoted context omitted.

What precisely is shitty and broken about gmail's IMAP implementation? Gmail's IMAP implementation implements three RFCs I wrote; I haven't noticed anything wrong in those areas. Are my RFCs unusual or am I overlooking something?

I'm curious if you've actually used an IMAP client witha Gmail account; if so, which one(s). A sibling comment has already mentioned the folder/flags mixup issue, but while it sounds like one small feature, that one thing is so fundamentally broken that I really can't see how any user of Gmail IMAP would overlook it. I get duplicate notifications for the same mail in INBOX and [Gmail]/All Mail and actions on one copy…

I try using pine here and there. Every time I try, whenever I attempt sending a mail it locks my account for suspicious activity

Re: Show HN: Gmail Classic – CSS for Reverting Gmail's New Look

#65

It's interesting how back when programs actually ran on your machine, you could just use an older version. I knew people who never upgraded Winamp. Today we do know this is problematic (due to security updates mostly) but when it comes to web applications we don't have a choice. Don't like the new look, well tough. If the application has an API (like Reddit) you could write your own or use a better client. I could sa…

If WinAMP still had support, you could still run it. This is why apps like QMMP exist. I use it to listen to my music because I manage my own playlists and prefer the way it works. On the web, the same thing is possible. My public library's search interface is old, but it's still maintained and I hope it doesn't get this "next level" Gmail-type upgrade. These big upgrades end up rewriting some of the biggest leverage…

> If WinAMP still had support

A company bought Winamp and is supporting/developing it again. A version supporting Windows 10 "leaked" just a few weeks ago.

https://techcrunch.com/2018/10/15/winamp-returns-in-2019-to-...

Re: Show HN: Gmail Classic – CSS for Reverting Gmail's New Look

#66

Earlier quoted context omitted.

You can load gmail is basic html mode, it might help. According to https://support.google.com/mail/answer/15049?hl=en , the following link should set it to basic html mode (I haven't tested it) https://mail.google.com/mail/u/0/h/1pq68r75kzvdr/?v%3Dlui I've used the basic html mode before when the normal (js heavy) one was a bit slow, and it ended up being much faster even if every action requires a whole new page req…

I thought the whole idea of JavaScript-heavy frontends was to make things faster . A rhetorical question: How is it that Google is somehow a leader in frontend technology and design when they often don't practice what they preach?

I'm sure it achieves that when you use Chrome on a recent developer workstation and only have one tab running. There is a nice JIT in the browser, plenty of RAM, and lots of high-end cores available for the task.

Today I'm struggling with 8 GiB of RAM and 2 cores. Admittedly I have many tabs open, but that is to be expected. Web site creators might believe that the world revolves around their web site, but really it does not, and so they must share my machine.

Weaker systems are of course unusable. Suppose the hardware is a 32-bit PowerPC Mac with one core and 512 MiB of RAM, and there are a bunch of tabs open to similarly taxing web sites or worse. I've mostly had to retire a system like this, which makes me really annoyed because it is quiet due to being fanless.

Note that the "weaker system" described above is not really weak. Long ago, I used the old gmail just fine with far less. There was a time when 32 MiB of RAM was enough to open several browser windows (we didn't have tabs) and run them. JIT didn't even exist yet, but the web ran fine.

It's the usual problem I think: software developers are rewarded with high-end developer workstations to keep them happy and productive, and then they test the software all by itself on this high-end hardware and everything looks good. Nobody is testing on older low-end hardware with lots of other things running in the background.

Re: Show HN: Gmail Classic – CSS for Reverting Gmail's New Look

#69

It's interesting how back when programs actually ran on your machine, you could just use an older version. I knew people who never upgraded Winamp. Today we do know this is problematic (due to security updates mostly) but when it comes to web applications we don't have a choice. Don't like the new look, well tough. If the application has an API (like Reddit) you could write your own or use a better client. I could sa…

I still do run most programs on my own computer; I think is better. Often I write my own.

For email, I run my own server and I like Heirloom-mailx as the user program (I find it much better than Outlook), although you can also use others if you like to do.

Re: Show HN: Gmail Classic – CSS for Reverting Gmail's New Look

#70

Impressive. Personally I preferred the version before this, in which Compose wasn’t “pay-attention-to-me red”.

I have a hard time understanding that one.

When I want to compose, I look for a normal button in a normal place. I can't get used to a red button. My mind filters it out, like an ad. I pretty much don't see it. Every time, there is a sort of disoriented and bewildered search to find a compose button.

Was it supposed to have the opposite effect?

Post reply on HN