This is a weekly roundup of awesome DEV comments that you may have missed. You are welcome and encouraged to boost posts and comments yourself using the #bestofdev tag.
Sometimes I feel like the only person who absolutely does not want ligatures in my programming font. I much prefer seeing
exactly the characters I typed. I don't want to risk reading something wrong because a ligature changed what I expected to see.
The What was your win this week? thread has been a ton of fun. This is the first Top-5 comment where the post author and the commenter are one in the same, none other than @jess
who has a killer home desk setup:
Generally "headless" means there is no graphic user interface for a piece of software.
To understand what a "headless" CMS is you have to understand that, historically speaking, a CMS does more than just "Manage Content."
There is often a "admin side" or "back side" of the CMS you use to enter data and files into the CMS. Some even let you define specific kinds of content; for example, "Blog Post." Blog posts have text and images and maybe other things like tags or categories.
Then the CMS has a public-facing "front side" that most visitors to a website see. This is generated by some kind of "theme" layer or "template" layer that the CMS provides. It takes the text and images and categories and generates the HTML to make the Blog Post display in a browser.
Headless is when you strip away that "front side" layer from the CMS. The CMS isn't generating a whole website anymore, it has been boiled down to just holding the content. It's up to another piece of software to do something with the data in the CMS.
As to your second question; I don't know if you would. Probably wouldn't want to; it depends a lot on what you want to accomplish!
After a rough fall and damage to a laptop, catalogued in Slid on ice, body-slammed my new Macbook Air. What should I check for?, @andy
drops some seriously-helpful knowledge:
Yikes, glad to hear you're okay. I remember I dented a MacBook Air rental from my college library because I had my headphones plugged in and walked too far away from it... Thankfully the librarians didn't seem to care too much.
Anyway, yeah Apple will know if you open the case. The thing is, you already don't have AppleCare, and I'm assuming it's not under warranty anymore. If it's not under warranty, Apple won't care if it's been serviced by someone else. So, feel free to do that!
Now, as someone who's fixed some MacBooks before, I guarantee you this would be a really easy fix. You can buy a replacement part on eBay, and they usually come with the screwdriver needed. If not, you'll need a tiny Philips head screwdriver (also found on eBay or a friend who likes hardware). A quick search on USA eBay for "MacBook Air bottom case" show the part ranges from $5 USD to $25 USD. Certainly not a hefty price, and most likely much cheaper than what you would pay at a third party or Apple. Plus very little downtime! The benefits are endless!
The hardest (not hard, just hardest) part will be figuring out which one is the right one for your MacBook Air. Once you get that info and the part shipped to your door, you can follow this awesome guide to replace your bottom case: ifixit.com/Guide/MacBook+Air+13-In... One thing to note: make sure you pick the right guide for your MacBook Air. You could probably get away with picking the "incorrect" guide. The MacBook Air construction has not really changed year to year, the exception being with the latest Air.
If you are feeling really lazy like I probably would, you could probably unscrew the case and bend it back with some pliers. 🙃 BUT I definitely am a believer in fixing it yourself because it's super empowering and totally worth the experience!
Let me know if you want help figuring out the right case or screwdriver to get.
breaks down the concept by using the idea of family generations:
Your father (parent class) gives you, the student/son (subclass A), a vaguely written textbook about addition and subtraction. Since your father was not able to give you a lesson on the topic, you are stuck on a problem that you do not know how to solve. You look to your right to see that your brother (subclass B) is also confused.
That is when you decide to ask your father for instructions. Unfortunately, for some reason, your father also does not know how to solve the problem.
That is why your father goes to ask your grandfather (parent of the parent class) about it. Finally, your grandfather understands the problem and tells your father how to solve it, who later tells you how to solve it yourself.
Your brother also goes to your father to ask him about the problem, which in turn leads to your father asking your grandfather about the problem again. After explaining, your father finally approaches your brother and answers his questions.
In a nutshell, this is prototypal inheritance, where the implementation of a certain property or method is delegated to a "parent/ancestor class" if the current object does not already have an implementation for said property or method.
See you next week for more great comments ✌