Live data from Hacker News

Introducing a new HTML element – welcome

shkspr.mobi

221–230 of 234 posts

Re: Introducing a new HTML element – welcome <clippy>

#221

Earlier quoted context omitted.

It looks like you're having some trouble understanding the purposes of our many different circular icons with squiggly things inside them, would you like some help?

No thanks but sensible alt attributes and hover labels would be a great start ;)

How can we rehabilitate hover labels (and alt-text) when you would also expect a significant fraction of visitors using touchscreens ?

Re: Introducing a new HTML element – welcome <clippy>

#222

Earlier quoted context omitted.

It is probably a quite subjective thing. I use Firefox as main browser but test things in Chrome. Neither UI really bothers me, but I prefer Firefox for ideological reasons. The dev tools in chrome are better though imo.

I feel like Firefox's Dev Tools are better in so many small ways at the fundamentals it's really sad every time someone says they prefer Chrome Dev Tools. (Plus, Firefox's Dev Tools inherited from Firebug and at least from that sort of continuity perspective arguably are the most mature Dev Tools codebase.) A lot of the reason so many people seem to like Chrome Dev Tools better seems to be exactly the sort of "Works…

Could well be. I do very little web development, and I used chrome back in the days when that was my fulltime job. It might be more of a case of familiarity rather than them actually being better. :)

Re: Introducing a new HTML element – welcome <clippy>

#223
post #208

Earlier quoted context omitted.

I keep seeing this come up, that it's practically impossible to write a brand new browser. This got me thinking, what would it take to make a better browser? A browser is something that 1 out of every 2 people on earth [1] use frequently. That's a lot of people! All developers in the world use a browser. Lots of them really believe in open software. Some are 10x developers. A certain percentage are literal geniuses.…

> What would it take? All the developers in the world combined can not solve a legal problem. You can't implement technologies like Widevine without a license, and if they simply won't give you one [0], you're dead in the water. [0]: https://blog.samuelmaddock.com/posts/google-widevine-blocked...

What would it take to reverse engineer Widevine?

Re: Introducing a new HTML element – welcome <clippy>

#224
post #13

The person writing this has to repeat frequently that they're OK with the element; it's quite funny how hard they try not to upset people. But their view of the situation is completely correct; just because this one feature might be useful (heck, when Microsoft dumped XMLHttpRequest on us that was incredible too), doesn't change the fact that we're now living in a web where Google does whatever it wants, adds whateve…

You must have missed the post where we all took a blood oath to stick to standards when we develop.

Re: Introducing a new HTML element – welcome <clippy>

#225

Earlier quoted context omitted.

It is probably a quite subjective thing. I use Firefox as main browser but test things in Chrome. Neither UI really bothers me, but I prefer Firefox for ideological reasons. The dev tools in chrome are better though imo.

I feel like Firefox's Dev Tools are better in so many small ways at the fundamentals it's really sad every time someone says they prefer Chrome Dev Tools. (Plus, Firefox's Dev Tools inherited from Firebug and at least from that sort of continuity perspective arguably are the most mature Dev Tools codebase.) A lot of the reason so many people seem to like Chrome Dev Tools better seems to be exactly the sort of "Works…

One thing I think Chrome is better at is emulating CSS media, so we can check layouts when printing, for example. I don't even see how to do that in Firefox.

Re: Introducing a new HTML element – welcome <clippy>

#226
post #77

Earlier quoted context omitted.

What aspect of the Firefox UI bothers you?

Not the OP, but I'll chip in with my $.02. I really want to like Firefox, but everything UI feels wrong (on macOS). From tabs, where the close button is on the wrong side (right) and if you click the + button to open a new tab the cursor ends up over the new tab, not over the + button so you can click again to open a new tab. The whole UI looks and feels non-native. Pressing ESC in full screen mode does not bring the…

> From tabs, where the close button is on the wrong side (right)

In Firefox, using the Customize option from the menu, you can move the new tab button to the left side of the tabs, or even to the far right side so that it doesn't move.

Re: Introducing a new HTML element – welcome <clippy>

#227
post #79
post #73

Earlier quoted context omitted.

When I type in ‘news.’ Firefox still gives me ‘hackernewsgrid.com’ as the first result, even though I haven’t visited that page in years, and in fact it is completely down. I’m not sure how the omnibar works, but I’m not extremely impressed.

When I type “n”, I’m likely either going to news.google.com or HN. Firefox will guess correctly that I’m thinking of HN and fills that in as the URL. However, the main HN URL and Google News are something like 8 and 9 in the list. Everything above those two is a mix of things that happen to have an “n” somewhere in the URL that I may have recently visited.

As the grandparent comment says, you just get used to how Firefox works. For example, I would've never even thought to type "news" to look for hackernews in the omnibar after using it so long-- I just instinctively know that Firefox will find it easier based on domain name, so I type "yc" for "ycombinator.com"

I can see how this is going to be confusing for a new Firefox user, but it's easy to get used to.

Re: Introducing a new HTML element – welcome <clippy>

#228
post #208

Earlier quoted context omitted.

> What would it take? All the developers in the world combined can not solve a legal problem. You can't implement technologies like Widevine without a license, and if they simply won't give you one [0], you're dead in the water. [0]: https://blog.samuelmaddock.com/posts/google-widevine-blocked...

What would it take to reverse engineer Widevine?

I don't know much about the law, but wouldn't reverse engineering Widevine be illegal, as it is protected by DRM?

Re: Introducing a new HTML element – welcome <clippy>

#229
post #200

Earlier quoted context omitted.

A lot of people saw Agents (and Bob before it) and expected Alexa/Siri/Cortana-level interaction. Agents were very good in relatively simple animation techniques at conveying an outer complexity that belied the simplicity of most of the actual code written for them. (That's part of why the "games" webpages I made with them, and the PPTs as well, impressed people a lot more than the rather rudimentary "screenplays" I…

But, also, Clippy was using suboptimal tech, when they could have had a better version: https://machinelearningagents.com/2009/08/31/lumiere-project...

Similarly interesting, it's also interesting to note that even the Office Assistant animation engine and support for text-to-speech and speech-to-text was extremely stripped down and underpowered compared to the Agents engine bundled with Windows. One more of those areas where the Office team needing to support older versions of Windows and other platforms pushed them to use a half-baked fork of the full Windows feature rather than just rely on a Windows feature.

(It's interesting to see even today which Office features are getting UWP treatment and how, with the most interesting part of "how" being how much they are moving to React Native.)

Re: Introducing a new HTML element – welcome <clippy>

#230
post #92

Earlier quoted context omitted.

It is different but not necessarily better. Where IE got really bad is when they stopped developing it. Development really slowed after 5.5 and once 6 was the undisputed champion they just left it to rot. Whatever else can be claimed about Chrome, they're not idle. TBH I think if you want a slogan then "Google is the new AOL" is better. When you look at what their doing across technologies it looks more like reinvent…

Obviously every Google product is different, but how many Google products have reached maturity only for Google to basically stop, and then eventually discontinue it after eliminating the competition in the interim?

search and youtube are the two things I can think of.
Post reply on HN