rident

Nice list! Noticed a few decent US hiking trails that aren't on it though. There are tons more of course, especially if you include BDR stuff.

Ice age trail - https://www.iceagetrail.org

Superior hiking trail - https://superiorhiking.org/

John Muir trail - https://www.johnmuirtrail.org/

Long trail - https://www.greenmountainclub.org/the-long-trail/

Pacific Crest trail - https://www.pcta.org/

Hayduke trail - http://www.hayduketrail.org/

Arizona trail - https://aztrail.org/

This story makes me recall Hertz $32M Accenture website services bill. https://www.henricodolfing.com/2019/10/case-study-hertz-acce...

I watched a lot of old Time Team episodes lately and this looks like more of the same from the era. Really nice, complex looking work but overall what can be expected for the time period. Cool that it's so well preserved though and hasn't suffered from having a plow or seismic event turn it into a puzzle.

Classics right there! We've got a long linage of this kinda stuff now from browser resets to full stylesheets to well specified content just for testing any of the above on. I love it! Simple. Consistent. And now more powerful than ever with the help of variables.

Might be fun to take all the w3 core styles rebuild them with modern CSS features. Maybe add some HTML5 elements to the test docs as well.

What other languages have it built in?

https://www.php.net/manual/en/function.levenshtein.php

They don't get gore in my house like a snap trap does yet fit in the same places where a catch-and-release trap would not. The mouse still lives and I get maybe two of them a year, in the fall as the temps cool. I really don't think it's a big deal.

Who leaves a mouse on a glue trap until it dies? That's messed up! I can hear when a mouse is on those things and at that point I carry the frightened mouse outside, pour a cap full of vegetable oil around it's feet and it frees itself, running off into the yard, then the trap goes in the trash. Heinously cruel? Only if you're a lazy shit.

Yeah this is a great way to tackle it. Image and branding comes along for the ride. Even if it's your desire - the client's desire is typically going to be functionality, security, usability, accessibility, etc. All of which are a means to an end for a lone wolf designer/engineer. Listen and learn from them about their pain points before promoting your own skills or favorite parts of the industry.

It would be cool to see a reboot of Firefox OS with Rust and WASM some day.

this one has been around for years - https://github.com/yegor256/tacit

The author actually loads 10x that much CSS (546 bytes) into the example page! [1]

Granted that is still not much but here I've augmented the 546 byte example to render nearly the same results with only 155 bytes. [2]

I've removed rem units as it's easier for all to understand without them. Pixel units scale just fine across the browsers available these days so there's no need for the mental hurdles and explained calculations. I've left them in the source HTML all the same for the sake of testing. The real feature making sites look good across a ever widening array of pixel densities today is this meta tag that was also used in the example HTML: <meta name="viewport" content="width=device-width"> [3]

Setting a font-family generically on the body tag gives the shortest path to consistent, doesn't-look-like-times-new-roman, font styling possible.

I left the unmentioned line-height in because it's a good default. It adds a little basic spacing between wrapping lines of text.

Styling elements that are children of the article to only have bottom margins gives consistent spacing to all content, and since top margins collapse [4] we can avoid dealing with them all together.

[1]: https://jrl.ninja/etc/post.css

[2]: https://jsfiddle.net/gb0ojdsL/8/

[3]: https://developer.mozilla.org/en-US/docs/Mozilla/Mobile/View...

[4]: https://css-tricks.com/what-you-should-know-about-collapsing...

There's a Lockheed A-12 on the USS Intrepid that you can get very close to with a guided tour. One of the facts the tour guides tell you about it is the titanium for the planes, as well as that of the SR-71s, was mostly sourced from Russia via shell companies for all kinds of bullshit reasons. So, America flew spy planes over Russia that were made from materials mostly of Russian origin.

The article says wraps up by stating the design hasn't lost any information but where's the fork count, watch count and other download options? Also, the lack of borders and flattening of button styles does not improve the design. Borders are even more necessary when data density is increased. Buttons, menus and links now have a variety of borders where they were consistent before.

The menu is marginally better but the extra density there makes the options run together, especially as counts increase, and lacks room for feature expansion. The grey background is useful also as it gives the page sections depth and context without having to label it. A all white background with various text sizes and lengths is not optimal for supporting more than the example design and projects using more text or with longer titles will suffer.

This design doesn't take into consideration how the homepage of a repo relates to the subpages of a repo. The article mentions showing more files yet the in the current design, file view one click away from the current homepage removes most of the account meta data and shows more files already.

This design also doesn't consider the logged out view which has a large call to action banner to get an account strategically embedded at the top of the code tab. This focal point is somewhat lost in the presented redesign and would likely require rounds of A/B testing to decide on a new content breakpoint for this business need.

5/10 - needs work

I think Wisconsin and North Dakota also have this system.

One lesser mentioned feature of AMP is when they are found through Google search, they are prefetched. So in addition to being size restricted, they are probably already partially if not completely downloaded in the background before the link is clicked. Giving them an extra advantage over other search results.

