131–140 of 487 posts
Earlier quoted context omitted.
This is hilarious! Turns out 18 year old websites were mobile friendly after all
Have you actually tried the site on a mobile device? It's impossible to read the text and navigation is hell. Wouldn't classify that as "mobile friendly".
Earlier quoted context omitted.
Have you actually tried the site on a mobile device? It's impossible to read the text and navigation is hell. Wouldn't classify that as "mobile friendly".
It's not so bad if your mobile browser supports pinch to zoom.
My 23 year old web site: https://jgc.org/ It's still updated from a Perl script that generates static HTML.
It's gone through many renames and redesigns, but, in true Japanese style, it's still the same website. I do have an old snapshot, though: https://anonymoussoftware.stavros.io/
My 21 year old site focuses on Windows NT and the upcoming Windows 2000 release. Back when MSFt focused on operating systems. Billg still in charge!
Earlier quoted context omitted.
This website looks extremely familiar. I think I visited it about 15 years ago and I am not completely sure but didn't you have a nice drawing and photo editing software there? I can't remember the name of it but it was the best ever, until it was disappointingly discontinued because of lack of buying customers :(
Yes, ArtGem ( https://rlvision.com/artgem_about.php ). We were a couple of guys that tried at making shareware, but sadly failed. I continued running the site to host my own utilities, some of which eventually turned into shareware. I don't earn much money from it, but I enjoy making software and it makes me happy when other people find them useful as well!
Earlier quoted context omitted.
Have you actually tried the site on a mobile device? It's impossible to read the text and navigation is hell. Wouldn't classify that as "mobile friendly".
Just tried on iPad, the site works great. Did you mean ‘phone’ and not ‘mobile device’?
https://developers.google.com/speed/pagespeed/insights/?url=... 100 Points. Mobile First. Better than React Native.
100 points on pagespeed is not that hard with static sites. - drop 99% of the JS (PWA, lazy-loading, infinite scroll, jquery, you don't need any of them for a webpage), convert the remaining for 1% to vanilla js and use it as progressive enhancement. - use EM or % as layout width/height - inline css, js, and svg EDIT - no webfonts! The only thing that'll remain as an issue are tables wider, than viewport, on mobile.…
But yeah, lazy-loading, infinite scroll, etc., are all designed to cover up design flaws that impact performance. I think lazy-loading can be potentially done right, but almost none of us do anything right.
> use EM or % as layout width/height
Why? EM/REM is good for handling font sizes, but for anything else it may not make sense and a custom font setting in the browser can break layouts if the size of boxes are based on font sizes. PX is perfectly adequate for layout, and is actually a relative unit(PX !== hardware pixel). Same for borders, padding, margin, etc. Even REM is better than EM for most cases. People who adjust the font size in their browser don't necessarily want their layout to change and potentially degrade as a result.
> inline css, js, and svg
Can be a good idea, especially if you can somehow identify the CSS used on page load and discard anything nonessential. Though maybe HTTP/2 makes inlining obsolete. IDK
> no webfonts!
Thank you! Web fonts are perfectly sufficient in 99% of cases.
Earlier quoted context omitted.
USD 25.000 according to GoDaddy https://godaddy.com/domain-value-appraisal/appraisal/?checkA...
They mean USD $25,000 and not $25.
https://docs.oracle.com/cd/E19455-01/806-0169/overview-9/ind...