It's that time of the week again. So wonderful devs, what did you learn this week? It could be programming tips, career advice etc.
Feel free to comment with what you learnt and/or reference your TIL post to give it some more exposure.
#todayilearned
Summarize a concept that is new to you.
And remember, if something you learnt was a big win for you, then you know where to drop it as well.👇👇🏻👇🏼👇🏽👇🏾👇🏿
What was your win this week?
Gracie Gregory (she/her) for The DEV Team ・ Feb 11 '22
#discuss
#weeklyretro
Top comments (38)
This week, I learned why Safari, a browser that I had celebrated for early adoption of parent selectors and CSS level 4 colors, is said to be "the new Internet Explorer" and that it's actually worse, because Microsoft at least always let the users install real alternative browsers.
On an iPhone 6 Plus there is no way to get a rendering engine more up to date than iOS 12.5.5 with Safari 12 (AppleWebKit/604) and so I have to use arcane browser hacks and prefixed vendor properties to make a modern website work on a device, that is still working well, despite its outdated browser and despite Apple's planned obsolesence policy.
What a waste of time!
The code below shows just some of the hacks needed to adjust a website using
apect-ratio
height: 100vh
clip-path
flex-basis
gap
Sorry for the rant. I'd rather have spent my time for something more productive this week as well!
Besides, I also learned that Gnome Web has a rendering engine similar to AppleWebkit and might be a good way to test macOS Safari experience on a Linux computer.
I also learnend that Opera mini is still quite popular in Africa and that it still works fine on a modern Android phone and has way less rendering problems than the old iOS Safari.
I know they've been working on it. Check out this thoughtful post from Dave Rupert about it.
I respect the hard work that browser vendors do! I try to make contructive contributions and bugzilla issues as well. And we definitely owe to @codepo8 for succeeding to launch a new Edge browser to replace Internet Explorer. I also respect Apple's innovative work on the original iPhone and Steve Job's achievements with NeXTSTEP and OSX. What I will never respect is companies intentionally blocking possible progress and open source software.
There are useful mobile browsers, there are different rendering engines, and there used to be alternative browsers using different rendering engines for iPhone users. It's not impossible to build and ship a working mobile browser based on the Gecko engine. Just so that the people who don't agree in Safari's 100vh implementation being a good feature can choose to use Firefox, Vivaldi or any other brother as their default user agent.
Browser developers are working hard, while companies like Apple (and formerly Microsoft, and currently Google as well) trying to use their power against open source software, usability, and sustainability.
Respect to the web browser people!
Read the linked posts and open bug reports if appropriate!
This week I created my own NFT minting website. The project I built came from the knowledge I got from a udemy course + youtube tutorial.
I am new to Web development so I had to learn myself React and Nextjs (which I am learning till now). I badly want to learn web development because I want to join the web3 craze but I came from a mobile app environment.
I also learned more about Solidity in Crypto Zombies they teach you the basics and fundamentals of coding in Solidity etc.
Nice!
I learned:
Awesome!
I learned a bunch about GitHub automations from the series by @blackgirlbytes so far. Really looking forward to more.
yay, I'm glad you were able to learn something. So exciting that you're finding it valuable
I learned to work with Nginx on Docker and config fastCGI for php-fpm :) Docker and Nginx official websites was good reference + @techworld_with_nana 's Youtube channel.
I have been using swagger for quite awhile, using fastapi, or connecting the swagger UI to other api's. Although, I have never actually used swagger to generate neither the server or the client code.
I always heard about it, but never took the time to try it or even really consider it.
I work with the CEO and apparently he is well aware about using this and has a solid plan in place for how to quickly spin up the API's in this way.
So that is what I learned, instead of writing APIs from scratch, generate the code, and if anything, build a solution that quickly integrates the models.
Brushed up HTML, CSS and JavaScript and built a small game use these. Check it out here. Would be great if you could give some feedbacks.
Learning by doing projects is so awesome!! ❤️
Yeah!
Hey Nick,
I started my own 100 Days of Data Science last week. And I realized that coming up with good ideas is tough. ;^)
Do you recommend placing something on Dev.to every day (even when it is small, like just reading...) or when I come up with a finished product, like an article?
P.S. I plan to write/add notes on the blog daily. ;))
I say start writing. Not a big deal if they're short posts. You can create a series too if you want. There's a cog icon near the save draft/publish post button where you can set the series.