This font was just added to codingfont a few minutes ago! https://www.codingfont.com/AtkinsonHyperlegibleMono you can compare it side by side to your other favorite coding font to see which one is better looking in a code editor!
You may also play the blindfold game to see if it will TRULY wins against all others in a blind test on codingfont.com
This might be of interest for you: https://www.codingfont.com/ I made it to select the perfect coding font. i will update it to include the Atkinson Hyperlegible Mono soon!
Hey, I'm a fan of your work. My font before this was Victor Mono, and I actually found it through your website. Do you publish the source code anywhere? I'd be interested to take a closer look at it.
The code was private but I see no reason not to open source it, so I just did! https://github.com/Typogram/coding-font-sveltekit This way you can add your own font to it, just modify codingfonts.ts and include the font files in the css!
If you feel like it, you can add this page https://www.codingfont.com/AtkinsonHyperlegibleMono to your article, it is the dedicated page for Atkinson Hyperlegible Mono with the options to compare it to other fonts on the side by side view.
This particular font seems to have very inconsistent kerning. The "isMultipleOf" identifier pushes the s & M & u and e & O way too tightly together, and the remaining letters seem inconsistently spaced as well.
Ah, thanks for digging this out, this is the version 1, which I made using a no code tool. the current version is made using sveltekit, it is also just open sourced in the other comment.
Lean and mean could mean people lose their job, lead to talent churn in the job market, wasting their talent and time doing things they don't love. Keep a steady cushy job so these talent can make great product while enjoy their life is a net gain for society.
> Keep a steady cushy job so these talent can make great product while enjoy their life is a net gain for society
No, it's a gross gain. And probably a small one, honestly. Whereas the associated costs to society are in the billions or trillions of dollars when we measure the environmental and social effects of mandatory-growth-culture. So it's a net loss.
I think growing !== making your product last shorter. Develop a brand new market like AR VR headset is growing. Develop a new service that people need is growing. Keep growing to compensate for shrinking market for existing business, so that your employee can have a steady job and do what they love and are trained well to do, without churning in the job market is a net gain for society.
As a backend dev that has dabbled in JavaScript (old school), I love Svelte. It makes reactivity so easy while keeping everything more or less optional and vanilla
> The tldr; is that we see a lot of similar requirements from developers across Angular and Wiz, so we're looking for opportunities to reuse work. Good example is the Angular Signals library that's now used in all the YouTube Mobile Web. In a similar way, Angular is bringing more fine-grained code loading that Wiz offers.
It sounds no different from Svelte borrowing concepts from SolidJS, or Vue borrowing ideas from Svelte, from you said — if it is just adding some features that Wiz has, it doesn't sound like merging? Why put a shocking title that Angular is merging with Wiz, when Wiz has no name recognition in the outer dev community — like we don't know what that means?
they screw us more than once already. CSS Tricks is not their first victim, there is also scotch.io, where I learn Angular stuff. One day I tried to visit a saved article in my bookmark, the entire site and all its subpage are gone, and just redirect to digital ocean. That is more screwed than CSS Tricks is today, all that content, puff, gone!
This is not the first time digital ocean did something like this. And unlike some other commenter here saying they only did it because CSS tutorials don't give them ROI, extra information here is that they also did it with javascript tutorials, like scotch.io, so I am leaning towards to that DO just do poorly with their investment regardless. I wrote more about their track record in buying indie dev blog and then kill them in my newsletter last year when CSS-Tricks's editor got laid off: https://build.typogram.co/p/dont-sell-your-indie-business-to
I think Chris pointed out a very key fact: running site like css tricks or scotch.io takes a special mix of skill, organically the site grows big with one or two person with that right mix of skills, but once big corporate bought it and for whatever reason didn't retain that talent, they have to replace it with a team, which kills the ROI.
Quote from my newsletter “Don’t Sell Your Indie Business to Digital Ocean!”:
The sad part of the story is that most of what happened can’t be traced easily. Domain redirect can be set up with a few clicks of a button, and soon enough, most people forget these indie blogs ever existed and what happened to them. I want to write down what I saw so that there is a record of what Digital Ocean has done or has not done.
Back in 2014, I turned to Scotch.io to learn AngularJS. Scotch.io offered clear and concise tutorials that were easy to follow, even for someone who was new to the framework. I saved many tutorial articles to my browser’s bookmark; as I don’t clean up my bookmarks, I still have them saved up in my messy bookmark folder today.
One day I dug up and clicked on a scotch.io article from my bookmark and was surprised to see that it returned a “404 page not found” error. After some research, it turned out that Digital Ocean bought scotch.io, so consequently, the scotch.io home page got redirected to Digital Ocean’s homepage, and articles like the ones I saved were removed.
What was my problem with that? I didn’t know where to begin. Redirecting a blog to a product page with no context was just intentionally wasting my time — why would a visitor of a blog not be surprised to land on “Try Digital Ocean for free for 60 days”? And the cherry on top? Not setting up a wild card page rule to redirect all scotch.io article links to Digital Ocean, hence why I got a 404 error — they can’t even do their evil with efficiency. They wanted to milk this cow dry but had a leaky bucket — the stupidity, the carelessness, the insult to the editor who spent years creating quality content. Also, wasn’t Digital Ocean a service to host websites? Setting up page redirects is literally part of their service, and what a demonstration they had put on!
The above was what I witnessed in 2022. As of writing this article in February 2023, Digital Ocean has fixed some of the issues. Now all links of scotch.io redirect to the Digital Ocean community, which at least hosts some tech content. The original blog articles of scotch.io are still missing from the Internet. I searched for the titles that were saved to my bookmarks and couldn’t find them, on the Digital Ocean community or elsewhere. It is as if they were never written.
What triggers me to write down these words above as “record” is that Digital Ocean bought CSS Tricks — another beloved tech blog — about a year ago, and recently they laid off the only editor of CSS Tricks. It is entirely possible that one day we will lose access to CSS Tricks content like “A Complete Guide to Flexbox” — a front-end “staple food,” a link that always shows up in purple in search results; and instead, we get to enjoy losing 3 seconds of our life being redirected and then bounce.
Some of you may think that Digital Ocean will treat CSS Tricks more nicely, and that they won’t take down its quality content written over a decade of time. CSS Tricks is much more famous and high-profile than scotch.io, after all. I wouldn’t be too sure because of what happened to coding-fonts.css-tricks.com — go ahead, click on it. It is broken and just redirects to another page.
I launched a similar project called codingfont.com back in 2021, which is a tournament-style game to pick the winner coding font. Chris Coyier, the founder of CSS Tricks, wrote about it, which brought massive traffic to my site (Thanks, Chris! I am grateful as a fellow tinkerer). The article mentioned that CSS Tricks had built their own coding font microsite. Fast forward to May 2022, less than two months after CSS Tricks got bought, the CSS Tricks microsite was broken, and someone reported an issue on Github. Chris, who would be in an advisory role according to the Digital Ocean announcement, answered quickly:
> I’m afraid I’m not sure what Digital Ocean plans to do with it. I would, of course, vote for it to be re-hosted right at coding-fonts.css-tricks.com — and would be happy to help put it on Digital Ocean App Platform as well!
It was clear that Chris as an advisor wasn’t given any real access to decision-makers at Digital Ocean to make any difference in such a simple matter. It was such a simple and easy matter to solve that a bystander came forward and hosted the microsite somewhere else, ironically on Netlify — a competitor to Digital Ocean.
So there you go, another record I put down here in case Digital Ocean bothers to correct it one day, let the Internet remember that it had happened.
My open plea to Digital Ocean:
Stop this unethical business practice NOW! Your company buys these blogs to build a good reputation among the developer community, but clearly, the plan has failed. Instead, it hurts your brand, and I will never use your service. It is not too late to keep your promises — publish new content to the site, or at least keep the site alive and working as it is.
My appeal to other content creators: Don’t sell your indie business to Digital Ocean.
