In light of Google's recent, tragic, and inevitable closure of Google Domains and sale of their customer list to Squarespace: what are you using for domain names?

Google Domains checked most of the boxes for me: good price, availability of TLDs, features, interface. The company's reputation went both ways, as we're now dealing with. Can't even remember what I used for domains before GD.

This thread is inspired by the recent thread on hosting providers, where I saw a lot of people were using Namecheap for domains. The name of the company sounds like a .biz from 2002, but if it's good it's good.

Let's figure out the best option for domain name services as of October 2023.

Between "enshittification" and my general admiration for hobbyist websites, I have felt more and more pressed to learn how to make the websites I want to see and offer it at low cost. At the same time, people usually have to maintain their day jobs and development expenses. I am curious how easy or difficult it is for people to do. (Also, I guess please share your small website if you'd like)

:wave: everyone, I've been thinking about where to put non-technical blog posts and what to call them since, so far, I have bookmark/, cheatsheet/, howto/, note/, snippet/ and tutorial/ folders already[1].

I think those cover most of the things I like writing about and I intend to share, but I also enjoy poetry, analyzing movies, political commentary and writing an essay here and there.

Following from that, I kept essay/, poem/ and commentary/ around for whenever I felt like sharing some of my non-technical writings, but I don't like those folders :smile:. They seem way too granular, more akin to tags than categories, both of which are contained in each file's metadata.

Tags, however, don't feel like a "pillar"/category of a Zettelkasten/ramblings/thoughts crate. They're empty at the moment and in draft/, so it's the perfect chance to do some re-structuring and avoid the issues I faced when I ditched blog/category and chose the current structure.

In case you're asking yourself why I didn't put everything in the same folder, as they reflect categories and each .md file has category metadata already, it's because the drafts in draft/ became unmanageable (+120). So, in an effort to give myself an easier way to navigate and edit, I decided /folders were going to reflect the categories that existed. I'm aware it can be that after note #50 or something I have the same problem, and thus it wouldn't have made a difference whether notes were together with tutorials or not. I've decided to deal with that problem when it arises :)

I'd be very interested in hearing your thoughts! Would you keep essay/, poem/ and commentary/ or merge them into something else? note/ are short and wouldn't feel right for longer ramblings. I am not a big fan of writings/ as everything is a "writing", prose/ also doesn't quite fit and so far the only one I've sort of liked is reflection/ since essays, poems, and comments on happenings are the result of reflecting.

/rant over, I know, I'm overthinking it. Let those not guilty throw the first stone :)

[1] I've removed quite a bit of the irrelevant stuff but kept what I believe is relevant, but feel free to ask away in case something necessary is missing.

.
├── bookmark/
│   └── sample.md
├── cheatsheet/
│   ├── sample.md
│   └── sample.md-data
├── commentary/
├── draft/
│   ├── bookmark/
│   │   └── sample.md
│   ├── cheatsheet/
│   │   └── sample.md
│   └── ...
├── essay/
├── extra/
│   ├── archive/
│   ├── blob/
│   └── robots.txt
├── howto/
│   └── sample.md
├── note/
│   └── sample.md
├── poem
├── private/
│   └── sample.md
├── snippet/
│   └── sample.md
└── tutorial/
    ├── sample.md
    └── sample.md-data/
        ├── sample.png
        └── ...

I know quite a controversial and opinionated question, one that might easily get blasted with downvotes on a site like StackOverflow or even Reddit! Nevertheless, one which I believe is still relevant to ask and useful one even in 2023.

The problem with backend web technologies is that we are overwhelmed with choices. Whilst getting spoilt with choices seems like a useful thing sometimes, it might easily be an impediment in decision making too. Based on my experience, there are a bunch of useful stacks and I will work on any of them if you pay me to work as a freelance coder. Each has its own pros and cons but I'm yet to find the ideal one which according to me is something that should be easy to code and deploy while also better performing at the same time.

• ASP.NET: C# is the language I started coding web apps with in my last company and ASP.NET web forms was quite the rage back then. PHP was also gaining traction in the open source world and the webdev was mostly divided between the Enterprisey .NET aristocrats of Microsoft world and the poor PHP peasants of the FOSS world! One good thing about ASP.NET was performance. Since MS controlled the whole stack, they also put great efforts at making it work faster. The bad thing, of course, was dependence on a closed tech stack and a closed black box that generated JS functionality on its own.
• PHP: When I resigned from that company and started freelancing, I came to know about open source, linux, XAMPP, etc. That was when I realized that my own attitudes and thinking was more attuned to the FOSS peasant mindset than the wealthy aristocrat's! I didn't earn quite as much in freelancing with WP, Drupal, SuiteCRM, CodeIgniter, etc. but I found great happiness and contentment in being part of the open source process. Till date, PHP remains my favorite language for backend development and most of my web projects involve CodeIgniter or even pure PHP.
• Python: Flask is what got me interested in Python web development. The sheer minimalism and flexibility of that framework is what I found quite remarkable and quite a rarity in the frameworks world. And jinja2 template system was just fantastic. The other framework called django is more popular I think and I've worked on that too but Flask still remains my favorite. Flask is good in performance dept. too but I think it gets tricky once you start scaling with too many users.
• Java: I've never really bothered with Java web development except a few tutorial experiments on the Apache TomEE server. The multi-layered approach that Java takes not only has very steep learning curve but unless you're a very gifted programmer, it's practically impossible to beat the performance of interpreted PHP/Flask!
• NodeJS: Again, not much work here except brief hobby projects like http-live-simulator. The npm packaging system really turned me off initially with so many packages and issues with that system in the earlier days. Nowadays, I've heard that it's much usable but I've never gotten into it.

And now, we also have the evolving languages like Golang, Rust, etc. taking their baby steps towards web development too! Are any of them worth giving a try? If someone were to ask you for a backend tech stack recommendation while giving equal weightage to performance, developer productivity and ease of deployment, which one will you suggest?

Title says it all. Bootstrap+jquery has been my default route and path of least resistance when it comes to web development. Perhaps because I'm coding since a long time and belong to the old school when modern libraries like react weren't yet invented yet?

I had tried to meddle with Angular.js 1.0 back in those days but was soon disillusioned! It was cool and cutting edge but highly opinionated. It tried to do so many things under the hood that I soon quit the effort and the word "Angular" was stigmatized in my mind ever since! I don't know how different today's typescript based Angular is but that stigma or phobia prevents me from even looking at that direction!

React is another cool technology which everyone is talking about and I'm sure it has some merits. But I'm not sure exactly what React brings to my development workflow which jquery doesn't already do. Can you tell me some specific advantages or pros of react over jquery which can motivate me to learn the former and let go of the latter? What should I do?

I'm working on an app idea, it's going to be "API first" in design which means there is a clear separation between the backend and frontend. Former will be accessible through a REST API and the latter can be simple HTML without me having to delve too much on it. The idea is that the end users or clients will write their own front-end interacting with this REST API in future.

Firstly, I want to know where to start. Writing a REST API seems quite easy and simple for me as a backend engineer but I've never implemented a "pure API" app in practice. Do you just validate the headers, do the crunching and return back a JSON response? What all must you take care of here?

Finally, authentication and session handling is something very important here, isn't it? If I make use of session feature in the REST API (like PHP sessions or Django sessions, for eg), authentication will be pretty easier. I don't have to worry about encryption as SSL/TLS would be already doing that for me through the browser. But then what is the downside of this method? Why do so many people use JWT tokens then?

Coming to JWT tokens, is that the only way of encrypting/validating REST APIs, or are there others? My biggest concern here is scaling and performance. I'm willing to implement the most efficient path here, the one that gives the most performance using least resources.

I'm primarily a freelance backend dev and for the first time venturing on full-stack development of a non-trivial web app on my own, hence I needed some guidance.

I've got all the backend stuff in php/mysql covered, I just want to know what's the best way to create a dashboard (with left sidebar) considering various aspects like long-term code maintenance and support, robustness, etc. Looks don't matter that much as it's a CRUD app but obviously, better is more appreciated.

Based on my research until now, AdminLTE seems to be the most popular way of doing it among most devs although a few others like material and coreui also seem to have some street cred.

But another approach I'm considering apart from AdminLTE is to just use pure bootstrap and fiddle up my own sidebar using something like this. That way, I won't be tied to just one Bootstrap version which is used by AdminLTE (v4.6) and troubleshooting will be much easier through google search and StackOverflow. What do you guys think is the right approach?

I’m a solo freelance programmer and want to write an app for internal project management, somewhere I can add projects, milestones, tasks, etc. and track them as I work on them, occasionally remind me of things like take a break, lunch time, etc. and over time I can track on which category I worked how many hours, etc.

I’m actually confused between whether to build this as a Web or Windows Desktop app. I’m considering latter because it can run efficiently on my laptop in the system tray using least memory and resources, web-based on the other hand will force me keep running an apache server too which will be an overhead (unless I host it on Google Cloud or someplace which might be an option?)

The only reason for considering web-based is that eventually I’m planning to make this tool open source and with web-based, many others can find this useful too (including OSX/Linux users). At that point, I may consider expanding its schema to include multi-user connectivity, client login, etc. but that’s going too far at this point!

The idea is that this tool should be useful not just for me but other freelancers, students, etc. who might be in my shoes. From that perspective, what do you think is the right technology to use? Web based or Windows based?

(I’ve extensively worked on C#/WinForms projects before and I’m thinking Visual Studio Express for desktop development. If web-based, it’ll be php/mysql based)