> A host for your index.html files Hostgator $33/year plan. - Google Cloud Firebase Hosting - free; really good tooling to deploy, automatic CDN - AWS S3 + CloudFront - a bit more setup, but more or less free - Azure Static Web Apps - free No need to have any hosting plan. Firebase Hosting in particular is really easy to get started and connect a domain to it. The Firebase CLI tooling makes it dead simple to deploy u…
If you are OK with just having an IPv6 IP, you can live in a country like the Netherlands and simply use your home connection to serve your Web page. Almost like it was intended by forefathers...
I've been arguing that HTML would've been a much better information-carrier if "basic browser styling" did this. I'm quite certain that a large part of the web would need no CSS or just a few lines of it, if the basic (browser applied styles) were good . As in: designed by (information) designers. They could even differ per browser, as long as all of them were good (or really good). But alas, base styles are a mess (…
Honestly - it'd be pretty nice to be able to opt-in/out of the default user agent styles applied by browsers. If we really want to preserve compatibility - opt-in to a version. Keep it all the same as current if there's no tag on the page, but if you add something like or something, apply an improved set of default styles. Get rid of the need for resets with Basically - I'd love a way to allow browser vendors to dram…
I agree that defaults are not perfect, but I'd like to add that the initial idea was that they are, well, defaults, and you -- as a user -- are supposed to adjust them to what you prefer. In some dashboard usually called "preferences" or "settings". And fact is that you still can: you can tell your browser "for this script, for serif, use this font family, for sans use that one" etc etc. You can set you preferred text colours. You can even write your own style that will sit between user agent styles (those "ugly defaults") and author styles (those forcing weird stuff). Initial idea was that our browsers will be truly individual tools and one of their main task will be consolidating those preferences from various sources. That's the "cascade" in the CSS.
Some years ago I was interviewing for head of automation position, and in the process was asked how'd I go about making sure a Web admin interface (to a product that by and large doesn't need a Web interface, think, in the same category as Kubernetes) is well-tested. To which I responded that I'd not use any JavaScript. Ideally, XML with stylesheets. Very light-weight, renders extremely fast, and is extremely friendl…
> if they don't put a fashionable JavaScript framework into job description, they will not be able to hire front-end programmers. This is exactly why we are vague with tech stack in our job reqs. Why would you want talent that is laser-focused on specific keywords? What is the average lifetime of a JS/CSS framework? The game isn't to come in knowing this crap. It's to grasp fundamentals such that you can quickly lear…
> I much prefer to hire less "skilled" employees who are more interested in the problem domain or product than they are any specific tooling. Goal-oriented developers can be taught to do anything in my experience.
A million times this. When I've hired, the specific languages/platforms/whatever the applicant has is of tertiary importance at best. What counts is the ability to engage in problem-solving, how well they will fit into the team, and how readily they can learn.
Curious if I am going crazy... On the main blog page, it sure looks like some of the entries are not sorted properly. For example the 10 Feb 2020 ThinkPad review. Oh wait a second. Some of the dates are DD/MM/YYYY and some are MM/DD/YYYY!
Thank for taking the time to report the issue. Fixed.
Also : there is a background color specified, but other colors are not overriden, which causes the text to appear in a color very close to the background color on my browser (the default text, and background colors are user configurable).
Clicking on the first website, I can't even view it because it's asking for captcha. So, to extend your comment: you do not need to worry about content if your website isn't even reachable. A GET request should never result in the client being bombarded with captchas. Unless you have a sure fire way to determine if said client is a human or an evil AI taking over the world (nobody does), just serve the damn page.
> Clicking on the first website, I can't even view it because it's asking for captcha. It's definitely not, there is something else doing that to you. But it's not this website.
It's using some form of DDOS protection, not Cloudflare, but something. Access it via tor to see an example.
Some years ago I was interviewing for head of automation position, and in the process was asked how'd I go about making sure a Web admin interface (to a product that by and large doesn't need a Web interface, think, in the same category as Kubernetes) is well-tested. To which I responded that I'd not use any JavaScript. Ideally, XML with stylesheets. Very light-weight, renders extremely fast, and is extremely friendl…
you can't get anything done if nobody wants to do the work
I see you got downvoted but people don’t get that choice of technology based on who you can hire is a valid point.
I remember a guy who wanted to make company documentation in LaTeX. Well yes it is great tool and we could put it in a git repo and render nice documents for the customers easily. Downside was 15-20 sales people who were not thrilled to use it and spend time learning how to use it.
It's a great example of how a little can do a lot. The balance between design & function can be at odds when the mission of the page is not clear. For consumption, these are awesome, your brain almost relaxes as it's easier than the usual onslaught.
It's also a great example of how even such a little can go wrong. The CSS of the second website is wrong, as it uses 'color' without setting 'background-color'. Assuming anything about the default background color is not possible because it is user-configurable in most browsers. At least http://motherfuckingwebsite.com remains readable when you change your color settings (the second one is completely unreadable on my…
It's a great example of how a little can do a lot. The balance between design & function can be at odds when the mission of the page is not clear. For consumption, these are awesome, your brain almost relaxes as it's easier than the usual onslaught.
It's also a great example of how even such a little can go wrong. The CSS of the second website is wrong, as it uses 'color' without setting 'background-color'. Assuming anything about the default background color is not possible because it is user-configurable in most browsers. At least http://motherfuckingwebsite.com remains readable when you change your color settings (the second one is completely unreadable on my…
This is another post illuminating the new minimalist trend in website design. The old minimalism was about "elegance", but this new trend is more about utility: we don't need CSS, just content, so why bother! I don't like this utilitarian take. It's fun to design a website.
I genuinely believe a site can be extremely minimal without sacrificing the visual component. But I also believe some people are pushing the visual part way too far to the point where sites are genuinely hard and frustrating to use.
I agree, it's a response to websites being over-designed to the point of being less usable/accessible, but this feels like a dramatic over-correction.
It's a great example of how a little can do a lot. The balance between design & function can be at odds when the mission of the page is not clear. For consumption, these are awesome, your brain almost relaxes as it's easier than the usual onslaught.
It's also a great example of how even such a little can go wrong. The CSS of the second website is wrong, as it uses 'color' without setting 'background-color'. Assuming anything about the default background color is not possible because it is user-configurable in most browsers. At least http://motherfuckingwebsite.com remains readable when you change your color settings (the second one is completely unreadable on my…
Good point. If the background color changes that often, I'm assuming there's probably a good test out there for that and more.
The text was readable as designed on a white-background. CSS that considers accessibility or print friendly is always good to add.