I copy/pasted it into my editor to see it larger. I still used my brain. This 'test' is not a true test but a trick, and the trick doesn't have to do with programming ability.
So cool! Thanks for sharing. It reminds me of one of those very old cameras with the bellows or accordion. I wish I could look through it myself to see what you see with it!
This leaves a bad taste in my mouth. I see that the man was Israeli in the original story and I don't want to presume a religious perspective, but I can share some thoughts from my own based on his story and yours. I've read the New Testament within a Jewish framework and one of the things it says, Rabbi Shaul says in 1 Corinthians 12:23 that those people in the community who are most embarrassing or cause us to blush, like the parts of our own body who are honoured or dignified by being clothed with underwear, likewise in the community are owed a special covering and to be afforded dignity by the other parts of the same body/community. Just something to think about in light of this story!
Back about 20 years ago there was a lightweight Gecko-based web browser called 'Camino' that was a delight compared to Firefox or other 'full' browsers. It was fast, simplified, and still rendered pages well. I didn't always use it, but it was a joy to use.
I downloaded Helium and gave it a spin and my first impression was "Ah, it's like Camino all over again". I can't use this for my job where I need to use stock {Chrome, Safari, Firefox, Edge} because our customers do - but for personal browsing I'm currently using Arc which is very comfortable but heavy, I might try to use Helium for quick simple things when I want less overhead! Thanks for sharing!
The PATH network is great, especially in Toronto's freezing cold and windy winters! The beautiful 'underpass' pictured in this article, with the white marble, is on my commute to work, and it really is breathtaking when you turn the corner.
In the Financial District, the various bank towers can be told apart by the colour of the marble and other stones they build with. For an underground walkway, some parts of it are really beautiful, other parts are just what you'd expect for an underground passage in a big city (especially those parts connected to the subway transit system).
“A webpage that counts down to a movie release.”
Not an app. Not a startup. Just a janky react/tailwind page.
Maybe part of the problem is trying to bite off more than you can chew, spinning up React and Tailwind for what could be a single HTML element, a CSS style rule or two, and a few lines of plain JavaScript code is a symptom here. This is like taking a cruise ship on a canoe trip and then complaining that it's too time consuming and difficult. Start simple, start small!
I think the key is that dotfiles are a different genre of (code) writing than production code, with different investment, different motivations, different pain points and histories, and a sensitivity to the author that's not required when analyzing production code. You're looking into someone's daily writings, not their polished releases.
I think the fear is scrutiny, rejection, mockery for something that clearly works for you and you don't ever expect anyone else to use. But also partly that it's exposure without much reward in return. All these feelings are normal and it's fine to share or not share them. Just please honour the authors of the dotfiles you read even if you wouldn't ever think to use code in the way they do!
I'm sure I have stupid and weird stuff in my dotfiles. At one point I had bash set up so if I typed something like "gi tlog" it would fix it for me; this is obviously not something that everybody needs because it's due to my idiosyncratic typing-too-fast.
I've been using Unix systems since last century; my standard way to do a find-and-replace in a file is still 'perl -pi -e s/foo/bar/ filename.txt'; I've been writing that for 25 years and I'm unlike to stop any time soon unless perl stops working. I'm sure there's a better way to do this, but :shrug:?
Counterpoint: External CSS stylesheets can be cached, saving future requests, but inlined CSS must be re-downloaded each time and you lose all the benefit of caching the styles independently from the document. Depending on the size of the CSS, there's a tradeoff.