You can implement this feature yourself too: https://developer.mozilla.org/en-US/docs/Web/HTTP/Link_prefe...

I recently replaced jQuery on a project with a small custom DOM library. It cut more than 20% from the footprint of the application and helped to push load times on 3G under 3 seconds.

If you use some of the weirder stuff in jQuery or use plugins you might end up doing some targeted refactoring or just porting that code but I found it a relatively painless transition to make.

Tip: write unit/integration tests for the code you're about to convert as it makes the process much easier and faster.

Buses can also pass each other or not stop at every stop. If two of the same line's buses hit a stop at once, maybe the second rolls on by to the next stop unless they have passengers to drop off? The example is a little too simplistic but does illustrate how rapidly the issue can appear.

Milwaukee does this, you get on the bus by when an app says it's gonna arrive around there. They also put express buses[1] on the busy routes which don't make the exact same stops. Two ways to split the difference on bunching I guess.

If you check out their site[2] you can click on the Route Map button and see the buses run in real time.

[1] https://urbanmilwaukee.com/2014/12/03/eyes-on-milwaukee-new-...

[2] https://www.ridemcts.com/routes-schedules/greenline

getting a bit long for a cheetsheet

  curl cht.sh/js/foreach

Falling into the 3-4 crowd myself I also agree with this. Changing emails - perhaps in an automatic fashion - to use AMP is going to do nothing but harm to anyone outside Google. Image inclusion the AMP way [1] alone will ruin HTML email for other services. If Google really wanted to improve emails they would push for full compliance HTML5 support. Because if emails could be built with grid layouts, content could be more semantic, you wouldn't need a plain text version, we'd use less mark up and save on server space and bandwidth.

[1] https://ampbyexample.com/components/amp-img/

Sure there were other and earlier offenders, but that doesn't mean Google had to follow suit. They could have contributed something open and federated - an upgrade to XMPP. Branding would have been easy and the darling of the web would have held that image a little longer.

But they didn't, the closing and interconnecting of Google's product ecosystem was the beginning of a trend which is now seen across most of their offerings:

The Pixel has silly restrictions as I mentioned. Android apps, Drive, Docs and the office suite apps have gone stale since they came out of beta and lack the commitment to open source that Google once championed.

Even their new HTML replacement, AMP, is heavily tied to Google resources, requiring entirely different implementations of the same experiences between the HTML and AMP versions further handcuffing the buyer to their ecosystem and the buyer's customers to Chrome.

Yeah I really liked Meebo too

Matrix [1], mentioned elsewhere in these comments, looks interesting too and the Riot [2] app is similarly styled to Slack.

[1] https://matrix.org/

[2] https://riot.im/app/#/room/#matrix:matrix.org

Thanks for the timeline!

It's already marked as "classic" in the help section for Meet.

> If you use hangouts.google.com for video calls, or need help on chat, visit the classic Hangouts Help Center.

Oh man, Slack really is a beast isn't it? I do like the multiple network nature of it (even though everything is saved to Slack's servers) but I find it hard to believe it does so little for it's footprint.

They too though made a Google-like transition and went from an open protocol (IRC/XMPP) to a closed/custom API. At least here, the server admin can enable those protocols if they want and the API seems to offer enough features that someone could probably integrate Slack into another IRC-like client.

Duo is a mobile only video/voice chat app that uses a experimental transport protocol.

Allo is a text chat app with lots of options for stickers and end-to-end encryption disabled by default.

I don't have a strong need for either of these apps.

Meet though is exclusively Chrome. They have now cut Safari out of the picture as well... https://support.google.com/meet/answer/7317473

Google Talk was only ok when they had a jabber service. It wasn't much better than the other options besides that it tied delayed messaging (email) to instant messaging (jabber) through the same contact info.

Then they killed off the jabber client to force users further into their software ecosystem. Then Hangouts came along and has to some degree replaced Talk with further ties into that ecosystem.

Then they removed browser support for anything but Chrome in Hangouts, initially promising to re-extend support, yet today the docs have changed to just say you must install Chrome.

The most recent eco-system tie-in that this article doesn't mention is Google Hangouts Meet. The corporate conference room version of Hangouts that has a different interface, custom Google hardware, and less memorable links (/xcf-fges-sce vs. /organization/meeting-name).

Pixel has similar limitations when it comes to screen mirroring, only a Chromecast will do for the Pixel! Yet other android phones freely connect to Chromecast/Roku/Firestick/etc all because of a hidden menu setting that Google has disabled and set to 0 by default. You must root your phone to get around it. Great flagship right?

All this points to a company that's so fucking worried that their tech is going to be outpaced by the little guy that they have to resort to handcuffing users to their wares. I've almost completely switched to Slack in the mean time.

Douglas Crockford would say The Seif Project: http://seif.place/

https://www.youtube.com/watch?v=fQWRoLf7bns